Test gdpr consent without is_test_europe_user_consent

[Xioor]

I was wondering what would trigger a gdpr prompt in release? Is it using the users ip address, account geographic location information or something else?

[gumaciel]

Hey!

Probably is by IP, we don't know for sure.

When we set is_test_europe_user_consent = true, we are doing this:

https://developers.google.com/admob/ump/android/quick-start#force_a_geography

In other words, we are telling to our application that we want to debug the Consent and we are on EEA.

[Xioor]

In the next few days, I will test if a EU IP if what triggers the gdpr prompt without is_test_europe_user_consent and let you know! As for your question on the naming for the singleton, I like MobileAds since that is the current one. But if you have to change it for some reason, I think GoogleAdMob is great.

[gumaciel]

Thank you!

[Xioor]

I tried a United Kingdom vpn ip and I do not get the prompt with is_test_europe_user_consent = false on Release or Debug. In a few days, I will test on a a few device that is actually located in Russia and Poland with this: https://developer.samsung.com/remotetestlab/galaxy/rtlDeviceList.action#502 Ill let you know how it went.

[gumaciel]

I think on Russia won't work, only on these:

Austria, Belgium, Bulgaria, Croatia, Republic of Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Poland, Portugal, Romania, Slovakia, Slovenia, Spain and Sweden.

But thank you so much anyway!

[Xioor]

I tested a device in poland with https://developer.samsung.com/remotetestlab/galaxy/rtlDeviceList.action#502 and is_real = true with is_test_europe_user_consent = false as a release build and the gdpr prompt appeared on first launch! It did not appear again after the first launch, but this: #57 will remedy that.
Good to know it's working!