Android Question google reject app - deprecated Personalized Ad Consent SDK

[samannnn]

i use latest sdk and b4a:

B4A Sdk Manager: 4.00
SDK version: 6609375

B4a Version: 10.90 BETA #1

and firebaseAdmob2.
but when i update my app, google reject my app:

We have detected that your app includes the deprecated Personalized Ad Consent SDK, which is not approved for use in child-directed services. The SDK has been deprecated in favor of the User Messaging Platform SDK and must be updated.

Apps in the Designed for Families program must only use ad SDKs that have certified their compliance with the Families Ads Program.

Make appropriate changes to your app, and be sure to remove any non-certified ad SDKs or SDKs that are not approved for use in child-directed services. Remember, apps in the Designed for Families program that use ad SDKs for serving ads must only use ad SDKs that have certified their compliance with the Families Ads Program. Additionally, all other SDKs used in your app must be appropriate to be used in child-directed services.

i think,it is related to AdmobSdk, but why?

 

[Erel]

How are you handling the user consent? You need to use User Messaging Platform: https://www.b4x.com/android/forum/t...irebaseadmob2-google-mobile-ads-v20-0.129696/

 

[samannnn]

How are you handling the user consent? You need to use User Messaging Platform: https://www.b4x.com/android/forum/t...irebaseadmob2-google-mobile-ads-v20-0.129696/

i follow this:

FirebaseAdMob2 - Google Mobile Ads SDK v20+

This is a wrapper for Google Mobile Ads v20+ SDK. It is a modified version of FirebaseAdmob (1). This library works with Google Mobile Ads v20+. The previous library works with v19-. Note that you can use FirebaseAdMob2 without creating a Firebase account. It supports banner ads and...

www.b4x.com

should i use User Messaging Platform?

 

[Erel]

Are you using ConsentManager?

 

[Ohanian]

I have the same problem, app rejected 2 times, getting the same error about deprecated Personalized Ad Consent SDK.
I’m using B4A 10.60, updated SDK, FirebaseAdMob2.
My guess is that there's some reference to the old sdk in the new library.

 

[Erel]

That's correct. I want to make sure that this is the issue. You aren't using ConsentManager, right?

 

[samannnn]

That's correct. I want to make sure that this is the issue. You aren't using ConsentManager, right?

yes, i m not using ConsentManager

 

[Ohanian]

That's correct. I want to make sure that this is the issue. You aren't using ConsentManager, right?

Should we use ConsentManager or not?!

This was in the starter :

Sub initConsent
    
    Try

        consent.Initialize("consent")
        consent.RequestInfoUpdate(Array("pub-00000000000"))
        Wait For consent_InfoUpdated (Success As Boolean)
        If Success = False Then
'        Log($"Error getting consent state: ${LastException}"$)
        End If

    Catch
        Log(LastException)
    End Try
    
End Sub

 

[Erel]

Should we use ConsentManager or not?!

No.

 

[samannnn]

No.

Can you check furthermore?

 

[Erel]

Of course. The deprecated SDK will be removed from FirebaseAdmob2 v1.13, which will be included in B4A v10.9.

It will be released in a few minutes.

 

[quimacama]

I have the same problem. Following the steps of

AdsHelper extends Firebase2

Now I use Google's User Messaging Platform and I have been rejected the apps.

We have detected the use of Ad Consent, which is not allowed in apps that are in the Families program.

• An ad SDK is not allowed if it is an ad SDK that has not self-certified its compliance with Play’s Families Ads Program (certified ad SDKs), or, even if it is not an ad SDK, it is not approved for use in child-directed services non-COPPA compliant per its own public documentation (unless, for apps that target both children and older audiences, it is used behind a neutral age screen or implemented in a way that does not result in the collection of data from children).
• SDKs that have not self-certified their compliance with Play’s Families Ads Program (certified ad SDKs) and SDKs that are not approved for use in child-directed services per their own public documentation cannot be used to serve children or users of unknown age. These SDKs may be allowed if they are used behind a neutral age screen or implemented in a way that does not result in the collection of data from children. Please note, the status of SDKs often changes and it is your responsibility to review documentation of all SDKs used in your app to ensure compliance with Families policies.

 

[sorex]

I also had this rejection of an app that was already more than a year not updated.
I thought it was because I had Tappx in it but apparently it's one of Google's own libs that they detect as outdated?

I also believe I changed or removed the family programs thing as it gives too much limitations.

 

[samannnn]

I also had this rejection of an app that was already more than a year not updated.
I thought it was because I had Tappx in it but apparently it's one of Google's own libs that they detect as outdated?

I also believe I changed or removed the family programs thing as it gives too much limitations.

The problem is related to firebaseAmob2 library.

Of course. The deprecated SDK will be removed from FirebaseAdmob2 v1.13, which will be included in B4A v10.9.

It will be released in a few minutes.

But i cant find new firebaseadmob version 1.13

 

[Ohanian]

Of course. The deprecated SDK will be removed from FirebaseAdmob2 v1.13, which will be included in B4A v10.9.

It will be released in a few minutes.

My App get rejected again with the same error!
is there any way to check the apk to see if there's any reference to the deprecated sdk?

 

[Erel]

But i cant find new firebaseadmob version 1.13

It is included in B4A v10.9: https://www.b4x.com/b4a.html

com.google.ads.consent.* were removed from FirebaseAdMob2 v1.13. You can open it with 7zip to see the classes.
It is still in FirebaseAdmob (not 2).

s there any way to check the apk to see if there's any reference to the deprecated sdk?

You can decompile the APK. There are many decompiling tools.
If you can ask the review team to send you the name of the class that they found.

 

[samannnn]

It is included in B4A v10.9: https://www.b4x.com/b4a.html

com.google.ads.consent.* were removed from FirebaseAdMob2 v1.13. You can open it with 7zip to see the classes.
It is still in FirebaseAdmob (not 2).


You can decompile the APK. There are many decompiling tools.
If you can ask the review team to send you the name of the class that they found.

The specialists answer:

Step 1: Fix the policy violations with your app
We have detected that your app, (APK Version: 63) includes non-certified ad SDKs and/or SDKs that are not approved for use in child-directed services. Any SDKs used in the app must be appropriate for use in child-directed services. Additionally, apps that solely target children must not contain any SDKs that are not approved for use in child-directed services, including ads SDKs. Apps in the Designed for Families program must only use ad SDKs that have certified their compliance with the Families Ads Program.

We have detected the use of AdsConsent SDK, which is not allowed in apps that are in the Families program. An ad SDK is not allowed if it is an ad SDK that has not self-certified its compliance with Play’s Families Ads Program (certified ad SDKs), or, even if it is not an ad SDK, it is not approved for use in child-directed services non-COPPA compliant per its own public documentation (unless, for apps that target both children and older audiences, it is used behind a neutral age screen or implemented in a way that does not result in the collection of data from children).

SDKs that have not self-certified their compliance with Play’s Families Ads Program (certified ad SDKs) and SDKs that are not approved for use in child-directed services per their own public documentation cannot be used to serve children or users of unknown age. These SDKs may be allowed if they are used behind a neutral age screen or implemented in a way that does not result in the collection of data from children. Please note, the status of SDKs often changes and it is your responsibility to review documentation of all SDKs used in your app to ensure compliance with Families policies.

Maybe the problem is use of AdsConsent SDK,

We have detected the use of AdsConsent SDK, which is not allowed in apps that are in the Families program. An ad SDK is not allowed if it is an ad SDK that has not self-certified its compliance with Play’s Families Ads Program (certified ad SDKs), or, even if it is not an ad SDK, it is not approved for use in child-directed services non-COPPA compliant per its own public documentation (unless, for apps that target both children and older audiences, it is used behind a neutral age screen or implemented in a way that does not result in the collection of data from children).
[/QUOTE

 

[Erel]

Did you compile your app with FirebaseAdMob2 v1.13?

 

[samannnn]

Did you compile your app with FirebaseAdMob2 v1.13?

Not yet, tomorrow i release new version that released with FirebaseAdMob2 v1.13. And I'm waiting for review.

 

[Ohanian]

Not yet, tomorrow i release new version that released with FirebaseAdMob2 v1.13. And I'm waiting for review.

I did it yesterday but got the same result!
waitng to get more details about the error from google.