Hi Søren,

disabling some (or all) products for a specific platform is included in the next major update, where these products are not handed over or fetched by Unity IAP to begin with.

It is ok to have all product identifiers in one build. Unity IAP will report back that it did not find some of the products, but that does not break any other functionality.

Do I need to add all the iOS IAP's (as dummies/standins) to Google Play ? or do I need to delete the iOS IAPS every time I build for Android ?

Depends on what you would like to do - you can have all identifiers in the IAP Settings editor as written above, but e.g. in separate groups. One for Android with all Android identifiers, one for iOS. If you let the ShopManager instantiate products in your shop automatically, you could destroy the container component for a platform in Awake.

So for example, when running on Android (#if UNITY_ANDROID) you could destroy the container component / game object for the iOS category in Awake. The ShopManager will not be able to instantiate shop items for that group later on.

As mentioned above, support without coding will be coming in the next update.

Currently Restore doesn't do anything on Android, but purchasing an IAP that have been made previously restores it.

Restore on Android is automatically invoked by Unity IAP, at the first app launch following an app uninstall and install. Triggering the restore process manually (I guess you are refering to the Restore button) does not have any effect indeed.

However when a purchase is made the UpdateFunds is never triggered, even when I use DBManager.increaseFunds in the IAPListener script.

Both methods invoke the DBManager.Save method, which fires the updatedDataEvent. Are you able to reproduce this in a separate project, after importing Simple IAP System? I'm pokering around in the dark on this as well.

Great, thanks for confirming.

1st time app run when verification was already ended (after 30 mins) shows next:
" The receipt for 'org.makaka.armasker.pro.subscription.monthly' could not be verified: []""

Yes: at this point, the product is set to purchased on the device, but the server tells it is not purchased / expired. The (debug) message indicates that it was now correctly set to not purchased on the device.

Thanks for the update, cross-linking release notes for completeness:

https://forum.unity.com/threads/unity-iap-store-package-2-2-7-and-core-package-2-2-2-are-now-available.415517/page-2#post-6789692

This callback is only used in the Oculus Store implementation. The deprecated method still works the same, there is no immediate update necessary.

@baron Awesome! Game is now updated with the latest Unity IAP.

Thank you once again Baron.

Hi there and welcome!

When navigating in the shop scene, product selections are saved in the DBManager under the hood. The DBManager offers a variety of methods for selections, which can be called outside the shop scene as well:

https://flobuk.com/docs/sis/DBManager.html

The IAPListener is not a good place to call these methods (I assume you tried using the "HandleSuccessfulPurchase" method), since this method is only called once, at the time of purchase.

In a real game scenario, you would call something like GetSelectedGroup("weapons") when loading the game scene to instantiate the correct weapon right at the start, then SetSelected("myOtherWeapon", true) when the player chooses to switch weapons.

@twolf said in ArgumentException: No binding for config type UnityEngine.Purchasing.IGooglePlayConfiguration:

@baron said in ArgumentException: No binding for config type UnityEngine.Purchasing.IGooglePlayConfiguration:

@twolf Hi,

I do not know what "a more modern version" should be, but the issue mentioned above was fixed a few versions ago. Make sure to update the Unity IAP package (Package Manager) and Unity IAP asset (services window) to the latest versions.

That would currently be package 2.2.1 and asset 2.2.5.

https://forum.unity.com/threads/unity-iap-store-package-2-2-5-and-core-package-2-2-1-are-now-available.415517/page-2#post-6629230

Thanks for the quick reply (amazing)...will work on the revised solution (See what happens).

As for the "A more modern..." agree don't know either just there is a button in the Unity IAP services section under the <reimport> button that offers an opportunity to migrate to it (whatever it is).

Smile...maybe 2.2.5 is the "modern" version of Unity IAP.

Thanks @Baron!

I applied the change and solved it.

Unfortunately your image link does not work.

Indeed, improving the events and callbacks is the top priority for the next update. In the IAPManager, there is a OnPurchaseFailed(Product, PurchaseFailureReason) callback, but the reason is passed to the IAPListener as a string. Since it is based on the following enum, you could already implement a switch case for the possible (string) values:

https://docs.unity3d.com/560/Documentation/ScriptReference/Purchasing.PurchaseFailureReason.html

The stores actually provide more store-specific failure codes, however Unity IAP does not implement them.