I know this is a common issue, but none of the advice I’ve found has helped. Perhaps I’m overlooking something.
During local development on a real device, everything works perfectly. However, as soon as I upload the build to TestFlight, I get the following error:
"There is an issue with your configuration. Check the underlying error for more details. There's a problem with your configuration. None of the products registered in the RevenueCat dashboard could be fetched from App Store Connect."
I am certain that the product exists on the RevenueCat dashboard. I am certain that the bundle identifier matches everywhere.
I do not use any store kit config file. The in-app purchase is in Ready to Submit status.
Could the issue be caused by the fact that this is a brand-new app that hasn’t been published in the App Store yet? Currently, my app is in Prepare for Submission status, the purchase is Ready to Submit, and none of the builds are detecting the purchase.
Best answer by matt-heaney
Hey @kostiantyn-f4ba41!
Matt from RevenueCat here! I’d love to help get this resolved.
I’ve taken a look at your RevenueCat account, and it looks like everything is set up correctly. As you mentioned, the item is currently in a “Ready to Submit” state, and it is correctly configured in your offering.
There are a few common reasons this issue can occur when using TestFlight. Could you please check the following:
Make sure the Paid Applications Agreement on your Apple Developer account is signed and up to date. Not signing the latest version is one of the most common causes of this issue.
Please check the availability of your subscription in App Store Connect, to make sure it is available in the region you are testing. You can do this by inspecting the subscriptions within your subscription groups.
To double-check everything is wired up correctly in your code, could you confirm that everything still works as expected when running locally on a device?
Let me know once you’ve checked these, and if the issue is still happening, we’ll dive deeper to get this sorted!
Matt from RevenueCat here! I’d love to help get this resolved.
I’ve taken a look at your RevenueCat account, and it looks like everything is set up correctly. As you mentioned, the item is currently in a “Ready to Submit” state, and it is correctly configured in your offering.
There are a few common reasons this issue can occur when using TestFlight. Could you please check the following:
Make sure the Paid Applications Agreement on your Apple Developer account is signed and up to date. Not signing the latest version is one of the most common causes of this issue.
Please check the availability of your subscription in App Store Connect, to make sure it is available in the region you are testing. You can do this by inspecting the subscriptions within your subscription groups.
To double-check everything is wired up correctly in your code, could you confirm that everything still works as expected when running locally on a device?
Let me know once you’ve checked these, and if the issue is still happening, we’ll dive deeper to get this sorted!
