{ "id": "174035", "key": "TIMOB-27425", "fields": { "issuetype": { "id": "4", "description": "An improvement or enhancement to an existing feature or task.", "name": "Improvement", "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": [], "resolution": null, "resolutiondate": null, "created": "2019-08-20T14:59:56.000+0000", "priority": null, "labels": [ "alert", "push" ], "versions": [], "issuelinks": [], "assignee": { "name": "emerriman", "key": "emerriman", "displayName": "Eric Merriman ", "active": true, "timeZone": "America/Los_Angeles" }, "updated": "2019-10-17T07:12:46.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": [], "description": "With the upcoming changes to iOS 13 regarding Location services, particularly the Always Allow location services I would like to make an improvement selection for sending Alerts on Appcelerator when choosing Geographic Selection. Since most apps will be moving away from Always Allow there are very few times when an app will be able to report the user leaving a location since they will have already backgrounded the app in most cases.\r\n\r\nHere is an example use case:\r\nA user attends a festival for which they already have the app for the event. They get to the event and open it to check the schedule. At that time we could update the users location to Appcelerator's servers. Even without Always Allow we could continue to update the users location while the app is open and then after is closed for a few more minutes. The problem is that we would not know when the user left the festival since the app is already backgrounded and our last reported location for them on the Appcelerator server says they are still there. But if there was an option to send to everyone within a radius of the festival who reported their location within the last XX minutes (maybe 15 minutes for example) then the Geographic Selection push notification alerts still serve a purpose. Without this feature I'm afraid it will not be as useful as you will be sending to a group of users who are false-reporting that they are currently at the festival.\r\n\r\nI've mocked up what this could look like when sending an alert using Geographic Location.", "attachment": [ { "id": "66863", "filename": "appcelerator_geographic_suggestion.jpg", "author": { "name": "abeswede", "key": "abeswede", "displayName": "Jeff Abele", "active": true, "timeZone": "America/Chicago" }, "created": "2019-08-20T16:22:16.000+0000", "size": 573771, "mimeType": "image/jpeg" } ], "flagged": false, "summary": "Add Time-Based Option to Alert Sending for Geographic Selection", "creator": { "name": "abeswede", "key": "abeswede", "displayName": "Jeff Abele", "active": true, "timeZone": "America/Chicago" }, "subtasks": [], "reporter": { "name": "abeswede", "key": "abeswede", "displayName": "Jeff Abele", "active": true, "timeZone": "America/Chicago" }, "environment": null, "comment": { "comments": [ { "id": "450858", "author": { "name": "jvennemann", "key": "jvennemann", "displayName": "Jan Vennemann", "active": true, "timeZone": "Europe/Berlin" }, "body": "[~amukherjee] this sounds like something the platform team could take a look at.", "updateAuthor": { "name": "jvennemann", "key": "jvennemann", "displayName": "Jan Vennemann", "active": true, "timeZone": "Europe/Berlin" }, "created": "2019-08-27T14:11:17.000+0000", "updated": "2019-08-27T14:11:17.000+0000" } ], "maxResults": 3, "total": 3, "startAt": 0 } } }