In the meantime, I managed to get it working by duplicating the purchasing package (4.9.3) and using it as a local package in which I modified GooglePurchaseUpdatedListener.cs from com.unity.purchasing@4.9.3/Runtime/Stores/Android/GooglePlay/AAR/Listeners and changed the onPurchasesUpdated method at line 53 from private to public, internal didn’t work .
BEFORE
//com.unity.purchasing@4.9.3/Runtime/Stores/Android/GooglePlay/AAR/Listeners/GooglePurchaseUpdatedListener.cs
[Preserve]
void onPurchasesUpdated(AndroidJavaObject billingResult, AndroidJavaObject javaPurchasesList)
{
IGoogleBillingResult result = new GoogleBillingResult(billingResult);
var purchases = m_PurchaseBuilder.BuildPurchases(javaPurchasesList.EnumerateAndWrap()).ToList();
OnPurchasesUpdated(result, purchases);
}
AFTER
//com.unity.purchasing@4.9.3/Runtime/Stores/Android/GooglePlay/AAR/Listeners/GooglePurchaseUpdatedListener.cs
[Preserve]
public void onPurchasesUpdated(AndroidJavaObject billingResult, AndroidJavaObject javaPurchasesList)
{
IGoogleBillingResult result = new GoogleBillingResult(billingResult);
var purchases = m_PurchaseBuilder.BuildPurchases(javaPurchasesList.EnumerateAndWrap()).ToList();
OnPurchasesUpdated(result, purchases);
}
@EinsofInnovecs I copied the folder from <PROJECT_FOLDER>/Library/PackageCache/com.unity.purchasing@4.9.3 to <PROJECT_FOLDER>/LocalPackages/com.unity.purchasing@4.9.3 (outside of the Assets folder) and modified the entry in <PROJECT_FOLDER>/Packages/manifest.json to use the local file path
It’s hard to understand for us how such a major error can make it’s way into a minor update used by Unity LTS.
Could you also investigate & improve your QA process for such updates?
Can you please post the link for the issue tracker here so we can follow it?
I’m trying your fix to move the package to the LocalPackages and I’ll update the build and soon I get some data I will post the results here… for now, Unity should update this as SOON AS POSSIBLE!!!
There is no issue tracker link, I think it’s only in their internal issue system.
I received a reply on Monday that they successfully reproduced the issue and it has been sent for resolution with their developer team so I guess a fix will be coming the in the following days/weeks, also I doubt that the fix for this issue will be other than mine.