Подскажите, пожалуйста, что это за ошибки, почему их так много(350 на 600-700 установок), и как с этим бороться. $Proxy7.OnProductsRetrieved $Proxy8.OnProductsRetrieved $Proxy9.OnProductsRetrieved $Proxy10.OnProductsRetrieved $Proxy9.onAdFailedToLoad UnityPlayer.nativeRestartActivityIndicator ViewGroup.dispatchApplyWindowInsets ReflectionHelper.nativeProxyFinalize $Proxy8.OnSetupFailed BaseDexClassLoader.findClass
Please provide exact steps to reproduce. I'm not sure what $Proxy8.OnSetupFailed is, it is not an IAP error.
I don't know what you mean. Error "$Proxy8.OnSetupFailed" was one time. I am very worried about errors "$Proxy7.OnProductsRetrieved" and "$Proxy9.onAdFailedToLoad". What you know about it?
Answer of Mobile Ads SDK Team https://groups.google.com/forum/#!topic/google-admob-ads-sdk/eFYMUMUbBvc Unity version: 2018.3.6f1 googleads-mobile-unity version - don't know how to see, but updating say that "Update complete" Callback setup: instance.rewardBasedVidenAdFailedToLoad += instance.HandleRewardBasedVideoFailedToLoad; callback body (very simple): public static bool bVideoLoading = false; public void HandleRewardBasedVideoFailedToLoad(object sender, AdFailedToLoadEventArgs args) { bVideoLoading = false; } result (hard to reproduce): java.lang.Error: FATAL EXCEPTION [Thread-45] Unity version : 2018.3.6f1 Device model : LGE LGMS550 Device fingerprint: MetroPCS/ph2n_mpcs_us/ph2n:7.0/NRD90U/180402143b640:user/release-keys Caused by at com.unity3d.player.ReflectionHelper.nativeProxyInvoke (Native Method) at com.unity3d.player.ReflectionHelper.a (Unknown Source) at com.unity3d.player.ReflectionHelper$1.invoke (Unknown Source) at java.lang.reflect.Proxy.invoke (Proxy.java:813) at $Proxy10.onAdFailedToLoad (Unknown Source) at com.google.unity.ads.RewardBasedVideo$1$1$2.run (RewardBasedVideo.java:89) at java.lang.Thread.run (Thread.java:761)
@kitoff, @mkudimov, @fiersking_unity There was an issue with Android java proxy in 2018.3: https://issuetracker.unity3d.com/is...java-proxy-while-the-app-is-in-the-background This bug was fixed in 2018.3.13: https://unity3d.com/unity/whats-new/2018.3.13