Setting .DEBUG_GEOGRAPHY_EEA causes requestConsentInfoUpdate to fail

[Muted Muted]

Hello,

Can someone please assist me with an issue I am having when using the .DEBUG_GEOGRAPHY_EEA

When I set the DebugGeography.DEBUG_GEOGRAPHY_NOT_EEA the requestConsentInfoUpdate returns successfully however if I then set it to .DEBUG_GEOGRAPHY_EEA the ConsentInfoUpdate fails.

This occurs on the real device below and on a simulated device.

implementation 'com.google.android.ads.consent:consent-library:1.0.6'

Device : Samsung Galaxy J4  (android version 8.0.0)

The DEVICE_ID and pub-MY-ID would be replaced when running the app.

The code I am using is below:

ConsentInformation.getInstance(this).addTestDevice("DEVICE-ID");

        // Geography appears as in EEA for test devices.

        ConsentInformation.getInstance(this).setDebugGeography(DebugGeography.DEBUG_GEOGRAPHY_EEA);

        // Geography appears as not in EEA for debug devices.

        //ConsentInformation.getInstance(this).setDebugGeography(DebugGeography.DEBUG_GEOGRAPHY_NOT_EEA);

        ConsentInformation consentInformation = ConsentInformation.getInstance(this);

        String[] publisherIds = {"pub-MY-ID"};

        consentInformation.requestConsentInfoUpdate(publisherIds, new ConsentInfoUpdateListener() {

            @Override

            public void onConsentInfoUpdated(ConsentStatus consentStatus) {

                Log.d("consent"," User's consent status successfully updated. ");

                

            }

            @Override

            public void onFailedToUpdateConsentInfo(String errorDescription) {

                // User's consent status failed to update.

                Log.d("consent"," User's consent status failed to update. ");

            }

        });

[Mobile Ads SDK Forum Advisor Prod]

Hi there,

Thank you for reaching out to us, and for giving extensive details on your concern.

Kindly note that we are aware of this issue, and our Engineering team is already working on a resolution. Rest assured that we are keeping an eye out on this, and that we will update you for any news regarding this issue.

Regards,
Ziv Yves Sanchez
Mobile Ads SDK Team

ref:_00D1U1174p._5001UKOslL:ref

[Muted Muted]

Does anyone know of a workaround that can be used to set the Consent SDK to think the app is in the EU? Other then using the .DEBUG_GEOGRAPHY

I have tried to use a gps emulator and although it fools google maps it does not seem to work on the Consent SDK.

Any suggestions would be appreciated.

[Mobile Ads SDK Forum Advisor Prod]

Hi there,

Currently, the Consent SDK only officially supports the DEBUG_GEOGRAPHY_EEA option in order to emulate the app being run in the EU. You may try using a VPN to change your IP to one belonging in the EU, although we cannot personally vouch for their effectiveness.

As for your original concern from your previous post: could you kindly provide the details below (via Reply privately to author) in order to help with the ongoing investigation?

• Publisher ID
• Copy of your sample project (replicating the issue), and steps on how to reproduce it