We also have no need for AI in our development environment. We are professional software developers, and we do not want to hand over our code to any AI companies. Furthermore, we would like to have Xcode without that rainbow-colored AI button or any other AI stuff. We had to buy new, expensive MacBooks with M-series processors just to install Xcode 27, even though our Intel MacBooks were still perfectly good. And now we're forced to have that colorful AI button in our faces all the time. Dear Apple, please remove all AI-related UI elements from Xcode when AI is disabled in the settings.

Update: The app went back into review overnight and was approved without any changes. The reason for the original rejection remains unclear. This was the reviewer’s response to my message: Hello …, Thank you for providing this information. We will continue the review, and we will notify you if there are any further issues. Best regards, App Review

Oh no. Intel is no longer supported? What do we do with these beautiful machines now? MacBook Pro 16" 2.4 GHz 8-Core Intel Core i9, 64GB RAM, 8TB SSD

It's working again for us. The crash logs are now downloading without any problems.

We're also seeing these crashes in our apps. However, we can't even download the crash logs right now because Xcode is reporting an error.

We are also unable to download crash logs anymore. Tested with Xcode 26.5:

We have updated the app to StoreKit 2 and submitted it to the App Store. It's already been approved, and everything is working perfectly with real users. Regarding the other app, the user who experienced problems reported that restarting their iPhone resolved the issue and restored all in-app purchases. It seems the problem is solved for us.

We’ve now conducted additional tests. We have a 10-year-old app with around 800 downloads per day that has already been migrated to StoreKit 2 for quite some time. With real users in the live app, there are no issues — purchases can be made and restored successfully. However, with a sandbox test user while launching the app from Xcode, neither purchasing nor restoring works. In another 13-year-old app with around 1,800 downloads per day, StoreKit 2 works perfectly both live and with the sandbox test user without any issues. All apps use the exact same code for the StoreKit 2 logic and are tested with the same users. Today we will take the risk and submit the app we were originally talking about for review after switching to StoreKit 2, and test whether it works live without any problems.

iOS 26.5 didn't bring any improvement either. Restoring the in-app purchases when attempting to purchase again with StoreKit 1 does not work and with StoreKit 2 restoring the in-app purchases does not work at all. How can we contact Apple Support for urgent help? It is a very serious problem. It's a 9 year old app with an average of 600 downloads daily.

We were even able to reproduce it on an iPad with iOS 17.5.1 and on iPhone with iOS 18.7.8 with one of these two affected apps. With StoreKit 2, AppStore.sync() does not synchronize previously purchased in-app purchases. When attempting to purchase the product again, the message appears that the purchase has already been made, and then the error is thrown at: let result = try await product.purchase() and the purchase cannot be restored. Printing description of nsError: Error Domain=SKErrorDomain Code=0 "Ein unbekannter Fehler ist aufgetreten" UserInfo={NSLocalizedDescription=Ein unbekannter Fehler ist aufgetreten, NSUnderlyingError=0x12cef54a0 {Error Domain=ASDServerErrorDomain Code=2047 "Du hast diesen Artikel nicht gekauft." UserInfo={NSLocalizedFailureReason=Du hast diesen Artikel nicht gekauft.}}} Translation: "Ein unbekannter Fehler ist aufgetreten" -> "An unknown error has occurred." "Du hast diesen Artikel nicht gekauft." -> "You did not purchase this item."

We have been experiencing the same issue for a few days now in two of our apps. Users have reported it via email and through negative App Store reviews. In all of our other apps, in-app purchases are still working without any problems. In our case, the issue affects non-consumable in-app purchases (one-time purchases). In one of the affected apps, we can reproduce the issue with a Sandbox user. The problem occurs not only with StoreKit 2, but also with the old StoreKit implementation. We noticed it because we are currently migrating this app to StoreKit 2. With StoreKit 1, in-app purchases can be restored using restoreCompletedTransactions. But when trying to purchase an in-app purchase that has already been bought, the App Store displays a message saying that the item has already been purchased and asks whether it should be downloaded again for free. However, the download/restore then fails: Printing description of nsError: Error Domain=SKErrorDomain Code=0 "Ein unbekannter Fehler ist aufgetreten" UserInfo={NSLocalizedDescription=Ein unbekannter Fehler ist aufgetreten, NSUnderlyingError=0x12cef54a0 {Error Domain=ASDServerErrorDomain Code=2047 "Du hast diesen Artikel nicht gekauft." UserInfo={NSLocalizedFailureReason=Du hast diesen Artikel nicht gekauft.}}} The messages are in German because this is a test user for the German store.

Same here. We submitted updates for three apps. One went into review and was approved within a few hours. The other two have been stuck in “Waiting for Review” for several days. We’ll just have to wait and see.

Everything is back to normal. Thanks to the Apple team for fixing this issue.

It appears that Swiss banks are affected. How can this issue be resolved? Who should we contact to get help? We were planning to finish development of a new app and enjoy our Christmas holidays, but now payouts are blocked and we don’t know how to resolve this issue.

In the email “Reject Payment Notification,” there is a “Contact Us” link at the bottom, but the contact form is not working. It is not possible to select a “Content Type” or a “Topic.” Therefore, it is not possible for us to contact the responsible team. Unfortunately, we have still not received any response to our email to App Store Connect Support. Is there really no Apple employee who can help us here? This is a serious issue.