[TIMOB-18590] CLI: Android: Difference in behavior of the CLI when using --no-launch on Genymotion emulators and Android emulators
GitHub Issue | n/a |
Type | Bug |
Priority | Medium |
Status | Open |
Resolution | Unresolved |
Affected Version/s | Release 4.0.0 |
Fix Version/s | n/a |
Components | Android, CLI |
Labels | cb-tooling, qe-4.0.0 |
Reporter | Ewan Harris |
Assignee | Praveen Innamuri |
Created | 2015-02-17T23:58:56.000+0000 |
Updated | 2020-01-30T10:26:18.000+0000 |
Description
Description
When building an Android project with the flag --no-launch there is a difference between Genymotion emulators and Android emulators behavior. When built to Genymotion the process exits after the build has finished but when building to an Android emulator the process does not exit.
Steps To Reproduce
1. Build a project to an Android emulator using ti build -p android -T emulator --no-launch
2. Build a project to a Genymotion emulator using ti build -p android -T emulator --no-launch
Actual Result
1. When the build finishes the process will not exit
2. When the build finishes the process will exit
Expected Result
I am unsure which of the two is meant to be the correct behavior but I believe it may be that the process should exit after the build.
Comments
JSON Source
No comments