Closed mcdurdin closed 2 weeks ago
Applied fix from SO answer:
So it turns out that this was due to XProtect payload 132. This has now been updated to XProtect payload 133. So do this:
Quit Xcode. Delete the contents of top-level /Library/Developer/CoreSimulator. You'll need to provide your admin password. Restart the computer. Open Settings and go to Software Update. You should see the computer checking for updates. It will report back that your Mac is up to date, but in fact it will now have downloaded the new XProtect payload. Confirm that step 4 worked. To do so, hold Option, click the Apple menu, choose System Information, click Software > Installations, and scroll down to the last entry whose type is XProtectPayloads. If it says 133, you're all set. Launch Xcode and download the simulator SDK. At the end of the download there is a heart-stopping pause, but be patient; it will work.
@sgschantz will apply this to ba-macos-keyman-2.
New mac build agent has self-immolated again overnight: https://build.palaso.org/buildConfiguration/Keyman_iOS_TestPullRequests/459852?buildTab=log&linesState=105.164&logView=flowAware&focusLine=146
We saw this before, it is related to: https://forums.developer.apple.com/forums/thread/751049 https://discussions.apple.com/thread/255601035?sortBy=best https://stackoverflow.com/questions/78372541/xcode-doesnt-show-simulators/78421026#78421026
Suggested fix is in StackOverflow comment.