If I untick Debug Executable for the scheme app starts normally but then logically debugging isn't possible so it's not a solution. Actually, I tried that with some limited success. With that box unchecked: my app launches quickly; and I can at least see the console log statements in real time.

Same here. The iOS "App Store Connect" app does allow assignment of external groups to a TestFlight build. But the App Store Connect website does not for some strange reason (it used to work).

Apple updated gesture specifications to include double tap in watchOS: https://developer.apple.com/design/human-interface-guidelines/gestures My guess is that you'd define a UIGestureRecognizer (maybe a UITapGestureRecognizer?) and attach it to a view that implements UIGestureRecognizerDelegate. Not sure how that would be handled in Simulator, however.

I'm having the same exact issue when building with Xcode 15.0.1: ld: framework 'CoreAudioTypes' not found clang: error: linker command failed with exit code 1 (use -v to see invocation)

Looks like Xcode can again be upgraded from the App Store.

Try pressing/releasing the Mac keyboard's option key. Then try again.

redacted

I'm experiencing the same fatal compile error with iOS 18 RC and Xcode 16 RC: /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator18.0.sdk/usr/include/c++/v1/__type_traits/is_integral.h:53:29 'std::is_integral<double>' has different definitions in different modules; definition in module 'std_private_type_traits_is_integral' is here /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS18.0.sdk/usr/include/c++/v1/__type_traits/is_integral.h:53:29 'std::is_integral<double>' has different definitions in different modules; definition in module 'std_private_type_traits_is_integral' is here I don't know how to resolve this since the issue involves the is_integral.h file which is part of the Foundation include. This appears to be an Xcode 16 bug.

Did you ever get this resolved? I'm experiencing the same fatal compile error with iOS 18 RC and Xcode 16 RC: /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator18.0.sdk/usr/include/c++/v1/__type_traits/is_integral.h:53:29 'std::is_integral<double>' has different definitions in different modules; definition in module 'std_private_type_traits_is_integral' is here /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS18.0.sdk/usr/include/c++/v1/__type_traits/is_integral.h:53:29 'std::is_integral<double>' has different definitions in different modules; definition in module 'std_private_type_traits_is_integral' is here I don't know how to resolve this since the issue involves the is_integral.h file which is part of the Foundation include. This appears to be an Xcode 16 bug as my app builds without errors using Xcode 15.4 (on a Mac running Sonoma instead of Sequoia).

Meanwhile, I found a solution to run Xcode 15 on Sequoia.

Meanwhile, I found a solution to run Xcode 15 on Sequoia.

Worked for me as well with Sequoia RC (2024-09-16). Thanks so much, AravShakya! Now I can build my app again (while waiting for showstopper fixes to Xcode 16).

Update: I was finally able to fix this issue by changing the project's Build Settings > Apple Clang Language C++ > C++ Language Dialect to "GNU++23" (from "Compiler Default").

Update: I was finally able to fix this issue by changing the project's Build Settings > Apple Clang Language C++ > C++ Language Dialect to "GNU++23" (from "Compiler Default").

I experienced this error message too, and was able to resolve it by using TimeMachine to restore my app's Xcode project file to a version from yesterday. The provisioning profile issue started today after Xcode 26b3 offered to update my app's project file, and I approved the updates. That update process altered something with the project's provisioning profile data which Xcode 16.4 did not like or did not understand. The result: Xcode 16.4 was unable to install my app on any of my devices (iPad, iPhone, Mac)-- even though Xcode 26b3 was able to.