Skip to main content
Question

Android app with different package ids for development and production not able to fetch products

  • December 23, 2022
  • 5 replies
  • 489 views

Forum|alt.badge.img+1

Hello everyone,

It’s a bit unclear if it’s possible to have a single Android app with 2 package ids (development and production), with 2 configured apps in the RevenueCat backoffice, and a single app in Google Play Console.

We are getting an error every time we try to get the products with our .dev suffixed app

"There's a problem with your configuration. None of the products registered in the RevenueCat dashboard could be fetched from the Play Store."

Is the only way around this to create a new app in Google Play Console with this .dev bundle?

It baffles us, because this works perfectly well with Google Billing Client, without the need of any additional app on the Google Play Console.

Thank you for your help!

This post has been closed for comments

5 replies

sharif
RevenueCat Staff
Forum|alt.badge.img+9
  • RevenueCat Staff
  • 513 replies
  • December 29, 2022

Hello,

"There's a problem with your configuration. None of the products registered in the RevenueCat dashboard could be fetched from the Play Store."

 

This error is caused by the communication between your device and Google Play. Essentially the device fetched the product identifiers from RevenueCat and tried getting the SkuDetails for them from Google, but they didn’t match.

Does the app without .dev (the production app) work with RevenueCat?

You can make multiple apps in the same RevenueCat project, each with a different package name. Then add a product for each app you add.


Forum|alt.badge.img+1
  • Author
  • New Member
  • 2 replies
  • December 30, 2022

Hello,

 

Yes, the app works perfectly without the .dev, communication is not the issue here.

Do we really need to create a new app with the .dev package Id in the Play Store Console?

sharif wrote:

Hello,

"There's a problem with your configuration. None of the products registered in the RevenueCat dashboard could be fetched from the Play Store."

 

This error is caused by the communication between your device and Google Play. Essentially the device fetched the product identifiers from RevenueCat and tried getting the SkuDetails for them from Google, but they didn’t match.

Does the app without .dev (the production app) work with RevenueCat?

You can make multiple apps in the same RevenueCat project, each with a different package name. Then add a product for each app you add.

 


MarcosC
RevenueCat Staff
Forum|alt.badge.img+7
  • RevenueCat Staff
  • 167 replies
  • May 30, 2023

Hi,

I know it’s an old thread, but you did not get an answer here

> Do we really need to create a new app with the .dev package Id in the Play Store Console?

Yes, you need to create a different app in google play console. When calling play store from the SDK, billing client uses the applicationId. On the backend we do the same. So if they are different, it won’t fetch any product on the SDK side and we’ll have issues on the backend side.

Having different packages for Dev and Prod means having two completely separate apps


Forum|alt.badge.img+6
  • Member
  • 6 replies
  • September 4, 2024

Hi @MarcosC, I also have same problem. How about RevenueCat ask for suffix that is used to create build variants/flavors and map to just root applicationId or bundle id? Any possibility to some how support this situation ?


sharif
RevenueCat Staff
Forum|alt.badge.img+9
  • RevenueCat Staff
  • 513 replies
  • September 11, 2024

Hi @Willow,

We could do that but that would be defeating the purpose of having a different package name for your dev app. Basically RevenueCat would drop the .dev part at the end of your package name and hit Google’s APIs for your production app (the package name without the .dev). Your app in Android Studio will also need to use the production package name because your app needs to communicate with Google directly as well, and they won’t recognize the .dev part of your package name. Really Google doesn’t support a “production” and “development” package name distinction, and that kind of limits what we (and you) can do here.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings