UserMessagingPlatform Web view timed out

[Mathew Duggan]

Hi all,

I've integrated the Google CMP into my Android application, but am running into a pretty frequent problems. The webview fails to load and times out. Here are the following logs for the error:
Writing to storage: [IABTCF_CmpSdkID] 300

Writing to storage: [IABTCF_gdprApplies] 1

Action[write]: {"IABTCF_idfaFlowControl":2}

Writing to storage: [IABTCF_idfaFlowControl] 2

Web view timed out.

Web view timed out.

Failed to load and cache a form, error=Web view

I can confirm that the network connection is great and that an iOS device on the same network connection never manifests the problem. What I've noticed is before the webView timeout I see the following lines:
variations_seed_loader.cc(69)] Failed to open file for reading

Unable to open '/data/app/~~WD3z0iAB5ZaD7XxLnV8szQ==/com.google.android.trichromelibrary_609914433-Sue247sfJo9q96kPHIA3DQ==/base.dm': No such file or directory

I'm unsure how to proceed troubleshooting this and would appreciate any assistance. I have ensured that Chrome and Android WebView are fully updated, I can recreate across multiple physical devices on different networks and it doesn't seem to happen with all webviews on these devices.

[Mobile Ads SDK Forum Advisor]

Hi,

Thank you for contacting the Mobile Ads SDK Support team.

I will check with our team regarding your query and one of my team members will reach out to you once we have an update on this. Meanwhile, your patience is highly appreciated.

 

This message is in relation to case "ref:!00D1U01174p.!5004Q02r53Tp:ref"

Thanks,
 

Mobile Ads SDK Team

[Mobile Ads SDK Forum Advisor]

Hello Matthew,

Thanks for reaching out.

This looks like a Web view issue instead. Can you provide the full stack trace of the timed out error and see if it was caused by the UMP SDK?


Regards,
Joshua

ref:!00D1U01174p.!5004Q02r53Tp:ref

[Vlad Alex]

Hey there, I had similar issue. In my case I was able to test the app on multiple devices and the consent message fails to show with the mentioned error (Web view timed out) only on the device with Mali 400MP GPU, which supports only the old Open GL ES 2.0. Right after calling UserMessagingPlatform.loadAndShowConsentFormIfRequired I see the following entry in the log:

01-09 18:30:15.745 17283 17417 E chromium: [ERROR:gl_surface_egl.cc(158)] eglChooseConfig failed with error EGL_BAD_ATTRIBUTE

The message is logged from the same process as the app (but from a dedicated thread).

This message is repeated twice, and then after 10 seconds the Web view timed out error happens.

The pre-UMP build of my app also logs the chromium error message, although once per ad load it seems. The AdMob ads are then displayed correctly.

On other devices that I have (OpenGL ES 3.0+) there is no EGL_BAD_ATTRIBUTE  chromium error and the UMP form is shown without issues.

Could the time out error be related to some WebView config which is incompatible with older GPUs?

Regards,

Vlad.

[Mobile Ads SDK Forum Advisor]

Hello Vlad,

Thanks for the question.

Since this error comes from WebView instead of the Google Mobile Ads SDK, I would suggest reaching out to the Android team for next steps.

[Mathew Duggan]

In case someone stumbles upon this: the issue for us was the number of ad partners. Once we reduced the number of ad partners in the AdMob Messaging control panel to under 200 the timeout issue went away.

[George & Tuula Davies]

--

---
You received this message because you are subscribed to the Google Groups "Google Mobile Ads SDK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-admob-ads...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/9056edb6-8d50-47bb-be6d-54bf3a53145en%40googlegroups.com.

[Ta-Dah Apps]

We also experienced this issue with timeout on a number of old slower devices. In the end we just captured the error loadAndShowError.getErrorCode() == 4)    and retried the loadAndShowConsentFormIfRequire after a short delay. We do this up to 4 times before abandoning and it would appear to work pretty much 100% of the time. Clunky but does resolve this issue.

[Egemen Hamutçu]

We have already less than 200 ad partners, and the problem still occurs. Anyway, this is an inappropriate workaround and it should be fixed by Google.

12 Ocak 2024 Cuma tarihinde saat 13:01:31 UTC+1 itibarıyla Mathew Duggan şunları yazdı:

[Mobile Ads SDK Forum Advisor]

Hello,

Thank your all for providing for the API you are using. I have escalated this issue to the Android engineering team to take a closer look. I will report back as soon as I have an update to share.

Thanks,
Justin

ref:!00D1U01174p.!5004Q02r53Tp:ref

[Mobile Ads SDK Forum Advisor]

Hello,

Feedback from Android engineering:

Can you try with the UserMessagingPlatform.loadConsentForm and ConsentForm.show APIs instead of loadAndShowConsentFormIfRequired to see if the issue is still reproducible?

[Ta-Dah Apps]

I agree it should be fixed by Google. They have chosen a timeout value and by retrying I have just increased this timeout I suppose.