RevenueCat reported this minor-impact incident on its official status page on Jul 27, 2026, 10:14 UTC. It was resolved after 3d 20h.
Right now RevenueCat is operational. Live RevenueCat status →
The issue appears to have been resolved on Apple's side. We're seeing keys being correctly validated now.
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.
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.
Our 5-minute checks didn't record a change in RevenueCat's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.
Overlapping incidents aren't necessarily related.
RevenueCat reported 10 incidents in the last 90 days, 5 of them major or critical. A typical incident lasted 2h 20m. See RevenueCat's uptime and incident history