{ "id": "169692", "key": "TIMOB-25228", "fields": { "issuetype": { "id": "1", "description": "A problem which impairs or prevents the functions of the product.", "name": "Bug", "subtask": false }, "project": { "id": "10153", "key": "TIMOB", "name": "Titanium SDK/CLI", "projectCategory": { "id": "10100", "description": "Titanium and related SDKs used in application development", "name": "Client" } }, "fixVersions": [ { "id": "19916", "description": "", "name": "Release 6.4.0", "archived": true, "released": false } ], "resolution": null, "resolutiondate": null, "created": "2017-09-05T07:39:32.000+0000", "priority": { "name": "Critical", "id": "1" }, "labels": [ "6.1.2", "engSchedule", "hyperloop" ], "versions": [ { "id": "19870", "description": "", "name": "Release 6.1.2", "archived": false, "released": true, "releaseDate": "2017-08-03" }, { "id": "19882", "name": "Release 8.0.0", "archived": false, "released": true, "releaseDate": "2019-03-14" } ], "issuelinks": [], "assignee": { "name": "vijaysingh", "key": "vijaysingh", "displayName": "Vijay Singh", "active": true, "timeZone": "America/Los_Angeles" }, "updated": "2019-05-13T21:01:19.000+0000", "status": { "description": "The issue is open and ready for the assignee to start work on it.", "name": "Open", "id": "1", "statusCategory": { "id": 2, "key": "new", "colorName": "blue-gray", "name": "To Do" } }, "components": [ { "id": "10206", "name": "iOS", "description": "iOS Platform" } ], "description": "It used to be in previous versions of the SDK, certainly pre-Hyperloop that if you tried to show a second Popover it would automatically close the original one. Now it crashes the whole app everytime!\r\n\r\nI've already re-written my app with a PopoverManager that keeps a pointer to the Popover and if it exists, hides it, nulls it then 200ms later will spawn a new one, otherwise it will just spawn a new one.\r\n\r\nSo the work around is easy enough, but I had to do quite a bit of re-writing for this.\r\n\r\nAttached is a small example that re-creates the issue. \r\n\r\nClick 1 then 2 = Crash\r\nClick 3 then 4 as many times as you want = No Crash\r\n\r\n", "attachment": [ { "id": "63182", "filename": "app.js", "author": { "name": "mark.henderson@snagr.co.uk", "key": "mark.henderson@snagr.co.uk", "displayName": "Mark Henderson", "active": true, "timeZone": "Europe/London" }, "created": "2017-09-05T07:39:00.000+0000", "size": 1391, "mimeType": "text/javascript" } ], "flagged": false, "summary": "iOS: Trying to open a second Ti.UI.iPad.Popover will crash the app", "creator": { "name": "mark.henderson@snagr.co.uk", "key": "mark.henderson@snagr.co.uk", "displayName": "Mark Henderson", "active": true, "timeZone": "Europe/London" }, "subtasks": [], "reporter": { "name": "mark.henderson@snagr.co.uk", "key": "mark.henderson@snagr.co.uk", "displayName": "Mark Henderson", "active": true, "timeZone": "Europe/London" }, "environment": "SDK 6.1.2", "comment": { "comments": [ { "id": "427583", "author": { "name": "hknoechel", "key": "hansknoechel", "displayName": "Hans Knöchel", "active": true, "timeZone": "Europe/Berlin" }, "body": "Thank you for reporting this issue! While we are trying to reproduce this issue, I am still not sure how Hyperloop plays into this crash, as you are not using it anywhere in the code. Hyperloop was released in 5.5.0 and lives independently from the Ti.* methods. I will get back to you once I found out what's causing the issue.", "updateAuthor": { "name": "hknoechel", "key": "hansknoechel", "displayName": "Hans Knöchel", "active": true, "timeZone": "Europe/Berlin" }, "created": "2017-09-05T09:59:41.000+0000", "updated": "2017-09-05T09:59:41.000+0000" }, { "id": "427585", "author": { "name": "hknoechel", "key": "hansknoechel", "displayName": "Hans Knöchel", "active": true, "timeZone": "Europe/Berlin" }, "body": "I was really thinking it would be the {{run-on-main-thread}} property blocking it, but it isn't (it's smart enough to not block the UI), so it's happening with both kroll- and main-thread. I am wondering when the last time it worked was. Investigating for the next iOS release (6.2.0 will be released this week already, 6.3.0 is iOS 11-only, so 6.4.0 will be the candidate). But as we will likely fix it earlier, hopefully this week, you can already patch your 6.1.x SDK early. I hope that helps you!", "updateAuthor": { "name": "hknoechel", "key": "hansknoechel", "displayName": "Hans Knöchel", "active": true, "timeZone": "Europe/Berlin" }, "created": "2017-09-05T10:45:32.000+0000", "updated": "2017-09-05T10:45:32.000+0000" } ], "maxResults": 5, "total": 5, "startAt": 0 } } }