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
Our app refetch data based on user movement from the last distance of the last fetch request location, for example every 10km distance we refetch data and we add those data as annotation on the map.
The app runs perfectly fine for a while on simulator but when we get to refetch data, after refetching and trying to add new annotation the app crashes! saying we have duplicate keys in our dictionary, i have searched all my code for that duplicated key but i did not find any.
Expected behavior
Previously in MapBox v10 we were using UIViewRepresentable to show our Map On SwiftUI App and we had coordinate and annotationManager Variable, we did not have those issue and the algorithm of our app remained the same.
Notes / preliminary analysis
We have noticed that if we simulated massive location change from the ios simulator that crash wont happen, for example when we use apple free-drive we already got some data in that area and when we eneter a custom location far away from the previous our app remains intact.
The text was updated successfully, but these errors were encountered:
Environment
Observed behavior and steps to reproduce
Our app refetch data based on user movement from the last distance of the last fetch request location, for example every 10km distance we refetch data and we add those data as annotation on the map.
The app runs perfectly fine for a while on simulator but when we get to refetch data, after refetching and trying to add new annotation the app crashes! saying we have duplicate keys in our dictionary, i have searched all my code for that duplicated key but i did not find any.
Expected behavior
Previously in MapBox v10 we were using UIViewRepresentable to show our Map On SwiftUI App and we had coordinate and annotationManager Variable, we did not have those issue and the algorithm of our app remained the same.
Notes / preliminary analysis
We have noticed that if we simulated massive location change from the ios simulator that crash wont happen, for example when we use apple free-drive we already got some data in that area and when we eneter a custom location far away from the previous our app remains intact.
The text was updated successfully, but these errors were encountered: