I see an update was made from the AIDL to Billing v3. Seeing as I modified the sample code from the demo, is there anything in particular I need to be aware of when upgrading? My game is scheduled for release on December 18th, so I will probably release with IAP 2.1.1 as it’s getting a little late to be retesting / swapping a major component of the app at this stage. On a related note, any idea when the AIDL implementation will actually become obsolete?
I would have upgraded sooner, but it seemed like it was a pretty big change, and I’m waiting for people a little less further along in their games to use the latest IAP and find all the bugs for me (shoutout to the early adopters)
One change (more on the Google v3 side) is Restore Across Devices, be sure to test that scenario. Same user with two Android devices, and a purchase on one device should show up during Restore on the second device. Also, we still have testing to do on subscription upgrades/downgrades, if you are using that. To your point, 2.2.4 is looking more stable. I’m not sure when the AIDL implementation will become obsolete, that would be up to Google.
I’m not using any subscription stuff, just a single non-consumable purchase at the moment. I understand I can also query google explicitly to see if a user owns a non-consumable somehow now? I assume you aren’t doing that for us, and it’s something we have to call?
(shoutout to the early adopters)