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.

redacted

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

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

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)

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.

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).

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.

I can confirm that I am still experiencing this issue after updating to macOS Big Sur 11.3.1. Tested on iMac Pro.