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

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?

This problem seems to be related to the billing side; the issue persists.

Same issue.

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,

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,

Is there an update?

Hello, is there any update? Thanks

You can track the incident status here. https://status.revenuecat.com/ 

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,

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,

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. 

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. 

Well, you might be onto something here. As Apple have recently changed the submission flow for in-app purchases and subscriptions. Previously, you had to include them with your next app build on the “version” page. Now you have to add each one of them separately to your “draft” submission via their dedicated page (i.e. in-app or subscription page). So definitely something have changed in this flow. Maybe it's somehow related to this issue?

I had the same thought. The change to how in-app purchases and subscriptions get submitted is recent enough, and the timing lines up almost too well for it to be a coincidence.

Hello, has the problem been resolved?

nope, I still have the issue.

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,

I just added a new app to App Store Connect and try to connect with revenueCat, and ran into the exact same issue, it’s driving me crazy.. it doesn’t seem to recognize any new bundle id created, I even recreated app, but it recognize my old bundle id even though I deleted it! hope we have a fix soon..

any resolution here ? 

​@matt-heaney one thing bothers me.

I've recently read that there's around ~1800 App Store app submissions daily (and these are only the ones that have already passed the verification). And we know that almost each and every app nowadays contains in-app purchases, right?

Does this mean that all of those apps are blocked since Jul 24th, and can’t be submitted to App Store? If that's the case, then it's kinda sick that Apple have not resolved this for almost a week now… 😮

It may as well be a controlled outage to stop us from flooding the app store with our super-useful slop 😀

Hey everyone,

Just looping back in with another update.

Whilst the incident is still ongoing, we have seen a small handful of apps have their credentials approved. There doesn’t seem to be any pattern to this, so I’d recommend checking your app again, just in case.

​@grzegorz-d-caac6b, this is a really fair point. Whilst we can't know for certain what is happening outside of our own data, we believe the impact may be more widespread.

We will continue to do everything we can.

In case it wasn't seen in my previous message, we do have a recommendation for those currently blocked from development:

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.

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

Thanks,

I’m having the same issue on my end. and i cant get the test purchase to work in sandbox mode. is this also a problem you guys are experiencing?