ATT dialog not showing following GDPR form

[Martin Ryan]

I am working on a Flutter app using firebase and Admob. 

I have configured both a GDPR and IDFA explainer message in Privacy & Messaging and linked them to the app.

In Xcode I have added the App Tracking Transparency framework and added a plist Tracking Usage Description 

"Note: For iOS, if you have created an ATT message for each of your apps in the AdMob UI, users will be prompted to provide ATT consent as part of the form presentation flow. No additional API calls are required."

However, in my case the user is NOT being presented with ATT Consent form. The GDPR consent form is displaying fine. 

My app makes a request for permission for notifications (IOS generated) and the GDPR displays in the background but is enabled immediately after however the ATT form is a no show. I have tried on multiple IOS devices.  

I am uninstalling and re-installing each time I test. 

Has anyone got this working?

[Mobile Ads SDK Forum Advisor]

Hi Martin,

Thank you for contacting the Mobile Ads SDK support team.

I will check with our team regarding your query and one of my team members will reach out to you once we have an update on this. Meanwhile, your patience is highly appreciated.  

This message is in relation to case "ref:!00D1U01174p.!5004Q02r50bP:ref"

Thanks,
 

Mobile Ads SDK Team

[Suraj Kumar G R]

Hi,

I'm also facing same issue. Any update ?

Regards,

Suraj.

[Mobile Ads SDK Forum Advisor]

Hi Martin,

Please see https://support.apple.com/en-us/HT212025. On your test device, inside the privacy and security settings, is "Allow Apps to Request to Track" turned on? You can also check the list of apps that have already requested permission.

Thanks,
Eric, Mobile Ads SDK Team

ref:!00D1U01174p.!5004Q02r50bP:ref

[Martin Ryan]

Hi Eric

Thanks for the reply.

Yes checked that - I also have now run a test using app_tracking_transparency: ^2.0.4  and that generates the requests on my test devices ok immediately after the GDPR message is displayed - so as a workaround I check if ATT has been requested by the admob sdk and if not use this package to fire off the request. Not massively happy with it as the solution - certainly looks like a bug in your SDK to me.