[DAEMON-341] Android: 1.x plugin fails to start when running Daemon 4
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | None |
Status | Resolved |
Resolution | Fixed |
Resolution Date | 2021-04-15T18:04:28.000+0000 |
Affected Version/s | n/a |
Fix Version/s | n/a |
Components | androidlib, appcd-plugin-android |
Labels | n/a |
Reporter | Ewan Harris |
Assignee | Ewan Harris |
Created | 2021-04-15T16:24:57.000+0000 |
Updated | 2021-04-15T21:50:34.000+0000 |
Description
Description
When running the daemon v4 the android plugin fails to start, it appears to be related to starting up adb as if the adb process is running already then it the plugin can start. This works for the 2.x plugin, so I'm guessing it's something fixed in newer androidlib versions, the node 14 note here looks most likely https://github.com/appcelerator/androidlib/blob/master/CHANGELOG.md#v500-jun-22-2020 It's important for 1.x to work as that's what Studio usesSteps to reproduce
1. Stop the daemonappc appcd stop
2. Kill any existing adb daemons - ps aux | grep adb
and run kill -9 <pid>
3. Start the daemon appc appcd start
4. Call the android 1.x plugin, appc appcd exec /android/1.x/info
Actual
Plugin does not startupExpected
Plugins starts and returns infoComments
- Ewan Harris 2021-04-15 PR: https://github.com/appcelerator/androidlib/pull/75
- Chris Barber 2021-04-15 androidlib@2.5.1 has been published.