Apple Rejecting App Update with UMP Custom ATT Consent Dialog

[idi...@gmail.com]

Hi,

Apple just rejected my update because my app displays a user consent request dialog before prompt for ATT permissions. Their note to me is as follows:

Guideline 5.1.2 - Legal - Privacy - Data Use and Sharing

We noticed you do not use App Tracking Transparency to request the user's permission before collecting data used to track them. Instead, your app displays a custom prompt that requests the user to allow tracking. 

Starting with iOS 14.5, apps on the App Store need to receive the user’s permission through the AppTrackingTransparency framework before collecting data used to track them. Requesting permission with a custom prompt is not appropriate. 

In a follow up they stated:

"..the custom prompt is not appropriate for the App Store, the modal alert should be the only prompt that is sufficient."

The UX flow is as follows:

Has anyone else experienced this? What's the solution? It seems that anything other than their native ATT prompt is now prohibited.

Thanks,

Ian

[Mobile Ads SDK Forum Advisor]

Hi Ian,

Thank you for reaching out to us with your concern. We have seen this issue before and would suggest reaaching out to Apple and seeing what they will allow to get through the review process. From what we have seen, that this also seems to be very dependant on who is reviewing the release. As sometimes it has fottne through and sometime it has not. From what I am seeing it would appear that you are not in violation of any rules, but that on Applkes side they are becoming more strict.

Regards,

William Pescherine Mobile Ads SDK Team

ref:_00D1U1174p._5004Q2QGMxG:ref

[idi...@gmail.com]

William,

Thanks for the response. I did contact them to ask them for clarification, and they responded with "..the custom prompt is not appropriate for the App Store, the modal alert should be the only prompt that is sufficient." and a screenshot of the first UMP, indicating that it isn't allowed. I will attempt again and report back, but it seems as though there has been a shift on this.

Ian

[Mobile Ads SDK Forum Advisor]

Hi Ian,

LEt me bring this also to my team, and see what they can see or if they know of some way we can work around with this. From what I have seen and heard it is really in Apples hands. As many people use these exact same things and most of them get through. Once in a while they do get stopped though.

[Mobile Ads SDK Forum Advisor]

Hello Ian,

Thanks for reaching out.

May I ask are you also implementing GDPR message? If you are implementing ATT request only, you can follow the instructions illustrated in this guide and find more information in this article.

Please let me know if you have any questions.


Regards,
Joshua

 

ref:_00D1U1174p._5004Q2QGMxG:ref

[idi...@gmail.com]

Thanks Joshua. I'm not implementing GDPR message. I'm following Google's implementation guides, and displaying an ATT pre-modal using Google's Funding Choices. It's this first modal that Apple will not allow.

[Mobile Ads SDK Forum Advisor]

Hello Ian,

Thank you for your response.

To help with our investigation, would you please provide the below information:

• Publisher ID
• App ID
• Sample project for the GDPR implementation (or code snippet)

In addition, are you implementing the UMP SDK ?