I last updated my app on 03/03/21. I was using the same version of Unity Editor, Google Mobile Ads and Facebook Audience Network Adapter. There is no problem and works fine. But now, I did External Dependency Manager/Android Resolver/Force Resolver without changing anything in the project , It doesn't work anymore. Builds and the game runs smoothly. But it gives this error while creating the new interstitial ad.
"AndroidJavaException: java.lang.NoClassDefFoundError: Failed resolution of: Lcom/google/android/gms/ads/Interstitialad;"
I later realized, Works fine with Play-Services-19.7.0 version But It doesn't work Play-Services-20.0.0 version and gives an error. Play Services Resolver automatically integrates Play-Services-20.0.0 version. I can't no longer roll back to Play-Services-19.7.0.
Google Mobile Ads Unity plugin needs to be updated urgently. It should compatible with Play-Services-20.0.0 version.
Hi there,
Thank you for reaching out to us.
Were you able to upgrade to newer Unity version and still encountered error into your project? Also, can you try these steps in adding the sample app and got the Facebook adapter to work with Interstitial loading, showing and destroying without crashing? Let me know how it goes.
Regards,
|
||||||
Hi there,
Thank you for your response.
Could you please provide us the following details so that we can investigate this further? You can send it via Reply privately to author option or send it directly to mobileads...@gmail.com.
classpath 'com.android.tools.build:gradle:3.4.3'
After saving and force resolving the sample app ran fine.
Every other permutation of versions of Unity, mediation packages and our SDK may have other build problems. The simplest way to resolve these issues is to have a later Unity version.
Feel free to get back to us if this doesn't help for your use case.
Regards,
|
||||||
Hi All,
Thank you for providing us information about this concern.
I know how frustrating it can be and as much as we would want to assists you on this. I'm afraid we can't replicate this on our end to investigate. If you could please provide us any sample app with minimum modification that showing the error you encountered, it will help us to investigate this further.
Regards,
|
||||||
Hi Eray,
I hope you're doing well.
I just want to circle back on this. The team mentioned that this has been fixed. Please let me know if you still encounter the issue so I could raise this to the team once again.