IAP Receipt verification Failed with 21004

I am always getting receipt verification status 21004 - Secret key error while verifying receipt in sandbox environment in Mac App.


We have one live version in store without IAP. Now we have created new version of app, with IAP subscription. Created Auto-Renewable Subscription and while testing in Sandbox environment, we are always getting 21004 status. This indicate that secret key is wrong, but i have double verified. Also try by generating new secret key. Still it is the same result.


Here are what we have tried already

- We have try by creating new sandbox users from different stores

- Generating new secret keys

- Try by creating new IAP products (Auto-Renewable Subscription)

- Try by creating new IAP products (Non - Consumable)

- Try in different machines

- Try by force killing store processes from Activity monitor

- Try by cleaning derived data, container data etc.

- Try to verify receipt with secret key and without it

- Also try by creating new app with same bundle ID and implementing sample code for IAP and Receipt verification.


Here we are sure that there is no issue with code side. Becasue we are usign same code in other apps from different developer account. And it is working perfectly.

Replies

Hi Moontechnolabs,


Looks like this is the same issue that a number of people are having: https://forums.developer.apple.com/thread/72991


From what I can tell it must be something to do with the Sandbox servers not getting informed of any newly generated Shared Secrets in iTunesConnect. Doesn't seem to effect people who had already generated a Shared Secret before this issue started.


Hopefully Apple will sort this out soon, we have been waiting almost a week for a fix.

Nearly one week we are unable to validate subscription receipt and worst, it lock all other receipt.

It seems to be fixed


https://forums.developer.apple.com/thread/72991

The problem still exists. Currently I'm having the same problem when try to test subscriptions. Hopefully they fix it soon!

Unfortunately, the problem still exists
If you have a reproducible case, please file a ticket and include all relevant information such as console logs, sysdiagnose, base64 encoded receipt, sandbox Apple ID used and screen recordings if applicable. https://feedbackassistant.apple.com