You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Several users in Discord have reported briefcase run android results in Briefcase getting stuck at the Wait Bar for Starting emulator.... When CTRL+C is pressed, Briefcase exits and the emulator opens.
This issue can be worked around by leaving the emulator open and running briefcase run android again and then choosing the running emulator in the list
Given that the emulator start running properly after Python exits, that suggests that Python is somehow blocking the emulator process. Or possibly that when Python closes the stdout pipe on its end, that unblocks the emulator so it can move forward... Maybe something else about the way Python is starting the emulator...
The text was updated successfully, but these errors were encountered:
Additionally, when it does start, my application is not installed
@f-bdolan: correct; when you press CTRL+C and the emulator opens, your app will not have been installed. However, if you run briefcase run android again and select the "running emulator", Briefcase will install your app then.
Describe the bug
Several users in Discord have reported
briefcase run android
results in Briefcase getting stuck at the Wait Bar forStarting emulator...
. When CTRL+C is pressed, Briefcase exits and the emulator opens.This issue can be worked around by leaving the emulator open and running
briefcase run android
again and then choosing the running emulator in the listSteps to reproduce
Not sure yet...
Expected behavior
Emulator opens while Briefcase is running.
Screenshots
No response
Environment
Logs
briefcase.2023_12_06-23_21_25.run(1).log
briefcase.2023_12_13-21_53_23.run(1).log
briefcase.2023_12_04-23_10_36.run.log
briefcase.2024_02_03-12_47_55.run.log
Additional context
Given that the emulator start running properly after Python exits, that suggests that Python is somehow blocking the emulator process. Or possibly that when Python closes the
stdout
pipe on its end, that unblocks the emulator so it can move forward... Maybe something else about the way Python is starting the emulator...The text was updated successfully, but these errors were encountered: