App crash on playing ad after few hours

[Raihan Abbas]

Hi IMA Team,

I am facing a crash in my app. Please have a look below.

 pid: 11034, tid: 12104, name: Chrome_InProcRe  >>> com.org.lpapp <<<

08-01 09:03:02.934 21300 21300 F DEBUG   : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xfbadbeef

08-01 09:03:02.934 21300 21300 F DEBUG   :     r0 c2a14520  r1 fffffffe  r2 00000000  r3 fbadbeef

08-01 09:03:02.934 21300 21300 F DEBUG   :     r4 d3142004  r5 d3117960  r6 d3142004  r7 c7c27f50

08-01 09:03:02.934 21300 21300 F DEBUG   :     r8 c2a14cd4  r9 c2a14ed8  sl d3142004  fp 00000001

08-01 09:03:02.934 21300 21300 F DEBUG   :     ip e6bac860  sp c2a145c0  lr d1cc65d3  pc d264c804  cpsr 40030030

I am playing Ad-Pods in my app and I have noticed that complete callback does not invoke and the next ad starts playback. After that IMA starts unusual behaviour and does not load any ad afterwards.

No matter how many times I request ads it will not play any ad. Please have a look at the pattern shown in the screenshot to better analyze the situation.

Additionally, the app was running absolutely alright for a long time and suddenly I am facing this without any change in my piece of code.

Can you tell me is there any API Service which IMA SDK is using for ad delivery?

Thanks

[IMA SDK]

Hi Raihan,

Thank you for reporting this crash situation to us. Were you able to reproduce the crash using one of our Android sample apps? Can you share the steps to reproduce the crash? Are you using the latest version of the SDK? If not, we would recommend you to upgrade to the latest version of the IMA SDK for Android.

Regards,
Arnaud Casame
IMA SDK Team

ref:_00D1U1174p._5001UEHUTN:ref

[Raihan Abbas]

Hi,

Thanks for asking. I am using Android SKD v3.11.2.

Please run the demo application uploaded here for more than 12 hours to reproduce the crash.

I will try to upload logcat as well for better analysis

Thanks

[Raihan Abbas]

Hi once again,

This is to let you know that I have reproduced this with android SDK v3.11.3 as well.

Below is the exception that I have faced in the demo app.

08-05 06:29:58.322 6758 6758 W System.err: java.lang.NullPointerException: Attempt to invoke interface method 'void com.google.ads.interactivemedia.v3.api.AdsManager.start()' on a null object reference 08-05 06:29:58.322 6758 6758 W System.err: at com.google.ads.interactivemedia.v3.samples.videoplayerapp.MyActivity$VideoFragment.onAdEvent(MyActivity.java:269) 08-05 06:29:58.322 6758 6758 W System.err: at com.google.ads.interactivemedia.v3.internal.acv.a(IMASDK:70) 08-05 06:29:58.322 6758 6758 W System.err: at com.google.ads.interactivemedia.v3.internal.acv.a(IMASDK:108) 08-05 06:29:58.322 6758 6758 W System.err: at com.google.ads.interactivemedia.v3.internal.acl.a(IMASDK:63) 08-05 06:29:58.322 6758 6758 W System.err: at com.google.ads.interactivemedia.v3.internal.aeb.e(IMASDK:168) 08-05 06:29:58.322 6758 6758 W System.err: at com.google.ads.interactivemedia.v3.internal.aeb.a(IMASDK:5) 08-05 06:29:58.322 6758 6758 W System.err: at com.google.ads.interactivemedia.v3.internal.adz.b(IMASDK:42) 08-05 06:29:58.323 6758 6758 W System.err: at com.google.ads.interactivemedia.v3.internal.aea.shouldOverrideUrlLoading(IMASDK:4) 08-05 06:29:58.323 6758 6758 W System.err: at android.webkit.WebViewClient.shouldOverrideUrlLoading(WebViewClient.java:73) 08-05 06:29:58.323 6758 6758 W System.err: at com.android.webview.chromium.WebViewContentsClientAdapter.shouldOverrideUrlLoading(WebViewContentsClientAdapter.java:339) 08-05 06:29:58.323 6758 6758 W System.err: at org.chromium.android_webview.AwContentsClient.shouldIgnoreNavigation(AwContentsClient.java:168) 08-05 06:29:58.323 6758 6758 W System.err: at org.chromium.android_webview.AwContentsClientBridge.shouldOverrideUrlLoading(AwContentsClientBridge.java:256) 08-05 06:29:58.323 6758 6758 W System.err: at org.chromium.base.SystemMessageHandler.nativeDoRunLoopOnce(Native Method) 08-05 06:29:58.323 6758 6758 W System.err: at org.chromium.base.SystemMessageHandler.handleMessage(SystemMessageHandler.java:39) 08-05 06:29:58.323 6758 6758 W System.err: at android.os.Handler.dispatchMessage(Handler.java:102) 08-05 06:29:58.323 6758 6758 W System.err: at android.os.Looper.loop(Looper.java:154) 08-05 06:29:58.323 6758 6758 W System.err: at android.app.ActivityThread.main(ActivityThread.java:6121) 08-05 06:29:58.323 6758 6758 W System.err: at java.lang.reflect.Method.invoke(Native Method) 08-05 06:29:58.323 6758 6758 W System.err: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:892) 08-05 06:29:58.323 6758 6758 W System.err: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:782) 08-05 06:29:58.326 6758 6758 F chromium: [FATAL:jni_android.cc(236)] Please include Java exception stack in crash report

The Demo app crashes in almost one hour.

Please let me know if could be of any assistance in this regard.

[IMA SDK]

Hi Raihan,

Thank you for providing additional insights with regards to the issue. Given the log you shared, it seems that at some point of your code, the AdsManager.start() is being called before AdsManager gets created/loaded. This should be solved if you add an if statement checking if the AdsManager is loaded before calling AdsManager.start().

[Raihan Abbas]

Hi there,

I have added the null check here and will share the details regarding that soon.

Secondly, I would like to share that the app was running absolutely fine before Tuesday, July 30th, 2019, 

Can you confirm that nothing has updated or changed within the last week in google APIs which may have some impact on the App?

Seeking your kind response
Thanks 

[IMA SDK]

Hi Raihan,

There was no changes in the IMA SDK for Android API that would cause your app to crash if it was previously running fine. Let us know the result once you finish testing your code.

[Raihan Abbas]

Hi,

This is to inform that I have reproduced the crash problem in Demo IMA project with latest v 3.11.3.

As per suggestion, I have added Null check before calling adsmanager.start() as well just like below

if (mAdsManager != null) {
    mAdsManager.start();
}

Please have a look at the attached logs herewith.