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

Hey ​@zeynep-yavuz!

Thanks for the update. I’m so glad to hear your credentials are now validating as expected. Hearing that this resolved itself after making a sandbox purchase is really interesting, so thank you for sharing that insight!

If anyone else is running into issues, I’d recommend following the same steps and making a sandbox purchase.

If anyone is still running into issues after that, please let me know, and I’ll take a deeper look at your account!

Thanks again,

Sorry for the late reply. It showing the same issue but when i go to the app and try to make a purchase, it was successful. Then i go to the dashboard after the subscription and reload the certificate status it fixed! Thank you for your help! 🤗

This issue was solved. Thanks a lot ​@matt-heaney ✌🏻

I can also confirm the issue is fixed in my case 👍

Thanks a lot ​@matt-heaney ! 🙌

AYYYY My key just go verified! i think its gonna be fixed now

​@zeynep-yavuz, could you send me a private message with the name of the app that's still impacted, please? I'll take a look on my end.

We have seen a few dashboards still showing this, but in those cases they've been genuine validation errors (such as an incorrect Bundle ID in the RevenueCat dashboard). These are usually issues we can resolve really quickly. However, I’ll investigate your impacted app to see what is happening there.

Hello i still get the issue. Should i wait for a bit longer? I tried to change the 'Country or Region Availability' in my subscription packages too. (I’m trying all ways) 


edit: when i tried to subscribe it worked! I still get the “The key is not valid or is not compatible with the Bundle ID of your app.” issue on revenuecat dashboard. But subscriptions worked very well.

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

It's worked!

I’ve just tried with my app created 3 days ago and finally got valid credentials. Also purchasing in sandbox using storekit2 is working fine today - yesterday I had some issues.

I first set the 'Country or Region Availability' section in the subscription packages to 'None' and saved it. Then, I edited it back to 'All' and saved it again. I did this for all subscription packages. After a short while, when I checked RevenueCat, the credentials showed up as valid. I had been waiting for them to become valid for about 4 days. This solved my issue. Maybe it was just a coincidence, I'm not sure, but you can give it a try.

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

I’m tired boss

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?

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,

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

​@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… 😮

any resolution here ? 

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..

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,

nope, I still have the issue.

Hello, has the problem been resolved?

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.

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?