Crashes in Android 11 when using the Consent APIs in UMP

[Tornike Khintibidze]

Hello, Firebase console for our project has been reporting unusual crashes only for devices running Android 11. 100% of these crashes happen on that version. We cannot reproduce the crash in the emulator and the Firebase Device Streaming environment. The app crashes on launch, as indicated by the "Early crashes" label on Firebase. 

There's nothing in the stacktrace that  mentions our app, however, we're positive the issue happens when calling UserMessagingPlatform.getConsentInformation(context.applicationContext).requestConsentInfoUpdate(activity, params, {}, {})

Here's the stacktrace:
Fatal Exception: java.lang.ExceptionInInitializerError
com.google.android.gms.internal.consent_sdk.zzda.zzg (com.google.android.ump:user-messaging-platform@@3.1.0:2)
com.google.android.gms.internal.consent_sdk.zzde.zzh (com.google.android.ump:user-messaging-platform@@3.1.0:1)
com.google.android.gms.internal.consent_sdk.zzdb.zzg (com.google.android.ump:user-messaging-platform@@3.1.0:1)
com.google.android.gms.internal.consent_sdk.zzde.iterator (com.google.android.ump:user-messaging-platform@@3.1.0:1)
com.google.android.gms.internal.consent_sdk.zzam.zzc (com.google.android.ump:user-messaging-platform@@3.1.0:4)
com.google.android.gms.internal.consent_sdk.zzn.zza (com.google.android.ump:user-messaging-platform@@3.1.0:18)
com.google.android.gms.internal.consent_sdk.zzl.zzc (com.google.android.ump:user-messaging-platform@@3.1.0:3)
com.google.android.gms.internal.consent_sdk.zzu.zzb (com.google.android.ump:user-messaging-platform@@3.1.0:5)
com.google.android.gms.internal.consent_sdk.zzt.run (com.google.android.ump:user-messaging-platform@@3.1.0:11)
java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1167)
java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:641)
java.lang.Thread.run (Thread.java:923)
Caused by java.lang.NullPointerException
Attempt to invoke virtual method 'int java.util.AbstractCollection.size()' on a null object reference
com.google.android.gms.internal.consent_sdk.zzcy.<init> (com.google.android.ump:user-messaging-platform@@3.1.0:1)
com.google.android.gms.internal.consent_sdk.zzda.<clinit> (com.google.android.ump:user-messaging-platform@@3.1.0:1)
com.google.android.gms.internal.consent_sdk.zzda.zzg (com.google.android.ump:user-messaging-platform@@3.1.0:2)
com.google.android.gms.internal.consent_sdk.zzde.zzh (com.google.android.ump:user-messaging-platform@@3.1.0:1)
com.google.android.gms.internal.consent_sdk.zzdb.zzg (com.google.android.ump:user-messaging-platform@@3.1.0:1)
com.google.android.gms.internal.consent_sdk.zzde.iterator (com.google.android.ump:user-messaging-platform@@3.1.0:1)
com.google.android.gms.internal.consent_sdk.zzam.zzc (com.google.android.ump:user-messaging-platform@@3.1.0:4)
com.google.android.gms.internal.consent_sdk.zzn.zza (com.google.android.ump:user-messaging-platform@@3.1.0:18)
com.google.android.gms.internal.consent_sdk.zzl.zzc (com.google.android.ump:user-messaging-platform@@3.1.0:3)
com.google.android.gms.internal.consent_sdk.zzu.zzb (com.google.android.ump:user-messaging-platform@@3.1.0:5)
com.google.android.gms.internal.consent_sdk.zzt.run (com.google.android.ump:user-messaging-platform@@3.1.0:11)
java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1167)
java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:641)
java.lang.Thread.run (Thread.java:923)

It would be great if you could help us fix this issue, as it affects a good amount of our users.

[arch...@gmail.com]

Would love a solution here as well.

[Mobile Ads SDK Forum Advisor]

Hi,

We have tried running our sample app in android 11 and unable to reproduce the issue. Could you tell me if it is device specific ? or any other way to replicate this crash via test ads ?
 

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

Thanks,
 

Mobile Ads SDK Team

Feedback
How was our support today?

               

 

[Mobile Ads SDK Forum Advisor]

Hi Micke,

You can use the value that is shown in the logcat "269BECXXXXXXXXXB181E2" and says new ConsentDebugSettings.Builder().addTestDeviceHashedId() to set this as a debug device. Kindly note that all the emulators and simulators are in testmode by default. 

[Tornike Khintibidze]

This is a device-specific issue. Here's the list of devices reported by Firebase: Galaxy S22 Ultra, Galaxy S22, Galaxy S20 Ultra 5G, Galaxy S20+ 5G, Galaxy S24 Ultra, Galaxy S21 Ultra 5G, WayDroid X86_64 Device, AMD Stoney Ridge Chromebook, Pixel TV 11, Pixel 5, Pixel 2 XL, Intel Jasper Lake Chromebook, Intel Gemini Lake Chromebook, Intel Alder Lake-N Chromebook, Sdk_gphone_x86_64_arm64, Pixel 6, OnePlus 10 Pro 5G, OnePlus 8T, OnePlus5.

[Mobile Ads SDK Forum Advisor]

Hi,

We require detailed debug information from a device where the problem is consistently observed. Unfortunately, we have been unable to reproduce the issue on our end. Therefore, to investigate further, we kindly request that you provide us with a project where the issue can be reliably reproduced. Once we receive this information, we will share it with wider team for further analysis and insights.

[Esa Firman]

Hi Ads Team,

We also have a similar issue on our app, it has same affected android version and devices, but in our case the issue comes from play-service-ads library. Here's our stack trace:

          Fatal Exception: java.lang.ExceptionInInitializerError:
            at com.google.android.gms.internal.ads.zzgax.zzj(com.google.android.gms: play - services - ads @ @23 .4 .0: 2)
          at com.google.android.gms.internal.ads.zzgax.zzl(com.google.android.gms: play - services - ads @ @23 .4 .0: 6)
          at com.google.android.gms.internal.ads.zzgax.zzk(zzgax.java: 1)
          at com.google.android.gms.internal.ads.zzgfo.zza(zzgfo.java: 1)
          at com.google.android.gms.internal.ads.zzdwg.zzj(zzdwg.java: 43)
          at com.google.android.gms.internal.ads.zzdwd.run(zzdwd.java: 1)
          at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java: 1167)
          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java: 641)

          at java.lang.Thread.run(Thread.java: 923) 

          Caused by java.lang.NullPointerException: Attempt to invoke virtual method 'int java.util.AbstractCollection.size()'

          on a null object reference

          at com.google.android.gms.internal.ads.zzgav. < init > (com.google.android.gms: play - services - ads @ @23 .4 .0)
          at com.google.android.gms.internal.ads.zzgax. < clinit > (com.google.android.gms: play - services - ads @ @23 .4 .0: 1)
          at com.google.android.gms.internal.ads.zzgax.zzj(com.google.android.gms: play - services - ads @ @23 .4 .0: 2)
          at com.google.android.gms.internal.ads.zzgax.zzl(com.google.android.gms: play - services - ads @ @23 .4 .0: 6)
          at com.google.android.gms.internal.ads.zzgax.zzk(zzgax.java: 1)
          at com.google.android.gms.internal.ads.zzgfo.zza(zzgfo.java: 1)
          at com.google.android.gms.internal.ads.zzdwg.zzj(zzdwg.java: 43)
          at com.google.android.gms.internal.ads.zzdwd.run(zzdwd.java: 1)
          at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java: 1167)
          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java: 641)
          at java.lang.Thread.run(Thread.java: 923)

It looks like the crash is happen after we initial the ads SDK.

The crash is 100% in Android 11, affecting mostly chromebook devices (AMD Stoney Ridge Chromebook, Intel Gemini Lake Chromebook, Intel Jasper Lake Chromebook) but also a tiny amount of Lenovo 81WT and Samsung S22. We cannot reproduce the crash in HP Chromebook 11 G8.

It's one of our top crashes, which is particularly concerning as it occurs during the SDK's early initialization phase. This early crash negatively impacts our reputation and user experience, making it a high-priority problem that requires immediate attention.

Is there a way to contains and or mitigate this issue? 

Best Regards.

The contents of this message and any attachments are for use by the addressee named in this message and contains information that may be privileged, confidential or copyrighted under applicable law. If you are not the intended recipient or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message and any attachments. Any disclosure, copying, distribution or taking action in relation of the contents of this message is strictly prohibited and may be unlawful. Thank you for your cooperation.