fix: prevent crash on min/max zoom changes and fix zoom on navigation#572
Draft
fix: prevent crash on min/max zoom changes and fix zoom on navigation#572
Conversation
…oom during navigation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Android Fabric delivers minZoomLevel and maxZoomLevel prop updates in
arbitrary order, which could create a transient state where min > max,
crashing the app with IllegalArgumentException. Fix by resetting both
zoom preferences before atomically re-applying the pair.
Add zoomLevel parameter to setFollowingPerspective so zoom can be
controlled during active navigation. On Android this uses
FollowMyLocationOptions; on iOS it sets followingZoomLevel on the map
view (or GMSNavigationNoFollowingZoomLevel to reset).
Fixes #570
Fixes #550
Pre-launch Checklist