{ "id": "170366", "key": "DAEMON-164", "fields": { "issuetype": { "id": "1", "description": "A problem which impairs or prevents the functions of the product.", "name": "Bug", "subtask": false }, "project": { "id": "12519", "key": "DAEMON", "name": "Appcelerator Daemon" }, "fixVersions": [ { "id": "19959", "description": "", "name": "Appc Daemon 1.1.0", "archived": false, "released": true, "releaseDate": "2018-04-09" } ], "resolution": { "id": "1", "description": "A fix for this issue is checked into the tree and tested.", "name": "Fixed" }, "resolutiondate": "2018-01-11T16:04:37.000+0000", "created": "2017-11-17T17:43:24.000+0000", "priority": { "name": "High", "id": "2" }, "labels": [], "versions": [], "issuelinks": [], "assignee": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "updated": "2018-01-11T16:04:37.000+0000", "status": { "description": "A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.", "name": "Resolved", "id": "5", "statusCategory": { "id": 3, "key": "done", "colorName": "green", "name": "Done" } }, "components": [ { "id": "15622", "name": "appcd-plugin-android" } ], "description": "If {{adb}} is not found, it cannot track devices. The Android plugin will watch for an Android SDK to be added, but then it needs start tracking devices using the installed {{adb}}.\r\n\r\nAs a workaround, the Android plugin can be manually stopped or be unloaded after 1 hour of inactivity. On the next request, it'll start and detect {{adb}} and begin tracking devices.", "attachment": [], "flagged": false, "summary": "appcd-plugin-android: Device tracking does not reinit when adb is installed/restarted", "creator": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "subtasks": [], "reporter": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "environment": null, "closedSprints": [ { "id": 986, "state": "closed", "name": "2018 Sprint 01 Tooling", "startDate": "2017-12-31T16:58:25.103Z", "endDate": "2018-01-14T16:58:00.000Z", "completeDate": "2018-01-17T22:42:40.307Z", "originBoardId": 219 } ], "comment": { "comments": [ { "id": "432777", "author": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "body": "PR: https://github.com/appcelerator/appcd-plugin-android/pull/6\r\n\r\nTo test and for simplicity, only have 1 Android SDK discoverable on your machine. Go into the sdk's platform tools directory. Run {{appcd exec /android/latest/info/devices --subscribe}} and then rename {{adb}} to {{adb2}} which will trigger {{adb}} disappearing. Change it back and it'll redetect Android devices. This should also work if you move the entire Android SDK directory from some undiscoverable directories such as subdir on your desktop, then move it to a discoverable directory such as {{/opt}}.\r\n\r\nThe list of devices should become empty if {{adb}} disappears.\r\n\r\nNote that on macOS and Linux, if {{adb}} is running, then you can do whatever you want to the executable on disk and {{adb}} will still be running. This is fine.\r\n\r\nAnother thing to test is subscribe to devices and then run {{adb kill-server}}. The daemon will say the devices are empty, then attempt to restart adb in 2 seconds. After a few more seconds, the list of devices will be refreshed.", "updateAuthor": { "name": "cbarber", "key": "cbarber", "displayName": "Chris Barber", "active": true, "timeZone": "America/Chicago" }, "created": "2018-01-05T05:49:08.000+0000", "updated": "2018-01-05T16:53:22.000+0000" } ], "maxResults": 1, "total": 1, "startAt": 0 } } }