It is breaking everything, the API has been completely rewritten you will need to redo all your IAP code. Even with a wrapper it is not something that can be done in few hours, especially since the example is overly complex and incomprehensible. Took me a while to filter out all the clutter.
hey @Laurie-Unity , we are also interested to know if you will have a patch version of Unity IAP 4 since 5.0.0 requires refactoring our current solution.
Even if you can not see it, you can add the preview version of the Unity IAP like this. Press the “+” icon on the top left corner and select Add package by name. The rest of it is here.
And as I told already last year, at the same time… As every year a new version is released.
There is a new billing Version 8.0.0. which just has released. It would be good that you would implement it earlier!!! Not just after 1 year. I have to update tons of apps and when you deliver your IAP so late it’s a mess!
Google Play Billing Library 8.0.0 Release (2025-06-30)
It did not work out of the box in my case. From what I’ve read, it should be fine if you’re using the codeless solution, but if it’s coded you may need to make some changes. In my case, it was as simple as changing the ConfigurationBuilder.Instance to new ConfigurationBuilder().
It has been stated that this workaround may not be available in future IAP versions, but it’s enough to get past the August 31 deadline.
Not sure if this has been mentioned before, but, you can extend this deadline via the Google Play Console until 1st November 2025. When asked for the reason, put ‘waiting for 3rd party SDK update’.
I’ve updated all versions on google play (internal test, closed test and production), but warning is still there. Maybe I have to wait? I explored aab file and billing.properties reports