I’ve been digging into the plugin.google.iap.billing.v2 stuff for subscriptions and I think there’s something missing (or at least unclear) around how it handles Google Play subscriptions with base plans.
Right now, the docs for store.purchaseSubscription() just say you pass a productIdentifier. But with the current Google Play system, a subscription isn’t just one thing anymore, you’ve got the main subscription ID and then one or more base plans under it.
What’s not clear is: which ID is actually expected here? Is it the subscription ID, or a base plan ID? And if a subscription has multiple base plans (like monthly and yearly), how are we supposed to choose between them?
From what I understand of Google’s side, purchases are tied to an offer (via an offerToken), which is linked to a specific base plan. So just passing a productId doesn’t really cover that case.
At least from the plugin side, I don’t see any way to:
-
pick a specific base plan
-
handle multiple pricing options under one subscription
-
or pass anything like an offerToken
So it feels like either:
-
only the default base plan is being used implicitly, or
-
we’re expected to split everything into separate subscriptions instead of using base plans
Maybe I’m missing something, but if not, it seems like the plugin doesn’t fully support how subscriptions work now on Google Play.
Has anyone run into this or found a workaround?