From 579d5672bfbe4476fb51e30f389c396fa3860dee Mon Sep 17 00:00:00 2001 From: Tim Miller Date: Tue, 10 Dec 2024 15:17:28 +0900 Subject: [PATCH 1/3] Update remote-simulator.md with workaround steps for boot loops Xcode can generate simulators with null data that causes the iOS Remote Simulator to trip up with an NRE. This has been addressed internally and can also be worked around by removing and recreating the simulators. --- docs/ios/remote-simulator.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/docs/ios/remote-simulator.md b/docs/ios/remote-simulator.md index 3c029dbd0..326bc767e 100644 --- a/docs/ios/remote-simulator.md +++ b/docs/ios/remote-simulator.md @@ -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: From 5c79e03a2732dcf0f70099e6f5b197498e4ff6da Mon Sep 17 00:00:00 2001 From: David Britch Date: Tue, 10 Dec 2024 09:25:28 +0000 Subject: [PATCH 2/3] Add colon. --- docs/ios/remote-simulator.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/ios/remote-simulator.md b/docs/ios/remote-simulator.md index 326bc767e..3881cd3a7 100644 --- a/docs/ios/remote-simulator.md +++ b/docs/ios/remote-simulator.md @@ -83,7 +83,7 @@ In some circumstances, an Xcode configuration problem can result in the remote i 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. +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` From 0b29b90761efea99d061de4e17cd45711fe8b97c Mon Sep 17 00:00:00 2001 From: David Britch Date: Tue, 10 Dec 2024 09:28:05 +0000 Subject: [PATCH 3/3] Add periods. --- docs/ios/remote-simulator.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/ios/remote-simulator.md b/docs/ios/remote-simulator.md index 3881cd3a7..768f9ca9d 100644 --- a/docs/ios/remote-simulator.md +++ b/docs/ios/remote-simulator.md @@ -86,11 +86,11 @@ In some cases, Xcode may have generated simulator devices that can also cause th 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 | 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** +- Open Xcode on your connected Mac. +- Open **Windows > Devices & Simulators**. +- Select **Simulators**. - Create a new simulator you wish to deploy to. ### Logs