The key is not valid or is not compatible with the Bundle ID of your app.

Hey everyone,

This currently appears to be an issue with Apple's validation affecting new apps, which is causing App Store Connect API keys to fail validation. This is currently impacting a wide range of apps, so the issue isn't caused by your configurations.

We have reached out to Apple via feedback and will continue to investigate and do everything we can on our end.

We'll keep you in the loop as we make progress towards a fix.

Thanks,

Hey everyone,

Matt from RevenueCat here.

I'm really sorry for the delay with the key validation issue. The team has been digging into this to get everyone unblocked as quickly as possible.

I'll share any updates here as soon as they're available.

In the meantime, if there's anything else we can do to help, please let me know.

Thanks,

This is not a RevenueCat bug, it's on Apple's side. I tested Apple's App Store Server API directly (no RevenueCat involved): the same key gets HTTP 200 for all of my apps created before July 23, and HTTP 401 for all new apps created July 24–25. Same key, same request, only the app changes.

In short: since ~July 23, Apple is not registering newly created apps with the system that validates in-app purchase keys. RevenueCat just show that failure as "key not compatible."

Nothing on our side fixes it. I tried new keys, new bundle IDs, deleting/recreating the app, uploading a build, setting pricing. All old apps keep working; all new apps fail.

I've filed an Apple Developer Support case with this evidence. I'd suggest others do the same so Apple prioritizes it: developer.apple.com → Contact Us → Distribution → In-app Purchase and Subscriptions.

I’m experiencing same issue and it’s been over 24 hours now. Tried all methods, even multiple keys. checked everything including bundle id, any typo errors, new key and existing key which is fully functional with old apps but nothing is working. Please update if someone found a solution. Stuck at this stage for now.

Hey everyone,

Unfortunately, this is still ongoing. We are continuing to investigate on our end.

I'm sorry, we completely understand how frustrating this issue is. I'm staying very close to the situation internally and will make sure updates are posted here as soon as we have them.

As ​@atek-d10b24 mentioned, the status page will always show the latest information. This can be found here: https://status.revenuecat.com

We'll keep pushing on our end to get this resolved as quickly as possible.

As always, if there is anything we can do to help in the meantime, please let us know!

Thanks,

I'm having the same issue right now.

I have just added my fourth iOS app to RevenueCat. All of them use the same Apple account - hence they all use the same P8 keys. And even though my first three apps work with no issues - the fourth one says:

The key is not valid or is not compatible with the Bundle ID of your app.

I’ve triple-checked everything: the P8 key file is correct, as well as Bundle ID, Key ID and Issuer ID - all correct.

I’m experiencing the same issue. RevenueCat shows “Credentials need attention” and says the key is not valid or is not compatible with my app’s Bundle ID.

I’ve double-checked the P8 file, Key ID, Issuer ID, and Bundle ID, and they all appear to be correct. The In-App Purchase Key is also active in App Store Connect. I’ve tried uploading the key again and revalidating it, but the error still remains.

Is this a known issue affecting newly added apps? Has anyone found a workaround, or does RevenueCat support need to resolve it?

Same issue since yesterday. I guess we have to wait for the hotfix till monday 😅
 

I'm still experiencing the same problem and it hasn't been fixed. By the way, I can successfully establish the same connection with the BundleIDs I created previously. I also tried connecting an old application that wasn't using revenuecat and it worked. I hope someone notices this!

Hey everyone,

I’m just looping back in to say, unfortunately, this issue is still ongoing.

The team is continuing to do everything we can on our end, and we will keep pushing to bring you updates as soon as there has been progress.

As mentioned, I’m really sorry about the delay here, and we know this is a really frustrating blocker for you all. Please be assured we’re doing everything we can on our end to get this resolved for you.

I will continue to keep you all in the loop!

Thanks,

Hey everyone,

As mentioned above, unfortunately this issue is still ongoing. We are continuing to push to get this resolved as quickly as possible.

In the meantime, we do have a workaround that may suit some use cases. We have a Test Store environment that can be used to help you set up a purchase flow in an iOS app without needing to work directly with products from App Store Connect. Whilst this won't unblock App Store submissions, it could be a great way to continue development whilst you're waiting for this issue to be resolved.

You can find more information here: https://www.revenuecat.com/docs/test-and-launch/sandbox/test-store

If you'd like to explore whether this could work for your app, I'd be delighted to help. Just let me know!

Thank you all again for your patience whilst we continue to investigate this.

Also, thank you to everyone above who suggested this may be linked to Apple's recent changes. This has been discussed as part of the investigation, but as there was some time between those changes and this issue starting, we currently believe the two are unrelated.

As always, if there is anything else we can do to help in the meantime, please let me know.

Thanks,

Have just created a new app and it seems like validation went alright. The old apps still face the same problem though.
 

IT IS RESOLVED ! PLEASE TRY VERIFYING AGAIN IT WILL WORK !

I'm having the exact same issue! 🙋‍♂️ My In-App Purchase Key is active and works completely fine for my other app under the same Team, but for the new app it throws: "The key is not valid or is not compatible with the Bundle ID of your app".

Everything is verified: Bundle IDs match, App Store Connect API shows valid, Paid Agreements are signed, and I've waited over 10 hours.

Did you manage to find a fix for this, or did RevenueCat support have to step in?

Same issue

I have checked:
1. The Bundle ID in App Store Connect
2. Bundle ID given in RevenueCat
3. Bundle ID in Xcode

All are same and case sensitivity check is also done

All my agreements in the App Store Connect are active

This is my 15th app in RevenueCat and this is the first time I have got this issue.

I created the App in the App Store Connect in less than 24 hours ago, is that the case ?

I have just opened a support ticket via: https://app.revenuecat.com/settings/support?tab=contact

You might want to do it too.

I’ve also mentioned this post in it.

I’ll let you all know if I get any response.

Exactly same issue too, spent the whole day trying to figure out what the issue is glad i’m not the only one, let’s hope apple fixes this soon

I still have the same issue on my side even tried to recreate the in app purchase key and still says ‘Credentials needs attention’…

Nobody received any response? I was almost going crazy. at least glad to know im not alone :)

It seems I may have succeeded during a brief window when the service was temporarily back up. Sorry for the confusion.

RevenueCat has now announced that the issue has been resolved, though.

https://x.com/RevenueCat/status/2081546014469853675?s=20

for me the issue still remains though.. was anyone able to resolve it?

Still getting same issue of The key is not valid or is not compatible with the Bundle ID of your app. Tried with another new generated key as well after they posted issues is resolved but looks like it hadn’t. Anyone here who was successful in doing it?

Is there an update?

I moved directly from RevenueCat to StoreKit 2. The issue isn't RevenueCat as Matt described. Maybe you shouldn’t wait.

What I see on a dev build, on device, with a sandbox account signed in:

- fetchProducts returns the product fine, with the correct localized price
- requestPurchase fails instantly with "Item Unavailable," and there is no sheet at all,
 it gets refused before any UI appears

I ruled out everything local first: Paid Apps Agreement is Active (another app on the same account sells IAP fine, so it's not account-level), the product is Ready to Submit with price schedule, territories, and review screenshot all set, the storefront matches the sandbox tester's region, no Screen Time purchase restrictions, apple sandbox account.

The one difference I can find: the App Store Connect API reports my unreleased app as CANNOT_SELL in every territory, while my already-released app on the same account reports AVAILABLE. The IAP has never been submitted.

So from what I can tell, a first in-app purchase can be fetched but not purchased until it goes through review along with the app. So this means Apple is not validating any IAP key even if you try from StoreKit. Instead of waiting, I submitted the app with IAP submission together. I won't know for sure until it's, but at this point, nothing else seems to be the cause. For the previous app I made, I remember that the IAP key was working in RevenueCat before my first submission. Maybe I remember it wrong, or maybe they changed something recently.