(Android) Ad frequently just goes black. Logcat only says Invalid internal message, ignoring.Gives url as message

[Adam Tentis]

Hello,

I have been having ads not load and get stuck on black screen quite frequently lately. When looking at logcat all I see is the below message. 

W/IMASDK: Invalid internal message, ignoring. Please make sure the Google IMA SDK library is up to date. Message: gmsg://afma.google.com/activityMonitor?type=getPageSignals&sid=ea153f5a-3a12-4f27-b584-6bd0935d3f95&dt=1550454217832

Also, the onAdError method never hits and it looks like the application just gets stuck when requesting the ad.

I am not sure what the gmsg url is supposed to tell me so any help would be appreciated!

Thanks!

[ima-sdk-fo...@google.com]

Hi Adam,

Thanks for contacting us.

To assist you further, could you share the specific IMA SDK and Ad Tag that you were using?

You may also share to us the code snippets of the onAdError method so we can check as well.

Regards,

Janica Khemlani

IMA SDK Team

--
You received this message because you are subscribed to the Google Groups "Interactive Media Ads SDK" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ima-sdk+unsubscribe@googlegroups.com.
To post to this group, send email to ima...@googlegroups.com.
Visit this group at https://groups.google.com/group/ima-sdk.
For more options, visit https://groups.google.com/d/optout.

[Adam Tentis]

Hi Janica,

I was using IMA SDK 3.9.0 but upgraded to 3.10.6 and am having the issue with both. Most of my code is straight from the IMA SDK example app and this seems to be happen about 50% of the time.

My Ad Tag: https://pubads.g.doubleclick.net/gampad/ads?iu=/21773726333/ad_unit_code&description_url=https%3A%2F%2Fwww.marketcast.co&env=vp&impl=s&correlator=&tfcd=0&npa=0&gdfp_req=1&output=vast&sz=400x300|640x480&unviewed_position_start=1

The last line of code that runs that successfully runs is mAdsManager.init(...) and then the view just goes black until I press the back button.

mAdsLoader.addAdsLoadedListener(new AdsLoadedListener() {
    @Override
    public void onAdsManagerLoaded(AdsManagerLoadedEvent adsManagerLoadedEvent) {
        // Ads were successfully loaded, so get the AdsManager instance. AdsManager has
        // events for ad playback and errors.
        mAdsManager = adsManagerLoadedEvent.getAdsManager();

        // Attach event and error event listeners.
        mAdsManager.addAdErrorListener(VideoFragment.this);
        mAdsManager.addAdEventListener(VideoFragment.this);

        AdsRenderingSettings adsRenderingSettings = mSdkFactory.createAdsRenderingSettings();
        adsRenderingSettings.setFocusSkipButtonWhenAvailable(true);

        mAdsManager.init(adsRenderingSettings);
    }
});

onAdError does not hit

@Override
public void onAdError(AdErrorEvent adErrorEvent) {
    Log.e(LOGTAG, "Ad Error: " + adErrorEvent.getError().getMessage());
}

onAdEvent does not hit

@Override
public void onAdEvent(AdEvent adEvent) {

Thanks,

Adam

[ima-sdk-fo...@google.com]

Hi Adam,

Thank you for sending the additional details. My apologies as well for the back and forth, however, could you confirm if you tried the basic example sans your implementation and the issue still persists?

Additionally, could you send to me your sample app so I can also try and replicate this issue on my end?

Thanks and regards,

Peter Laurence N. Oliquino

IMA SDK Team

=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+ page:
    http://googleadsdeveloper.blogspot.com
    https://plus.google.com/115658573333388777174/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

[Adam Tentis]

Hi Peter,

No problem. I'm just glad I have you helping out with this. 

I tried the basic example with my ad tag and saw similar results. I tested on three different platforms with results below. I should note that my app is not on mobile which is why you only see OTT hardware and the sample ad has never shown the issue.

Nvidia Shield Android TV 2015 (Android 8.0)

Ad worked 3 times 

Failed 7 times

Amazon Fire TV 2nd gen (Android 5.1.1)

Ad worked 8 times 

Failed 2 times

Android Studio Android TV Emulator (Android 8.0)

Ad worked 10 times

Failed 0 times 

Here is the sample app using my ad tag.

https://drive.google.com/drive/folders/1aBfA7XkqGPo5MXE7NAMMM5NwTFky25I7?usp=sharing

Thanks!

Adam

[ima-sdk-fo...@google.com]

Hi Adam,

Thank you for providing more details. I have also used the basic example and I was able to replicate the issue. I'll have this issue checked also by the rest of the team and I'll update once I have more information.

Best regards,

Peter Laurence N. Oliquino
IMA SDK Team

=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+ page:
    http://googleadsdeveloper.blogspot.com
    https://plus.google.com/115658573333388777174/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

[Adam Tentis]

Hi Peter,

Glad you were able to reproduce the issue. Hopefully it is a quick fix since this is an issue in production. 

Thanks for your help.

Adam

[ima-sdk-fo...@google.com]

Hi Adam,

I'm Peter's colleague and I'll be assisting you on this.

Please note that the team is actively looking into this. We will get back to you for updates.

Regards,

Janica Khemlani

IMA SDK Team

[Westin music]

Hi,
    I Have same issue. I before it worked fine. Last two days onwards not working. I don't know what is bug. I'm using exoplayer with ima extesion 2.9.5.

   W/IMASDK: Invalid internal message, ignoring. Please make sure the Google IMA SDK library is up to date. Message: gmsg://afma.google.com/activityMonitor?type=getPageSignals&sid=2cba1013-aa86-470b-ade7-e6e8fa67f3fa&dt=1550750281187
 
   I also got same msg. Can you guide me.

[Ram Kumar]

Users Get blocked

In iOS, 

Ads Loader delegate called successfully,(- (void)adsLoader:(IMAAdsLoader *)loader adsLoadedWithData:(IMAAdsLoadedData *)adsLoadedData)

But we didn't get ADLoaded event in below specified delegate method

- (void)adsManager:(IMAAdsManager *)adsManager didReceiveAdEvent:(IMAAdEvent *)event

also this failiure function is not called

- (void)adsLoader:(IMAAdsLoader *)loader failedWithErrorData:(IMAAdLoadingErrorData *)adErrorData 

Now it blocks our users in production, Fix this ASAP it is the major issue, We didn't face this kind of issues from Google. It's Very bad. Please fix it soon, We can't able to accept this kind of issues. We think many developers and users affected by this issue.

Also, We use the IMA SDK iOS sample Applications with our video tag URL is not working !!! 

So a quick fix would be appreciated! 

[ima-sdk-fo...@google.com]

Hi there,

Thanks for reaching out to us.

To help us investigate further, could you confirm the specific IMA SDK (HTML5, Android, iOS) and share the Ad Tag that you were using?

Also, are you using the latest version of the SDK? If you are able to reproduce the issue on your end, could you also share the steps so we can check on our end?

Regards,

Janica Khemlani

IMA SDK Team 

On 02/21/19 21:11:17 johnsakt...@gmail.com wrote:

Hi,
    I Have same issue. I before it worked fine. Last two days onwards not working. I don't know what is bug. I'm using exoplayer with ima extension 2.9.5.

   W/IMASDK: Invalid internal message, ignoring. Please make sure the Google IMA SDK library is up to date. Message: gmsg://afma.google.com/activityMonitor?type=getPageSignals&sid=2cba1013-aa86-470b-ade7-e6e8fa67f3fa&dt=1550750281187
 
   I also got same msg. Can you guide me.

On Monday, February 18, 2019 at 7:33:10 AM UTC+5:30, Adam Tentis wrote:

Hello,

I have been having ads not load and get stuck on black screen quite frequently lately. When looking at logcat all I see is the below message. 

W/IMASDK: Invalid internal message, ignoring. Please make sure the Google IMA SDK library is up to date. Message: gmsg://afma.google.com/activityMonitor?type=getPageSignals&sid=ea153f5a-3a12-4f27-b584-6bd0935d3f95&dt=1550454217832

Also, the onAdError method never hits and it looks like the application just gets stuck when requesting the ad.

I am not sure what the gmsg url is supposed to tell me so any help would be appreciated!

Thanks!

[ima-sdk-fo...@google.com]

Hi there,

We understand your concern.

Could you confirm if you are currently using the latest version of the IMA SDK for iOS? 

You may also share to us the Ad Tag that you were using, logs that you captured with error details and steps to reproduce the issue so we can check on our end.

Regards,

Janica Khemlani

IMA SDK Team

On 02/21/19 21:38:55 ram.ra...@gmail.com wrote:

Users Get blocked

In iOS, 

Ads Loader delegate called successfully,(- (void)adsLoader:(IMAAdsLoader *)loader adsLoadedWithData:(IMAAdsLoadedData *)adsLoadedData)

But we didn't get ADLoaded event in below specified delegate method

- (void)adsManager:(IMAAdsManager *)adsManager didReceiveAdEvent:(IMAAdEvent *)event

also this failure function is not called

[Adam Tentis]

HI Janica, 

Any updates on this? This is causing my stream to fail in production so I will have to take out use of IMA SDK if this is not resolved soon. 

Thanks,

Adam

[ima-sdk-fo...@google.com]

Hi Adam,

We understand your concern. However, we do not have any updates as of the moment. 

I'll send another follow up with the team and let you know.

Also, I would suggest reaching out to your serving provider for help configuring your ad serving as this may help as well.

Regards,

Janica Khemlani

IMA SDK Team

[ima-sdk-fo...@google.com]

Hi Adam,

Could you provide another ad tag that reliably reproduces the issue on your end? 

As per checking, the ad tag you shared is returning an empty VAST response (AdError 1009) when tested against our Video Inspector Tool.

Regards,

Janica Khemlani

IMA SDK Team

[Adam Tentis]

HI Janica, 

I already submitted a sample app to Peter and he confirmed he was able to reproduce the issue using my sample app. You will also see the document is not empty when using it in app. The ad tag will return an empty response unless it is used in app so you will always get an empty response document in the inspector. I have been told this is normal behavior from my provider. 

Below I have another ad tag from a completely separate provider that has sometimes exhibited the same black screen with no onAdResult or onAdError response. Sometimes the ads play fine. I have not done any formal testing on devices like I did for Peter with the other tag above though. Keep in mind this is random and does not happen every time. 

https://pubads.g.doubleclick.net/gampad/ads?iu=/21773726333/ad_unit_yp1&description_url=https%3A%2F%2Fwww.marketcast.co&env=vp&impl=s&correlator=&tfcd=0&npa=0&gdfp_req=1&output=vast&sz=400x300|640x480&unviewed_position_start=1

Thanks,

Adam

[Sakthivel Appavu]

Hello IMA FORUMADVISOR and Adam Tentis,
 
     We are having the same issue both in IOS and ANDROID what he(Adam Tentis) has been faced. OnAdMamagerLoaded every timer but after that no response called either onAdEvent nor onAdError. In Sample VideoPlayerController.java class also getting same response. we already send AdTagUrl through mail content. Please find your bug and quick fix. I request, from your each response is high value to us. We expect from your quick response or any other chat forum is there?. Highly recommended to fix this issues.

Hereby I have attach Android Advanced Sample project's screen shot For Your Reference.

Thanks,
Sakthi

    

On Monday, February 18, 2019 at 7:33:10 AM UTC+5:30, Adam Tentis wrote:

[ima-sdk-fo...@google.com]

Hi Sakthi,

Thanks for reaching out to us and for providing details.

Could you share the Ad Tag that you were using that reliably reproduces the issue on your end?

If available, you can also share the sample of your implementation both for iOS and Android so we can test as well.

Regards,

Janica Khemlani

IMA SDK Team

[Sakthivel Appavu]

Hi Janica Khemlani,
    
     Okay, we already shared all the details through email. Once I'll discuss with TL after that sharing the details.
 
     What are the failure cases occur?.

     Can you share, possibilities of all failure cases?

     What are the concern needed to providing Advertisement?

 Thanks,
 Sakthi   

[ima-sdk-fo...@google.com]

Hi Sakthi,

Apologies for the confusion.

I noticed that you already have an existing thread with regards to this issue.

For better tracking, please continue your discussion with my colleague.

Regards,

Janica Khemlani

IMA SDK Team

[Adam Tentis]

Hi Janica,

The Nexus Player is EOL and no longer sold. 

I have experienced this on the Amazon Fire TV, The Nvidia Shield Android TV and now I have even reproduced it on Google's own ADT-2 official Android TV developer device.

https://developer.android.com/tv/adt-2

As requested I tested for this issue on a different network and I was successfully able to reproduce the issue.

I understand this has been hard for you to reproduce on your end because it doesn't even happen consistently on my end. However, it is enough to be a large concern. 

I don't think this is an isolated case since you have reports of it from other users here and even on IOS:

https://groups.google.com/forum/#!topic/ima-sdk/rRAEtBZAGz4

https://groups.google.com/forum/#!topic/ima-sdk/_h74a6IDgaM

Thanks,

Adam

On Thu, Feb 28, 2019 at 1:09 AM <ima-sdk-fo...@google.com> wrote:

Hi Adam,

I did another round of testing with your sample app (the one you shared via google drive) using our Android Nexus device, this time the ad plays continuously and when the skip button is clicked, the black screen appears (see attached for the video recording).

It's possible that this may specific to your device or network. Can you please try another network and see if you have similar results? 

I'm going to share this with the rest of our team to investigate further. I will follow-up on this thread as soon as I have an update. 

Please keep in mind, that with the low reproducibility rate that I've seen, this may be difficult for us to diagnose. 

[ima-sdk-fo...@google.com]

Hi Adam,

Thanks for the additional details.

Please note that the team is actively looking into this. 

I'll send another follow up and let you know once I get an update.

Regards,

Janica Khemlani

IMA SDK Team

On 03/04/19 00:33:51 ada...@gmail.com wrote:

Hi Janica,

The Nexus Player is EOL and no longer sold. 

I have experienced this on the Amazon Fire TV, The Nvidia Shield Android TV and now I have even reproduced it on Google's own ADT-2 official Android TV developer device.

https://developer.android.com/tv/adt-2

As requested I tested for this issue on a different network and I was successfully able to reproduce the issue.

I understand this has been hard for you to reproduce on your end because it doesn't even happen consistently on my end. However, it is enough to be a large concern. 

I don't think this is an isolated case since you have reports of it from other users here and even on IOS:

https://groups.google.com/forum/#!topic/ima-sdk/rRAEtBZAGz4

https://groups.google.com/forum/#!topic/ima-sdk/_h74a6IDgaM

Thanks,

Adam

On Thu, Feb 28, 2019 at 1:09 AM <ima-sdk-forumadvisor@google.com> wrote:

Hi Adam,

I did another round of testing with your sample app (the one you shared via google drive) using our Android Nexus device, this time the ad plays continuously and when the skip button is clicked, the black screen appears (see attached for the video recording).

It's possible that this may specific to your device or network. Can you please try another network and see if you have similar results? 

I'm going to share this with the rest of our team to investigate further. I will follow-up on this thread as soon as I have an update. 

Please keep in mind, that with the low reproducibility rate that I've seen, this may be difficult for us to diagnose. 

Regards,

Janica Khemlani

IMA SDK Team

--

[Adam Tentis]

Hi Janica,

I just wanted to share more info with you. Even though I was not able to reproduce the issue before using the emulator I am now able to. Please share these videos to the team of the ad working and failing with the emulator.

Video of ad working: https://photos.app.goo.gl/i4rCW9vr8w4cVdph7

Video of ad failing: https://photos.app.goo.gl/nrs3vuUX6H1RW4Co8

Tag used: https://pubads.g.doubleclick.net/gampad/ads?iu=/21773726333/ad_unit_yp1&description_url=https%3A%2F%2Fwww.marketcast.co&env=vp&impl=s&correlator=&tfcd=0&npa=0&gdfp_req=1&output=vast&sz=400x300|640x480&unviewed_position_start=1

Logs from ad failing video:

2019-03-07 19:18:36.384 11924-11924/? I/zygote: Not late-enabling -Xcheck:jni (already on)

2019-03-07 19:18:36.404 11924-11924/? W/zygote: Unexpected CPU variant for X86 using defaults: x86

2019-03-07 19:18:36.490 11924-11924/com.google.ads.interactivemedia.v3.samples.videoplayerapp W/ActivityThread: Application com.google.ads.interactivemedia.v3.samples.videoplayerapp is waiting for the debugger on port 8100...

2019-03-07 19:18:36.497 11924-11924/com.google.ads.interactivemedia.v3.samples.videoplayerapp I/System.out: Sending WAIT chunk

2019-03-07 19:18:37.369 11924-11931/com.google.ads.interactivemedia.v3.samples.videoplayerapp I/zygote: Debugger is active

2019-03-07 19:18:37.504 11924-11924/com.google.ads.interactivemedia.v3.samples.videoplayerapp I/System.out: Debugger has connected

2019-03-07 19:18:37.504 11924-11924/com.google.ads.interactivemedia.v3.samples.videoplayerapp I/System.out: waiting for debugger to settle...

2019-03-07 19:18:37.706 11924-11924/com.google.ads.interactivemedia.v3.samples.videoplayerapp I/System.out: waiting for debugger to settle...

2019-03-07 19:18:37.908 11924-11924/com.google.ads.interactivemedia.v3.samples.videoplayerapp I/System.out: waiting for debugger to settle...

2019-03-07 19:18:38.515 11924-11924/com.google.ads.interactivemedia.v3.samples.videoplayerapp I/chatty: uid=10049(u0_a49) com.google.ads.interactivemedia.v3.samples.videoplayerapp identical 3 lines

2019-03-07 19:18:38.716 11924-11924/com.google.ads.interactivemedia.v3.samples.videoplayerapp I/System.out: waiting for debugger to settle...

2019-03-07 19:18:38.917 11924-11924/com.google.ads.interactivemedia.v3.samples.videoplayerapp I/System.out: debugger has settled (1485)

2019-03-07 19:18:39.229 11924-11924/com.google.ads.interactivemedia.v3.samples.videoplayerapp I/WebViewFactory: Loading com.google.android.webview version 58.0.3029.125 (code 303012510)

2019-03-07 19:18:39.277 11924-11924/com.google.ads.interactivemedia.v3.samples.videoplayerapp I/cr_LibraryLoader: Time to load native libraries: 22 ms (timestamps 553-575)

2019-03-07 19:18:39.307 11924-11924/com.google.ads.interactivemedia.v3.samples.videoplayerapp I/chromium: [INFO:library_loader_hooks.cc(140)] Chromium logging enabled: level = 0, default verbosity = 0

2019-03-07 19:18:39.308 11924-11924/com.google.ads.interactivemedia.v3.samples.videoplayerapp I/cr_LibraryLoader: Expected native library version number "58.0.3029.125", actual native library version number "58.0.3029.125"

2019-03-07 19:18:39.331 11924-11951/com.google.ads.interactivemedia.v3.samples.videoplayerapp W/cr_ChildProcLauncher: Create a new ChildConnectionAllocator with package name = com.google.android.webview, inSandbox = true

2019-03-07 19:18:39.336 11924-11924/com.google.ads.interactivemedia.v3.samples.videoplayerapp I/cr_BrowserStartup: Initializing chromium process, singleProcess=false

2019-03-07 19:18:39.383 11924-11924/com.google.ads.interactivemedia.v3.samples.videoplayerapp D/EGL_emulation: eglCreateContext: 0xa6278ae0: maj 3 min 1 rcv 4

2019-03-07 19:18:39.407 11924-11924/com.google.ads.interactivemedia.v3.samples.videoplayerapp D/EGL_emulation: eglMakeCurrent: 0xa6278ae0: ver 3 1 (tinfo 0x9a4c9310)

2019-03-07 19:18:39.410 11924-11924/com.google.ads.interactivemedia.v3.samples.videoplayerapp E/eglCodecCommon: glUtilsParamSize: unknow param 0x000082da

2019-03-07 19:18:39.410 11924-11924/com.google.ads.interactivemedia.v3.samples.videoplayerapp E/eglCodecCommon: glUtilsParamSize: unknow param 0x000082da

2019-03-07 19:18:39.552 11924-11980/com.google.ads.interactivemedia.v3.samples.videoplayerapp W/cr_media: Requires BLUETOOTH permission

2019-03-07 19:18:39.619 11924-11988/com.google.ads.interactivemedia.v3.samples.videoplayerapp D/OpenGLRenderer: HWUI GL Pipeline

2019-03-07 19:18:39.629 11924-11976/com.google.ads.interactivemedia.v3.samples.videoplayerapp I/cr_LibraryLoader: Using linker: org.chromium.base.library_loader.ModernLinker

2019-03-07 19:18:39.675 11924-11988/com.google.ads.interactivemedia.v3.samples.videoplayerapp I/OpenGLRenderer: Initialized EGL, version 1.4

2019-03-07 19:18:39.675 11924-11988/com.google.ads.interactivemedia.v3.samples.videoplayerapp D/OpenGLRenderer: Swap behavior 1

2019-03-07 19:18:39.676 11924-11988/com.google.ads.interactivemedia.v3.samples.videoplayerapp W/OpenGLRenderer: Failed to choose config with EGL_SWAP_BEHAVIOR_PRESERVED, retrying without...

2019-03-07 19:18:39.676 11924-11988/com.google.ads.interactivemedia.v3.samples.videoplayerapp D/OpenGLRenderer: Swap behavior 0

2019-03-07 19:18:39.690 11924-11988/com.google.ads.interactivemedia.v3.samples.videoplayerapp D/EGL_emulation: eglCreateContext: 0x9cf861a0: maj 3 min 1 rcv 4

2019-03-07 19:18:39.731 11924-11988/com.google.ads.interactivemedia.v3.samples.videoplayerapp D/EGL_emulation: eglMakeCurrent: 0x9cf861a0: ver 3 1 (tinfo 0x9cf83860)

2019-03-07 19:18:39.734 11924-11988/com.google.ads.interactivemedia.v3.samples.videoplayerapp E/eglCodecCommon: glUtilsParamSize: unknow param 0x000082da

2019-03-07 19:18:39.734 11924-11988/com.google.ads.interactivemedia.v3.samples.videoplayerapp E/eglCodecCommon: glUtilsParamSize: unknow param 0x000082da

2019-03-07 19:18:39.747 11924-11996/com.google.ads.interactivemedia.v3.samples.videoplayerapp D/EGL_emulation: eglCreateContext: 0x89dc5c60: maj 3 min 1 rcv 4

2019-03-07 19:18:39.769 11924-11996/com.google.ads.interactivemedia.v3.samples.videoplayerapp D/EGL_emulation: eglMakeCurrent: 0x89dc5c60: ver 3 1 (tinfo 0x89dedb20)

2019-03-07 19:18:39.773 11924-11996/com.google.ads.interactivemedia.v3.samples.videoplayerapp E/eglCodecCommon: glUtilsParamSize: unknow param 0x000082da

2019-03-07 19:18:39.773 11924-11996/com.google.ads.interactivemedia.v3.samples.videoplayerapp E/eglCodecCommon: glUtilsParamSize: unknow param 0x000082da

2019-03-07 19:18:39.847 11924-11988/com.google.ads.interactivemedia.v3.samples.videoplayerapp D/EGL_emulation: eglMakeCurrent: 0x9cf861a0: ver 3 1 (tinfo 0x9cf83860)

2019-03-07 19:18:39.929 11924-11996/com.google.ads.interactivemedia.v3.samples.videoplayerapp I/VideoCapabilities: Unsupported profile 4 for video/mp4v-es

2019-03-07 19:18:39.945 11924-11996/com.google.ads.interactivemedia.v3.samples.videoplayerapp W/cr_MediaCodecUtil: HW encoder for video/avc is not available on this device.

2019-03-07 19:18:39.956 11924-11996/com.google.ads.interactivemedia.v3.samples.videoplayerapp W/cr_MediaCodecUtil: HW encoder for video/avc is not available on this device.

2019-03-07 19:18:40.004 11924-11996/com.google.ads.interactivemedia.v3.samples.videoplayerapp D/EGL_emulation: eglCreateContext: 0x889cbf60: maj 3 min 0 rcv 3

2019-03-07 19:18:40.006 11924-11996/com.google.ads.interactivemedia.v3.samples.videoplayerapp D/EGL_emulation: eglMakeCurrent: 0x889cbf60: ver 3 0 (tinfo 0x89dedb20)

2019-03-07 19:18:40.187 11924-11929/com.google.ads.interactivemedia.v3.samples.videoplayerapp I/zygote: Do partial code cache collection, code=28KB, data=30KB

2019-03-07 19:18:40.187 11924-11929/com.google.ads.interactivemedia.v3.samples.videoplayerapp I/zygote: After code cache collection, code=28KB, data=30KB

2019-03-07 19:18:40.187 11924-11929/com.google.ads.interactivemedia.v3.samples.videoplayerapp I/zygote: Increasing code cache capacity to 128KB

2019-03-07 19:18:40.292 11924-12010/com.google.ads.interactivemedia.v3.samples.videoplayerapp D/NetworkSecurityConfig: No Network Security Config specified, using platform default

2019-03-07 19:18:40.610 11924-11935/com.google.ads.interactivemedia.v3.samples.videoplayerapp I/zygote: Background concurrent copying GC freed 15986(1114KB) AllocSpace objects, 0(0B) LOS objects, 54% free, 1289KB/2MB, paused 887us total 106.026ms

2019-03-07 19:18:42.737 11924-11949/com.google.ads.interactivemedia.v3.samples.videoplayerapp W/zygote: Skipping duplicate class check due to unrecognized classloader

2019-03-07 19:18:42.891 11924-11929/com.google.ads.interactivemedia.v3.samples.videoplayerapp I/zygote: Do partial code cache collection, code=61KB, data=52KB

2019-03-07 19:18:42.892 11924-11929/com.google.ads.interactivemedia.v3.samples.videoplayerapp I/zygote: After code cache collection, code=61KB, data=52KB

2019-03-07 19:18:42.902 11924-11929/com.google.ads.interactivemedia.v3.samples.videoplayerapp I/zygote: Increasing code cache capacity to 256KB

2019-03-07 19:18:43.567 11924-11924/com.google.ads.interactivemedia.v3.samples.videoplayerapp I/ExoPlayerImpl: Init ExoPlayerLib/1.5.16

2019-03-07 19:18:47.817 11924-11924/com.google.ads.interactivemedia.v3.samples.videoplayerapp I/Choreographer: Skipped 254 frames!  The application may be doing too much work on its main thread.

2019-03-07 19:18:47.856 11924-11924/com.google.ads.interactivemedia.v3.samples.videoplayerapp W/IMASDK: Invalid internal message, ignoring. Please make sure the Google IMA SDK library is up to date. Message: gmsg://afma.google.com/activityMonitor?type=getPageSignals&sid=2e4fcb5b-29ba-4413-b4a7-3444a5a08479&dt=1552007927851

Thanks! 

Adam

[ima-sdk-fo...@google.com]

Hi Adam,

Thank you for providing additional insights with regards to the issue. The team is still looking into this issue so rest assured we will update you once we have our findings.

Regards,
Arnaud Casame

IMA SDK Team

=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+ page:
    http://googleadsdeveloper.blogspot.com
    https://plus.google.com/115658573333388777174/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

[Adam Tentis]

Hello,

It's been a while with no update. Any news?

Also, here is another report of the same issue from a user on stack overflow.

https://stackoverflow.com/questions/55034660/ima-sdk-issue-on-android

Thanks,

Adam

[ima-sdk-fo...@google.com]

Hi Adam,

Thank you for following up with support. The team is currently working on reviewing the behavior you reported previously. However, we would like to know if you were able to reproduce the behavior running your ad tag against our Android BasicExample sample on mobile? In the meantime, I've relayed the information to the rest of the team and I'll get back to you once we have our findings.

Regards,

Arnaud Casame

IMA SDK Team

=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+ page:
    http://googleadsdeveloper.blogspot.com
    https://plus.google.com/115658573333388777174/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

[Adam Tentis]

Hi Arnaud,

As mentioned in previous comments one of the devices I was able to reproduce the issue with the basic sample is on Amazon Fire TV.  Fire TV is based on Android mobile (not the Android TV leanback framework) so it's behavior is very similar to mobile.

However, I will also test on a mobile device for you as well but suspect I will have the same results as I do on Fire TV and Android TV.

Thanks,

Adam

[Adam Tentis]

Hi Arnaud,

Using the basic sample I was able to reproduce the issue on a Google Pixel 3. Specifically, I used the copy I shared in an earlier comment which can be found here: https://drive.google.com/drive/folders/1aBfA7XkqGPo5MXE7NAMMM5NwTFky25I7?usp=sharing 

It took about 10 rebuilds but it eventually started doing it consistently. I modified the sample app to load the video automatically when the app starts so you can just keep rebuilding until the issue starts happening. (no commercial and no onAdError event)

So total devices that I have reproduced this issue on are:

Google Pixel 3

Nvidia Shield TV

Google ADT-2 

Sony Bravia Android TV

Amazon Fire TV

Android TV emulator

Here are some other reports of the exact issue if you had not seen them.

https://groups.google.com/forum/#!topic/ima-sdk/_h74a6IDgaM

https://groups.google.com/forum/#!topic/ima-sdk/rRAEtBZAGz4

https://stackoverflow.com/questions/55034660/ima-sdk-issue-on-android

Please escalate this problem as much as you can. I have had to turn off the IMA SDK in production due to user complaints for over a month now.

Thanks,

Adam

On Friday, March 22, 2019 at 2:25:54 PM UTC-5, ima-sdk-forumadvisor wrote:

[ima-sdk-fo...@google.com]

Hi Adam,

Thank you for providing additional insight with regards to the issue. I've relayed the information to the rest of the team, they are going to review the issue and I'll get back to you as soon as I have more details.

Regards,

Arnaud Casame

IMA SDK Team

=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+ page:
    http://googleadsdeveloper.blogspot.com
    https://plus.google.com/115658573333388777174/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

[Adam Tentis]

Hi Arnaud,

It has been ~6 weeks since I reported this issue.

- Please follow up with how my issue differs from this issue since I get stuck on init as well. https://groups.google.com/forum/#!topic/ima-sdk/ayvmLfwSqYE

- Please give me an update on my issue other than the team is working on it.

- Please provide an ETA when the issue will be fixed.

Thank you,

Adam

[ima-sdk-fo...@google.com]

Hi Adam,

The issues are not the same because:

1. In your use case, you modified our IMA Sample app before you can reproduce the issue.
2. In your use case, the ad getting stuck is only reproducible on your sample app.
3. In your use case, the ad getting stuck is reproducible intermittently.
4. In their use case, the issue is specific to their VAST XML and reproducible each and every time.

Unfortunately, we have no updates for you at this time and no ETA on when the issue will be fixed. However, I'll let you know as soon as i have more information.

Regards,

Arnaud Casame

IMA SDK Team

=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+ page:
    http://googleadsdeveloper.blogspot.com
    https://plus.google.com/115658573333388777174/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

[Adam Tentis]

Hi Arnaud,

Thanks for the detailed reply. Please see below for my responses.

1. I have reproduced this on an unmodified sample plenty of times.I only modified the sample to make it even easier to reproduce by having the commercial load automatically without button click.

2. This is incorrect. Your team has already reproduced it using an unmodified sample app. Please see here. https://groups.google.com/d/msg/ima-sdk/sR4K4UMWcCU/hOv-XsdXAwAJ

3/4. This is only because I do not know what commercial is causing the failure. The other thread the person knew exactly what xml to use which is why I asked them how they figured it out so I could make it easier to reproduce.

The issue is your sdk is not handling these ad failures correctly. Ad requests will never work perfectly but the sdk is expected to handle these failures by hitting onAdError which it is not correctly doing. It would be helpful if you read through all the responses in this thread since the beginning since I have given a lot of information.

Thanks,

Adam

[ima-sdk-fo...@google.com]

Hi Adam,

From what you described, fixing the issue coming from the specific ad (on the other thread) will fix the black screen issue you're facing. As the team is actively working on fixing the issue coming from the specific ad, you can monitor the other thread and start running tests once the fix is released. In the meantime, I'll share your last comment with the team.

Regards,

Arnaud Casame

IMA SDK Team

=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+ page:
    http://googleadsdeveloper.blogspot.com
    https://plus.google.com/115658573333388777174/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

[ada...@gmail.com]

Hi Arnaud, 

This is in fact fixed now since it looks like whatever broken ads were causing this issue were fixed. 

I am a little disappointed it took so many agents and weeks for the support side to understand thats' all the issue was. Especially since I was told my issue was different when it was the exact same problem in the other threads I was reporting. However, at least I will know for next time if this issue comes up again.

Thanks,

Adam