Figured it out, I had to remove the app version from the currently staged review, and the button is now enabled.

Another example from a unit test, where the color isn't black but is definitely not what the fragment shader is returning.

I was able to work around this issue by setting the Host Application to "None" for my test scheme. This stops Xcode Cloud from attempting to start up the application binary.

I was able to work around this issue by setting the Host Application to "None" for my test scheme. This stops Xcode Cloud from attempting to start up the application binary.

I'm getting this same issue. build-for-testing seems to be working fine, but test-without-building experiences the error mentioned above. Logs are attached. Came over here from https://forums.developer.apple.com/forums/thread/725660?page=1#810351022, which is what's happening on iOS. xcodebuild-test-without-building.log

I'm also seeing this consistently within Xcode Cloud, but haven't seen it locally. I've downloaded the crash log bundle, and it contains one for AccessibilityControlsExtension and a bunch for MercuryPosterExtension (examples attached). I don't really know what either of those things are, but can't find any references to my code in either. MercuryPosterExtension-2024-10-22-....ips AccessibilityControlsExtension-2024-10-22-....ips

I'm seeing the same issue (same error message) on my Xcode Cloud macOS test run. iOS also isn't working though, with a different error message: [AppName] (3484) encountered an error (Early unexpected exit, operation never finished bootstrapping - no restart will be attempted. (Underlying Error: Test crashed with signal ill before starting test execution.))

I'm seeing this as a major issue as well, most of the time is taken up decoding my objects on the main thread.

This is now supported natively with the scrollClipDisabled() modifier (documentation) on the ScrollView