Yes, I installed 27.2 on my iPhone today and that also fixed the issue for me. 🎉

I'm experiencing the same issue on iOS 27.0.1 on my iPhone 17 Pro. The certificate expired three days ago, and I haven't found a way to renew it. I confirmed the expiration date by inspecting the certificate embedded in AppTransaction.shared.jwsRepresentation. Even newly created StoreKit transactions are signed with the expired certificate. The issue affects two different apps on the same iPhone, using different StoreKit configuration files. Both work correctly on my iPad Pro. I've also reproduced the issue with Xcode 26.6, 27.0, and 27.1. Restarting the iPhone, resetting transactions, and clearing Xcode's StoreKit caches didn't help.

Same here for a new build compiled and uploaded with Xcode 16.3.

I also got this today for a new build compiled and uploaded with Xcode 16.3. I also I don't use APNs and I don't implement UIApplicationDelegate application:didRegisterForRemoteNotificationsWithDeviceToken:.

I could just successfully refresh the sandbox app store receipt of my Mac app. Yay! I didn't try it for a few days, so I'm not sure when it started working again. https://auth-sandbox.itunes.apple.com still returns an invalid SSL certificate for me, so maybe that was not the root cause after all.

My DTS request was closed telling me "Please submit a complete bug report regarding this issue using Feedback Assistant". Of course I did that before contacting developer technical support and the feedback id number was included in the DTS form (FB13353908). I hope this gets resolved soon.

Yeah, it's quite annoying. The order isn't kept no matter if you use the open panel or drag & drop to upload the screenshots. It would be an improvement if the screenshots were at least ordered by filename (screenshot01.png, screenshot02.png, …).

I'm stuck with the same problem regarding AppTransaction and volume purchase program customers. Did you find a solution? It looks like it would be possible to use the AppReceiptValidator library to locally determine if the environment is "ProductionVPP" (see https://github.com/IdeasOnCanvas/AppReceiptValidator/blob/49e95b1d67ba5c86b016231264832e12496897e8/Sources/AppReceiptValidator/UnofficialReceipt.swift#L32). It's impossible for me to test this though since I don't have access to a sample VPP receipt. I'm not sure if a VPP receipt does contain the originalAppVersion field for example.

I'm also having these problems with complications that use configuration intents and it would be great to get some clarification from Apple engineers. Even the EmojiRangers sample code doesn't work correctly on device. The same code that doesn't work properly for watchOS complications works on iOS as lock screen widgets.

I'm having the same problem.