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

Update remote-simulator.md with workaround steps for boot loops #2672

Merged
merged 3 commits into from
Dec 10, 2024
Merged
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions docs/ios/remote-simulator.md
Original file line number Diff line number Diff line change
Expand Up @@ -81,6 +81,18 @@ In some circumstances, an Xcode configuration problem can result in the remote i
- Run `killall -9 com.apple.CoreSimulator.CoreSimulatorService`.
- Run `xcrun simctl list devices`.

In some cases, Xcode may have generated simulator devices that can also cause the remote iOS Simulator for Windows to be unable to read its properties correctly as it attempts to verify which ones can be deployed to, causing a boot loop.

You can work around this by removing and creating new simulators which you can deploy to:

- Ensure that Xamarin Mac Agent (XMA) and Xcode aren't running.
- Run `xcrun simctl list | grep -w "Shutdown" | grep -o "([-A-Z0-9]*)" | sed 's/[\(\)]//g' | xargs -I uuid xcrun simctl delete uuid`
- Run `xcrun simctl list devices`. You should see no devices listed.
- Open Xcode on your connected Mac
- Open **Windows > Devices & Simulators**
- Select **Simulators**
- Create a new simulator you wish to deploy to.

### Logs

If you experience issues with the remote iOS Simulator, you can view the logs in the following locations:
Expand Down
Loading