Skip to main content
Question

Receiving ''Configuration error: Contact customer support''. Everytime i try to purchase my app's subscription using RevenueCat

  • October 12, 2025
  • 1 reply
  • 19 views

Forum|alt.badge.img+2

Hi

For the past weeks i have been having a serious with trying to purchase my app's subscription that i set with RevenueCat. I have followed all the documentation steps required to set up subscription in my app, but i still get get an error saying purchase failed due to configuration error and also saying i should contact customer support. My product ID from google play console is correct that i put in RevenueCat and everything in Google play console

The problem happens with my android app when i test it in internal testing using google play console. Please do note that it is an app i created using expo react-native.. I would really like help A.S.A.P.

This post has been closed for comments

1 reply

guilherme
RevenueCat Staff
Forum|alt.badge.img+6
  • RevenueCat Staff
  • October 16, 2025

Hey ​@fannie-mae,

I tested your configuration on our end and was able to successfully load the offerings, which means your RevenueCat setup and product IDs are correctly configured - this suggests the issue could be with the Google Play testing setup.

The "configuration error" during purchase typically occurs when the Google Play testing environment isn't fully configured. Based on your setup, here are the most common causes:

  • closed track setup required: Google Play internal testing alone isn't sufficient for testing purchases. You need to create a closed track release and have your testers join it. More importantly, testers must open the opt-in URL while signed into their test account - this marks their account for testing. See full setup instructions here
  • application ID mismatch: your test build's Application ID must exactly match the one in Google Play Console. Expo development builds sometimes use different bundle IDs, which will cause purchases to fail even though the products load correctly - this is especially common with Expo apps. More about Application ID requirements

Could you sanity check those and see if it helps? Also, adding a couple of blogpost that I think give helpful tips and context:

Best,