We started to get this error since our last app update. In that update we upgrade the Unity IAP version. We now have some users, not all users who are getting the “FAILED: ProductUnavailable”. Our product has be in the store for over 5 years and our IAP code has not change. The only change we made regarding the IAP side was upgrading Unity IAP as we had issue with iOS staging that we believe in the end was Apple isssue as the upgrade did not help and the issue went away by itself. However since that release we have people sending report of not being able to purchase anymore. Any idea what can cause this and how we can fix this issue?
We are unable to reproduce ourselves, we have gather logs from the purchase failure, but so far we know about 5% of users are affected. We initialize fine. Here is a clip form one of our logs
[05/11/2021 19:10:29] [IAP] Start creating ITransactionProcessor in Release build
[05/11/2021 19:10:29] [IAP] create an UnityIAPProcessor
[05/11/2021 19:10:29] [IAP] Call UnityIAPProcessor.Initialize()
[05/11/2021 19:10:29] [IAP] Create a ConfigurationBuilder
[05/11/2021 19:10:29] [IAP] Add normal product IDs declared in Apple/Google Store
…
[05/11/2021 19:10:29] [IAP] Finish adding product
…
[IAP] Init purchase successfully
…
[05/11/2021 19:10:36] [IAP] Step 2. Contact to third party
[05/11/2021 19:10:36] [IAP] Purchase offer_0299 failed: ProductUnavailable
Step 1 and Step 2 is us calling Unity IAP. When we get a successful purchase we take the receipt and then do a server verification. This error we never get a success from Unity IAP.
This seems to be happening to only Google Play Users Android devices.
Since we have not experience this locally we do not have a debugger log.
These users had no issue making purchases before the update. We were only made aware recently when a user sent a zendesk asking for support.
We roll back to version Unity IAP we had before, which was 2.2.1 and the error has gone away for the user who were having issues. We got confirmation from a user via customer support. Do you know if you guys have identify the issues as while rolling back work for us now, we are getting a warning from google regarding Google Play Billing. Can we update this while using Unity IAP 2.2.1?
We can confirm that this was cause by Upgrading to Unity IAP 3.02 as for the 2 months using Unity IAP 3.02, we had a consistent 5-6% failure rate due to this error for user coming from Google. It has been two month after rolling back and there is no failure cause by the Error: ProductUnavailable.
FYI: With our “3.x” product we simplified to have one version, today. And with our 1.x and 2.x, we have two versions: one in the menus, and one in the Package Manager…which is complicated :(.
Sorry for some reason I am not getting mail notification when someone post in this thread. Any we are using 2.2.1 from the Asset Store. We switch to the Package Manager version 3.02 when we ran into the issue.
Edit. My engineers are saying our 2.2.1 is not from Asset store, but Package Manager.
Please provide specific steps to reproduce. Or perhaps you mistyped, are you not able to reproduce? One user just mentioned to check the Play Store version on the device, upgrade to the latest version.
@JeffDUnity3D we’re not able to reproduce this on our side. Users complaining are generally able to buy the product eventually (like on the 4th try, maybe after app restart). This error is Google Play only. On other platforms (Amazon, iOS) we have similar error with Unknown code, but I’m not sure it is the same case.
We on the other hand think it was the update regarding a fix they made in 2.3 and 3.01 from IAP error for unknown product. We will be trying version 2.2.2 in our next release to see if it still cover the google requirement, and continue to work for our customers.
I think this is something different, but you are welcome to test. If the user wasn’t logged into the Play Store on the device, they would receive NoProductsAvailable, an area you’ll want to test.
Is there anyway to download Unity IAP 2.2.2 from the asset store, we can only get 2.3 and someone here already confirm this bug happens using 2.3. We upgrade Unity IAP via Package Manager, but google is still flaging us with not using the correct billing system