Unity IAP fix?

[cheesemaster]

Hi @JeffDUnity3D

After switching from Prime31 in-app-billing to Unity IAP (3.0.1) we noticed a drop in revenue of about 50%. This came with several complaints from users about being unable to make purchases, where pressing the “checkout” button fails to load the store.

The issue is very hard to reproduce locally yet seems to be well documented as a common problem affecting many Unity users in this thread:

Android users can’t make a purchase via Google Play

Hello, We have a very weird issue using Unity IAP with Google Play. [Unity Version: 2019.4.5f1] [Unity IAP Version: 2.2.7] All of our in-app products are active in Google Play Console, and we can “buy” them without any issues with our test users, but it seems like something is going wrong when it comes to the users on production. The app was already released to production few weeks ago, but it seems like all of our users are having issues with purchasing these products. As far as we und…

On the rare occasion we could reproduce it locally the adb log read as follows:

I notice the relevant thread was locked however after the Unity moderator said “we are looking into this”.

It would be great to know where to look exactly for developments on this issue as the thread is now locked. Has there already been an update to Unity IAP that should address this? If not, is this a confirmed Unity IAP issue that will be addressed soon?

Many thanks

[FLOBUK]

I do not think you will receive help for that version (3.0.1), since it is old (half a year) and got several critical bugs fixes since then. The latest version for 3.x is 3.2.3. I would not use something older than 3.2.x in production.

[cheesemaster]

Hi Baroni,

Thanks for this, it’s totally killing our app so I appreciate the help. I’m not sure if I am interpreting the version incorrectly or if I have somehow failed to install the latest version of IAP correctly. When I install IAP version 4.0.0 via the Package Manager it appears to be up-to-date in the Services Window:

Yet, when I run the app in the editor, and call the following line in a Start() function:

print("UnityEngine.Purchasing.StandardPurchasingModule.k_PackageVersion = "+UnityEngine.Purchasing.StandardPurchasingModule.k_PackageVersion);

The output is as follows:

I wonder if this is also the case for the rest of the people in the thread I linked and they are somehow misled into thinking they have a newer version than they do?

Many thanks

[JeffDUnity3D]

@cheesemaster

Hi Baroni,

Thanks for this, it’s totally killing our app so I appreciate the help. I’m not sure if I am interpreting the version incorrectly or if I have somehow failed to install the latest version of IAP correctly. When I install IAP version 4.0.0 via the Package Manager it appears to be up-to-date in the Services Window:

Yet, when I run the app in the editor, and call the following line in a Start() function:

print("UnityEngine.Purchasing.StandardPurchasingModule.k_PackageVersion = "+UnityEngine.Purchasing.StandardPurchasingModule.k_PackageVersion);

The output is as follows:

I wonder if this is also the case for the rest of the people in the thread I linked and they are somehow misled into thinking they have a newer version than they do?

Many thanks

You have IAP 4.0.0, the message is incorrect and we are working on it. The thread was close because it kept going off topic. One note, ensure you are not installing the Google plugin (don’t follow the directions here, it is outdated https://developer.android.com/google/play/billing/unity ). Please share your purchasing code (not a screenshot, please use an attachment)

[cheesemaster]

Hi @JeffDUnity3D

Thanks a lot for this and for the helpful clarification around the version. I only installed 4.0.0 today, so with some luck the issue may well be addressed in this version on which we are yet to reproduce it. Prior to this, and in our live/buggy build we were using version 3.0.1 if the adb logcat statement on app-open is reliable:

08-12 14:32:16.998 19161 19193 I Unity : UnityIAP Version: 3.0.1
08-12 14:32:16.998 19161 19193 I Unity : UnityEngine.Purchasing.StandardPurchasingModule:Instance(AppStore)
08-12 14:32:16.998 19161 19193 I Unity : CompleteProject.Purchaser:InitializePurchasing()

Do you know by any chance whether this was a confirmed IAP bug that got addressed in the last six months or so? It is reassuring that Baroni (above) seems to think that anything older than 3.2.x is unfit for production.

If we notice that it is still present in 4.0.0 (baring in mind the difficulties in reproducing), I’ll try to get you our purchasing code in case we have made some sort of implementation error as we’re a bit funny about posting code with various security checks in a public forum and don’t want to waste your time.

Cheers

[JeffDUnity3D]

@cheesemaster

Hi @JeffDUnity3D

Thanks a lot for this and for the helpful clarification around the version. I only installed 4.0.0 today, so with some luck the issue may well be addressed in this version on which we are yet to reproduce it. Prior to this, and in our live/buggy build we were using version 3.0.1 if the adb logcat statement on app-open is reliable:

08-12 14:32:16.998 19161 19193 I Unity : UnityIAP Version: 3.0.1
08-12 14:32:16.998 19161 19193 I Unity : UnityEngine.Purchasing.StandardPurchasingModule:Instance(AppStore)
08-12 14:32:16.998 19161 19193 I Unity : CompleteProject.Purchaser:InitializePurchasing()

Do you know by any chance whether this was a confirmed IAP bug that got addressed in the last six months or so? It is reassuring that Baroni (above) seems to think that anything older than 3.2.x is unfit for production.

If we notice that it is still present in 4.0.0 (baring in mind the difficulties in reproducing), I’ll try to get you our purchasing code in case we have made some sort of implementation error as we’re a bit funny about posting code with various security checks in a public forum and don’t want to waste your time.

Cheers

Please see if it reproduces for you with 4.0.0. We have many studios successfully using this version, so it may be something in your code. Feel free to send it to me via private message (just your purchasing script). One note, we’ve heard of issues with Codeless, ensure to be using Scripted IAP.

[Arslanmirza313]

i m facing one isssue and i have asked this issue from different developer but i didnt get the ans and i have seen the complete documentatiion of unity IAP of version 4.4.1 and i dont know about lower version about this issue. so the issue is when i ask for coins multiple quantity in single transection i got only 1time coins . means if i have 200 coins on Purchase and then i want to buy 200 * 4 in single transection i only got 200 coins only . i didnt got any variable where i got the quantity variable of product . so i m just stuck in this thing . can any one give the solution of this problem

[JeffDUnity3D]

@Arslanmirza313

i m facing one isssue and i have asked this issue from different developer but i didnt get the ans and i have seen the complete documentatiion of unity IAP of version 4.4.1 and i dont know about lower version about this issue. so the issue is when i ask for coins multiple quantity in single transection i got only 1time coins . means if i have 200 coins on Purchase and then i want to buy 200 * 4 in single transection i only got 200 coins only . i didnt got any variable where i got the quantity variable of product . so i m just stuck in this thing . can any one give the solution of this problem

We are working on supporting multiple product purchases in a single transaction, hopefully available later this year. For now, you would need to create a 800 coin product separately, in your example.