Upgraded com.unity.services.core from 1.3.1 to 1.5.2
Upgraded com.unity.services.analytics from 4.0.1 to 4.2.0.
I have some questions that might help us fix your bug :
Do you have some logs from Unity’s Cloud Diagnostics ?
Are you able to reproduce it locally ?
Does the exception make your app crash ?
I am using higher versions of the packages:
Core: 1.7.1
Analytics: 4.3.0
The Stack Trace field is emtpy in the Cloud Diagnostic, see the attached screenshot (disconnect2.png). I see some warning, but it is not related to this problem and you can see how far apart are the times.(disconnect3.png). Maybe the game sent to the background and some time later the billing library sends the disconnect event?
No, I am not able to reproduce it locally.
I don’t think it crashes the game, but I see some ANRs at Crashlytics related to purchasing.
I updated to Unity 2021.3.19f1, but I still get the message.
What is “No such proxy method” means?
Can I subscribe to the onBillingServiceDisconnected event somehow?
UPDATE: it seems like it’s causing crash sometimes.
Thank you for your feedback @domonyiv and @rvaleev .
4.6.0 sadly introduced a bug with onBillingServiceDisconnected(). Our signature didn’t match google’s which throws “No such proxy method” exceptions.
It will be fixed in our next release.
@Arnaud_Gorain@aVerrecchia We just released an update that includes 4.6.0, and we are seeing this exception a lot in production. I wonder if you could elaborate on the expected side effects? Will players notice the issue? Will purchasing be broken for them? Will there be app crashes (either user visible or ‘behind the scenes’ when the app is in the background)? What determines if players are affected or not (or is it all players?). We’re reluctant to release a hotfix update unless it’s necessary to, as the release we just pushed out was already a hotfix, and we don’t want to overwhelm players with updates. Thanks in advance,
Hi @AndyBlock ,
Unfortunately I would suggest to update to 4.7.0, I understand your view and is totally fair.
This impact only the android users, can cause crashes which could be noticeable.
Thus, this is called only when the connection to the billing system was lost. This does not prevent transactions to be successful, so it’s a specific scenario were a transaction would have failed.
unfortunately, this thread fixes another problem… and now I’m seeing this error:
No such proxy method: UnityEngine.Purchasing.SkuDetailsResponseListener.onSkuDetailsResponse(UnityEngine.AndroidJavaObject,null)
Hi, I got this on canceling the subscribe payment page.
Exception: No such proxy method: UnityEngine.Purchasing.GooglePurchaseUpdatedListener.onPurchasesUpdated(UnityEngine.AndroidJavaObject,null)