Skip to main content
Question

Issue with product identifiers in RevenueCat across different platforms.

  • March 25, 2025
  • 1 reply
  • 33 views

Forum|alt.badge.img

I am facing an issue with product identifiers in RevenueCat across different platforms.

In my app, I have the same product available on both the App Store and Google Play. While I have attached the same entitlement to both, the issue is that the identifiers are different, which is making it difficult to manage on both the backend and frontend.

  • On the App Store, the identifier is correct.

  • On Google Play, a base plan ID is automatically appended to the identifier.

  • Because of this, I need to handle different identifiers separately in my backend and frontend, which is causing complexity.

Since the entitlement is the same, purchases are working fine, but managing separate identifiers for the same product is not ideal.

Additionally, I have mapped all products to the offering for both App Store and Google Play in RevenueCat.

Could you suggest an efficient way to handle this issue?

1 reply

joan-cardona
RevenueCat Staff
Forum|alt.badge.img+6
  • RevenueCat Staff
  • 339 replies
  • March 27, 2025

Hi ​@thomason-varghese-9fa52c,

Why would you need to deal with the product identifiers in the backend and frontend?

The main idea is that you check the premium status through the active entitlements and you fetch directly the current offering or any specific offering by id. You shouldn’t need to deal with product identifiers in the app nor in the backend.

I’m interested in understanding your use case so I can propose you a more efficient solution.

Best,


Reply


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