Ironsource via Admob Mediation Unity error

[Alex]

Hi,

I integrated Ironsource with the help of tutorial: https://developers.google.com/admob/unity/mediation/ironsource

Also I added ProGuard code, as noted in tutorial, from here: https://developers.ironsrc.com/ironsource-mobile/android/android-sdk/#step-5

Build goes fine, but after runnink the APK file I receive such error:

2021.04.27 20:22:01.668 29628 29628 Error Unity AndroidJavaException: java.lang.ClassNotFoundException: com.ironsource.mediationsdk.IronSource

2021.04.27 20:22:01.668 29628 29628 Error Unity java.lang.ClassNotFoundException: com.ironsource.mediationsdk.IronSource

2021.04.27 20:22:01.668 29628 29628 Error Unity at java.lang.Class.classForName(Native Method)

2021.04.27 20:22:01.668 29628 29628 Error Unity at java.lang.Class.forName(Class.java:454)

2021.04.27 20:22:01.668 29628 29628 Error Unity at com.unity3d.player.ReflectionHelper.nativeProxyInvoke(Native Method)

2021.04.27 20:22:01.668 29628 29628 Error Unity at com.unity3d.player.ReflectionHelper.a(Unknown Source:0)

2021.04.27 20:22:01.668 29628 29628 Error Unity at com.unity3d.player.ReflectionHelper$1.invoke(Unknown Source:31)

2021.04.27 20:22:01.668 29628 29628 Error Unity at java.lang.reflect.Proxy.invoke(Proxy.java:1006)

2021.04.27 20:22:01.668 29628 29628 Error Unity at $Proxy11.onInitializationComplete(Unknown Source)

2021.04.27 20:22:01.668 29628 29628 Error Unity at com.google.android.gms.internal.ads.yta$a.c(com.google.android.gms:play-services-ads-lite@@19.6.0:5)

2021.04.27 20:22:01.668 29628 29628 Error Unity at com.google.android.gms.internal.ads.Kd.a(com.google.android.gms:play-services-ads-lite@@19.6.0:6)

2021.04.27 20:22:01.668 29628 29628 Error Unity at com.google.android.gms.internal.ads.zja.onTransact(com.google.android.gms:play-services-ads-base@@19.6.0:3)

2021.04.27 20:22:01.668 29628 29628 Error Unity at android.os.Binder.transact(Binder.java:1079)

2021.04.27 20:22:01.668 29628 29628 Error Unity at gc.bb(:com.google.android.gms.policy_ads_fdr_dynamite@210890500@210890500057.3591690

What should I do to fix this?

P.S.:

Unity 2019.4.19f1
Admob SDK v5.4.0

GoogleMobileAdsFacebookMediation 3.2.0

GoogleMobileAdsUnityAdsMediation 2.6.0

GoogleMobileAdsAppLovinMediation 4.8.1

GoogleMobileAdsIronSourceMediation 2.0.3

[Mobile Ads SDK Forum Advisor Prod]

Hi Alex,

Thank you again for sending over this question. I know I have responded back to your other question in a previous thread. I will also respond here with basically the same thoughts. this is something that we are currently looking into and would suggest to check out these 2 sections of the documents I gave you from the other thread for Interstitial and Rewarded ads. At the moment it would appear to be an issue with the resolver pushing yoru Unity and AdMob to the v20 versions when your app still have earlier version methods in it that have been depreciated.

Regards,

William Pescherine Mobile Ads SDK Team

ref:_00D1U1174p._5004Q2GI1Cd:ref

[Alex]

Hi William,

The error is connected to some wrong setup. Maybe proguard config is wrong or smthg else. The error appears on startup. No placements are ready in that time.

As I used tutorial from the link, I think the tutorial or SDK should be fixed, not  Interstitial or Rewarded ads tutorials.

Still waiting for some answer on how to fix Ironsource SDK implementation.

среда, 28 апреля 2021 г. в 00:37:27 UTC+3, mobileadssdkforumadvisor:

[Mobile Ads SDK Forum Advisor Prod]

Hi Alex,

I work along with William. Allow me to assist you in this.

Is the build issue that you reported locally reproducible on your end? If so, could you please provide a test project replicating the issue via Reply privately to author option? If the option mentioned doesn't work, you may send the the requested information directly to mobileads...@gmail.com, then let us know in this thread once it has been sent.

Regards,

Teejay Wennie Pimentel Mobile Ads SDK Team

ref:_00D1U1174p._5004Q2GI1Cd:ref

[Alex]

Hi Teejay,

TestProject08956 sent to mobileads...@gmail.com

Regards,
Alex.

среда, 28 апреля 2021 г. в 08:12:25 UTC+3, mobileadssdkforumadvisor:

[Mobile Ads SDK Forum Advisor Prod]

Hi Alex,

I work with Teejay and William. Thank you for sending us your project. When attempting to compile it reached the dex limit. When raising the minimum SDK version to 21 it ran without the error and I received banners on the bottom. Is there any way to replicate what you saw?

Regards,

Aryeh Baker Mobile Ads SDK Team

ref:_00D1U1174p._5004Q2GI1Cd:ref

[Alex]

  Hi Aryeh,

Thank you for checking the test project.

I'm using Unity 2019.4.19f1. All other SDKs and libraries are included in my test project as well as all proguard and other files.

I tried to raise the minimum SDK version to 21 and the error was gone. I am not sure the problem is in the minimum API level, because I can't see any words about minimum API level in tutorial: https://developers.google.com/admob/unity/mediation/ironsource
No info in CHANGELOGS: 

https://github.com/googleads/googleads-mobile-android-mediation/blob/master/ThirdPartyAdapters/ironsource/CHANGELOG.md#version-70310

https://bintray.com/google/mobile-ads-adapters-unity/GoogleMobileAdsIronSourceMediation

Can you check somehow that the problem is in the supported API level? 

Does raising the API level give us the opportunity to use more headers(links) in the DEX file? Or does it remove some headers?

Regards,
Alex.

среда, 28 апреля 2021 г. в 22:49:56 UTC+3, mobileadssdkforumadvisor:

[Mobile Ads SDK Forum Advisor Prod]

Hi Alex,

Thank you for reaching out to us.

I work with Aryeh and will be assisting you. Upon building your sample project, I was able to get a prompt message "Missing Project ID. Because you are not a member of this project this build will not access Unity services". Then, when I tried to remove the project ID I got prompt message "Can not sign in the application. Unable to sign the application; please provide passwords!". With this, could you please provide us sample project that didn't needed any password? If you can replicate it in our sample project it will a big help to us to further investigate this. You can send it via Reply privately to author option or send it directly to mobileads...@gmail.com.

Regards,

Princess Pamela Pineda Mobile Ads SDK Team

 

ref:_00D1U1174p._5004Q2GI1Cd:ref

[Alex]

Hi guys,

"Can not sign in the application. Unable to sign the application; please provide passwords!" -

You can just uncheck "Custom keystore" flag in the Publishing Settings.

I found, that the first issue was with the old "Library" folder. In order to minimize test project size, I removed it. After raising minimum API level to 21, ironsource SDK works fine. W/o deleting "Library" folder it gives error.

But the issue with minimum API level is still there. Why it should be raised?

Btw. ironSource updated their SDK version and now every user should update it also. Check here: https://developers.ironsrc.com/ironsource-mobile/unity/unity-plugin/
There is no new mediation adapter for ironSource in Admob. It should be updated.

Regards,

Alex.

четверг, 29 апреля 2021 г. в 09:56:48 UTC+3, mobileadssdkforumadvisor:

[Mobile Ads SDK Forum Advisor Prod]

Hi Alex,

Thank you for the response back. We have been looking further into this issue for you. But have been unable to reproduce anything on our side. Also the we have tried to use the steps that you have mentioned but have run into DEX issues which have been blocking us from really being able to test this out. We are asking if you are able to try against one of our samples , as mentioned previously.

Also as for the need to raise the API level to 21? This would only seem to be due to the previously mentioned DEX issues. Which as we can see here , would make sense. As to why it is happening? I am thinking Unity might be forcing it up so as to be able to compile properly. The question I would have in general is, could it be possible that the adapter is looking for a higher version? Because of the fact that the stacktrace shows it is unable to find certain classes. With the fact that the newest plugin for Unity has not been released yet, could be causing a conflict? Just a general thought.

Regards,

William Pescherine Mobile Ads SDK Team

ref:_00D1U1174p._5004Q2GI1Cd:ref

[Alex]

Hi William,

Thank you for trying to run the project.

I will try to test these things out after releasing new Unity plugin and other ad networks plugins.

As for now I can see that I have many SDKs in my project so it can be the cause of DEX issues.

Regarding API level 21, there is post about multidex: https://developer.android.com/studio/build/multidex

I think I should check and enable multidex on previous API level.

Reagrds,

Alex.

четверг, 29 апреля 2021 г. в 23:06:00 UTC+3, mobileadssdkforumadvisor:

[Mobile Ads SDK Forum Advisor Prod]

HI Alex,

Thank you for the response back. Thinking if that issue can be resolved and with all the SDK's that you are using. There could also be something in any one of them that might be causing some conflict that either we do not know or could predict happening. As always we would suggest also trying one of our sample apps and seeing what happens as we know they work, and can help to narrow down possible causes.