Mediation with Vungle interstitials not working

902 views
Skip to first unread message

Gabriel M. Popescu

unread,
Oct 9, 2017, 8:51:17 AM10/9/17
to Google Mobile Ads SDK Developers
Trying to implement Vungle mediation on Android but hit some issues.

My steps:

                - added Google Mobile Ads Unity Plugin v3.7.1

                - Added our app id and interstial ads id

                - added Vungle SDK 5.3.0 (2 jars in Assets\Plugins\Android\Vungle_lib | vunglePlugin.jar & vunglePub.jar)

                - added VungleAdapter 2.2.0 in Plugins\Android

               

I Get:

Could not request interstitial ad from adapter.

java.lang.NoClassDefFoundError: Failed resolution of: Lcom/vungle/mediation/VungleManager;

at com.vungle.mediation.VungleInterstitialAdapter.requestInterstitialAd(VungleInterstitialAdapter.java:68)

Caused by: java.lang.NoClassDefFoundError: Failed resolution of: Lcom/vungle/publisher/EventListener;

 

Tried adding EventListener from a different VunglePub.jar > vungle-publisher-adaptive-id-4.1.0 and got:

Could not request interstitial ad from adapter. java.lang.NoSuchMethodError: No virtual method init(Landroid/content/Context;Ljava/lang/String;)Z in class Lcom/vungle/publisher/VunglePub; or its super classes


Any ideas or links to implementing this Vungle mediation?


Thanks

Bharani Cherukuri (Mobile Ads SDK Team)

unread,
Oct 9, 2017, 3:04:32 PM10/9/17
to Google Mobile Ads SDK Developers
Hello, 

Thank you for contacting us. There might be an issue integrating the Vungle SDK and Adapter. You may refer to our Mediation guide which illustrates steps to include SDK and Adapter on Android. You may also refer to the Vungle integration guide where you can download the latest SDK and Adapter. Once you download the latest SDK and Adapter, you will have to add them to the Assets > Plugins > Android > GoogleMobileAdsPlugin > libs folder. Please refer to the additional steps mentioned here for implementing AdMob mediation with Vungle. Let me know if you run into any issues and I'll be happy to assist you further.

Regards,
Bharani Cherukuri
Mobile Ads SDK Team.

Gabriel M. Popescu

unread,
Oct 10, 2017, 6:44:55 AM10/10/17
to Google Mobile Ads SDK Developers
Hi Bharani,

Thanks for the quick response.

Moved the files VunglePub, VunglePlugin & VungleAdaptor to GoogleMobileAds/libs and double checked all the 5 steps in https://support.vungle.com/hc/en-us/articles/207604108

Result:
1) direct build&run from Unity > No fill for any networks (double checked the ad unit and Vungle is on top, all others disabled)
2) export gradle project -> build android studio > Same error as mentioned in prev post

Any ideas on what to try next?

Thanks

Bharani Cherukuri (Mobile Ads SDK Team)

unread,
Oct 10, 2017, 2:10:00 PM10/10/17
to Google Mobile Ads SDK Developers
Hello Gabriel, 

Thank you for the additional details. No fill error is usually experienced when there is no ad returned from the ad server. Can you provide us your Ad Unit ID, so I can take a look? Do look out for an email from us requesting your Ad Unit ID privately. 

Additionally, if you're implementing the Unity Mediation, you will be able to compile the project using the Unity Editor directly. 

Regards,
Bharani Cherukuri
Mobile Ads SDK Team

On Monday, October 9, 2017 at 8:51:17 AM UTC-4, Gabriel M. Popescu wrote:

Bharani Cherukuri (Mobile Ads SDK Team)

unread,
Oct 11, 2017, 2:58:18 PM10/11/17
to Google Mobile Ads SDK Developers
Hi Gabriel, 

Thank you for the details. You implementation looks fine and I was able to load ads without any issues with your sample app. It looks like you're trying to load the video interstitials, so there is ~1-2 second delay loading the video ad. All the callback events are called correctly. You can take a look at the attached screen recording and the logs for the sample app. Can you try loading the ads again and record the logs so I can take a look and assist you further?

Regards,
Bharani Cherukuri
Mobile Ads SDK Team

On Monday, October 9, 2017 at 8:51:17 AM UTC-4, Gabriel M. Popescu wrote:
Logs Sample app.rtf
SampleRecording.mp4

Bharani Cherukuri (Mobile Ads SDK Team)

unread,
Oct 27, 2017, 10:49:23 AM10/27/17
to Google Mobile Ads SDK Developers
Hi Gabriel, 

Thank you for your patience. Our team has resolved the issue and latest version of Unity plugin has been released to support the latest version of the Vungle SDK. Feel free to write back to us if you have any issue implementing Mediation with Vungle to load ads.

Regards,
Bharani Cherukuri
Mobile Ads SDK Team

On Monday, October 9, 2017 at 8:51:17 AM UTC-4, Gabriel M. Popescu wrote:

Axel

unread,
Nov 20, 2017, 10:43:05 PM11/20/17
to Google Mobile Ads SDK Developers
Hi Bharani,

I would like to know which version of Unity plugin is compatible with which version of Vungle SDK.

Regards,
Axel

Bharani Cherukuri (Mobile Ads SDK Team)

unread,
Nov 21, 2017, 10:25:30 AM11/21/17
to Google Mobile Ads SDK Developers
Hi Axel,

The current version of Unity v3.9.0 and v.3.8.0 are now compatible with the latest version of Vungle v5.3.0. If you're using previous versions of the Unity plugin, you will have to use an older version of the SDK, as the 5.x Vungle SDK requires placements, which was not supported by Admob's Unity plugin. Let me know if you have any other questions. 

Regards,
Bharani Cherukuri
Mobile Ads SDK Team

On Monday, October 9, 2017 at 8:51:17 AM UTC-4, Gabriel M. Popescu wrote:

Joe Man

unread,
Dec 18, 2017, 7:21:45 PM12/18/17
to Google Mobile Ads SDK Developers
Using version 3.10 of the plugin and Vungle 5.3 does not work on Android.  Unity version is 5.4.

All Vungle SDK files are in:
Assets/Plugins/Android/GoogleMobileAds/Lib
Vungle Adapter is in
Assets/Plugins/Android/
Manifest has been updated.

Also noticed precache error, not sure if it is related to Vungle.

12-18 19:20:32.860 20364 20364 W Ads     : Precache error
12-18 19:20:32.860 20364 20364 W Ads     : com.google.android.gms.ads.exoplayer3.source.s: None of the available extractors (n, d) could read the stream.
12-18 19:20:32.860 20364 20364 W Ads     : at com.google.android.gms.ads.exoplayer3.source.e.a(:com.google.android.gms.DynamiteModulesA@11951448:19)
12-18 19:20:32.860 20364 20364 W Ads     : at com.google.android.gms.ads.exoplayer3.upstream.m.a(:com.google.android.gms.DynamiteModulesA@11951448:11)
12-18 19:20:32.860 20364 20364 W Ads     : at com.google.android.gms.ads.exoplayer3.upstream.l.run(:com.google.android.gms.DynamiteModulesA@11951448:36)
12-18 19:20:32.860 20364 20364 W Ads     : at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133)
12-18 19:20:32.860 20364 20364 W Ads     : at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607)
12-18 19:20:32.860 20364 20364 W Ads     : at java.lang.Thread.run(Thread.java:762)
12-18 19:20:32.860 20364 20364 W Ads     : Precache error
12-18 19:20:32.860 20364 20364 W Ads     : com.google.android.gms.ads.exoplayer3.b
12-18 19:20:32.860 20364 20364 W Ads     : at com.google.android.gms.ads.exoplayer3.g.handleMessage(:com.google.android.gms.DynamiteModulesA@11951448:543)
12-18 19:20:32.860 20364 20364 W Ads     : at android.os.Handler.dispatchMessage(Handler.java:98)
12-18 19:20:32.860 20364 20364 W Ads     : at android.os.Looper.loop(Looper.java:154)
12-18 19:20:32.860 20364 20364 W Ads     : at android.os.HandlerThread.run(HandlerThread.java:61)
12-18 19:20:32.860 20364 20364 W Ads     : Caused by: com.google.android.gms.ads.exoplayer3.source.s: None of the available extractors (n, d) could read the stream.
12-18 19:20:32.860 20364 20364 W Ads     : at com.google.android.gms.ads.exoplayer3.source.e.a(:com.google.android.gms.DynamiteModulesA@11951448:19)
12-18 19:20:32.860 20364 20364 W Ads     : at com.google.android.gms.ads.exoplayer3.upstream.m.a(:com.google.android.gms.DynamiteModulesA@11951448:11)
12-18 19:20:32.860 20364 20364 W Ads     : at com.google.android.gms.ads.exoplayer3.upstream.l.run(:com.google.android.gms.DynamiteModulesA@11951448:36)
12-18 19:20:32.860 20364 20364 W Ads     : at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133)
12-18 19:20:32.860 20364 20364 W Ads     : at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607)
12-18 19:20:32.860 20364 20364 W Ads     : at java.lang.Thread.run(Thread.java:762)

Bharani Cherukuri (Mobile Ads SDK Team)

unread,
Dec 19, 2017, 12:51:35 PM12/19/17
to Google Mobile Ads SDK Developers
Hi Joe, 

Thank you for contacting us. Could you provide us a sample project of your implementation along with the detailed steps to reproduce the precache error, so I can take a look and assist you further? Please use Reply privately to author option to share the details. 

Joe Man

unread,
Dec 21, 2017, 1:58:46 PM12/21/17
to Google Mobile Ads SDK Developers
I am no longer seeing the precache error, I think it might be due to vungle not correctly being setup?

5.3 vungle requires a totally different setup which is different from the previous version.
This page found on vungle provides a working setup.
Reply all
Reply to author
Forward
0 new messages