@vsmedia @sk95 I've had zero luck with the two users experiencing this issue. They've both confirmed they are on the latest iOS and have restarted their devices but still getting the same issue. I have since pushed new builds of the app to the App Store with no change either.

@Maria1234 Are you able to reliably recreate the issue? I haven't yet managed to recreate it on a real device or in a simulator.

@jwcarr I've done that now, awaiting a reply. Thanks. I'll update here with any info.

@jwcarr Yes it is still happening today. It seems to only really start at the beginning of this week. It's only a very small number of users so debugging is very difficult.

First time I've ever had an issue here so I'm not sure of the path of escalation but I appreciate others confirming they're seeing the same issue. I've filed a feedback report but ideally I want to make some more noise about this as I now have multiple users leaving negative reviews as I'm unable to provide them with a solution to a problem that is completely out of my control I've exhausted so many paths now with no clear workaround found.

We're already gating AppStore.sync() behind a Restore Purchases button, so that path is covered. On the App Store Server API suggestion — we don't store transaction IDs server-side as we have no user account system. The app relies entirely on StoreKit to surface the transaction, which is then verified server-side in the moment but never persisted against a user identity other than in the apps local database. So that avenue isn't available to us. I have asked the user if they will sign out and sign back in to verify this issue but they so far haven't agreed to do this.

@DTS Engineer it’s a M2 pro MacBook Pro and I’m not running anything in a VM it’s all running natively. I’ve tried both stable xcode and the beta and get the same error.

I only build my app locally, and when validating the app I get this same error.