Exception in AdMob interstial video ads

[XS]

Some interstitial video ads fails. The interstial ad is loaded and I can show it. On the video there is a spinner icon, waiting for the video to load.

After a few seconds the interstitial closes and this exception is in the Android Studio console.

E/ExoPlayerImplInternal: Source error.

    com.google.android.gms.ads.exoplayer3.source.ae: None of the available extractors (n, g) could read the stream.

        at com.google.android.gms.ads.exoplayer3.source.g.a(:com.google.android.gms.policy_ads_fdr_dynamite@21001004@21001004.272763194.272763194:6)

        at com.google.android.gms.ads.exoplayer3.upstream.n.run(:com.google.android.gms.policy_ads_fdr_dynamite@21001004@21001004.272763194.272763194:6)

        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:764)

The problem now is that the interstitial displayed doesn't count, so when I have frequency in AdMob set to 1 hour, it doesn't register and the user gets a new interstitial shortly after. This goes on and on to the users frustration.

The problem is seen on a Samsung Galaxy S8 with Android 9 installed.

[XS]

SDK used:

'com.google.firebase:firebase-core:17.2.1'
'com.google.firebase:firebase-ads:18.3.0'

[XS]

Example url of video manifest that causes the crash:

https://manifest.googlevideo.com/api/manifest/dash/expire/1578247876/ei/RLYRXvCOCsmVgQe7yJ6IBw/ip/85.184.184.237/id/e2061b4786684e2b/source/youtube/requiressl/yes/susc/gvp/acao/yes/playback_host/r2---sn-xoxgbphpqu-3g2s.googlevideo.com/mm/31/mn/sn-xoxgbphpqu-3g2s/ms/au/mv/m/mvi/1/pl/19/mt/1578218978/itag/0/sparams/expire,ei,ip,id,source,requiressl,susc,acao,itag/sig/ALgxI2wwRgIhAIdN68C8grMyuPM7GBINSEJ9ceD4e7u0FaVn2b-heHYnAiEAuMeyxBnvBJmQKSg49Pq0E17jAdAkLEisV5nskbYXtgA%3D/lsparams/playback_host,mm,mn,ms,mv,mvi,pl/lsig/AHylml4wRQIhAKpoD_rh7vnKWhOSyZ7oYUBYgbtKWxzpbqa_t25N2a68AiBqBss2MTIrBnjzthcWLSCmQsNgUr1GG8zJPdN-1jRk6w%3D%3D

It looks like the AdMob SDK 18.3.0 uses ExoPlayerLib 2.4.2

On Sunday, January 5, 2020 at 9:47:42 AM UTC+1, XS wrote:

[Mobile Ads SDK Forum Advisor Prod]

Hi there,

Thank you for reporting this.

For us to investigate the issue further? Could you please providing the following details via "Reply Privately to Author" option?

• Ad Unit ID
• Charles log (see instruction here) capturing the behavior

Regards,
Teejay Pimentel
Mobile Ads SDK Team

ref:_00D1U1174p._5001UOFtS0:ref

[Mobile Ads SDK Forum Advisor Prod]

Hi there,

Thank you for providing the details privately.

As per checking with the Charles log, it appears that the SSL Proxy was not turned on and thus, no traffic data was gathered (please see attached screenshot).
With this, could you please follow this guide specifically to number 4 instruction and provide to us again the Charles log? This would be a big help for us to investigate the issue further.