Is RevenueCat down?

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.

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.

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

We are investigating errors with Apple's services. We have enabled a temporary fallback mechanism that should provide limited functionality.

Apple have acknowledged problems with multiple services. We will keep granting short-lived, temporary entitlements until the problem is resolved. Once the error rate returns to normal, we will disable this mitigation and revalidate the affected purchases.

We're monitoring the Receipt Server for recovery Because we're unable to validate new purchases with the store, we're granting new users a short-term entitlement (at most 24 hours). This prevents customers from being denied access during exceptional situations, such as partial app store outages After connectivity is restored, if validation succeeds, expect a regular initial purchase. If validation fails, the temporary entitlements will expire

Apple's Receipt Server is back up We're replaying purchases Temporary entitlements will either turn into 'real' purchases, or will expire, and related webhook and intergation events for the duration of the outage will start coming through

We are continuing to replay impacted receipts. This does not impact customers that made purchases during the outage window as the temporary entitlement granted by RevenueCat will ensure a seamless transition. This incident will be closed out once all the purchases have been replayed.

All the impacted purchases have been replayed.

We are getting 5xx errors when calling Apple Store Kit 2 to validate receipts. We have enabled mitigations to keep customer purchases uninterrupted and we are investigating the issue.

App Store Connect is experiencing slow response times, which may affect some users. They may encounter delays or issues when managing App Store products in the dashboard or through MCP.

App Store Connect is experiencing slow response times, which may affect some users. They may encounter delays or issues when managing App Store products in the dashboard or through MCP.

App Store Connect issues are now resolved.

The Stripe Marketplace page for the RevenueCat app doesn't show anymore the Install button to install it in the Stripe account. This makes it impossible to install the RevenueCat app in new accounts from the Marketplace page. No existing Stripe connection is affected. Connecting new Stripe accounts to RevenueCat is only possible by using the new Stripe Projects integration through the Stripe cli at the moment. We are working with Stripe to restore the Install CTA button in the marketplace page, allowing customers that don't want to use the Stripe cli to connect Stripe to their RevenueCat account. Please contact support if you are having issues connecting your Stripe account to RevenueCat.

The issue has been resolved by Stripe and it's now possible to install again the RevenueCat Stripe app through the Stripe Marketplace page.