Trying to update an IAP price on Google Play Store and I'm locked from making any changes because I need to migrate to wards the OneTimeProduct REST API (away from the current InAppProduct resource).
Is there any plans to migrate to the new OneTimeProduct API so that we can migrate away from the old and be unblocked to manage our prices?
Best answer by matt-heaney
Hey there,
Thank you for your patience whilst I discussed this further with the engineering team.
Most importantly, it is confirmed that your products will remain fully functional as they are today after migrating. It is fully safe to migrate your products.
In terms of the backwards compatibility aspect, I need to apologise, as there was some confusion in my previous response. Whilst backwards compatibility is relevant here, this refers to backwards compatibility within the Google Play Console, not within the RevenueCat dashboard. I’m sorry for the confusion.
Products marked as “backwards compatible” within the Google Play Console work across all subscription versions.
As noted, the new features that become available after migration (the new one-time purchase products) are currently not supported by RevenueCat. If you set these up, it will not impact your existing products in RevenueCat, but they will not display in the app.
Again, I’m sorry for the confusion in my previous response.
However, to clarify, yes, it is safe to migrate your items. This will allow you to update your prices as intended.
I hope this helps.
If you have any additional questions, please let me know!
Thank you for your message. Matt from RevenueCat here!
This is actually something the team has been investigating recently, after Google introduced a new way to support one-time purchases using a new API.
Our current understanding is that this is a warning rather than a blocker. Since we already support both APIs, it should be fine to use either the inappproducts or oneTimeProducts endpoints, and you shouldn’t run into any issues making purchases. That said, we’d love to better understand why you’re seeing this and whether this is a newly introduced warning from Google or a case we haven’t yet considered.
Can you confirm if you’re seeing this error in Google Play Console when updating the price? If you’re able to share a screenshot, that would be really helpful. If the screenshot contains any sensitive data, please feel free to private message me, or open a support ticket and reference this post so we can investigate further.
Thank you for clarifying. I have spoken to the engineering team about this one.
Yes, I can confirm that to use these features in the Google Play Console, you will need to migrate within the Google Play Console. You can start this by tapping “review migration”.
Doing this would not have any impact on using RevenueCat. However, we currently do not support OTP offers with the dashboard and the SDK. As long as you work with backwards-compatible products in the dashboard, you will be fine to migrate to use these areas of the Google Play Console, and doing so is safe.
I hope this helps! If you have any additional questions regarding this, please let me know!
When you migrate, Google may give you access to some newer offer features for one-time purchases as part of the latest One Time Products updates. Some of these features are still very new and are not yet supported by RevenueCat.
However, regular one-time purchases themselves continue to work completely fine with RevenueCat. For any newer functionality we do not yet support, we have backwards compatibility systems in place, where supported versions can continue to be used to ensure there are no issues within your app or for your users.
You can confirm whether your product is backwards compatible directly in the RevenueCat dashboard. Navigate to your app's product details page, where there is a backwards compatibility flag synced from Google Play Console. If you want to trigger an immediate sync of this status, simply opening the product details page will do so.
I don’t see any backwards compatibility flags in the product page of RevenueCat… I went through the docs you sent but I just don’t see anything like it.
I only see these fields
When clicking on the “Review Migration” button in the Play Console I get this pop-up which is a bit scary.
Can you please confirm that everything will be fine? I have a lot of users using this IAP and use RevenueCat to check for the entitlements. If it were to stop working that would be catastrophic and I would lose the trust of all those users which have supported me.
Thank you for your patience whilst I discussed this further with the engineering team.
Most importantly, it is confirmed that your products will remain fully functional as they are today after migrating. It is fully safe to migrate your products.
In terms of the backwards compatibility aspect, I need to apologise, as there was some confusion in my previous response. Whilst backwards compatibility is relevant here, this refers to backwards compatibility within the Google Play Console, not within the RevenueCat dashboard. I’m sorry for the confusion.
Products marked as “backwards compatible” within the Google Play Console work across all subscription versions.
As noted, the new features that become available after migration (the new one-time purchase products) are currently not supported by RevenueCat. If you set these up, it will not impact your existing products in RevenueCat, but they will not display in the app.
Again, I’m sorry for the confusion in my previous response.
However, to clarify, yes, it is safe to migrate your items. This will allow you to update your prices as intended.
I hope this helps.
If you have any additional questions, please let me know!