Newly created apps error with "The key is not valid or is not compatible with the Bundle ID of your app"

What to do

• Check whether you use RevenueCat Apple Receipt Server. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 3d 20h it lasted.

  Anything that failed between 2026-07-27 10:14 UTC and 2026-07-31 06:30 UTC may need a replay.

• Subscribe to RevenueCat's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=revenuecat works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from RevenueCat 3

1. investigatingJul 27, 2026, 10:14 AM UTC

   Developers setting up a newly created app may see "Credentials need attention" for their In App Purchase key. This is caused by Apple's App Store Server API rejecting recently registered Bundle IDs. Existing apps are unaffected, and we have reported it to Apple. Regenerating the key does not resolve it.

   provider

2. identifiedJul 29, 2026, 9:18 AM UTC

   We're awaiting a fix from Apple. Apple’s App Store Server API returns a 401 for Bundle IDs registered on or after 24 July. The same key works against older Bundle IDs in the same account, and we have reproduced this directly against Apple’s API. The failure happens before any RevenueCat logic. For affected apps, the “Credentials need attention” warning is not accurate. Your key is almost certainly correct. Regenerating the key, re registering the Bundle ID or recreating the app will not resolve it. We have reported the issue to Apple and will continue to assist Apple in resolving it.

   provider

3. resolvedJul 31, 2026, 6:30 AM UTC

   The issue appears to have been resolved on Apple's side. We're seeing keys being correctly validated now.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.