fix: race condition in User Location initialization causing MapKit crashes #82
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.
Fixes a crash observed in
MKPuckAccuracyLayerduring_updateColorsby removing redundantCLLocationManagerupdates in FlutterMapView.swift.When
myLocationEnabledis true, the plugin was redundantly startinglocationManagerupdates while also settingshowsUserLocation = trueon theMKMapView. This dual-management appeared to cause a race condition or conflict within MapKit's internal layers, leading toEXC_BAD_ACCESScrashes during trait collection changes (e.g., toggling Dark Mode). This PR removes the manuallocationManagerconfiguration, relying solely onMKMapView's built-in user location handling.List which issues are fixed by this PR.
MKPuckAccuracyLayer_updateColors(Issue Crash in MKPuckAccuracyLayer _updateColors due to CFStringGetLength (iOS) #81)Pre-launch Checklist
///).