A little more detail, in case it's useful: I'm now getting past the line of code above but I'm failing when generating user tokens. So: let developer = try await MusicDataRequest.tokenProvider.developerToken(options: [.ignoreCache]) let token = try await MusicDataRequest.tokenProvider.userToken(for: developer, options: [.ignoreCache]) is now failing on the second line, not the first. I think I got to this point by completely signing-out of Media & Purchases and then signing back in again. This is now documented in FB24959416.

Same issue here

I did try the "Clean" option in Xcode Cloud a few days ago and I'm afraid it made no difference for me. Unfortunately because it's a random issue it's quite possible to get a few good builds before you get a bad one ☹️.

I started seeing this exact issue on Tahoe but then started getting it on macOS 15 too, so I don't think it's Tahoe specific. There's an existing thread running here: https://developer.apple.com/forums/thread/791541.

I reported this via Feedback Assistant - see FB18666175

Reported as FB17265373

Same for me. My app has has never used APNs. It's probably had a hundred+ previous builds and I've never had this message before. I was using Xcode 16.2 on my desktop but can see that Xcode Cloud (which I used to build the release) is using 16.3.

I am getting the same notification. Submitted a new version to Xcode Cloud today and got this message out of nowhere. I don't use APNs and I don't implement UIApplicationDelegate application:didRegisterForRemoteNotificationsWithDeviceToken. Is there a resolution to this yet?

We're seeing > 1 hour. Again, nothing showing on the System Status page.

I'm getting the exact same error, very similar circumstances: extension NSItemProvider { func loadObject<T>(ofClass: T.Type) async throws -> T? where T : _ObjectiveCBridgeable, T._ObjectiveCType : NSItemProviderReading { return try await withCheckedThrowingContinuation { continuation in _ = self.loadObject(ofClass: ofClass) { item, error in switch (item, error) { case (.some(let item), .none): continuation.resume(returning: item) /* Task-isolated value of type 'T' passed as a strongly transferred parameter; later accesses could race; this is an error in the Swift 6 language mode */ case (.none, .some(let error)): continuation.resume(throwing: error) default: let error = NSError(...) continuation.resume(throwing: error) } } } } } Based on the advice below I changed the method signature to: func loadObject<T>(ofClass: T.Type) async throws -> T? where T : _ObjectiveCBridgeable, T._ObjectiveCType : NSItemProviderReading, T: Sendable which seems to have fixed it!

Shortcuts involving Text URLs are equally broken in iOS 17.6 beta 3, although the error message has changed:

In the end I had to escalate to the App Review Board, who approved the release. Since then I’ve added some text at the top of the “Notes” section of each release asking App Review not to reject me for 4.0 as use of a browser in this way is a) required and b) has been approved by App Review Board. I haven’t had an issue since then. Really not good that you are still getting rejected for this though - it doesn’t reflect well on App Review that this message still hasn’t got out.

It's not just a GoogleSignIn issue: they just rejected my app for using completely standard OAuth 2 web authentication, for precisely this reason. It's incredibly frustrating: if they don't like it they should be complaining to the Apple team who develop ASWebAuthentication. It's not like we app developers can do anything about it - we are just caught in the middle. I've raised an appeal to App Review but I have no idea what the "Plan B" is if they reject my appeal.

I switched to Github Desktop a month ago. It's like Xcode used to be: a simple list of changed files, side-by-side comparison and a big blue commit button. A breath of fresh air. And it works perfectly next to Xcode too e.g. Xcode updates in real time when you check-in. Until Xcode gets fixed I can recommend it.

Another new Github Desktop user here. I've battled with Xcode 15 long enough and I'm fed up with commits which take twice as long as they should (because it's so hard to review changes) and then seem to leave half the committed files behind. And that's if it doesn't freeze. Am not sure what was driving these changes and why Apple thought adding steps, complexity and poor UX to this process was necessary but it needs a fast re-think. This isn't something we'll learn to love given time. We will just switch away.