IAP restore issues (Android)

Okay, "short live the Bug!" then.

 

Jeff,
You're fixating on the word "restore."

True, we don't need to do a "restore" to the google store but we sure as heck need to be able to know if a "receipt" (m_StoreController.products.WithID(id).hasReceipt) exists for a given non-consumable.
(Mostly because we set a bool in OnInitialized() (or more accurately for me, 0.5 seconds AFTER OnInitialized()) that is used elsewhere in our apps that disables Ads, increases multipliers, adds time, or a host of other 'perks' that are granted when a user has purchased our apps.)

IAP does the automatic 'restore' great but SOMETHING is providing: "Already recorded transaction <TransactionID>" in the Debug.Log() (I thought it would be in ProcessPurchase, but I'm logging EVERYTHING in that function and NONE of my debug.logs are getting hit in ProcessPurchse or OnPurchaseFailed() during the "automatic restore"), and we really want/need to be able to set our bools based on this "SOMETHING...."

 

@JeffDUnity3D,

2.2.3 fixed the issue with timing of the restore of non-consumable purchases with the Google play store.

IDK what the bug number is but the solution is listed in the release notes:
- GooglePlay - `IStoreListener.OnInitialized` is now called after all purchases have been fetched from the store.

(Yes, I understand that the fetching occurs automatically with google but having OnInitialized returning before the fetch is completed is what caused @Funtyx's (and my) issue.)

Tested and verified on API 19, 21, & 27 devices

Thank you for fixing this one! <3

 

Hello,

Is it intended behaviour, that in 2.2.4 on every application focus lost and restore i see following in the log?

2020-12-16 20:58:46.004 4751-4813/? I/Unity: Already recorded transaction xxx
UnityEngine.Purchasing.PurchasingManagerrocessPurchaseIfNew(Product)

I tried to switch the screen off and back on, and every time new such line added.

BR, Alexey

 

Hi,
With 2.2.4 and 2.2.5 i have following behavior:

On application start my purchase is restored. When restoring, it is succesfully validated on our server, but after validation, when calling

Code (CSharp):

1. _storeController.ConfirmPendingPurchase(product)

it writes following:
"Unable to confirm purchase; Product has missing or empty transactionID"

It is the same product, which was succefully validated before.

Is it a bug, and is it dangerous?

BR, ALexey

 

Thanks.
But can you, please, describe the current state of issue, what exactly happens and how it can affect the flow? I need to decide, can i release the game with 2.2.5 or not.

 

And if i don't have consumables (and i don't) this issue is not affecting my users?

 

Is there any hope, that we will get 2.2.6 with this fix anytime soon?
It happened that this behaviour broke our game logic badly.

 

There needs to be an easier way for us to rollback to an earlier IAP version..

 

We have epic consequences for chosing to stay on 2.2.5
We just changed the code to compensate the bug, but after a week or so started to get mass refunds for purchases.
All these refunds are the same, happened exactly after 72 hours after purchase was made. User himself have no way to request refund after 48 hours, so it's Google doing. And after some seach we discovered, that Google refund purchases automatically if they not confirmed in 72 hours. So it was VERY bad decision to release the game with 2.2.5

 

Meantime, we will try to roll back to fix it fast, but how do we decide which version to chose? We need to roll back to some stable version without critical bugs.
Every version has description with issues fixed, but no one has description with issues broken. I wrote about it before, it's not a good behavior, cause users can still keep installing 2.2.5 without knowing about this epic bug.
And i read in 2.2.5 "- Fixed - GooglePlay - Fails to initialize when the player has made no purchases" - it's important fix, but where it was broken, in 2.2.4 or earlier?

 

Jeff?
Is there any chance we will get update in the 1-2 days? We are losing a lot of money every day on refunds.
If we have to wait more, i better roll back for now, but which version to chose for rolling back? It's hard to chose without knowing the bugs of each version.

As far as i can suppose:

2.2.5 - bug with refunds
2.2.4 - bug with initialization (?) It said in 2.2.5 "Fixed - GooglePlay - Fails to initialize when the player has made no purchases" I haven't seen this bug, and don't know, is it bug from 2.2.4 or from other vesrion.
2.2.3 - "ProcessPurchase called more than once for any purchase which is not consumed" (fixed in 2.2.4) - i believe it's not the same that in 2.2.5, cause as far as i remeber, it was only in purchase process, but purchases was confirmed succesfully, so we didn't get new ProcessPurchase every start (Correct me if i am wrong)
2.2.2 - initialization was finised before fetching all purchases.

So, maybe 2.2.3 is the best candidate to roll back, what do you think?

BR, Alexey

 

Yes.

 

Good day! Help please, we have already made a bunch of releases and our clients complain beforehand that they cannot restore their purchase using our "Restore" button. Below I attach the code that is activated when you click on the "Restore" button and there are events RestoreSuccess.Invoke (); and RestoreFail.Invoke (); which perform the actions we need to restore the purchase or give an error. When we click on the button, we freeze and do not get into more than one state not in RestoreSuccess.Invoke (); not RestoreFail.Invoke ();
Please help to restore the non-consumable purchase correctly.

Code (CSharp):

1. #if UNITY_PURCHASING || UNITY_UNIFIED_IAP
2. using UnityEngine.Events;
3. using UnityEngine.UI;
4. using System.IO;
5. using System.Collections.Generic;
6.  
7. namespace UnityEngine.Purchasing
8. {
9.     public class IapRestore : MonoBehaviour
10.     {
11.         public UnityEvent RestoreSuccess;
12.         public UnityEvent RestoreFail;
13.  
14.         public void RestorePurchase()
15.         {
16.             //Windows
17.             if (Application.platform == RuntimePlatform.WSAPlayerX86 ||
18.                 Application.platform == RuntimePlatform.WSAPlayerX64 ||
19.                 Application.platform == RuntimePlatform.WSAPlayerARM)
20.             {
21.                 CodelessIAPStoreListener.Instance.ExtensionProvider.GetExtension<IMicrosoftExtensions>()
22.                     .RestoreTransactions();
23.             }
24.  
25.             //Apple
26.             else if (Application.platform == RuntimePlatform.IPhonePlayer ||
27.                 Application.platform == RuntimePlatform.OSXPlayer ||
28.                 Application.platform == RuntimePlatform.tvOS)
29.             {
30.                 CodelessIAPStoreListener.Instance.ExtensionProvider.GetExtension<IAppleExtensions>()
31.                     .RestoreTransactions(OnTransactionsRestored);
32.             }
33.  
34.             //Android Samsung
35.             else if (Application.platform == RuntimePlatform.Android &&
36.                 StandardPurchasingModule.Instance().appStore == AppStore.SamsungApps)
37.             {
38.                 CodelessIAPStoreListener.Instance.ExtensionProvider.GetExtension<ISamsungAppsExtensions>()
39.                     .RestoreTransactions(OnTransactionsRestored);
40.             }
41.  
42.             //Android Google Play
43.             else if (Application.platform == RuntimePlatform.Android &&
44.                             StandardPurchasingModule.Instance().appStore == AppStore.GooglePlay)
45.             {
46.                 CodelessIAPStoreListener.Instance.ExtensionProvider.GetExtension<IGooglePlayStoreExtensions>()
47.                     .RestoreTransactions(OnTransactionsRestored);
48.             }
49.  
50.             else
51.             {
52.                 Debug.LogWarning(Application.platform.ToString() + " is not a supported platform for the Codeless IAP restore button");
53.             }
54.         }
55.  
56.         void OnTransactionsRestored(bool success)
57.         {
58.             if (success)
59.             {
60.                 if (CodelessIAPStoreListener.Instance.StoreController != null
61.                  && CodelessIAPStoreListener.Instance.StoreController.products.WithID("com.companyname.gmae.fullversion") != null
62.                  && CodelessIAPStoreListener.Instance.StoreController.products.WithID("com.companyname.game.fullversion").hasReceipt)
63.                 {
64.                     RestoreSuccess.Invoke();
65.                 }
66.             }
67.             else
68.             {
69.                 RestoreFail.Invoke();
70.             }
71.         }
72.     }
73. }
74. #endif

 

Actually i don't completely understand what's going on. Here is my whole story again.
I have a lot of refunds after releasing my game with iAP 2.2.5 to Google Play. All refunds are same, exactly 72 hours after purchase. Users have no way to do this, so it's auto-refunds by Google Play.

Here is what i found on the subject:
https://stackoverflow.com/questions/61303150/google-in-app-purchase-are-always-refunded
They say, that Google Play will refund purchases automatically, if they are not properly acknowledged within 72 hours.

But not all my purchases are refunded, only about 20-25% of them. This means, that some purchases got succesfully confirmed after purchase, and some didn't.

I didn't reproduced the whole thing on my device (didn't wait for 3 days). But when i buy something, i have no errors.
All purchase flow is working correctly. At first the code initialized purchase, then ProcessPurchase is fired. In ProcessPurchase we call server validation, and return PurchaseProcessingResult.Pending. Server validation returns correct result, and then we call _storeController.ConfirmPendingPurchase(product);
Confirmation brings no errors at this point, purchase finished, and content opened.

When i launch the game the next time, i have only this in log:

Code (CSharp):

1. 021-01-13 00:27:28.418 8278-8320/? I/Unity: Already recorded transaction ofcicjgfpfdbaieajdagmfed.AO-J1OyVvkjooRjEvS_vs2gjlyHN-M4HEHpyZUC3KSg0tJU8mNpwe3mtr4tOnKaFBCpV-UiLH8iJv9CfhYWMX5bSrHhdHj6Z9-R_RRhV0XYa_pRiu36n8Ns
2.     UnityEngine.Purchasing.PurchasingManager:ProcessPurchaseIfNew(Product)
3.     System.Action:Invoke()
4.     UnityEngine.Purchasing.Extension.UnityUtil:Update(

But ProcessPurchase is not called, whitch means purchase was confirmed succesfully.

Next, i remove the game from device and install it again. And that's there error begin to appear.
On the first start restoration is launched, and we get ProcessPurchase fired. It again sends data to server validation and got "OK" result, but when _storeController.ConfirmPendingPurchase(product) called after it, we get an error:
"Unable to confirm purchase; Product has missing or empty transactionID"
And after it we have it on every app launch. This code was working correctly in the old iAP (1.23.5), but now restoration process somehow reopens transaction and it can't be confirmed anymore.

But it looks like i miss something, cause i still don't understand where are refunds originated from, If where are no error in purchases itself, only in restoration. But they all are 72 hours from initial purchase, whitch means that transactions got broken upon purchases, not restorations.




Jeff, do you have thoughts on this?

BR. Alexey

 

I decided to switch from server validator lo local CrossPlatformValidator for the time being while waiting for the update, and not using pending transaction. This way it will work without rolling back to the old iAP.

 

@JeffDUnity3D Are there any updates on the issues with IAP?
We have issues since updating to 2.2.2 with the consumable product confirmation that seems to never happen. Thanks