AppStore rejection: The receipt is not valid

This was the reply from Apple review team

Thank you for your response. We tried the In App Purchase with a different Deve and observed the same issue.

After purchasing the In App Purchase, the App Store authenticated and confirmed, but the app failed to validate the receipt. Attempting to repurchase reported a successful purchase from the App Store, but the app did not implement the purchased features.

We look forward to reviewing your app once these issues have been addressed and the new build has been received and queued for review. Please be sure to resubmit any In App Purchase products along with the revised binary.

Best regards,

App Store Review


I guess revenuecat should do something about this. It’s matter of luck, I can get approved one time and get rejected 10 times for the same reason

I also had this issue. After a number of rejections, the only thing that seemed to help was setting 

usesStoreKit2IfAvailable: false

in the RC config (in Purchases.configure).

Of course, it could just be coincidence...

Same issue here, Yesterday I tried appealing the review with Ryan’s comment, but I am still waiting for their response. 

We were just bit by this rejection as well. Message from reviewer: “We discovered one or more bugs in your app. Specifically, we were unable to subscribe, we had an error message.”

Checking the logs the error was: “The receipt is missing.”

My macOS app has now been rejected twice for this “invalid receipt” error. I’m using RevenueCat on Flutter. It works fine when I test it via TestFlight, but Apple’s app review people keep hitting this error.

Has anyone found a solution?

The same happened to our App two days ago, we just resolved it.

This is how we did it.

First to know if you are having the same issue or something else, our payments did work perfectly inside TestFlight and the issue only happened inside the AppStore.

If this is the case, then you should see a "ready for sale" in the left upper corner.

However, if we checked the in-App payments under subscription groups it still said "waiting for review"

Sending the app into a new version review did not resolve the issue.

Solution: We opened a dispute and chatted with the support https://developer.apple.com/contact/app-store/?topic=appeal

We arranged a Callback with this hotline https://developer.apple.com/contact/

Be specific with the problem, and if possible send screenshots. It took two days to resolve.

However, for some the only thing that seemed to work was deleting the in-app payments and setting them up new before submitting a new build. https://developer.apple.com/forums/thread/35757

Good Luck

I had this issue so I’ll chime in as maybe it will help others.
I went through 4 or 5 submissions before it got approved.

In my case they were having trouble getting through the paywall (I believe) or the subscription process wasn’t working. We weren’t able to replicate any issues and our subscription workflow is fairly standard. I’m not sure how they test their apps. I did a bunch of usability improvements to the paywall page (like a spinner while things are loading). The change I did that finally got us over the hump was just displaying the full error to the user on the paywall page if the subscription fails. (In our case with flutter this is catching the exception to the revenuecat calls and showing the full text to the user). Our thinking was that we would then have the screenshot they provide as part of the review to see what error they’re hitting.

However, after this change it was accepted. My guess is that they saw an error and realized what the issue was and changed something in their test environment to work around it. It could have been something as simple as not having online connectivity during the review, which I believe might have been the issue as I’ve seen others mention it.

It may have also just been luck and they happened to accept it.

Same Issue.

What should I do?

--------------------------------------------------------

Bug Fix Submissions

The issues we've identified below are eligible to be resolved on your next update. If this submission includes bug fixes and you'd like to have it approved at this time, reply to this message and let us know. You do not need to resubmit your app for us to proceed.

Alternatively, if you'd like to resolve these issues now, please review the details, make the appropriate changes, and resubmit.
 

Guideline 2.1 - Performance - App Completeness

We found that your in-app purchase products exhibited one or more bugs which create a poor user experience. Specifically, your app displayed an error message when we tried to purchase the subscription plan. Please review the details and resources below and complete the next steps.

Review device details:

- Device type: iPad
- OS version: iOS 17.2

Next Steps

When validating receipts on your server, your server needs to be able to handle a production-signed app getting its receipts from Apple’s test environment. The recommended approach is for your production server to always validate receipts against the production App Store first. If validation fails with the error code "Sandbox receipt used in production," you should validate against the test environment instead.

Resources

- Learn how to set up and test in-app purchase products in the sandbox environment.
- For more information on receipt validation, see the In-App Purchase FAQ.
- If your app makes a SKReceiptRefreshRequest call and fails, do not retry the call. Assume the user does not have access. Continue by making the addPayment call.
- If your app makes a SKReceiptRefreshRequest call to restore previously purchased in-app purchases, make sure the app calls restoreCompletedTransactions when the user selects the "Restore" button.

Please see attached screenshot for details.

First, create a new Sandbox account. Second, in "app review reject," you need to explain your shortcoming and give them a Sandbox account.
end, wait for Apple's response.

We have overcome rejections two times now by providing a new test account under the "Sign-In Information" section. To avoid problems, we now always create a new test account (with the same credentials) for App Review.

same issue here.

I got 10+ rejections and I tried all posted in this community.
1. asked to re signin to the reviewers.
2. uploaded the builds that working on my side.
3. recreated the subscriptions.
4. provided the sandbox account.
5. usesStoreKit2IfAvailable in Configure.
6. explained to the reviewers that RevenueCat automatically handles sandbox and production purchases.

​​​​​​​But nothing helped me.
 

In the screenshot they attached, it says this error.
“There was a problem with the App Store. Problem communicating with the Store when trying to validate the receipt.”

I guess it is System Error from StoreKit.

What should I do for now?
I am almost dead and I am doubting if it is the right way to use the RevenueCat for the paywall.

I get also the same rejection. Have solved the problem?

Hi, I have the same problem. I told them to login again with @ryan suggestion but the problem still persists. Why does this problem occur? Can you help us solve it?