Issues with Connecting Test Device for Admob Testing

Question

I’ve encountered issues with Admob, specifically with its test device connection system

A bit of backstory:

I tried to integrate the User Messaging Platform (UMP) panel into my Unity project, but every time I faced the issue that the UMP panel didn’t pop up on the test device. After testing various cases and checking the logs, I discovered that the UMP panel doesn’t show because my device doesn’t require it (ConsentStatus.NotRequired). I started re-reading and double-checking all the Admob documentation

Here’s what I’ve done:

1. Created GDPR and USA forms
2. Added a test European regional zone DebugGeography.EEA
3. Added my cached ID, which I took from logcat: TestDeviceHashedIds = "TEST-DEVICE-HASHED-ID"
4. Used ConsentInformation.Reset(); before each new UMP request
5. Double-checked Admob keys
6. Re-imported Admob
7. Performed Resolve and Force resolve
8. Regenerated the manifests
9. Waited 24+ hours. None of these helped

I decided to use the Admob Ad Inspector to see if I could get any feedback, so I started setting it up:

1. Registered my device via the Admob Console and entered the advertising ID
2. Waited 24+ hours

I tried to invoke the inspector with a gesture — it didn’t work. Then, I tried invoking it through code — still nothing. I looked at the logs:

Error: Unity Ad inspector cannot be opened because the device is not in test mode. 
See https://developers.google.com/admob/android/test-ads#enable_test_devices for more information

I followed all the documentation — still no success, and now I’m stuck

My main issue: Admob doesn’t recognize my device as a test device. Can anyone point out what I might have missed?

Thanks in advance!

Context:

• Unity: 2022.3.57f1
• Min API Level: 25; Target API Level: 35
• Admob: v9.5.0
• Test Device: Galaxy M35 5G and BlueStacks emulator (Samsung Galaxy S21 Ultra)