I am seeing this same error with one of my apps. I have submitted FB21885923 with the logs attached.

Success! I finally noticed a difference between the instructions in the latest Xcode beta release notes and Quinn's instructions: … remove related profiles from ~/Library/Developer/Xcode/UserData/Provisioning Profiles and ~/Library/MobileDevice/Provisioning Profiles I had cleaned out that first directory but not the second. Deleting the relevant profiles in both directories seems to have fixed everything.

@DTS Engineer Still no luck for me. I have an unusual arrangement: my app is a Mac Catalyst app that embeds a non-Catalyst Mac app as a LoginItem. All my Mac targets (Catalyst and non-Catalyst) have REGISTER_APP_GROUPS = YES and all have the App Group entitlement. When I inspect the archived build as you suggest, every provisioning profile appears to have application-groups set correctly. But I still get the same error from ASC. I filed a Feedback and attached an archive build, if you or the ASC team could please take a look: FB16664827

I've been stuck on this for two days now. Specifically, I have two Mac (non-Catalyst) targets bundled with my Mac Catalyst app and these fail on submission with the same error everyone else is seeing. First, I tried generating manual provisioning profiles with the application-group entitlement added. Archive works but submitting to ASC fails with the same error as before. Second, I installed the Xcode 16.3 beta, toggled "Automatically manage signing" off and on, and then deleted and re-added the App Group capability. This finally updated my Xcode Managed Profiles to include the application-group entitlement. However, submitting to ASC still fails (I tried archiving and submitting with both Xcode 16.3 and 16.2). I'm not sure what else to try at this point.

In your target's build settings, set User Script Sandboxing to NO. Thank you to jpb for this answer: https://stackoverflow.com/questions/76490618/xcode-15-beta-does-not-allow-run-script-access-to-git-head-and-info-plist

Download via Xcode is working now!

I see the same error. There is also no sign of the "watchOS 10 beta 4 Simulator Runtime" download at https://developer.apple.com/download/all/.

I am seeing this same issue in Xcode 15 beta 4, though I am importing an xcframework directly rather than using SPM.

Is anyone still seeing this issue? I am not, but one of my customers is still getting the error with iOS and watchOS Beta 8.