@joan-cardona @Haley Pace @guilherme any insight here? It’s affecting multiple people. I submitted a support ticket but haven’t heard back.
After some more work I’ve been able to get it to change to this which is similar to the problem this user was having just 7 days ago.
T
@joan-cardona in that thread you said that it “it can take a bit of time to verify them which it seems what happened here.” but all of my other apps have been instant
@alejandra-wetsch anyone that can comment on this? I’m still blocked on this.
Hey @victor-07d2b0,
I'm sorry for the delay in responding. I’ll be happy to help here!
When you get the “The key is not valid or is not compatible with the bundle ID of your app” error, it could indicate that your In-App Purchase Key was generated under a different Apple account than the one where your app is located, or the Bundle ID entered in RevenueCat is not correct.
Please ensure that your app is under the same Organization/Account where your In-App Purchase API Key is generated and that the app Bundle ID in App Store Connect exactly matches the one entered in the Dashboard. Please check the following documentation to help you troubleshoot further.
You mentioned creating a support ticket; however, while searching our help desk tickets, I couldn’t find any open tickets created with the email associated with your community user’s email. Would you mind sharing which email was used to create the ticket so I can review it as well?
Best,
@alejandra-wetsch thanks for the response. This app is an app that was transferred to me. Is there a special process for these types? It is under the same organization. I just checked and it looks my support ticket might not have been correctly logged. I’ll recreate it.
I have the exact above problem as victor, and also waiting for support.
It would be great to have some instructions what to do after an app transfer. And if the problem with these certificates is that is always necessary to wait some time, then give some more info about it (but I’m pass 48 hours and no changes or support).
Hi all,
Can you try re-uploading the same key and see if that works? That will kick a new full check and we’ve seen it working for other customers.
Best,
It did not help, I also remove the app secret as you suggested, but that also did not help. The situation right now it is bunch of very angry users emailing me that they have bought the apps but do not get the product.
GPT5:
Yep—your Apple side is clean. The problem isn’t the keys; it’s the RevenueCat project binding.
You’re clearly on a legacy single-provider project. In those projects RC hard-binds the app to the old Apple provider/vendor. After a transfer, new keys from the new owner will never validate against that binding.
If you want the truly safe option: rip out RevenueCat and go pure StoreKit 2.
Now all my credentials are finally validated.
First, big thanks to Joan for the quick and accurate help!
I found the RevenueCat credentials page can be a bit tricky:
-
Changing your In-App Purchase key updates the Key Name but not the Issuer ID. Double-check the Issuer ID—each character matters as they can look very similar. Update it if necessary, then click Save Changes at the bottom.
-
Sometimes updating the key and having the correct Issuer ID isn’t enough. If you just change the key you might notice the Save Changes button stays disabled. If you reload the page sometimes the old key is still there.
My workaround:
-
Add a space to the Key Name → Save Changes
-
Remove the space → Save Changes again
-
Reload the page.
If the Issuer ID is correct, your keys should now validate.
-
Why this matters: If credentials aren’t valid, users can buy your app’s IAPs but never receive the products. This can quickly escalate into a serious problem, especially for apps using StoreKit 2 (iOS 15+).
Hopefully RC can fix this or at least add clear instructions for those transferring apps. 
