[Android] Invalid internal message

[Igor]

Hi,

  we are integrating IMA SDK and got VAST tage from our ad provider. We've got the following message while trying to load the ad in device log. No error message from SDK, so we keep waiting.

  IMASDK: Invalid internal message. Please make sure the Google IMA SDK library is up to date. Message: gmsg://afma.google.com/activityMonitor?type=getPageSignals&sid=f720285f-d878-41df-831d-aa843c604433&dt=1630583531322

[Igor]

2.24.0 sdk is used.

[Igor]

Everything forks just fine with your sample application.

[IMA SDK]

Hi Igor,

Thank you for reaching out to us with your concern. I was looking over your thread and from what I can seee the implementation on your end seems to be returning some kind of message about not being able to find the SDK. But when you have tested with one of our samples? This does not seem to happen. If this is the case, then it would indicate that the SDK is not properly set up. We would need more details about what you are building for, HTML 5, Android, iOS? What environment you are building in as well as a simple sample that displays this issue with any steps that show the error.

Regards,

William Pescherine IMA SDK Team

ref:_00D1U1174p._5004Q2Mkvvm:ref

[Igor]

Hi, William.

  will try to provide more details. We've got android application (the topic). We use 2.24.0 Google IMA SDK. Our implementation is based on your Android Advanced sample. The main difference is that we've removed the code we don't need and we use the hidden popup window as a parent for the views which are created by your sample to preload the ad before it is shown (we've got the same issue with and without setEnablePreloading(true);).

  Our application works perfectly with the sample linear non-skippable ad tag. However, when we try the tag of our ad provider, nothing happens after adsManager.init(adsRenderingSettings); is called. No methods from neither adsManager.addAdErrorListener() nor adsManager.addAdEventListener() callbacks are triggered. IMA SDK just keeps silence. However, when we check device's log we can see the following message there:

IMASDK: Invalid internal message. Please make sure the Google IMA SDK library is up to date. Message: gmsg://afma.google.com/activityMonitor?type=getPageSignals&sid=f720285f-d878-41df-831d-aa843c604433&dt=1630583531322

  When we build your Android Advanced sample with the CUSTOM VideoMetadata value pointing to our ad tag, everything works just fine. When we put our tag into https://developers.google.com/interactive-media-ads/docs/sdks/html5/client-side/vastinspector everything works either. So I'm a bit confused about this cryptica message in device log and what possibly could go wrong. Please, note that I've already had a topic with you here about SDK not sending error messages when internet connection is disabled. Is it possible that IMA SDK could conflict with one of SDKs we are already using or their dependencies might conflict.

[IMA SDK]

Hi Igor,

Thank you for providing an additional context. 

As per checking, it appears that you're using an old version of the SDK, which I think the reason that you're getting an error message "IMASDK: Invalid internal message. Please make sure the Google IMA SDK library is up to date". The latest version of the SDK is 3.24.0 which is far from the version 2.24.0 that you're currently using. That said, could you please update your SDK, then let me know how it goes?

Regards,

Teejay Wennie Pimentel IMA SDK Team

ref:_00D1U1174p._5004Q2Mkvvm:ref

[Igor]

Sorry for misleading you.

  We are actually using 3.24.0. Just double-checked that.

[Igor]

I've performed a couple of experiments here.

  When the player view is attached to the PopupWIndow before the add loading is started, I've get the following events: AD_BREAK_FETCH_ERROR, CONTENT_RESUME_REQUESTED, ALL_ADS_COMPLETED. Please, note that I got this events both when preloading is active and adsManager.start(); is not called and when preloading is disabled and adsManager.start(); is called. None of error callbacks are called in both cases.

  Unfortunately I can't easily attach the player view to our activity at the moment since we use NativeActivity as the base and the input is routed the different way. Do you think some functionality of your SDK (anti-fraud or custom UI controls or whatever) might require the player to be attached to the activity while we use the PopupWindow instead?

[IMA SDK]

Hi Igor,

 

I work along with Teejay and William.

 

Upon reading through the thread, it would appear that it is most probably an implementation issue as we haven't received any reports recently regarding conflict with other SDKs or their dependencies. But, we could raised this to the rest of the team and have it check, if you can send us the sample project implementation where this issue is reproducible, it would be best if you could send a screen recording of the behavior as well.

Please share the requested information through "reply to author" option button or send it directly to our testing alias imate...@gmail.com. Please confirm in this thread once it has been sent.

Regards,

Michael Angelo Legaspi IMA SDK Team

ref:_00D1U1174p._5004Q2Mkvvm:ref

[Igor]

Hi Michael.

  I've sent you a private message with the google drive link.

  Both the sample and our game use the same VAST tag and the same in-house wrapper for your SDK. We also get and show ads similar way.

  Our application now finally receives error message AD_BREAK_FETCH_ERROR with the following call stack:
onAdEvent:142, VideoPlayerController$AdsLoadedListener$2 (com.wildspike.advertise.imawrapper)
b:10, dg (com.google.ads.interactivemedia.v3.internal)
b:15, cv (com.google.ads.interactivemedia.v3.internal)
k:13, ed (com.google.ads.interactivemedia.v3.internal)
f:5, ej (com.google.ads.interactivemedia.v3.internal)
shouldOverrideUrlLoading:2, eg (com.google.ads.interactivemedia.v3.internal)
shouldOverrideUrlLoading:83, WebViewClient (android.webkit)
shouldOverrideUrlLoading:14, AwContentsClientBridge (org.chromium.android_webview)
nativePollOnce:-1, MessageQueue (android.os)
next:335, MessageQueue (android.os)
loop:183, Looper (android.os)
main:7656, ActivityThread (android.app)
invoke:-1, Method (java.lang.reflect)
run:592, RuntimeInit$MethodAndArgsCaller (com.android.internal.os)
main:947, ZygoteInit (com.android.internal.os)

  The sample application received these events occasionally, but shows the ads just fine.

  Both of the applications for every ad load have IMASDK: Invalid internal message. in the log.

  This looks really odd to me since all the ads I get from this tag in the test app I've sent you I see a small onscreen banner, which has a simple animation and a link to the advertiser landing page. So I'd expect WebView to send shouldOverrideUrlLoading callback for all ads.

[IMA SDK]

Hi Igor,

Thank you for reaching back out to us. I was able to test the APK that you sent us and was able to play around on the app with the Test Ad attached to it. I was able to see the ad being served fine. But I am confused as to why you are using the IMA SDK inside a mobile game app? We would normally recommend that you use the Mobile Ads SDK. I was also able to see the error, and based on what I am seeing. This is not an SDK issue so much as I believe that the SDK is not being properly implemented in the app which is why you are getting this error. As stated above, I was able to see the ad just fine, I saw all the quartiles fire and everything seems to be ok.

Regards,

William Pescherine IMA SDK Team

ref:_00D1U1174p._5004Q2Mkvvm:ref

[Igor]

Hi William.

  I've double-chekhed your SDK for all diagnostics options once again. I've found out that additionally error info can be delivered via onAdEvent() callback: AD_BREAK_FETCH_ERROR event and error info via LOG event. Sorry for missing this.

  Now for our game I get
AdEvent[type=LOG, ad=null, adData={errorMessage: The response does not contain any valid ads., errorCode: 1009, type: adLoadError}]
AdEvent[type=AD_BREAK_FETCH_ERROR, ad=null, adData={adBreakTime: 0}]

Since the same VAST tag is used to get ads for both our game and test appliaction I assume that either IMA SDK generates different tag from ours (as far as I understood IMA SDK overloads some parameters before the request is issued) or for some reason IMA SDK the same VAST response suitable for the sample app and non-suitable for our game...

Is there any way we could get the actual tag after all modifications by the SDK? Is there any way to get the VAST response SDK receives from the server? This will significantly simplify debugging for us.

P.S.  Unfortunately IMA SDK is the only option to show ad on Android TV which is officially suggested as AdMob replacement by AdMob guys: they don't support Android TV officcialy and in practice some AdMob parts don't work on Android TV anymore. And other game-specific SDKs don't support Android TV either. IMA SDK is challenging to make it running for the game, since the usage pattern is very different from the one you've developed it for.

[IMA SDK]

Hi Igor,

Thank you for the additional information. Also based on this it explains why you are using the IMA SDK, which would be correct for this. Since you are developing for Android TV it is best that you use the IMA SDK. With that also in mind I will need to bring this to our team to look into more. As I did not test on Android TV and we will want to so as to get you better feedback about this.

[Igor]

Hi,

  I must admit that the issue we've met is due to the ad configuration our provider set up for our VAST tag. Capturing the traffic showed the difference and we've found out that simply changing application ID in the manifest automagicaly fixes everything. The VAST tag provides ads to all applications except ours. Hope we'll sort all the issues out finally.

  Thanks for your time. btw, AdMob just dropped unofficial AppleTV support recently, so your SDK is the only ad SDK available.

[IMA SDK]

Hello Igor,

Sorry for the delay in response.

The message error you are receiving can be ignored:

Invalid internal message. Please make sure the Google IMA SDK library is up to date.

Please let me know if you have any other questions.

Thank you,
Jackson
IMA SDK team.

ref:_00D1U1174p._5004Q2Mkvvm:ref