{ "id": "107943", "key": "AC-2356", "fields": { "issuetype": { "id": "1", "description": "A problem which impairs or prevents the functions of the product.", "name": "Bug", "subtask": false }, "project": { "id": "12217", "key": "AC", "name": "Appcelerator - INBOX", "projectCategory": { "id": "10000", "description": "", "name": "Customer Service" } }, "resolution": { "id": "3", "description": "The problem is a duplicate of an existing issue.", "name": "Duplicate" }, "resolutiondate": "2013-01-29T01:10:45.000+0000", "created": "2013-01-16T10:23:19.000+0000", "labels": [ "3.0.0.GA", "Activity", "Android", "pause", "resume" ], "versions": [], "issuelinks": [], "assignee": { "name": "mpmiranda", "key": "mpmiranda", "displayName": "Mauro Parra-Miranda", "active": true, "timeZone": "America/Mexico_City" }, "updated": "2016-03-08T07:41:22.000+0000", "status": { "description": "The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.", "name": "Closed", "id": "6", "statusCategory": { "id": 3, "key": "done", "colorName": "green", "name": "Done" } }, "components": [ { "id": "14548", "name": "Titanium SDK & CLI", "description": "Please enter tickets related to the MobileSDK here." } ], "description": "The issue is well described inside the Q&A including code from Kitchen Sink 3.0.\r\nevent listeners for Android activity pause and resume events do not fire on the TabGroup nor on its windows, and the listeners have been positioned inside the respective \"open\" event handlers for good measure. The release notes for SDK 3.0.0 mention changes for TabGroup activities - but these are also not reflected in the 3.0 SDK docs. Here is the link to the relevant Q&A:\r\n[http://developer.appcelerator.com/question/146990/android-tabgroup-activity-pauseresume]", "attachment": [], "flagged": false, "summary": "Android pause/resume activity events do not fire inside TabGroup", "creator": { "name": "mokesmokes", "key": "mokesmokes", "displayName": "Mark Mokryn", "active": true, "timeZone": "Asia/Jerusalem" }, "subtasks": [], "reporter": { "name": "mokesmokes", "key": "mokesmokes", "displayName": "Mark Mokryn", "active": true, "timeZone": "Asia/Jerusalem" }, "environment": "SDK 3.0.0", "comment": { "comments": [ { "id": "234617", "author": { "name": "mokesmokes", "key": "mokesmokes", "displayName": "Mark Mokryn", "active": true, "timeZone": "Asia/Jerusalem" }, "body": "I found the problem: from all my testing, the only apparent way to get the activity object while inside the TabGroup is to use the TabGroup.getActivity() method. The Ti.Android.currentActivity does not work, as apparently don't the window properties/methods. The 3.0 SDK release notes state that TabGroup.activity property is available - yet this is not true. In short - all the documentation for Android activity management/events should be seriously reviewed for 3.0 - it's very confusing at the moment.", "updateAuthor": { "name": "mokesmokes", "key": "mokesmokes", "displayName": "Mark Mokryn", "active": true, "timeZone": "Asia/Jerusalem" }, "created": "2013-01-16T11:27:31.000+0000", "updated": "2013-01-16T11:27:31.000+0000" }, { "id": "236349", "author": { "name": "egomez", "key": "egomez", "displayName": "Eduardo Gomez", "active": false, "timeZone": "America/Los_Angeles" }, "updateAuthor": { "name": "egomez", "key": "egomez", "displayName": "Eduardo Gomez", "active": false, "timeZone": "America/Los_Angeles" }, "created": "2013-01-29T01:10:45.000+0000", "updated": "2013-01-29T01:10:45.000+0000" }, { "id": "281015", "author": { "name": "mpmiranda", "key": "mpmiranda", "displayName": "Mauro Parra-Miranda", "active": true, "timeZone": "America/Mexico_City" }, "body": "DUP issue. ", "updateAuthor": { "name": "mpmiranda", "key": "mpmiranda", "displayName": "Mauro Parra-Miranda", "active": true, "timeZone": "America/Mexico_City" }, "created": "2013-11-24T22:29:57.000+0000", "updated": "2013-11-24T22:29:57.000+0000" } ], "maxResults": 3, "total": 3, "startAt": 0 } } }