Skip to content

Conversation

@slavikdenis
Copy link
Contributor

Summary:

  • docs: fix missing code block langs & typos
  • feat: add iPhone 14 as a fallback simulator
  • feat: add last booted simulator pick, if no other matches the finder
** last booted simulator **

Sometimes, it's better to have the last booted simulator as a fallback, instead of the first available simulator.

Test Plan:

After a new Xcode install, when the simulators are fresh, and CLI yet doesn't have the latest iPhone listed as a fallback simulator, CLI fails to pick an appropriate simulator. If the user however run already any preferred simulator, it gets picked instead of failing on picking the appropriate simulator.

Copy link
Collaborator

@adamTrz adamTrz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! 🏅

#### Initializing project with custom template

It is possible to initialise a new application with a custom template with
It is possible to initialize a new application with a custom template with
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

UK v US English ;)

@thymikee
Copy link
Member

That's definitely an improvement, thanks! One thing I'd add as a followup, is to select the first available simulator if none of the fallbacks exist and a user never opened a simulator—which will happen for first-time users next year when starting with fresh Xcode 15 I suppose :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

No Simulator Available bug after updating to XCode 14

3 participants