Skip to main content

Google now uses the new Subscriptions API, I would like to know if this version is already supported or if it is still using the InAppProduct API

Maddie from RevenueCat answered this here:

 

If we make the subscription editable, will that break the “Backwards Compatible” badge?
 

Can someone from RevenueCat answer this very important question?

I made my subscription editable and it didn’t break the backward compatibility.

If we make the subscription editable, will that break the “Backwards Compatible” badge?
 

Can someone from RevenueCat answer this very important question?

Currently when looking at a migrated subscription I see the message:

“This subscription has been migrated from a legacy subscription and is read-only

You can make this subscription editable. This means that you will no longer be able to configure or update this subscription through the InAppProducts API.”
 
If we make the subscription editable, will that break the “Backwards Compatible” badge?

When it will support the new subscription features?

@Mauricio José de Lima,

RevenueCat doesn’t yet support the new subscription features announced at Google IO 22. That being said, they migrated existing subscriptions to the new system and we support the backwards compatible features as indicated in the Google Play Console.

Read more here: https://docs.revenuecat.com/docs/android-products

Community post here:

 

Reply


Terms & ConditionsCookie settings