Now, with the introduction of async init for google play, the divergence between the iOS and Google stores is growing. Can’t you make an identical change to iOS init method to return the same event name after initiation is concluded? If apple doesn’t provide such response you can emulate it just for compatibility sake. You already do something similar with apple unique store.canMakePurchases attribute (which is working also on android although not documented).
I can ask engineering to do this. We want consistency where possible in our APIs. However, that said, Apple requires store.restore() to be on a button in the UI. That leaves store.loadProducts() which can be deferred and doesn’t need to be called in main.lua.
Rob
Thanks, this seems like a reasonable approach as you already have default implementation for several other methods for Google/amazon plug-ins and event based triggering is the best way to move anyway. We have a restore button but we also check our local file and if corrupted somehow we invoke restore at launch as well.
I can ask engineering to do this. We want consistency where possible in our APIs. However, that said, Apple requires store.restore() to be on a button in the UI. That leaves store.loadProducts() which can be deferred and doesn’t need to be called in main.lua.
Rob
Thanks, this seems like a reasonable approach as you already have default implementation for several other methods for Google/amazon plug-ins and event based triggering is the best way to move anyway. We have a restore button but we also check our local file and if corrupted somehow we invoke restore at launch as well.