B4A Library OldGoogleConsent - FirebaseAdmob2 with the old Google consent manager

ConsentManager SDK was removed from FirebaseAdMob2 as it can cause the app to be rejected in some cases (child directed apps).
Google recommends using User Messaging Platform instead: https://www.b4x.com/android/forum/t...dmob2-google-mobile-ads-v20-0.129696/#content

The attached library includes the old consent SDK and allows using it together with FirebaseAdmob2.

 

[mcqueccu]

Am a bit confuse.
If Google recommends using UMP, in which case can we use this old google consent?

 

[Erel]

If your app is not "child directed app" then you can currently keep using the old consent sdk (from a technical point of view).

 

[Computersmith64]

There is a problem with this. If the device is outside of the EU, the ConsentState comes back as UNKNOWN - which means when you request an ad through FirebaseAdmob2 (which is using Google Mobile Ads SDK v20+), it returns:

failed to load ad: {
"Code": 3,
"Message": "No ad config.",
"Domain": "com.google.android.gms.ads",
"Cause": "null",
"Response Info": {
"Response ID": "null",
"Mediation Adapter Class Name": "",
"Adapter Responses": []
}
}

The result is you can never get an ad for a device that's not in the EU.

- Colin.

 

[Erel]

I don't think that this message "no ad config" is related to the consent state. It is the same as the old "no fill" error.

 

[Computersmith64]

I don't think that this message "no ad config" is related to the consent state. It is the same as the old "no fill" error.

So on further testing, it works fine on devices running Android 10 & 7.0 - however I always get that error on my device running Android 12 (Beta 2 I think). I don't think it's a "no fill" error because if I test all 3 devices at the same time, I get ads on 2 & the error on the Android 12 device.

Also, when I was testing consent using UMP, the "no ad config" error would come up unless I selected the "Personalized Ads" (or whatever the equivalent is) option.

- Colin.