-
Notifications
You must be signed in to change notification settings - Fork 124
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Errors after unmount component (Android only) #2
Comments
Thanks for noting this and I'm aware of these logs as of the latest release ( I tried to get rid of these errors that crop up after destroying the I'll leave this issue open for anyone else that might come across it. It is working as intended despite these errors showing from the native SDK. |
Thank you for the detaile explanation. Anyway, the application works fine and the app does not crash. Best regards. |
Hey I wanted to provide an update on this based on a finding. This will not occur in a release build on android. It only happens when running a debug build and the slowdown appears to be caused by the RN bridge getting flooded with logs. |
…box-navigation#2). Does not affect performance.
…roid-sdk Update styling for android view to allow more screen real estate
Hi!
I use react natigation to show the mapboxnavigation in a new screen, after press back button I have several errors in the console, I suppose the mapbox instance should be detroyed correctly before unmount the component.
The text was updated successfully, but these errors were encountered: