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.

It seems to be something to do with FetchRequest… if I comment that out, the rest of the app runs fine. I have a second List and FetchRequest in my app that also crash. I don’t know if it’s related to the other crash, but it has a different error so I’m attaching that here along with some code. struct RecentlyDeletedView: View {     @Environment(\.managedObjectContext) var managedObjectContext     @FetchRequest(         fetchRequest: CheatManager.deletedCheatFetchRequest()     ) var cheats: FetchedResults<CSCheat>          var body: some View {         List(cheats, id:\.self) { cheat in             NavigationLink(destination: DeletedDetailView(cheat: cheat)) {                 CheatRow(cheat: cheat)             }         }         .navigationBarTitle("Recently Deleted")     } } So it looks like both crashes occur when I try to call/use fetchRequest.wrappedValue in a View body. It could be an issue with my model or the CSCheat object, which is an Obj-C class? I don’t think it’s that I’m using an NSFetchRequest to build my FetchRequest — I tried replacing it and that still failed: &#9;&#9;@FetchRequest( &#9;&#9;&#9;&#9;entity: CSCheat.entity(), sortDescriptors: [] &#9;&#9;) var cheats: FetchedResults<CSCheat> Other crash (simulator) - https://developer.apple.com/forums/content/attachment/e70f93d3-6e57-4fc8-8369-a3a8fd247995

@NicoD I seem to be running into this same crash, except I’m not even using any iOS 14 features in my Watch app! I’m building with Xcode 12 beta 6, but running (well, crashing) on iOS 13.6. Did you or the Developer Tools Engineer ever find a fix?

I take it back, I think they are working… thanks ppix!

I’m still having trouble with CloudKit notifications on watchOS 6.2. I did everything @ppix suggested, which got notifications partly working — my watch app does receive CloudKit remote notifications, but only when it is active. If I push changes to CloudKit while the app is inactive, nothing happens; if I then open the app, the notification is immediately delivered. I would expect CloudKit notifications to wake my app so it can sync in the background — is that working for anyone?

The error I was seeing has been fixed. I did contact Apple Developer Program Support and they eventually escalated the issue to an "internal team". A couple of days later, I tried uploading a Catalyst build and it works. I don't know if the internal team fix it or someone else did, but the problem has disappeared.

I'm still seeing a similar error. This is from last night:ITMS-90338: Non-public API usage - The app references non-public symbols: _IOObjectRelease, _IORegistryEntryCreateCFProperty, _IORegistryEntryFromPath, _kIOMasterPortDefault,…Those are all public symbols in IOKit for Mac. I haven't touched any of this code, which pass submission dozens of times before this past weekend when this error appeared. I'll file a complaint with Apple, since they don't seem to have fixed this problem for everyone.