iOS and Android UMP SDK: ConsentStatus always NotRequired, and FormStatus always Unavailable

[Sam Rayner]

We are attempting to add GDPR consent collection from our users but cannot get the form to display to test it. Please could somebody at Google check our configuration to figure out why we always receive a ConsentStatus of NotRequired and a FormStatus of Unavailable?

App: 4082097345
App name: Sendwave Staging

App unverified (testing)

No app store page yet (testing)

Approval not yet needed (testing)

Notes:

- We are using the latest SDK on Android and iOS

- We have no ad units or campaigns

- We have 1 active GDPR message for personalised ads, 3 custom ad partners and 11 purposes selected

- The GDPR message has the test app selected, ad unit deployment is off, targeting Everywhere geography, it is published

- Payment setup is incomplete for the account

- No ad units or campaigns or mediations are configured

- We are testing on simulator/emulator but have also tried on device with the device ID added to testDevices

- We have set our debug geo to .EEA and applied the debugSettings to the parameters

- We have tried UserMessagingPlatform on its own as well as starting GoogleMobileAds as well as UserMessagingPlatform

Thanks for your help!

---------------

This message may contain confidential information. If you are not the intended recipient please notify the sender immediately, delete and destroy all copies. Any unauthorised dissemination of this message is not permitted. WorldRemit Ltd is a limited company registered in England and Wales (registration number: 07110878).

[Mobile Ads SDK Forum Advisor]

Hi,

Can you confirm that you followed the instructions to enable your device as a test device(Android / iOS ) ? Please remember that debug settings such as setting the geography to EEA do not apply in release mode. Kindly provide us below app ID via "Reply to author" option for further investigation.
 

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

Thanks,
 

Mobile Ads SDK Team

[Sam Rayner]

Hi there,

We are testing on simulator/emulator but have also tried on device with the device ID added to testDevices. We are running a Debug build.

App ID: ca-app-pub-2801153313424534~4082097345

Thanks!

[compute...@hotmail.com]

+1 - I am having the same issue on all my apps. They have all been working for some time, however in the process of adding GDPR consent to a new app I was having issues so I went back & tested my other apps & found none of them are now working. 

[compute...@hotmail.com]

After spending an entire day trying to figure this out, I discovered that the issue is actually with the Ladybug 2024.2.2 Canary 9 of Android Studio. When I upgraded from Canary 8, somehow the Gradle-aware Make action got dropped from the Before Launch actions in the run configuration. The result was that it would fail to compile every time I ran the app in debug mode & would just launch immediately on my test device. I knew there was something weird going on because I would make code changes & they wouldn't be reflected when the app ran. Apparently this isn't an uncommon issue with the Canary releases. The other thing I found when I did a clean & manual build in the AS terminal, it turned out that the JVM version 8 I was using was too old. I had changed the compileSdk to 35 & upgraded the com.android.application plugin to version 8.8.0-alpha09, which requires a minimum JVM version of 11. I thought I was using JVM version 17, but it turned out I was still using version 8.

Don't know if either of these things will help the original poster, but might be worth looking into.

[Abubakar Aminu]

Please any Whatsapp group for admob guide 

On Wednesday 9 October 2024 at 22:35:45 UTC+1 Mobile Ads SDK Forum Advisor wrote:

[Mobile Ads SDK Forum Advisor]

Hi Abubakar Aminu, 

Thank you for contacting the Mobile Ads SDK Support team.

Please note that our support channel can only best assist you with regards to Google Mobile Ads SDK implementation and technical issues. Should you encounter any difficulties related to the Mobile Ads SDK, kindly provide a detailed description of your concern, and we will guide you accordingly. 

[Kim Taylor]

Hi Google Support Team, 

I work with Sam, the original poster.

We have given you our app id as requested, but we are still waiting for your reply after a month. Please can we have some support in understanding why our GDPR message is not displaying?

Some further details: 

We have tried added a US message in addition to the EU message, and tested by setting the debug geography to "regulated US state", but still we are getting "consent status = not required" on both our iOS and Android apps. We did get "form available = true" but only for this "regulated US state" geography, and only on Android. For the EU geography, we get "form available = false" and "consent = not required" on both iOS and Android. Same result even if we set "Everywhere" as the targeted location for the EU message.

In our console logs on Android, when we call UserMessagingPlatform.getConsentInformation( we are getting: 

Stored info not exists: IABTCF_TCString
Stored info not exists: IABGPP_HDR_GppString
Stored info not exists: IABGPP_GppSID
Stored info not exists: IABUSPrivacy_String

And when setting our geography to "us regulated state", we get this console line in addition to the above: 

Action[write]: {"IABTCF_CmpSdkID":300,"IABTCF_gdprApplies":0}

We created a Google AdMob account to configure these messages. Please note that we aren't using the AdMob SDK, because we aren't displaying ads in our app. We are just trying to use the UMP SDK to collect the user's consent, so that we can forward the IAB TCF consent string values to our 3rd party advertisers, such as Braze, Appsflyer and Facebook, so that we can serve personalised ads on e.g. Facebook platforms.  Can you also confirm if this use-case for the UMP SDK is valid? 

Thanks.

[Mobile Ads SDK Forum Advisor]

Hello,

I was able to replicate your issue on iOS. I have escalated your case to the engineering team to take a closer look. I will follow up here as soon I have an update to share.  

 

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

Thanks,
 

Justin Malandruccolo Mobile Ads SDK Team

[Mobile Ads SDK Forum Advisor]

Hello,

Thank you for your patience. EU regulations messages will not serve if your publisher account is not verified. Make sure you have entered and verified your payment details after signing up for your account. Once your account is verified, the issue you're experiencing is expected to be fixed.
 

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

Thanks,
 

Justin Malandruccolo Mobile Ads SDK Team

Feedback
How was our support today?