This repository has been archived by the owner on Aug 8, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Crashes when removing and adding annotations on regionDidChangeAnimated #2681
Comments
@Zakay Would you mind posting the crash log here, as well? Thanks. |
Looks like
/cc @jfirebaugh |
Has something been updated these last couple of days in the underlying code for this issue? I just merged from upstream, and I still haven't been able to reproduce the bug which I was able to 100% of the times before. I'm going to keep on testing, if I'm not able to reproduce it by the end of the day, then this issue can be closed. |
This may have been addressed incidentally by #2617. |
Yes, this is now fixed since #2617 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Purpose of adding/removing annotations on regionDidChange is very clear, user pans the map and we update the result set for that region.
With a simple test, I can reproduce a crash every time.
Patch included, repositions the map on viewDidLoad, and then on regionDidChange is removes all annotations and re-adds a random amount of annotations.
Steps to reproduce:
(Ignore that some annotations aren't visible after switching layers, there is already a issue reported on this matter, in our own fork we've solved this issue temporarily)
The text was updated successfully, but these errors were encountered: