Missing Receipt leading to (many) App Store rejections

Question

We are hitting the same issues many others on this forum are seeing with multiple App Store rejections trying to get our new app approved. We are on submission #8. Everything works fine for us in Sandbox (and XCode) testing across multiple devices over multiple weeks. We get successful purchases that show up in the RevenueCat sandbox.

The App Reviewer is getting the same error message on the multiple devices they are trying:

Our code is Swift with min iOS 16 support. We are using v4.15.0 of the RevenueCat API (purchases-ios imported using Swift Package Manager)

This error occurs after we call: Purchases.shared.purchase(package: package)

In the above screenshot, the RevenueCat error is “Unknown error” with Code 0.

The only useful part of the error message is “The receipt is missing”, which is coming from the localizedDescription of the underlyingError

if let underlying = err.userInfoyNSUnderlyingErrorKey] as? Error{

errorToShow += underlying.localizedDescription

}

So far, we have been setting usesStoreKit2IfAvailable to true in Purchases.configure. (We are now trying another submission - our 9th! - with that set to false.)

Other things we have tried in previous submissions:

Recreating (and re-configuring) our subscription SKUs
Asking the App Reviewer to sign out/sign in of their App Store account
Multiple tweaks to our purchase flow to better catch errors

Any help in tracking this down would be extremely appreciated.

Thanks

Haley Pace · Accepted Answer

Great, glad you got approved! Sorry for the late reply, but some notes on this for anyone else that runs into this problem:

“The receipt is missing”

This is a sandbox quirk (https://www.revenuecat.com/docs/errors#-missing_receipt_file) in which case to fix the reviewer should make a purchase. This can also happen when calling syncPurchases/restorePurchases before a purchase is made (in which case make sure you're catching errors from those function calls and wait until a purchase is made.)

Issues can also be caused if IAPs are not approved before testing them - ask the reviewer to approve them before testing your app.

And it's a good idea to show the reviewer that your app works in sandbox/testflight. Communication helps! (even though it's a frustrating process)

So far, we have been setting usesStoreKit2IfAvailable to true in Purchases.configure. (We are now trying another submission - our 9th! - with that set to false.)

This is good to do, no need to use StoreKit 2 if that complicates things.

Other things we have tried in previous submissions:

Recreating (and re-configuring) our subscription SKUs

No need to do this.

Asking the App Reviewer to sign out/sign in of their App Store account

Instead of this, you should ask the app reviewer to (1) approve the IAPs first and (2) make a purchase before trying any restore purchases functionality

Multiple tweaks to our purchase flow to better catch errors

Yep, this is a great thing to do!

Adam Houghton · Answer

Following up on this - we finally got approved on our 8th try. The only change we made was setting usesStoreKit2IfAvailable: false in the ConfigBuilder when initializing Purchases

I’m not sure if the storekit change made the difference, or it was other items related to the reviewer’s environment. During the review, we saw a sandbox subscription purchase and renewal successfully come through RevenueCat, which we were not seeing in earlier rejections.

Missing Receipt leading to (many) App Store rejections

4 replies

Reply

Reply

Sign up

‏‏‎ ‎

Log in to the Community

‏‏‎ ‎

Scanning file for viruses.

This file cannot be downloaded