Hi Folks,
Looks like from 31st August 2024, apps must move to Google Play Billing Library V6; this can be extended in some cases to 1st November 2024.
Is there any way this can be supported with JUCE 7?
Best wishes, Pete
1 Like
Maybe there are few users of JUCE with Android?
Anyhow, FWIW I’ve dropped the JUCE implementation of Google Play Billing, and instead use my own custom implementation; mainly Java, some JNI, working with Google Play Billing Library V6.
NB: I’ve found that queryPurchasesAsync doesn’t work (!) … it only ever returns 0 rows for me; it has proven necessary for me to use queryPurchaseHistoryAsync instead (!)
Hoping that info helps somebody.
Best wishes, Pete
1 Like
+1 for keeping the Android Billing implementation in JUCE up to date.
5 Likes
Hi again folks,
By experimenting with the V7 library, I have found that the reason queryPurchasesAsync was returning zero rows, was that it returns purchases that are subscriptions or non-consumed items.
queryPurchaseHistoryAsync returns all “most recent” purchases for all items; irrespective of “consumption” status. However, from V7 onwards, queryPurchaseHistoryAsync is marked as deprecated! So from V8 onwards, we’ll be forced to use only queryPurchasesAsync.
Anyhow: the upshot is that depending on your non-subscription IAP item, you might not want to call consumePurchase; if you want it to show-up in subsequent calls to queryPurchasesAsync. That is important if you want an IAP item to show-up on IAP restoration on a different device with the same account, for example.
Hoping that helps somebody!
Best wishes, Pete
2 Likes
+1
+1
It is quite easy to create your own alternative interface with Java/Kotlin and a bit of JNI…
Similarly, my app’s Apple and Windows store interfaces (and Amazon store interface) are all my own platform-specific code.
Pete
+1
Somehow I forgot to update this thread, sorry about that.
JUCE’s develop branch has been updated to add support for v7 of the Google Play Billing library:
2 Likes