iOS 27.2 adds a second ATT prompt in the EU. What to check

· 7 min read

#apple-dev

In iOS 27.2, the App Tracking Transparency prompt gets a second form in the EU: a full-page, expanded version. In five countries it is the only form you can show, and it comes with a new method and a rule that you cannot ask the same user again for a year.

The rule for when you need to ask does not change. What changes is what the user sees and what your code has to call.

What Apple announced

Apple's announcement from September 16 says that, beginning with iOS 27.2 and iPadOS 27.2, developers have the option to use an alternative version of the ATT system prompt in the EU. It also says the requirements for when you must seek permission to track users stay the same.

The option becomes an obligation in some places. Apple's wording: due to legal requirements, only the alternative version of the system prompt is available for apps distributed in Germany, France, Italy, Poland and Romania. The iOS 27.2 RC release notes say the same from the system side: the alternative prompt is required for users in those five countries.

So the question for your app is not "do I need to ask". It is "which prompt will my users get, and does my code ask in a way that supports it".

The new call

The existing requestTrackingAuthorization call stays. Apple's reference documents a new one for iOS 27.2.0 and later:

requestTrackingAuthorization(preferExpandedInterface:additionalInformationAction:completionHandler:)

Three parameters matter:

How the flag behaves depends on where the user is. Outside the EU, the method presents the system alert with your original NSUserTrackingUsageDescription, as before, and the new parameters have no effect. In the five countries above, the expanded prompt is shown regardless of what you set for preferExpandedInterface. In the rest of the EU, the flag is your option: Apple's reference lists these countries separately and says the full-page sheet is shown when preferExpandedInterface is true.

The two screens also differ in their buttons. The classic alert has "Ask App Not to Track" and "Allow". Apple's example image of the expanded sheet shows "Allow" and "Reject" instead.

An iPhone showing Apple's example of the expanded ATT sheet for a sample app named Example App. A text block headed App Explanation ends with a blue Additional Information link, and two full-width buttons at the bottom read Allow and Reject.
Apple's example of the expanded ATT sheet in the EU. Image: Apple

One more detail for the EU: the full-page sheet uses NSUserTrackingMarkdownUsageDescription if you define it. Apple's reference says it supports bold, italics, bullets and paragraphs.

Which ATT prompt a user sees in iOS 27.2 A decision flow. A box asks whether the user is in the EU. Outside the EU the classic system alert is shown and the new parameters are ignored. In Germany, France, Italy, Poland and Romania only the expanded prompt is shown. In other EU countries the preferExpandedInterface flag decides. After the user answers in the EU, the prompt is not shown again for one year. User in the EU? iOS 27.2 or later Classic alert new parameters ignored Expanded prompt required: DE FR IT PL RO Other EU: your call preferExpandedInterface User answers silent for a year no 1 of 5 other
Read left to right: the user's location picks the prompt, and an answer in the EU starts a one-year pause.

Three details that are easy to miss

The yearly re-ask. Apple's reference says that after the user responds, the system notes the date and does not allow the prompt to display again until a year passes. The privacy page words it as being able to re-prompt a user one year after the previous choice, regardless of whether that choice was to accept or reject. The RC release notes list this as part of the same feature: re-prompting on a yearly basis for EU users.

The practical effect is that a second call inside that year is not a retry. If your code asks on every launch until it sees authorized, a user in the EU who has answered will not see the prompt again for twelve months, whatever the answer was. If you want to ask again after a year, you need your own record of when and why, and a place in your flow where asking again makes sense.

The "Additional Information" button. When you pass a closure, the prompt shows "Additional Information". In Apple's example image it is a blue text link at the end of the explanation, not a button at the bottom next to "Allow" and "Reject". Apple's reference says that when the user taps it, the sheet dismisses without recording an answer, your closure runs, and the completion handler is called with notDetermined, so you have to call the method again to get a decision. Whatever your closure shows, usually your own explanation screen, has to lead somewhere: back to the prompt, or to an explicit "not now". If you want the button, plan the screen first. If you do not, pass nil.

The rename. The RC release notes list a Resolved Issue: the API name changed during the beta, and the Objective-C name changed too. Code or blog snippets written against an early 27.2 beta can fail to compile for that reason. Check the parameter labels against Apple's reference page, not against a snippet you found earlier.

What to check this week

  1. Look at where you call requestTrackingAuthorization. The sources I used do not say what the old call shows in the five required countries, so test that case rather than assume it. Decide whether you want the expanded form elsewhere in the EU too.
  2. If you adopt the new call, remember it is iOS 27.2.0 and later. Keep your old call for earlier systems, behind an availability check.
  3. Decide on the Additional Information button before you write code. Passing nil is a valid answer.
  4. Look for loops that re-ask. Under the one-year rule, a second request in the same year does not show anything.
  5. Check your NSUserTrackingUsageDescription. Outside the EU it is still the text users see in the system alert. For the full-page sheet in the EU, consider adding NSUserTrackingMarkdownUsageDescription, which supports bold, italics, bullets and paragraphs.
  6. Test on a real device or a configuration where you can confirm the region behavior, rather than assuming it from reading. The sources I used describe the behavior but I have no first-hand test of it.

Apple's wording is careful about one more thing, so I will be too: nothing in these sources says you have to design a new screen. The change is the prompt format, the five required countries and the yearly rule.

iOS 27.2 reached release candidate status on October 19, together with Xcode 27.2 RC. The final release date is not stated in the sources, so treat this as a "soon" and read the RC notes for the ATT section before your next build.

Sources