-
-
Notifications
You must be signed in to change notification settings - Fork 378
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
Error on first run after iOS simulator is updated #780
Comments
@rmartin16 Your logging work has paid off big time - this is the bug I've been trying to track for over a year, and I've finally been able to catch it! |
Confirmed that this is still an issue with the current version of Xcode. |
@freakboy3742: I've renamed the tag "first-timers-only" to "good-first-issue" to avoid potentially losing contributions from second-time contributors. Also, what's the purpose of "up-for-grabs"? It's currently on 67 out of 80 open issues, so it isn't conveying much information. It might be better to mark those issues which are not up for grabs by assigning them to someone. |
@mhsmith No disagreement that "first-timers-only" isn't a great name, and that our tags could definitely do with some rationalisation. However, it's not just a matter of changing the name in the Github GUI; at the very least:
I've reverted this name change for now so we can have a more complete conversation about our desired end state for issue tagging across the project. |
checking this out at pycon `24 |
The first time you attempt to run an app in the iOS simulator after installing or updating the iOS simulator, the simulator fails to start at the point when it tries to identify the available simulators.
To Reproduce
Steps to reproduce the behavior:
briefcase run iOS
briefcase.2022_07_06-11_12_50.run.log
The error will also occur when Xcode undergoes a major version update, and the simulator is updated.
Expected behavior
Briefcase should present a list of available simulator images on first run.
Environment:
Additional context
The problem appears to be caused by stray content in the output being parsed. From the log above:
Briefcase currently takes the literal output of the command, and attempts to parse it as JSON. The stray content in the first two lines ("Install started, 1%... ") isn't valid JSON, so the parse fails.
When you run a second time, the stray content isn't present; the entire command output is parseable JSON.
The text was updated successfully, but these errors were encountered: