You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 8, 2023. It is now read-only.
I already solved this problem to avoid this crash but I still think this exception should be caught differently by mapbox. Let's assume I have an app which is using a set of layers. For some reasons I have a state within the app when the app is trying to check the visibility of layers which are not attached to mapbox anymore. This can be reproduced when you change the orientation, have your app handle config change and not the system and your code is not re-adding the any layers to mapbox. When the app is trying to access one of the old layers via getVisibility/setProperties(visibility) (triggered via onCameraMoved) the following crash happens (all layers are kept as a seperate list to simplify the access to check which one should be displayed):
I already solved this problem to avoid this crash but I still think this exception should be caught differently by mapbox. Let's assume I have an app which is using a set of layers. For some reasons I have a state within the app when the app is trying to check the visibility of layers which are not attached to mapbox anymore. This can be reproduced when you change the orientation, have your app handle config change and not the system and your code is not re-adding the any layers to mapbox. When the app is trying to access one of the old layers via getVisibility/setProperties(visibility) (triggered via onCameraMoved) the following crash happens (all layers are kept as a seperate list to simplify the access to check which one should be displayed):
Instead of this crash it might be more useful to show a warning instead.
Configuration
Android versions: 9.0.0
Device models: Pixel XL
(Verified with) Mapbox SDK versions: 7.0.x/7.x.0
The text was updated successfully, but these errors were encountered: