Issue with User Messaging Platform (UMP) in Flutter Android Production Environment

113 views
Skip to first unread message

GenieMagic

unread,
Mar 12, 2024, 7:23:19 AMMar 12
to Google Mobile Ads SDK Developers
Hello,

We are experiencing issues with the User Messaging Platform (UMP) in our Flutter app. Below are the details of the issue:

Framework: Flutter
Package: google_mobile_ads (version: ^4.0.0)
Environment: Production
Issue Description: We are encountering intermittent exceptions related to UMP, with error messages such as "Exception: Error making request." and "Exception: The server timed out." Approximately 5 to 10% of our users are facing this issue on a daily basis.

Stack Trace
Non-fatal Exception: io.flutter.plugins.firebase.crashlytics.FlutterError: Exception: The server timed out.
   at FirebaseCrashlytics.recordError(firebase_crashlytics.dart:119)
   at LandingScreenState._requestConsent.<fn>(landing_view.dart:101)
   at UserMessagingChannel.requestConsentInfoUpdate(user_messaging_channel.dart:54)

Dart Implementation Details
_requestConsent(FirebaseAnalytics firebaseAnalytics, FirebaseCrashlytics firebaseCrashlytics) {
  try {
    // Production code
    final params = ConsentRequestParameters();
    ConsentInformation.instance.requestConsentInfoUpdate(
      params,
      () async {
        if (await ConsentInformation.instance.isConsentFormAvailable()) {
          ConsentForm.loadConsentForm(
            (ConsentForm consentForm) async {
              var status = await ConsentInformation.instance.getConsentStatus();
              if (status == ConsentStatus.required) {
                consentForm.show((formError) {
                  if (formError == null) {
                    firebaseAnalytics.logEvent(name: eConsentShown);
                  } else {
                    firebaseAnalytics.logEvent(name: eConsentNotShown);
                  }
                });

                if (mounted) {
                  firebaseAnalytics.logEvent(name: eConsentRequested);
                }
              }
            },
            (FormError formError) {
              firebaseCrashlytics.recordError(
                  Exception('Message: ${formError.message} ErrorCode: ${formError.errorCode.toString()}'),
                  null);
            },
          );
        }
      },
      (FormError error) {
        firebaseCrashlytics.recordError(Exception(error.message), null);
      },
    );
  } catch (error, stack) {
    firebaseCrashlytics.recordError(error, stack);
  }
}



Statistics
On a particular day, we observed the following statistics, which seem contradictory to the above error:

eConsentShown: 3497
eConsentNotShown: 4
eConsentRequested: 3556

We requested consent for around 3556 users, but it was displayed for only 3497 users. On the same day, we recorded 164 instances of "Error in making request."

We would appreciate any insights or solutions to address this issue.

Thank you.

Mobile Ads SDK Forum Advisor

unread,
Mar 12, 2024, 8:24:13 AMMar 12
to abhijeetsur...@gmail.com, google-adm...@googlegroups.com

Hi,

Thank you for contacting the Mobile Ads SDK support team.

In response to your inquiry, I will confer with our team. A member of our team will contact you promptly once an update is available. In the meantime, your patience is much appreciated.

This message is in relation to case "ref:!00D1U01174p.!5004Q02rzs9Z:ref" (ADR-00226943)

Thanks,
 
Google Logo Mobile Ads SDK Team

 

Mobile Ads SDK Forum Advisor

unread,
Mar 14, 2024, 10:25:55 AMMar 14
to abhijeetsur...@gmail.com, google-adm...@googlegroups.com
Hi GenieMagic,

We have seen reports on this issue and we are working towards fixing it. Will let you know once we have an update.

Thanks,
Jill
Google Mobile Ads SDK Team

ref:!00D1U01174p.!5004Q02rzs9Z:ref

Konstantin Shkulev

unread,
Jun 18, 2024, 12:55:00 AM (9 days ago) Jun 18
to Google Mobile Ads SDK Developers
Hi! Any ETA on fix?

четверг, 14 марта 2024 г. в 19:25:55 UTC+5, Mobile Ads SDK Forum Advisor:

Mobile Ads SDK Forum Advisor

unread,
Jun 21, 2024, 8:41:04 AM (5 days ago) Jun 21
to konstanti...@mytona.com, google-adm...@googlegroups.com
Hi Konstantin,

The fix is likely happening in July but we can't make promise on that.
 
This message is in relation to case "ref:!00D1U01174p.!5004Q02rzs9Z:ref" (ADR-00226943)

Thanks,
 
Google Logo
Jill Song
Mobile Ads SDK Team


Reply all
Reply to author
Forward
0 new messages