Still crashing on Xcode 16.0 and iOS 18.0

I have the same, I’m guessing it’ll be available in a few hours or tomorrow

Did anyone end up figuring this out? This is working fine on one of my machines, but not another. 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 machine 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.

iOS 17.1 beta 2/3 has actually made this problem worse. @Environment(\.colorScheme) var colorScheme Always returns light mode. Attempting to use UIColor { traitCollection in traitCollection == .light ? .white : .black } is again always white. Color(uiColor: UIColor.systemBackground) is also always white. So everything adapts properly until you actually try to write code to modify it. I can't figure out anyway to make the background transparent without it getting stuck in light mode. .clear as the color works in dark mode, but makes the text illegible in light mode.

@Gong I'm seeing the background and text change properly, but @Environment(\.colorScheme) var colorScheme is always returning light, are you seeing the same?

Just as a quick follow up, I was able to get transparency to match the system by doing .activityBackgroundTint(.black.opacity(0.4)) However, it's still stuck in dark mode

Same issue here on the release candidate. Blake, have you heard back on your TSI?

Try installing duti via brew install duti. Then run duti -s com.adobe.Reader com.adobe.pdf all to set Adobe Reader to open all PDF documents. Note that I don't actually have Adobe Reader so the com.adobe.Reader bundle id may be wrong. If so, navigate to the application in Applications>right click it>show package contents>Contents. Open Info.plist and find the Bundle identifier to replace in that command.

This is definitely not fixed in 13.2.1. 13.3 beta 1 I can't really tell because that has it's own issues preventing the project from compiling

I ended up figuring this out months later. Our software ships with this folder /usr/local/opt/company_name that contains a few libraries, software packages, etc. Our Swift code links with a number of them, so it was easiest to set Xcode to recursively search that directory for both headers and libraries rather than individually specifying them. For some rather painful reasons, a copy of python is actually shipped in that folder. Well turns out some header file in that python directory was making Xcode very unhappy and triggering that compiler error. I manually specified the libraries we needed to link against and problem solved.