Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Android emulator does not open until CTRL+C is pressed during "Starting emulator..." #1573

Closed
rmartin16 opened this issue Dec 13, 2023 · 4 comments · Fixed by #1687
Closed
Labels
android The issue relates to Android mobile support. bug A crash or error in behavior.

Comments

@rmartin16
Copy link
Member

rmartin16 commented Dec 13, 2023

Describe the bug

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

Steps to reproduce

Not sure yet...

Expected behavior

Emulator opens while Briefcase is running.

Screenshots

No response

Environment

  • Operating System: Windows 10/11
  • Python version: 3.8, 3.10, 3.11
  • Software versions:
    • Briefcase: 0.3.16

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...

@rmartin16 rmartin16 added bug A crash or error in behavior. android The issue relates to Android mobile support. labels Dec 13, 2023
@JaxkDev
Copy link
Contributor

JaxkDev commented Mar 1, 2024

Can add Python 3.8 + 23H2 to the list, seems to replicate 100% of the time...
briefcase.2024_03_01-00_08_47.run.log

@f-bdolan
Copy link

f-bdolan commented Mar 6, 2024

Additionally, when it does start, my application is not installed

@rmartin16
Copy link
Member Author

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.

@f-bdolan
Copy link

f-bdolan commented Mar 6, 2024

Ah! Excellent, so there is a work-around. For those of you just showing up:

If briefcase run android stalls on "starting":

  1. Run briefcase run android
  2. Pick an emulator (if you use beePhone it will have debugging options turned on)
  3. Wait a moment to stall
  4. Hit Ctrl-C
  5. Leave the emulator open
  6. Run briefcase run android again and choose the SAME emulator
  7. It will install

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
android The issue relates to Android mobile support. bug A crash or error in behavior.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants