[MOD-2371] iOS: ti.map module crashes application when selecting different map annotations rapidly
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | Critical |
Status | Closed |
Resolution | Fixed |
Resolution Date | 2017-10-17T09:20:52.000+0000 |
Affected Version/s | n/a |
Fix Version/s | Release 6.3.0, Ti.Map iOS 2.12.1, Ti.Map iOS 3.0.1 |
Components | Map |
Labels | n/a |
Reporter | rlarmore@gmail.com |
Assignee | Hans Knöchel |
Created | 2017-10-16T15:57:19.000+0000 |
Updated | 2018-08-06T17:49:19.000+0000 |
Description
When opening a map view with multiple annotations rapidly clicking between them crashes the application. This was introduced in 2.12 version of ti.map and still and issue with 3.0.0. I have tested version 2.11 of ti.map and have been unable to recreate the issue.
Steps to reproduce:
Create a window with a button, on button click open a window in a navigation flow with a map
Populate the map with pins/annotations
Select annotations and deselect them by clicking on map.
the application will crash on the 4 or 5 click.
Hey there! Was it 2.12.0 or 2.12.1 / 2.12.2? If it was 2.12.0, the ticket causing it was TIMOB-24375, which is kind of unrelated. If it was MOD-2357, it would make more sense. We'll try to create a test-case for you if you are not able to provide one. *EDIT*: Reproducible with this test-case:
*EDIT 2*: It's definitely 2.12.2 and [this commit](https://github.com/appcelerator-modules/ti.map/commit/e64d01021bf81078ca92df165426aeef28125487). Not sure how to fix the race-condition so far, so this might need more time for investigation.
Hey there, would you mind to test [this build](https://www.dropbox.com/s/br7cgoh3xqe7tmc/ti.map-iphone-2.12.3.zip?dl=0) (2.1.3) and try to reproduce it? I was not anymore but would like to await your feedback before setting up the PR. Thanks!
Fixed in Ti.Map [2.12.3](https://github.com/appcelerator-modules/ti.map/releases/tag/ios-2.12.3) and [3.0.1](https://github.com/appcelerator-modules/ti.map/releases/tag/ios-3.0.1).
Cleaning up older fixed issues. If this issue should not have been closed as fixed, please reopen.