UMP (AdMob) Consent Form Not Appearing on Android (Unity), Despite Logs Indicating Success and Extensive Troubleshooting

[Bergson Menezes Gondim]

Problem Description: I'm facing a persistent issue where the User Messaging Platform (UMP) consent form from Google AdMob is not being displayed on Android devices (tested on Samsung SM-M315F, Android 12). Logcat indicates that the form has been "displayed," but it never visually appears on the screen.

Configuration Details:

• Engine: Unity 6.0 LTS (latest Long Term Support release)
• AdMob Plugin: Google Mobile Ads Unity Plugin (10.2.0)
• Test Device: Samsung SM-M315F, Android 12

Symptoms:

1. Invisible Form: The consent form never appears on the device screen.
2. Success Logs: Logcat consistently shows the following messages (among others), indicating that the UMP SDK believes the form has been displayed:
   • ConsentManager: Consent RESET for debug. (Using ConsentInformation.Reset() to force display).
   • ConsentManager: MobileAds SDK initialized. Status: SUFFICIENT
   • ConsentManager: Consent status updated: REQUIRED
   • ConsentManager: Form available: True
   • ConsentManager: Consent REQUIRED or form AVAILABLE. Loading and displaying form...
   • ConsentManager: Consent form displayed (or already displayed).

Troubleshooting Steps Taken (and results):

1. Remove In-Game UI Overlap:

   • Action: Disabled all UI GameObjects in my first Unity scene to ensure nothing in my game was covering the form.
   • Result: Form still did not appear.

2. Delay Initialization Due to Unity Splash Screen:

   • Observation: Noticed that UMP logs indicating "form displayed" appeared while the default Unity Splash Screen was still active.
   • Action: Shifted the ConsentManagerUMP initialization to occur after the Unity Splash Screen. This was done by moving the initialization logic to a public method (InitializeUMPAndAds()) and calling it from a GameManager script in a later scene, with a Coroutine delay (yield return new WaitForSeconds(0.75f);). The ConsentManagerUMP GameObject is initially disabled and activated by the Coroutine.
   • Result: Form still did not appear.

3. async/await and Threading Issues (UnityException: set_enabled):

   • Action: Attempted to introduce a 5-second debug pause (await System.Threading.Tasks.Task.Delay(5000);) in the OnConsentInfoUpdated method (which is a UMP SDK callback).
   • Result: This caused a runtime error pop-up on the device: UnityException: set_enabled can only be called from the main thread. (Stack trace pointed to ConsentManagerUMP.OnConsentInfoUpdated).
   • Attempted fix: Added await Task.Yield(); to try and force execution back to the main thread. The error persisted.
   • Final Action (Current State): Completely removed the await pauses and removed the async modifier from the OnConsentInfoUpdated method to eliminate any threading issues.
   • Result: Form still does not appear, and a NEW RUNTIME ERROR POP-UP appears in the bottom-left corner of the device screen. (The exact text of this new error has not yet been provided).

Critical Observation: I am using Unity 2022.3.x LTS, which is a stable and officially supported version.

Questions for the Community:

• Has anyone encountered a scenario where the UMP SDK reports successful form display, but the form is not visible on Android devices, even with Unity 2022.3 LTS and after eliminating UI overlap and resolving threading issues?
• What could be causing the new runtime error that appears on the device screen, even after removing the async/await logic that caused the set_enabled error? (I will provide the exact error text as soon as I have it).
• Are there any specific configurations in Android Manifest, Player Settings, or other build settings that might prevent the UMP SDK pop-ups from appearing in a Unity 2022.3 LTS environment?

---

Please provide the exact text of the new runtime error when you get it. That will be crucial for further debugging!

[Mobile Ads SDK Forum Advisor]

Hi,

Thank you for contacting the Mobile Ads SDK Support team.

Can you please confirm if the reported issue is reproducible in our Google unity samples? If yes, then share us with the below details privately for further investigation:

• app ID
• ad unit ID
• Charles logs
• Confirm if the reported issue is occurring only in mentioned device Samsung SM-M315F
• Minimal sample app that reproduces the issue

You can provide the following details via reply privately to the author option or below link.

If the file(s) you are looking to share are less than 25mb in total you can attach them to this case on your next reply. If you are having trouble attaching your file to this case or if your file(s) are larger than 25mb, you can share your files with me by performing the following steps:

1. Navigate to

https://docs.google.com/forms/d/e/1FAIpQLSfkAiXMeYP-fw1W3Z-tT9uwmATEKO5X6S-th0gR2ezdKaaqfg/viewform?usp=pp_url&entry.400550049=Mobile+Ads+SDK&entry.460850823=500Ht00001rfFuoIAE&entry.80707362=00314242

2. Fill out all fields, and attach your file(s).

3. Please reply back on this thread when you have uploaded your file(s). Please do not share this link.

Thanks,
 

Mobile Ads SDK Team

Feedback
How was our support today?

               
[2025-06-13 20:55:31Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01rfFuo:ref" (ADR-00314242)

[Mobile Ads SDK Forum Advisor]

Hi,

Please utilize the Sample ad unit ID for the Unity sample applications.

Could you kindly provide the complete sample project for further investigation.

If the file(s) you are looking to share are less than 25mb in total you can attach them to this case on your next reply. If you are having trouble attaching your file to this case or if your file(s) are larger than 25mb, you can share your files via reply to author option or by performing the following steps:

https://docs.google.com/forms/d/e/1FAIpQLSfkAiXMeYP-fw1W3Z-tT9uwmATEKO5X6S-th0gR2ezdKaaqfg/viewform?usp=pp_url&entry.400550049=Mobile+Ads+SDK&entry.460850823=500Ht00001rfFuoIAE&entry.80707362=00314242 

2. Fill out all fields, and attach your file(s).

3. Please reply to this thread when you have uploaded your file(s). Please do not share this link.

Thanks,
 

Mobile Ads SDK Team

Feedback
How was our support today?

               

[2025-06-16 07:31:13Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01rfFuo:ref" (ADR-00314242)

[Bergson Menezes Gondim]

Yes, I confirm.