UserMessagingPlatform: Web view timed out

[noureen jan]

Hi, I'm using UMP library version 2.1.0 and following the same implementation guide, but it works on my other projects excluding the one where I get webview timeout error. I'm doing it in android using Kotlin.

W/UserMessagingPlatform: Web view timed out.
W/ContentValues: 4: Web view timed out.
W/UserMessagingPlatform: Web view timed out.
E/UserMessagingPlatform: Failed to load and cache a form, error=Web view timed out.

Didn't find any solution for it on the internet can anybody help me with it?

[Mobile Ads SDK Forum Advisor]

Hi Noureen Jan,

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.!5004Q02r2jPk:ref"

Thanks,
 

Mobile Ads SDK Team

[Mobile Ads SDK Forum Advisor]

Hello,

Are you able to consistently reproduce the web view timing out? If so, can you provide steps. Keep in mind the web view is powered by Android which the UMP SDK does not control. The web view may be limited by adverse network conditions. 

Thanks,
Justin

ref:!00D1U01174p.!5004Q02r2jPk:ref

[Egemen Hamutçu]

I have the same problem.

I am able to consistently reproduce the web view timing out with my phone. My wife has the exact the same phone and in her phone, the issue never happens.

I figured out that the main difference between two devices is that my phone's region is set to Germany, and her phone's region is set to Turkey.

The time is running out for us and Google should hurry up to fix the issue.

20 Aralık 2023 Çarşamba tarihinde saat 20:37:55 UTC+1 itibarıyla Mobile Ads SDK Forum Advisor şunları yazdı:

[Mobile Ads SDK Forum Advisor]

Hello,

To further diagnose your issue can you please share your device information? OS, type, etc.

[Egemen Hamutçu]

Device: Huawei P30 Pro (with Google Play Services)

Android version: 10 (EMUI 12)
Connection type: Does not matter (Wi-Fi, 4G Mobile Data)

Location: Germany

Device region: Germany

Device language: Turkish

Is that enough?

16 Ocak 2024 Salı tarihinde saat 19:29:02 UTC+1 itibarıyla Mobile Ads SDK Forum Advisor şunları yazdı:

[Mobile Ads SDK Forum Advisor]

Hello,

Thanks for providing that information. I can one more question from the Android engineering team. For your devices, are you using the same UMP SDK version in the same app version with the same implementation?

If so, what UMP SDK version are you using? And what API are you using to load the form?

[mec...@gmail.com]

Hi
We are also seeing this, and I can reproduce it 100% of the time.

I tried with all UMP versions since 2.1 up to 3.2

The device is Mi-4c with Android Version 5.1.1. (A really bad phone, on purpose)

Android System WebView is in Version 45.0.2454.95

One question: What's the minimun WebView Version needed to run UMP? ... or Recommended, because as a workaround I would like to known which min versión to avoid initializing UMP on devices with a really old web view, like this one, and instead run my old house-made CMP.

I now paste my implementation for the UMP call:

ConsentRequestParameters.Builder paramsBuilder = new ConsentRequestParameters.Builder();
if (UnderAgeOfConsent >= 0) paramsBuilder.setTagForUnderAgeOfConsent(UnderAgeOfConsent == 1);

//IF DEBUG OPTIONS ARE PASSED IN
if (deviceIds.length > 0 || DebugEEA > 0) {
  ConsentDebugSettings.Builder debugSettingsBuilder = new ConsentDebugSettings.Builder(a);

  if (DebugEEA > 0) {
    switch (DebugEEA) {
      case 1:
        debugSettingsBuilder.setDebugGeography(ConsentDebugSettings.DebugGeography.DEBUG_GEOGRAPHY_EEA);
      case 2:
        debugSettingsBuilder.setDebugGeography(ConsentDebugSettings.DebugGeography.DEBUG_GEOGRAPHY_NOT_EEA);
     }
  }
  if (deviceIds.length > 0) {
    for (int i = 0; i < deviceIds.length; i++) {
      debugSettingsBuilder.addTestDeviceHashedId(deviceIds[i]);
    }
  }
paramsBuilder.setConsentDebugSettings(debugSettingsBuilder.build());
}

//BUILDER
ConsentRequestParameters params = paramsBuilder.build();

consentInformation = UserMessagingPlatform.getConsentInformation(a.getBaseContext());

consentInformation.requestConsentInfoUpdate(a,params,(ConsentInformation.OnConsentInfoUpdateSuccessListener) () -> {

  //A popup was needed?
  Boolean wasPopUp = consentInformation.getConsentStatus() == ConsentInformation.ConsentStatus.REQUIRED;
  UserMessagingPlatform.loadAndShowConsentFormIfRequired(
    a,
    (ConsentForm.OnConsentFormDismissedListener) loadAndShowError -> {
      if (loadAndShowError != null) {
      // Consent gathering failed.
        callback.OnError(2,String.format("%s: %s",
        loadAndShowError.getErrorCode(),
        loadAndShowError.getMessage()));
      }else
      {

        // Consent has been gathered, format data and return
        callback.OnSuccess("Success",wasPopUp,new KrakenUMPData(a).toJSON());
      }
      
    }
  );

},
(ConsentInformation.OnConsentInfoUpdateFailureListener) requestConsentError -> {
  // Consent gathering failed.
  callback.OnError(1, String.format("%s: %s",
    requestConsentError.getErrorCode(),
    requestConsentError.getMessage()));
});

[Mobile Ads SDK Forum Advisor]

Hello,

Thank you for your inquiry. For Android, the UMP SDK has a minSDK requirement of 21, which enforces a minimum WebView version. Per the release notes, "the initial release for Android 5.0 includes a version of Chromium for WebView based on the Chromium M37 release."

It also known that older devices have performance issues when requesting consent information as it is a resource-heavy task. Reducing the number of ad partners in your AdMob UI to ones you actually need has been known to have a positive result on performance. 

Thanks,
 

Justin Malandruccolo Mobile Ads SDK Team

Feedback
How was our support today?
               
[2025-04-04 18:25:30Z GMT] This message is in relation to case "ref:!00D1U01174p.!5004Q02r2jPk:ref" (ADR-00216069)

[mec...@gmail.com]

Thank you for your response.

The device is 5.1.1, so it is above minimum

We do not use Admob, we call UMP and After that we initialize every other SDK that needs consent.
Mainly our UMP calls is done mostly by its own.

Any chance for a better way to initialize on low end devices? Maybe a lighter way for slow devices or something?

[Mobile Ads SDK Forum Advisor]

Hello,

At this time there is not a different way to initialize the UMP SDK on low end devices. We recommend to avoid other work when requesting consent with the UMP SDK as it is a resource-heavy task. 

Thanks,
 

Justin Malandruccolo Mobile Ads SDK Team

Feedback
How was our support today?
               

[2025-04-07 15:14:23Z GMT] This message is in relation to case "ref:!00D1U01174p.!5004Q02r2jPk:ref" (ADR-00216069)