purchases-ios: Issue with receipt. Receipt is not valid

The receipt verification service is down https://developer.apple.com/system-status/

Looks like it’s related to this news: https://developer.apple.com/news/?id=ytb7qj0x

It would have been good if this was more widely reported to users - really disappointed that I have to check a GitHub issue to see this information in regards to not using SK2

@msavaria we recently fixed a sort of related issue in the backend, so I’m not surprised that you can’t reproduce anymore 😃

We’re also doing more work to ensure that “receipt is not valid” errors provide more context, since there’s actually many reasons why that error can occur (many of which are misconfigurations).

I’ll close this issue for now, but please let us know if you encounter this again and we’ll be happy to help.

I can reproduce this via the following steps.

1. On a sandbox account start a subscription.
2. Cancel the subscription
3. Wait for the subscription period to lapse (helpful to use weekly as this lapses in a few minutes)
4. Try to repurchase the subscription

receive the error: The purchased product was missing in the receipt. This is typically due to a bug in StoreKit.

Interestingly enough, I can successfully purchase non-purchased subscriptions, which is why I think step 2** is the key to this bug. I can also repurchase subscriptions that expire naturally (sandbox does this after a dayish for most durations)

** update, the subscription started working again after the “natural” expiration period lapses. I am implying that the natural expiration is some default limit on the subscriptions that sandbox accounts impose. So I found this error to be apparent during the period after cancelling and next expiration cycle and the “natural” sandbox expiration time.

@tawhidkuet04 thanks for the update! We’re still seeing some apps having issues so it looks like it’ll take a bit to propagate to everyone, but it’s good to hear it’s working for you.

@piersebdon you’re right. It’s been a bit of a struggle on our side since SK2 does handle many things better, but it seems more prone to this sort of unpredictable behavior in practice.

In production, both Sk1 and Sk2 work reasonably well (better than in sandbox at least), but settling on a recommendation has been a bit difficult to be honest. We’re working on improving our own data w/regards to real life performance of both, which will allow us to provide a more informed recommendation, and when we have that we’ll communicate it out.

I apologize for the inconvenience.

i think i have same issue how can i solve it ?

@NachoSoto So… I’ve been trying to get a repro for the past two days but now it works every time 🥲 Nothing really changed on my end except enabling verbose logs.

I’ll follow up when/if I get the error again.

I was unable to reproduce this. Is this in sandbox + on device? You let the subscription expire, then tried to subscribe again?

Yes NachoSoto, Sandbox env and on device. If it makes a difference, I got the error on a couple of different builds, Testflight build as well as a deploy to device from Xcode.

Your second point is also correct: I let the subscription expire by opting out of auto-renew (it is done automatically after 12 renewals). Here’s a screenshot from my RC dashboard if that helps:

Subscription expires every hour and automatically renews 12 times until automatically opting out. At that point, when I try to manually resubscribe, I get the Receipt is not valid error.

Any chance you can send us the complete debug (or .verbose if you can set that logLevel) logs, starting from SDK initialization? 🙏🏻

Of course, I’ll work on getting you those verbose logs.

Any ETA on when we can expect a fix? I have the issue as well and it’s obviously a show stopper for my release.

Here’s the error logs that I got:

error	20:16:02.385941-0400	Turbo	ERROR: 😿‼️ The receipt is not valid. The purchased product was missing in the receipt. This is typically due to a bug in StoreKit.
error	20:16:02.465739-0400	Turbo	ERROR: 😿‼️ The receipt is not valid. The purchased product was missing in the receipt. This is typically due to a bug in StoreKit.
error	20:16:02.466415-0400	Turbo	ERROR: 💰 Product purchase for 'my_product_name' failed with error: Error Domain=RevenueCat.ErrorCode Code=8 "The receipt is not valid. The purchased product was missing in the receipt. This is typically due to a bug in StoreKit." UserInfo={readable_error_code=INVALID_RECEIPT, source_file=RevenueCat/HTTPClient.swift:551, source_function=parseUnsuccessfulResponse(), NSUnderlyingError=0x10eb9b510 {Error Domain=RevenueCat.BackendErrorCode Code=7712 "The purchased product was missing in the receipt. This is typically due to a bug in StoreKit." UserInfo={rc_backend_error_code=7712, NSLocalizedDescription=The purchased product was missing in the receipt. This is typically due to a bug in StoreKit.}}, NSLocalizedDescription=The receipt is not valid. The purchased product was missing in the receipt. This is typically due to a bug in StoreKit., rc_response_status_code=422, rc_backend_error_code=7712}

And here’s what I noticed:

1. It happens most of the times when the subscription has expired and I try to re-subscribe
2. Doesn’t seem to have issue when the subscription auto-renews
3. Error seems to happen way more often after I upgraded the purchases-ios to 4.24.0 and disabled the usesStoreKit2IfAvailable flag, as recommended. Anecdotal, but before I was on version 4.17.8 with usesStoreKit2IfAvailable set to true and I only had the issue once. After upgrading the package, it now basically happens every time I try to resubscribe.
4. Killing the app before trying to resubscribe seems to help mitigate the issue, but it is not an acceptable solution to tell my users.

I’ve been getting similar errors from the Flutter SDK on iOS while testing purchases. I’m on RevenueCat Flutter SDK 4.11.1.

Purchase Error: PlatformException(8, The receipt is not valid. The purchased product was missing in the receipt. This is typically due to a bug in StoreKit., {code: 8, underlyingErrorMessage: The purchased product was missing in the receipt. This is typically due to a bug in StoreKit., userCancelled: false, message: The receipt is not valid. The purchased product was missing in the receipt. This is typically due to a bug in StoreKit., readableErrorCode: INVALID_RECEIPT, readable_error_code: INVALID_RECEIPT

I’ve run into this issue in the past as well. A few things that fixed it for me:

1. Using usesStoreKit2IfAvailable: false, already outlined above by several people
2. Removing the StoreKit configuration (debug builds) from the RC app’s configuration page
3. Ensuring the DerivedData (and subsequently the .app/.ipa binary) is on the host OS’ disk. If this folder is on any other disk, Sandboxing prevents the OS from writing the receipt to the app’s contents folder.

Using StoreKit2 style web hooks under AppStoreConnect has no effect on any of this. RC continues to correctly parse the webhook and process it.

In my case, my app was being built for iOS-Universal and Mac Catalyst.

I hope this helps someone.