This issue is a bit strange. On one machine at work, attempting to use the Xcode 15.0 CarPlay simulator results in devices saying "Accessory Not Supported". The redesigned 15.3 simulator crashes on launch. We have tried 5 different phones with USB C, Lightning to USB C, Lighting to USB A, etc and the same result occurs on all of the above. Taking the same phones and cables to 4 other laptops works fine. The non functioning machine connects to any other USB device just fine. We even tried different partitions, installing Xcode, different macOS versions, etc. There are some suspicious parts of the log on the non working machine: default 09:18:10.075726-0400 mobileactivationd Client certification requested by CarPlay Simulator error 09:18:10.088862-0400 CarPlay Simulator Failed to obtain valid certificates from server: <private> error 09:18:10.103753-0400 CarPlay Simulator Incoming message ID 0xaa04 AuthenticationFailed and error 09:18:09.452387-0400 CarPlaySimulatorDeviceLink RemotePairing.framework is not available. default 09:18:09.452419-0400 CarPlaySimulatorDeviceLink RemotePairing.framework not found. Meanwhile the working machines according to Activity Monitor is loading /Library/Apple/System/Library/PrivateFrameworks/RemotePairing.framework/Versions/A/RemotePairing just fine. The non working machine does have that file on disk, so that's not the issue. The non working machine is a 2019 i9 16" MBP. Working machines include a 2018 i7 13" MBP, 2021 M1 Max 16" MBP, and 2020 M1 13" MBP.

Normally we get an email stating: App Store Connect: Version X.Y.Z (Q) for APP_NAME has completed processing. when a build is ready for App Store submission. They have not come in since around 1:30pm EST yesterday (April 12). Is there a bug that's preventing them from going out? We rely on these emails as a part of our CI process

I’ve tried submitting feedback on this numerous times but have gotten absolutely nowhere over 3 years. Every time I start my iMac Pro up, it boots in verbose mode. nvram -x -p reveals no boot-args present in the NVRAM. /Library/Preferences/SystemConfiguration/com.apple.Boot.plist also contains nothing. This issue originally started on a 2017 iMac which I later upgraded to an iMac Pro. I migrated my data to the iMac Pro via a time machine backup and the issue transferred. This makes me think it isn’t anything hardware, EFI, or NVRAM related as time machine rules that out. I should also mention that I’ve tried apps like Onyx to see if they have some hidden preference that I was missing, but no dice.

When attempting to compile my app, I’m getting an error from the SDK itself: <module-includes>:1:9: note: in file included from <module-includes>:1: #import "LibcOverlayShims.h"         ^ /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.15.sdk/usr/lib/swift/shims/LibcOverlayShims.h:66:10: error: use of undeclared identifier 'errno'   return errno;          ^ <module-includes>:1:9: note: in file included from <module-includes>:1: #import "LibcOverlayShims.h"         ^ /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.15.sdk/usr/lib/swift/shims/LibcOverlayShims.h:70:3: error: use of undeclared identifier 'errno'   errno = value;   ^ <unknown>:0: error: could not build Objective-C module 'SwiftOverlayShims' It almost seems like errno.h isn’t included, but I can see that it is on line 33 of that file. I’ve tried the usual derived data delete, product clean, reinstall Xcode, reboot. I’ve tried stripping parts out of the app to try to see what’s causing it, but haven’t gotten very far. Edit: An archive of the app appears to trigger it. Running in debug mode is perfectly fine, then I archive and it breaks it. Trying to run from debug again fails. Making random changes to the project file, then running a git reset --hard then allows debug to work again until I try to archive. It seems like something is wrong with the release settings that then carries over into subsequent debug builds (even with a clean)