AppStore rejection: The receipt is not valid

  • 31 October 2021
  • 32 replies

Show first post

32 replies

Badge +2

Same issue here. Is there a solution now?

Badge +2

Same issue 50/50 chance I get this on a new app review.

Badge +2

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.

Badge +1

Adding my 2 cents here.

  1. When checking the user’s entitlement I used ‘isActiveInCurrentEnvironment’ instead of ‘isActive’.
  2. When replying to the reviewer, I told them that I’m using RevenueCat and pointed to this article: Under the “Other tips” section they specifically saying that there’s nothing to do with such rejection.

I don’t know if what I did helped or was it just voodoo/luck, but the version got approved.


Badge +3

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.

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...

Badge +1

I just got the same rejection message - 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.