Admob Native Advanced Video ads are not playing the video content

[jude....@greedygame.com]

Hey,

I am using the following placement id ca-app-pub-3940256099942544/1044960115  to test my native video ad implementation. I am upgrading my implementation to Admob SDK v20 using 'com.google.android.gms:play-services-ads:20.2.0'. 

The ad is getting loaded but the video is playing. The log shows an error from exo player.

2021-07-05 14:46:27.439 28102-28844/com.greedygame.app E/ExoPlayerImplInternal: Source error.

    com.google.android.gms.ads.exoplayer3.upstream.i: Unable to connect to 139

        at com.google.android.gms.ads.exoplayer3.upstream.h.a(:com.google.android.gms.policy_ads_fdr_dynamite@211512000@211512000057.367949677.367949677:19)

        at com.google.android.gms.ads.exoplayer3.upstream.n.run(:com.google.android.gms.policy_ads_fdr_dynamite@211512000@211512000057.367949677.367949677:4)

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)

        at java.lang.Thread.run(Thread.java:920)

     Caused by: java.net.MalformedURLException: no protocol: 139

        at java.net.URL.<init>(URL.java:601)

        at java.net.URL.<init>(URL.java:498)

        at java.net.URL.<init>(URL.java:447)

        at com.google.android.gms.ads.exoplayer3.upstream.h.a(:com.google.android.gms.policy_ads_fdr_dynamite@211512000@211512000057.367949677.367949677:2)

        at com.google.android.gms.ads.exoplayer3.upstream.n.run(:com.google.android.gms.policy_ads_fdr_dynamite@211512000@211512000057.367949677.367949677:4) 

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167) 

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641) 

        at java.lang.Thread.run(Thread.java:920) 

The log says that the video url is incorrect and doesn't have a valid protocol. Please check and let me know. 

[Mobile Ads SDK Forum Advisor]

Hello there,

Thank you for reaching out to us.

Could you please provide the following details via Reply privately to author option or send it directly to mobileads...@gmail.com? Kindly inform us on this thread if you sent it directly to the email provided.

• Sample app(if any)
• Steps to replicate the error

Regards,

Princess Pamela Pineda Mobile Ads SDK Team

ref:_00D1U1174p._5004Q2JYgJF:ref

[jude....@greedygame.com]

is there any update on this issue. 

[Mobile Ads SDK Forum Advisor]

Hi Jude,

It seems that you didn't receive our last response, so I'll be resending it again here.

I tried our sample app, and update it to latest version 20.2.0. As per checking, the native advanced video ads is displaying without any issue. With this, it would be greatly help if you could provide a sample app showing the issue that you reported. You may send it via Reply privately to author option or send it directly to mobileads...@gmail.com.

Regards,

Teejay Wennie Pimentel Mobile Ads SDK Team

ref:_00D1U1174p._5004Q2JYgJF:ref

[jude....@greedygame.com]

Hi,

I checked out the sample app you had given and it seems to be working fine. But please help me out with one question I have. I also have access to a native video test ad placement id from DFP. Without changing any of my code, the video ad from DFP is working perfect, but its only the AdMob placement id that doesn't work. Is there any difference between both in how the response is structured or how assets are delivered?

[Mobile Ads SDK Forum Advisor]

Hi Jude,

I work with Teejay and will assist you. I also tried replicating your error with the AdMob Native video test ad unit Id in our sample Native Advanced app with SDK 20.2.0 on an API 30 simulator with no luck.

There must be other steps to take to see this error. The best way to sort this out is to add to our sample apps the minimum it takes to replicate this error and send it privately to us. What would also be helpful would be to set up the sample app with Charles proxy and give us privately the log that occurs when you receive the error.

Regards,

Aryeh Baker Mobile Ads SDK Team

ref:_00D1U1174p._5004Q2JYgJF:ref