<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: OrbitKit</title>
    <description>The latest articles on DEV Community by OrbitKit (@orbitkit).</description>
    <link>https://dev.to/orbitkit</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4258194%2Febf8e9fc-47c7-4193-a01b-9b79ec61fb0f.png</url>
      <title>DEV Community: OrbitKit</title>
      <link>https://dev.to/orbitkit</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/orbitkit"/>
    <language>en</language>
    <item>
      <title>iOS privacy policy generator — what to use, and what App Review asks of it</title>
      <dc:creator>OrbitKit</dc:creator>
      <pubDate>Sun, 22 Nov 2026 05:26:36 +0000</pubDate>
      <link>https://dev.to/orbitkit/ios-privacy-policy-generator-what-to-use-and-what-app-review-asks-of-it-28k2</link>
      <guid>https://dev.to/orbitkit/ios-privacy-policy-generator-what-to-use-and-what-app-review-asks-of-it-28k2</guid>
      <description>&lt;p&gt;You search "iOS privacy policy generator" because Apple won't let you submit your app without one, and you don't want to write 1,500 words of legalese from scratch. The first ten Google results are generic privacy-policy SaaS tools — Termly, iubenda, TermsFeed, Get Terms, plus a long tail of free templates.&lt;/p&gt;

&lt;p&gt;Most of them weren't built with App Review in mind.&lt;/p&gt;

&lt;p&gt;Not because the legal content is wrong. It's usually fine. The gap is that your privacy policy has to agree with three other things — your &lt;code&gt;Info.plist&lt;/code&gt; permission strings, your App Privacy Details questionnaire in App Store Connect, and your &lt;code&gt;PrivacyInfo.xcprivacy&lt;/code&gt; file — and a generic generator has no idea what any of those say. So your policy ends up declaring data practices that don't match what your app actually does.&lt;/p&gt;

&lt;p&gt;This post is what an iOS privacy policy actually has to do, why generic generators miss the mark, and what to look for in a generator that's specifically built for App Store submission.&lt;/p&gt;

&lt;p&gt;If you're working through your full submission, see the broader &lt;a href="https://orbitkit.io/blog/app-store-required-urls-and-files-for-ios-apps/" rel="noopener noreferrer"&gt;checklist of every URL and file Apple requires for an iOS App Store submission&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  What App Review actually checks
&lt;/h2&gt;

&lt;p&gt;Guideline 5.1.1(i) requires a privacy policy link in App Store Connect and inside the app, and Apple lists broken links and privacy policy issues among its most common review issues. The page must:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Load on a public URL&lt;/strong&gt; — no login wall, no IP allowlist, no expired SSL.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Be reachable as long as the app is in the App Store&lt;/strong&gt; — so the URL has to outlive your marketing site redesigns.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Disclose every category of data the app collects&lt;/strong&gt; — using terminology that maps to Apple's 16 &lt;a href="https://developer.apple.com/app-store/app-privacy-details/" rel="noopener noreferrer"&gt;App Privacy Details&lt;/a&gt; categories.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Match what your app actually does&lt;/strong&gt; — the policy has to agree with the permission strings in your &lt;code&gt;Info.plist&lt;/code&gt;, the answers in App Store Connect's privacy questionnaire, and the declarations in your bundled &lt;code&gt;PrivacyInfo.xcprivacy&lt;/code&gt;.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The fourth one is where generic generators fail. They generate plausible legalese, but they don't know whether your app uses &lt;code&gt;CLLocationManager&lt;/code&gt;, what your third-party SDKs do, or which Required Reasons APIs your binary touches. Your binary does, and that's what you're accountable for.&lt;/p&gt;

&lt;h2&gt;
  
  
  The 5 sections every iOS privacy policy needs
&lt;/h2&gt;

&lt;p&gt;Below are the five sections that have to exist in some form for an iOS, iPadOS, macOS, tvOS, or visionOS app's privacy policy to clear App Review without clarification requests.&lt;/p&gt;

&lt;h3&gt;
  
  
  1. Identity of the data collector
&lt;/h3&gt;

&lt;p&gt;Who is collecting the data — your legal entity name, contact email, optionally a postal address. Apps from individual developers can name themselves; apps from a company need the registered business name that matches the App Store Connect "Seller" field.&lt;/p&gt;

&lt;p&gt;Make sure the contact email actually receives mail: it's the address users (and Apple) will write to.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Categories of data collected, mapped to Apple's taxonomy
&lt;/h3&gt;

&lt;p&gt;Apple's 16 data categories from the &lt;a href="https://developer.apple.com/app-store/app-privacy-details/" rel="noopener noreferrer"&gt;App Privacy Details questionnaire&lt;/a&gt;:&lt;/p&gt;

&lt;p&gt;Contact Info · Health &amp;amp; Fitness · Financial Info · Location · Sensitive Info · Contacts · User Content · Browsing History · Search History · Identifiers · Purchases · Usage Data · Diagnostics · Surroundings · Body · Other Data&lt;/p&gt;

&lt;p&gt;Your privacy policy should declare each category your app or its SDKs collect, using these exact category names where natural. Generic generators use their own taxonomy ("Personal Information", "Technical Data", etc.) which doesn't map cleanly. App Review can match either, but the cleaner the mapping, the faster the approval.&lt;/p&gt;

&lt;p&gt;There's a &lt;a href="https://orbitkit.io/blog/ios-privacy-nutrition-labels-by-category/" rel="noopener noreferrer"&gt;category-by-category guide to what each one actually means&lt;/a&gt; if you want to know what counts as "Identifiers" vs "Diagnostics" vs "Other Data".&lt;/p&gt;

&lt;h3&gt;
  
  
  3. Purposes for each data type
&lt;/h3&gt;

&lt;p&gt;For every data category you declared in section 2, your policy must state &lt;em&gt;why&lt;/em&gt; you collect it. Apple's six purposes:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;App Functionality&lt;/li&gt;
&lt;li&gt;Analytics&lt;/li&gt;
&lt;li&gt;Product Personalization&lt;/li&gt;
&lt;li&gt;Developer's Advertising or Marketing&lt;/li&gt;
&lt;li&gt;Third-Party Advertising&lt;/li&gt;
&lt;li&gt;Other Purposes&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Same as the categories, your policy doesn't have to use these literal labels — but it has to declare a purpose that maps clearly to one of them. "We collect your email address" without a purpose statement gets bounced.&lt;/p&gt;

&lt;h3&gt;
  
  
  4. Account deletion (if your app supports account creation)
&lt;/h3&gt;

&lt;p&gt;This is the &lt;a href="https://developer.apple.com/app-store/review/guidelines/#data-collection-and-storage" rel="noopener noreferrer"&gt;Apple Guideline 5.1.1(v)&lt;/a&gt; requirement. As of June 30, 2022, any iOS or macOS app that supports account creation must also support account deletion — and the privacy policy must explain how to initiate it, what gets deleted, what gets retained, and on what timeline.&lt;/p&gt;

&lt;p&gt;The flow itself has to be in the app (not just on a web page), but the policy is where the legal disclosure lives. Apple's &lt;a href="https://developer.apple.com/support/offering-account-deletion-in-your-app/" rel="noopener noreferrer"&gt;official page on account deletion&lt;/a&gt; is the canonical reference. There's also a &lt;a href="https://orbitkit.io/blog/account-deletion-flow-guideline-5-1-1-v/" rel="noopener noreferrer"&gt;dedicated guide to designing the account deletion flow&lt;/a&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  5. Children &amp;amp; tracking disclosures
&lt;/h3&gt;

&lt;p&gt;If your app is in a kids category or you allow under-13 sign-ups, COPPA-specific language is required. If your app or any third-party SDK engages in &lt;a href="https://developer.apple.com/documentation/apptrackingtransparency" rel="noopener noreferrer"&gt;tracking as Apple defines it&lt;/a&gt;, the App Tracking Transparency permission requirement and tracking practices must be disclosed in the policy.&lt;/p&gt;

&lt;p&gt;Generic generators often skip these unless you explicitly toggle "this app is for children" or "we use third-party advertising," which most developers don't think to do during the wizard.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why most generators fall short for iOS
&lt;/h2&gt;

&lt;p&gt;Run through the major options against the four App-Review checks:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Generator&lt;/th&gt;
&lt;th&gt;Hosted URL&lt;/th&gt;
&lt;th&gt;Apple-mapped categories&lt;/th&gt;
&lt;th&gt;Account deletion section&lt;/th&gt;
&lt;th&gt;Privacy manifest awareness&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Termly&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;yes (paid plans)&lt;/td&gt;
&lt;td&gt;partial — uses generic categories&lt;/td&gt;
&lt;td&gt;configurable but not Apple-specific&lt;/td&gt;
&lt;td&gt;no&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;iubenda&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;yes (paid plans)&lt;/td&gt;
&lt;td&gt;partial&lt;/td&gt;
&lt;td&gt;configurable&lt;/td&gt;
&lt;td&gt;no&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;TermsFeed&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;not by default&lt;/td&gt;
&lt;td&gt;generic&lt;/td&gt;
&lt;td&gt;optional add-on clause&lt;/td&gt;
&lt;td&gt;no&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Free template generators&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;no — you self-host&lt;/td&gt;
&lt;td&gt;generic&lt;/td&gt;
&lt;td&gt;usually missing&lt;/td&gt;
&lt;td&gt;no&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;App-store-built tools&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;yes&lt;/td&gt;
&lt;td&gt;yes — designed around them&lt;/td&gt;
&lt;td&gt;yes — required path&lt;/td&gt;
&lt;td&gt;yes (link to manifest)&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The first four leave one or more of those four gaps open. The last category — generators built specifically for App Store compliance — covers all four because the tool's entire purpose is matching your declared data practices to what Apple expects to see.&lt;/p&gt;

&lt;h2&gt;
  
  
  What to look for in a privacy policy generator for iOS
&lt;/h2&gt;

&lt;p&gt;If you're picking a tool, the requirements that matter for fast App Review approval:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;The policy URL is hosted by the generator&lt;/strong&gt; — your obligation is "publicly accessible URL that doesn't break for the lifetime of the app." Self-hosting on a custom site means another piece of infrastructure to maintain.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The questionnaire maps 1:1 to Apple's App Privacy Details fields&lt;/strong&gt; — so what you fill out for the policy is the same thing you'll paste into App Store Connect. No translation step.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;It includes account deletion language by default&lt;/strong&gt; if you indicate the app has accounts.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;It outputs (or links to) a &lt;code&gt;PrivacyInfo.xcprivacy&lt;/code&gt; file&lt;/strong&gt; with the declared data categories — the policy and this file's &lt;code&gt;NSPrivacyCollectedDataTypes&lt;/code&gt; field describe the same data, so they should come from the same answers.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The hosted URL works on iPhone first&lt;/strong&gt; — that's where most people will open it.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Bonus: a generator that warns you when your declared practices conflict (e.g., "you said you collect email but didn't declare a purpose") catches errors before App Review does.&lt;/p&gt;

&lt;h2&gt;
  
  
  What about free templates?
&lt;/h2&gt;

&lt;p&gt;Free templates work &lt;em&gt;if&lt;/em&gt; you customize them carefully and self-host the result. The two reasons not to:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Hosting a static HTML file forever is not free.&lt;/strong&gt; GitHub Pages drifts, marketing sites get redesigned, custom domains expire. Apps get rejected on update because the URL that used to work now 404s. The whole point of a generator is moving that obligation off your plate.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;App Review treats unmodified templates as a yellow flag.&lt;/strong&gt; Reviewers have seen the same boilerplate text from every free generator. If your policy looks identical to one of those templates and your app's actual data practices are non-trivial, you'll get clarification requests asking for specifics.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The shortest path to a clean approval is a generator that produces a policy specific to your app's data practices, hosted somewhere that doesn't depend on you remembering to renew anything.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;I build &lt;a href="https://orbitkit.io/privacy-policy-generator/" rel="noopener noreferrer"&gt;OrbitKit&lt;/a&gt;, a generator built specifically for Apple-platform App Store submission — a guided policy editor built on Apple's 16 data categories, hosted policy URL on your own domain, a data-deletion page for apps with accounts, and a check that flags collected data with no stated purpose before App Review does. You can build and preview free. This post was &lt;a href="https://orbitkit.io/blog/ios-privacy-policy-generator/" rel="noopener noreferrer"&gt;originally published on the OrbitKit blog&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ios</category>
      <category>swift</category>
      <category>appstore</category>
      <category>privacy</category>
    </item>
    <item>
      <title>Universal Links not working? A debugging checklist for iOS</title>
      <dc:creator>OrbitKit</dc:creator>
      <pubDate>Sun, 22 Nov 2026 05:18:41 +0000</pubDate>
      <link>https://dev.to/orbitkit/universal-links-not-working-a-debugging-checklist-for-ios-1p91</link>
      <guid>https://dev.to/orbitkit/universal-links-not-working-a-debugging-checklist-for-ios-1p91</guid>
      <description>&lt;p&gt;The most frustrating thing about iOS Universal Links is that when they break, &lt;strong&gt;iOS gives you no error message&lt;/strong&gt;. The link just opens Safari. Your app doesn't launch. There's nothing in the console to tell you why.&lt;/p&gt;

&lt;p&gt;When that happens, the cause is almost always one of twelve things, once you've ruled out testing it wrong (step 0). This is the systematic checklist to walk through them, starting with the ones a single &lt;code&gt;curl&lt;/code&gt; command can settle. Most of the checks come straight from Apple's own troubleshooting note, &lt;a href="https://developer.apple.com/documentation/technotes/tn3155-debugging-universal-links" rel="noopener noreferrer"&gt;TN3155&lt;/a&gt;, and its &lt;a href="https://developer.apple.com/documentation/xcode/supporting-associated-domains" rel="noopener noreferrer"&gt;associated-domains documentation&lt;/a&gt;; the rest are hosting pitfalls those pages don't cover.&lt;/p&gt;

&lt;p&gt;Run through it top to bottom. Stop when something fails — that's almost certainly your problem.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Looking for the full list of files and URLs your iOS app needs before App Store submission, not just Universal Links? See &lt;a href="https://orbitkit.io/blog/app-store-required-urls-and-files-for-ios-apps/" rel="noopener noreferrer"&gt;the complete checklist of App Store required pages&lt;/a&gt;.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  0. First: confirm you're testing correctly
&lt;/h2&gt;

&lt;p&gt;Before you assume Universal Links are broken, make sure you're not just testing them wrong:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Don't paste the link into Safari's address bar.&lt;/strong&gt; Safari treats those as in-Safari navigations and won't trigger Universal Links. Send yourself the link via Notes, Messages, or Mail. Long-press it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;You should see "Open in &amp;lt;App Name&amp;gt;"&lt;/strong&gt; as the first option in the long-press menu. If you only see "Open in Safari", Universal Links aren't activating.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Test on a real device.&lt;/strong&gt; Apple's own test steps in TN3155 (the long-press in Notes, the Associated Domains diagnostics under Settings &amp;gt; Developer) are written for a device, so check there before you trust a result.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  1. Is the AASA file reachable at the canonical URL?
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl -I https://your-domain.com/.well-known/apple-app-site-association
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;You should see &lt;code&gt;HTTP/2 200&lt;/code&gt;. If you see &lt;code&gt;404&lt;/code&gt;, your file is missing or at the wrong path. If you see &lt;code&gt;301&lt;/code&gt; or &lt;code&gt;302&lt;/code&gt;, you have a redirect — see #2.&lt;/p&gt;

&lt;p&gt;Also test the legacy root path, which third-party validators check:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl -I https://your-domain.com/apple-app-site-association
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Modern iOS uses &lt;code&gt;/.well-known/&lt;/code&gt;, but some validators flag a missing root-path file as a setup error. Easiest fix: serve both.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Are there any redirects in the way?
&lt;/h2&gt;

&lt;p&gt;Apple's &lt;code&gt;swcd&lt;/code&gt; will not follow &lt;code&gt;301&lt;/code&gt; or &lt;code&gt;302&lt;/code&gt; responses for the AASA file. The file must be at the canonical URL with a direct &lt;code&gt;200&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;Common offenders:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;HTTP-to-HTTPS redirects.&lt;/strong&gt; Apple's CDN always requests HTTPS, so this rarely matters — but if you're testing in dev, make sure you're hitting HTTPS directly.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Trailing-slash redirects.&lt;/strong&gt; Some web servers redirect &lt;code&gt;/folder&lt;/code&gt; → &lt;code&gt;/folder/&lt;/code&gt;. Make sure the AASA URL doesn't get redirected.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Apex-to-www redirects&lt;/strong&gt; (or the reverse). If your DNS redirects &lt;code&gt;myapp.com&lt;/code&gt; → &lt;code&gt;www.myapp.com&lt;/code&gt;, the AASA file at &lt;code&gt;myapp.com/.well-known/apple-app-site-association&lt;/code&gt; will fail.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The fix: serve the file directly from the canonical URL, no redirect chain.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Is the Content-Type header exactly &lt;code&gt;application/json&lt;/code&gt;?
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl -I https://your-domain.com/.well-known/apple-app-site-association &lt;span class="o"&gt;|&lt;/span&gt; grep -i content-type
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;We recommend &lt;code&gt;content-type: application/json&lt;/code&gt;. Apple's current documentation doesn't name a Content-Type for this file; its earlier guides did (the archived &lt;a href="https://developer.apple.com/library/archive/documentation/UserExperience/Conceptual/Handoff/AdoptingHandoff/AdoptingHandoff.html" rel="noopener noreferrer"&gt;Handoff guide&lt;/a&gt; says the file "may be a JSON file with a MIME type of application/json"), so that's the type to serve. If you see something else:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;text/plain&lt;/code&gt; or &lt;code&gt;application/octet-stream&lt;/code&gt; — not the type Apple described; fix it before you look further. GitHub Pages picks the type from the file extension and &lt;a href="https://docs.github.com/en/pages/getting-started-with-github-pages/creating-a-github-pages-site#mime-types-on-github-pages" rel="noopener noreferrer"&gt;doesn't let you set one per file&lt;/a&gt;, so an extension-less file there needs a different host.&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;application/json; charset=utf-8&lt;/code&gt; — still JSON, but bare &lt;code&gt;application/json&lt;/code&gt; is the safe choice&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  4. Does the file have a &lt;code&gt;.json&lt;/code&gt; extension?
&lt;/h2&gt;

&lt;p&gt;It must not. The filename is literally &lt;code&gt;apple-app-site-association&lt;/code&gt; with no extension. If your editor or build process appended &lt;code&gt;.json&lt;/code&gt;, Apple's &lt;code&gt;swcd&lt;/code&gt; won't find it at the expected path.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl -I https://your-domain.com/.well-known/apple-app-site-association.json
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;If that returns 200 but the no-extension URL returns 404, that's your problem.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Is the JSON actually valid?
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl -s https://your-domain.com/.well-known/apple-app-site-association &lt;span class="o"&gt;|&lt;/span&gt; jq .
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;If &lt;code&gt;jq&lt;/code&gt; errors, your JSON is broken. Common issues:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Trailing commas in arrays or objects (legal in JS, illegal in JSON)&lt;/li&gt;
&lt;li&gt;Single quotes instead of double quotes&lt;/li&gt;
&lt;li&gt;Unquoted keys&lt;/li&gt;
&lt;li&gt;A BOM (byte-order mark) at the start of the file from Windows-edited files&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  6. Does the App ID format match exactly?
&lt;/h2&gt;

&lt;p&gt;The &lt;code&gt;appIDs&lt;/code&gt; array entries must be in &lt;code&gt;TEAMID.bundleid&lt;/code&gt; format:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="nl"&gt;"appIDs"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"ABCDE12345.com.yourcompany.yourapp"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;ul&gt;
&lt;li&gt;The Team ID is exactly 10 alphanumeric characters (uppercase letters and numbers).&lt;/li&gt;
&lt;li&gt;The bundle ID must match what's in your Xcode project's &lt;code&gt;Bundle Identifier&lt;/code&gt; field exactly. Case-sensitive.&lt;/li&gt;
&lt;li&gt;A common typo: using a lowercase Team ID. Apple's are always uppercase.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;You can find your Team ID in &lt;a href="https://developer.apple.com/account" rel="noopener noreferrer"&gt;Apple Developer → Membership&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  7. Does the Xcode &lt;code&gt;Associated Domains&lt;/code&gt; entitlement match?
&lt;/h2&gt;

&lt;p&gt;In Xcode, select your app target → &lt;strong&gt;Signing &amp;amp; Capabilities&lt;/strong&gt; → &lt;strong&gt;Associated Domains&lt;/strong&gt;. You should see:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;applinks:your-domain.com
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;ul&gt;
&lt;li&gt;No &lt;code&gt;https://&lt;/code&gt; or &lt;code&gt;http://&lt;/code&gt; prefix.&lt;/li&gt;
&lt;li&gt;No trailing slash.&lt;/li&gt;
&lt;li&gt;For subdomains, each one needs its own entry: &lt;code&gt;applinks:myapp.com&lt;/code&gt; and &lt;code&gt;applinks:www.myapp.com&lt;/code&gt; are different.&lt;/li&gt;
&lt;li&gt;If you removed the capability and re-added it, &lt;strong&gt;delete the app from your device and reinstall&lt;/strong&gt; — iOS caches the entitlement.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  8. Is Apple's CDN serving a stale version?
&lt;/h2&gt;

&lt;p&gt;Starting in iOS 14, devices don't fetch the AASA file directly. Apple's CDN does it on their behalf, then devices pull from there. Apple's associated-domains documentation puts numbers on it: its CDN "requests the &lt;code&gt;apple-app-site-association&lt;/code&gt; file for your domain within 24 hours", and "devices check for updates approximately once per week after app installation." So freshly-deployed AASA changes can take a while to propagate.&lt;/p&gt;

&lt;p&gt;To see what the CDN currently has for your domain, hit:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;https://app-site-association.cdn-apple.com/a/v1/your-domain.com
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;If this shows your &lt;em&gt;old&lt;/em&gt; file, the CDN hasn't refreshed yet. To bypass it during development, change your Xcode &lt;code&gt;Associated Domains&lt;/code&gt; entitlement from:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;applinks:your-domain.com
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;to:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;applinks:your-domain.com?mode=developer
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;That tells iOS to skip the CDN and fetch the file directly from your origin. &lt;strong&gt;Remove the &lt;code&gt;?mode=developer&lt;/code&gt; flag before submitting to the App Store&lt;/strong&gt; — it's a development-only mode.&lt;/p&gt;

&lt;h2&gt;
  
  
  9. Did iOS actually re-fetch the AASA after your change?
&lt;/h2&gt;

&lt;p&gt;A device doesn't pick up a changed AASA file right away: per TN3155, it downloads the file when the app is installed and then checks for updates about once a week. To force a refresh during development, &lt;strong&gt;delete and reinstall the app&lt;/strong&gt;. That's Apple's own instruction ("To download a newer version of the AASA file, reinstall the app"), and TN3155 adds that there is no way to invalidate the CDN's copy.&lt;/p&gt;

&lt;h2&gt;
  
  
  10. Is something blocking Apple's &lt;code&gt;AASA-Bot&lt;/code&gt; user agent?
&lt;/h2&gt;

&lt;p&gt;Apple's documentation tells you which user agents to let through: the App Clip setup page says to allow &lt;code&gt;AASA-Bot&lt;/code&gt; and &lt;code&gt;CFNetwork&lt;/code&gt;, and TN3155 says your server "should accept all user agent requests". Some bot-protection layers will block them:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Cloudflare&lt;/strong&gt; with "I'm Under Attack" mode or aggressive bot challenges. Allow &lt;code&gt;AASA-Bot&lt;/code&gt; explicitly, or exempt the AASA path from the challenge.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;AWS WAF&lt;/strong&gt; rules that challenge or block bots.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Custom IP allowlists.&lt;/strong&gt; Apple doesn't publish its CDN's address ranges (TN3155: they "cannot be guaranteed"), so the file has to be reachable from any IP.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Check your origin logs for &lt;code&gt;AASA-Bot&lt;/code&gt; requests. If you don't see them, something's blocking the bot before it reaches your app. TN3155's quick test is to request the file with a made-up user agent, &lt;code&gt;curl -A "MyAgent-Bot/*" https://your-domain.com/.well-known/apple-app-site-association&lt;/code&gt;, and confirm it still comes back.&lt;/p&gt;

&lt;h2&gt;
  
  
  11. Are your URL paths actually matching?
&lt;/h2&gt;

&lt;p&gt;If &lt;code&gt;swcd&lt;/code&gt; fetches the file successfully and your app entitlement is correct, but Universal Links &lt;em&gt;still&lt;/em&gt; don't open the app, the path patterns in your AASA file probably don't match the URL you're testing.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="nl"&gt;"components"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;
  &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nl"&gt;"/"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"/products/*"&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="p"&gt;]&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This matches &lt;code&gt;/products/123&lt;/code&gt; and &lt;code&gt;/products/&lt;/code&gt;, but &lt;strong&gt;not&lt;/strong&gt; &lt;code&gt;/products&lt;/code&gt; (no trailing slash). Common pitfalls:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;*&lt;/code&gt; matches zero or more characters, so &lt;code&gt;/products/*&lt;/code&gt; still needs the slash. Add a second component for &lt;code&gt;/products&lt;/code&gt;, or use &lt;code&gt;/products*&lt;/code&gt; if you don't mind it matching &lt;code&gt;/products-old&lt;/code&gt; too.&lt;/li&gt;
&lt;li&gt;Patterns are case-sensitive by default. &lt;code&gt;/Products/&lt;/code&gt; won't match &lt;code&gt;/products/*&lt;/code&gt; unless you set &lt;code&gt;"caseSensitive": false&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Query strings and fragments (&lt;code&gt;?utm_source=x&lt;/code&gt;, &lt;code&gt;#section&lt;/code&gt;) don't affect the match unless the component has its own &lt;code&gt;"?"&lt;/code&gt; or &lt;code&gt;"#"&lt;/code&gt; pattern.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For wide-open testing, use &lt;code&gt;"/": "*"&lt;/code&gt; (matches every path) to confirm the rest of your config works, then narrow down to specific patterns.&lt;/p&gt;

&lt;h2&gt;
  
  
  12. The "I just changed it and it stopped working" case
&lt;/h2&gt;

&lt;p&gt;If everything was fine yesterday and stopped working today, scan your recent changes for:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A web server config change (new redirect, new Cache-Control rule, new bot challenge)&lt;/li&gt;
&lt;li&gt;A DNS change (new CNAME, new Cloudflare proxy enabled)&lt;/li&gt;
&lt;li&gt;An SSL cert that expired or rotated to a different issuer&lt;/li&gt;
&lt;li&gt;A Cloudflare "Always Use HTTPS" toggle&lt;/li&gt;
&lt;li&gt;An app deploy that changed your build's bundle ID&lt;/li&gt;
&lt;li&gt;A new web framework (Next.js / Nuxt / etc.) that started routing the well-known path through application code instead of serving it as a static file&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This last one is sneaky: many web frameworks intercept all paths by default. They'll serve a 404 page (with &lt;code&gt;Content-Type: text/html&lt;/code&gt;) for &lt;code&gt;/.well-known/apple-app-site-association&lt;/code&gt; instead of letting your static file be found.&lt;/p&gt;

&lt;h2&gt;
  
  
  A condensed diagnostic flow
&lt;/h2&gt;

&lt;p&gt;If you want to walk through it fast:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="c"&gt;# 1. File reachable, 200, no redirect&lt;/span&gt;
curl -I https://your-domain.com/.well-known/apple-app-site-association

&lt;span class="c"&gt;# 2. Correct content-type&lt;/span&gt;
curl -I https://your-domain.com/.well-known/apple-app-site-association &lt;span class="o"&gt;|&lt;/span&gt; grep -i content-type

&lt;span class="c"&gt;# 3. Valid JSON, expected appIDs&lt;/span&gt;
curl -s https://your-domain.com/.well-known/apple-app-site-association &lt;span class="o"&gt;|&lt;/span&gt; jq .

&lt;span class="c"&gt;# 4. CDN sees the same content&lt;/span&gt;
curl -s https://app-site-association.cdn-apple.com/a/v1/your-domain.com &lt;span class="o"&gt;|&lt;/span&gt; jq .

&lt;span class="c"&gt;# 5. Branch's validator runs through everything&lt;/span&gt;
open https://branch.io/resources/aasa-validator/
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;If all five pass and Universal Links &lt;em&gt;still&lt;/em&gt; don't work, it's almost certainly the Xcode entitlement (#7) or a stale device cache (#9 — delete and reinstall).&lt;/p&gt;

&lt;h2&gt;
  
  
  Further reading
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;a href="https://developer.apple.com/documentation/technotes/tn3155-debugging-universal-links" rel="noopener noreferrer"&gt;Apple — TN3155: Debugging universal links&lt;/a&gt; (the official troubleshooting note)&lt;/li&gt;
&lt;li&gt;&lt;a href="https://developer.apple.com/documentation/xcode/supporting-universal-links-in-your-app" rel="noopener noreferrer"&gt;Apple — Supporting Universal Links in Your App&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://branch.io/resources/aasa-validator/" rel="noopener noreferrer"&gt;Branch — AASA Validator&lt;/a&gt; (free third-party validator)&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;&lt;em&gt;I run &lt;a href="https://orbitkit.io/features/" rel="noopener noreferrer"&gt;OrbitKit&lt;/a&gt;, which hosts your AASA file with every server-side gotcha in this checklist handled by default — served at both paths, &lt;code&gt;application/json&lt;/code&gt; enforced, zero redirects, auto-SSL, no bot-challenge layer, 128 KB size guard, and the file generated from a typed config so there are no JSON syntax errors. This post was &lt;a href="https://orbitkit.io/blog/universal-links-debugging-checklist/" rel="noopener noreferrer"&gt;originally published on the OrbitKit blog&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ios</category>
      <category>swift</category>
      <category>debugging</category>
      <category>apple</category>
    </item>
    <item>
      <title>How to fix ITMS-91053 — a complete guide to PrivacyInfo.xcprivacy for iOS</title>
      <dc:creator>OrbitKit</dc:creator>
      <pubDate>Sun, 22 Nov 2026 05:17:59 +0000</pubDate>
      <link>https://dev.to/orbitkit/how-to-fix-itms-91053-a-complete-guide-to-privacyinfoxcprivacy-for-ios-20mc</link>
      <guid>https://dev.to/orbitkit/how-to-fix-itms-91053-a-complete-guide-to-privacyinfoxcprivacy-for-ios-20mc</guid>
      <description>&lt;p&gt;You uploaded a build to App Store Connect. The processing-complete email arrives. You open it expecting a green check, and instead you see:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;ITMS-91053: Missing API declaration — Your app's code in the "YourApp" file references one or more APIs that require reasons, including the following API categories: NSPrivacyAccessedAPICategoryUserDefaults. While the API(s) are recognized, no API reasons have been provided.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;You haven't shipped this build. It's stuck in App Store Connect with a blocker. Submission window slipping by the hour.&lt;/p&gt;

&lt;p&gt;This is the systematic guide for getting unstuck — what &lt;code&gt;ITMS-91053&lt;/code&gt; actually means, how to identify which APIs in your binary trigger it, and the precise &lt;code&gt;PrivacyInfo.xcprivacy&lt;/code&gt; declarations to ship.&lt;/p&gt;

&lt;p&gt;&lt;code&gt;PrivacyInfo.xcprivacy&lt;/code&gt; is one of about a dozen things Apple's review process verifies — see &lt;a href="https://orbitkit.io/blog/app-store-required-urls-and-files-for-ios-apps/" rel="noopener noreferrer"&gt;every URL and file Apple requires for an iOS App Store submission&lt;/a&gt; for the full submission checklist.&lt;/p&gt;

&lt;h2&gt;
  
  
  What &lt;code&gt;ITMS-91053&lt;/code&gt; actually checks
&lt;/h2&gt;

&lt;p&gt;Since May 1, 2024, App Store Connect doesn't accept an app that uses a "Required Reason API" unless its &lt;code&gt;PrivacyInfo.xcprivacy&lt;/code&gt; file declares which categories it uses and why. There are exactly five categories:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;NSPrivacyAccessedAPICategoryUserDefaults&lt;/code&gt;&lt;/strong&gt; — &lt;code&gt;NSUserDefaults&lt;/code&gt; / &lt;code&gt;UserDefaults&lt;/code&gt; reads and writes&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;NSPrivacyAccessedAPICategoryFileTimestamp&lt;/code&gt;&lt;/strong&gt; — file modification, creation, attribute timestamps&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;NSPrivacyAccessedAPICategorySystemBootTime&lt;/code&gt;&lt;/strong&gt; — &lt;code&gt;systemUptime&lt;/code&gt; and related boot-time APIs&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;NSPrivacyAccessedAPICategoryDiskSpace&lt;/code&gt;&lt;/strong&gt; — available / total disk space queries&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;NSPrivacyAccessedAPICategoryActiveKeyboards&lt;/code&gt;&lt;/strong&gt; — current input method / keyboard list&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;When you submit a build, Apple's static analyzer scans your bundled binary for symbols from those five categories. For every category it finds, it checks whether your manifest declares that category with a valid reason code. If not — &lt;code&gt;ITMS-91053&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;The related error is &lt;strong&gt;&lt;code&gt;ITMS-91055: Invalid API reason declaration&lt;/code&gt;&lt;/strong&gt; — same analyzer, same scan, but the manifest declared a reason code that's invalid for the category. (Each category has its own set of reason codes; using a &lt;code&gt;UserDefaults&lt;/code&gt; reason on a &lt;code&gt;FileTimestamp&lt;/code&gt; declaration is a common mistake.)&lt;/p&gt;

&lt;h2&gt;
  
  
  Why this catches indie developers off guard
&lt;/h2&gt;

&lt;p&gt;The static analyzer runs at &lt;em&gt;submission&lt;/em&gt; time. You can't catch the rejection in TestFlight, in your CI, or with &lt;code&gt;xcodebuild&lt;/code&gt;. You only find out after upload, after the queue, when the email arrives. Indie developers regularly lose 1–2 days to this loop.&lt;/p&gt;

&lt;p&gt;There's no warning in Xcode. There's no compiler error. Your build runs perfectly. The first time you find out is mid-release.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 1: Identify which APIs in your binary trigger the rejection
&lt;/h2&gt;

&lt;p&gt;The rejection email lists the categories. Read it carefully. The example above mentions &lt;code&gt;NSPrivacyAccessedAPICategoryUserDefaults&lt;/code&gt; — that's your starting point.&lt;/p&gt;

&lt;p&gt;To find &lt;em&gt;where&lt;/em&gt; in your code (or in a third-party SDK) the API is used, run &lt;code&gt;nm&lt;/code&gt; over your archived binary:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="c"&gt;# After archiving, find your .app inside the archive&lt;/span&gt;
&lt;span class="nv"&gt;APP&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"/path/to/Archives/YYYY-MM-DD/YourApp.xcarchive/Products/Applications/YourApp.app/YourApp"&lt;/span&gt;
nm &lt;span class="s2"&gt;"$APP"&lt;/span&gt; &lt;span class="o"&gt;|&lt;/span&gt; grep -E &lt;span class="s2"&gt;"(NSUserDefaults|UserDefaults\.standard|attributesOfItem|systemUptime|fileSystemAttributes|activeInputModes)"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;You'll see symbols like &lt;code&gt;_OBJC_CLASS_$_NSUserDefaults&lt;/code&gt; or method names that confirm the API is in your binary. Sometimes the call is from your own code (easy to fix); sometimes it's from a third-party SDK (need to check the SDK's privacy manifest).&lt;/p&gt;

&lt;p&gt;For SDKs specifically, check your &lt;code&gt;Podfile.lock&lt;/code&gt; or &lt;code&gt;Package.swift&lt;/code&gt; against the SDK vendor's release notes. Most major SDKs have shipped privacy manifests since 2024 — Firebase, Sentry, Stripe, Mixpanel, RevenueCat, Adjust, Branch, etc. If you're on an old SDK version, upgrading to the latest is usually the fix.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 2: Pick the right reason codes
&lt;/h2&gt;

&lt;p&gt;Each category has its own Apple-defined set of reason codes. You declare which reasons apply.&lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;code&gt;NSPrivacyAccessedAPICategoryUserDefaults&lt;/code&gt;
&lt;/h3&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Code&lt;/th&gt;
&lt;th&gt;Use this when...&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;CA92.1&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;You read/write &lt;code&gt;UserDefaults.standard&lt;/code&gt; for app-only data. &lt;strong&gt;Almost every app.&lt;/strong&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;1C8F.1&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;You read/write &lt;code&gt;UserDefaults(suiteName:)&lt;/code&gt; for an App Group shared with other apps you control.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;C56D.1&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;You're a third-party SDK wrapping &lt;code&gt;UserDefaults&lt;/code&gt; calls — only for SDK authors, not host apps.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;AC6B.1&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;You read the managed app configuration MDM sets (&lt;code&gt;com.apple.configuration.managed&lt;/code&gt;) or write feedback for MDM to query (&lt;code&gt;com.apple.feedback.managed&lt;/code&gt;).&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;If your app calls &lt;code&gt;UserDefaults.standard.set(_:forKey:)&lt;/code&gt; anywhere — and almost every app does — you need &lt;code&gt;CA92.1&lt;/code&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;code&gt;NSPrivacyAccessedAPICategoryFileTimestamp&lt;/code&gt;
&lt;/h3&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Code&lt;/th&gt;
&lt;th&gt;Use this when...&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;DDA9.1&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;You display a file's modification date in your UI. The data cannot be sent off-device.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;C617.1&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;You read file timestamps for files inside your app container, app group, or app's CloudKit container. &lt;strong&gt;A common case for indie apps.&lt;/strong&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;3B52.1&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;You read timestamps of files the user explicitly granted access to (document picker, file importer).&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;0A2A.1&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;SDK wrapping file-timestamp APIs — for SDK authors only.&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;If your app reads &lt;code&gt;attributesOfItem(atPath:)&lt;/code&gt; or &lt;code&gt;Date&lt;/code&gt; properties on &lt;code&gt;URLResourceValues&lt;/code&gt; for app-managed files, you need &lt;code&gt;C617.1&lt;/code&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;code&gt;NSPrivacyAccessedAPICategorySystemBootTime&lt;/code&gt;
&lt;/h3&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Code&lt;/th&gt;
&lt;th&gt;Use this when...&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;35F9.1&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;You measure elapsed time between in-app events or run timer calculations. Only the elapsed time between in-app events may be sent off-device.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;8FFB.1&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;You calculate absolute timestamps for events inside your app (e.g., UIKit or AVFAudio event times). The timestamps may leave the device; boot time may not.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;3D61.1&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;You include boot time in an optional bug report the user chooses to submit, shown prominently in the report.&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h3&gt;
  
  
  &lt;code&gt;NSPrivacyAccessedAPICategoryDiskSpace&lt;/code&gt;
&lt;/h3&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Code&lt;/th&gt;
&lt;th&gt;Use this when...&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;85F4.1&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;You display available disk space in your UI.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;E174.1&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;You verify sufficient disk space before writing files. &lt;strong&gt;Common in download-heavy apps.&lt;/strong&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;7D9E.1&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;You include disk-space info in optional bug reports the user explicitly submits.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;B728.1&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Health-research apps detecting low disk space affecting health-data collection.&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h3&gt;
  
  
  &lt;code&gt;NSPrivacyAccessedAPICategoryActiveKeyboards&lt;/code&gt;
&lt;/h3&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Code&lt;/th&gt;
&lt;th&gt;Use this when...&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;3EC4.1&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Your app &lt;em&gt;is&lt;/em&gt; a custom keyboard.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;54BD.1&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;You customize UI based on user's active keyboards (e.g., RTL/LTR layout switching).&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  Step 3: Build the manifest file
&lt;/h2&gt;

&lt;p&gt;Create a file named &lt;code&gt;PrivacyInfo.xcprivacy&lt;/code&gt;. The structure for a typical iOS app:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight xml"&gt;&lt;code&gt;&lt;span class="cp"&gt;&amp;lt;?xml version="1.0" encoding="UTF-8"?&amp;gt;&lt;/span&gt;
&lt;span class="cp"&gt;&amp;lt;!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"&amp;gt;&lt;/span&gt;
&lt;span class="nt"&gt;&amp;lt;plist&lt;/span&gt; &lt;span class="na"&gt;version&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"1.0"&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&lt;/span&gt;
&lt;span class="nt"&gt;&amp;lt;dict&amp;gt;&lt;/span&gt;
    &lt;span class="nt"&gt;&amp;lt;key&amp;gt;&lt;/span&gt;NSPrivacyTracking&lt;span class="nt"&gt;&amp;lt;/key&amp;gt;&lt;/span&gt;
    &lt;span class="nt"&gt;&amp;lt;false/&amp;gt;&lt;/span&gt;
    &lt;span class="nt"&gt;&amp;lt;key&amp;gt;&lt;/span&gt;NSPrivacyCollectedDataTypes&lt;span class="nt"&gt;&amp;lt;/key&amp;gt;&lt;/span&gt;
    &lt;span class="nt"&gt;&amp;lt;array&amp;gt;&lt;/span&gt;
        &lt;span class="c"&gt;&amp;lt;!-- one entry per data type your app collects --&amp;gt;&lt;/span&gt;
    &lt;span class="nt"&gt;&amp;lt;/array&amp;gt;&lt;/span&gt;
    &lt;span class="nt"&gt;&amp;lt;key&amp;gt;&lt;/span&gt;NSPrivacyAccessedAPITypes&lt;span class="nt"&gt;&amp;lt;/key&amp;gt;&lt;/span&gt;
    &lt;span class="nt"&gt;&amp;lt;array&amp;gt;&lt;/span&gt;
        &lt;span class="c"&gt;&amp;lt;!-- UserDefaults, almost every app needs this --&amp;gt;&lt;/span&gt;
        &lt;span class="nt"&gt;&amp;lt;dict&amp;gt;&lt;/span&gt;
            &lt;span class="nt"&gt;&amp;lt;key&amp;gt;&lt;/span&gt;NSPrivacyAccessedAPIType&lt;span class="nt"&gt;&amp;lt;/key&amp;gt;&lt;/span&gt;
            &lt;span class="nt"&gt;&amp;lt;string&amp;gt;&lt;/span&gt;NSPrivacyAccessedAPICategoryUserDefaults&lt;span class="nt"&gt;&amp;lt;/string&amp;gt;&lt;/span&gt;
            &lt;span class="nt"&gt;&amp;lt;key&amp;gt;&lt;/span&gt;NSPrivacyAccessedAPITypeReasons&lt;span class="nt"&gt;&amp;lt;/key&amp;gt;&lt;/span&gt;
            &lt;span class="nt"&gt;&amp;lt;array&amp;gt;&lt;/span&gt;
                &lt;span class="nt"&gt;&amp;lt;string&amp;gt;&lt;/span&gt;CA92.1&lt;span class="nt"&gt;&amp;lt;/string&amp;gt;&lt;/span&gt;
            &lt;span class="nt"&gt;&amp;lt;/array&amp;gt;&lt;/span&gt;
        &lt;span class="nt"&gt;&amp;lt;/dict&amp;gt;&lt;/span&gt;
        &lt;span class="c"&gt;&amp;lt;!-- File timestamps, if you read file metadata --&amp;gt;&lt;/span&gt;
        &lt;span class="nt"&gt;&amp;lt;dict&amp;gt;&lt;/span&gt;
            &lt;span class="nt"&gt;&amp;lt;key&amp;gt;&lt;/span&gt;NSPrivacyAccessedAPIType&lt;span class="nt"&gt;&amp;lt;/key&amp;gt;&lt;/span&gt;
            &lt;span class="nt"&gt;&amp;lt;string&amp;gt;&lt;/span&gt;NSPrivacyAccessedAPICategoryFileTimestamp&lt;span class="nt"&gt;&amp;lt;/string&amp;gt;&lt;/span&gt;
            &lt;span class="nt"&gt;&amp;lt;key&amp;gt;&lt;/span&gt;NSPrivacyAccessedAPITypeReasons&lt;span class="nt"&gt;&amp;lt;/key&amp;gt;&lt;/span&gt;
            &lt;span class="nt"&gt;&amp;lt;array&amp;gt;&lt;/span&gt;
                &lt;span class="nt"&gt;&amp;lt;string&amp;gt;&lt;/span&gt;C617.1&lt;span class="nt"&gt;&amp;lt;/string&amp;gt;&lt;/span&gt;
            &lt;span class="nt"&gt;&amp;lt;/array&amp;gt;&lt;/span&gt;
        &lt;span class="nt"&gt;&amp;lt;/dict&amp;gt;&lt;/span&gt;
    &lt;span class="nt"&gt;&amp;lt;/array&amp;gt;&lt;/span&gt;
&lt;span class="nt"&gt;&amp;lt;/dict&amp;gt;&lt;/span&gt;
&lt;span class="nt"&gt;&amp;lt;/plist&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Get the &lt;code&gt;NSPrivacyCollectedDataTypes&lt;/code&gt; declarations from your privacy nutrition label answers (App Store Connect's App Privacy section). Each data type entry needs four keys: &lt;code&gt;NSPrivacyCollectedDataType&lt;/code&gt;, &lt;code&gt;NSPrivacyCollectedDataTypeLinked&lt;/code&gt;, &lt;code&gt;NSPrivacyCollectedDataTypeTracking&lt;/code&gt;, &lt;code&gt;NSPrivacyCollectedDataTypePurposes&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;Apple's &lt;a href="https://developer.apple.com/documentation/bundleresources/app-privacy-configuration/nsprivacycollecteddatatypes/nsprivacycollecteddatatype" rel="noopener noreferrer"&gt;&lt;code&gt;NSPrivacyCollectedDataType&lt;/code&gt;&lt;/a&gt; and &lt;a href="https://developer.apple.com/documentation/bundleresources/app-privacy-configuration/nsprivacycollecteddatatypes/nsprivacycollecteddatatypepurposes" rel="noopener noreferrer"&gt;&lt;code&gt;NSPrivacyCollectedDataTypePurposes&lt;/code&gt;&lt;/a&gt; reference pages list every valid data type and purpose constant. There are 35 data types and 6 purposes; spell them exactly as Apple does (it's &lt;code&gt;NSPrivacyCollectedDataTypePhotosorVideos&lt;/code&gt;, lower-case "or"), because &lt;a href="https://developer.apple.com/documentation/bundleresources/describing-data-use-in-privacy-manifests" rel="noopener noreferrer"&gt;Describing data use in privacy manifests&lt;/a&gt; warns that Xcode won't generate a privacy report correctly from values that aren't listed. Leave out a top-level array you have nothing to put in: Apple's &lt;a href="https://developer.apple.com/documentation/technotes/tn3181-debugging-invalid-privacy-manifest" rel="noopener noreferrer"&gt;TN3181&lt;/a&gt; lists an empty &lt;code&gt;NSPrivacyAccessedAPITypes&lt;/code&gt; array as invalid (&lt;code&gt;ITMS-91056&lt;/code&gt;).&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 4: Add the manifest to your Xcode project
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Drag &lt;code&gt;PrivacyInfo.xcprivacy&lt;/code&gt; into your Xcode project navigator.&lt;/li&gt;
&lt;li&gt;In the &lt;em&gt;Add to targets&lt;/em&gt; sheet, ensure the file is added to your app target. Add to additional targets (Watch app, App Clip, extensions) independently — each target needs its own manifest if it uses any required-reason API.&lt;/li&gt;
&lt;li&gt;Verify the file is in &lt;em&gt;Build Phases&lt;/em&gt; → &lt;em&gt;Copy Bundle Resources&lt;/em&gt; under your target.&lt;/li&gt;
&lt;li&gt;Build a fresh archive and re-submit.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Step 5: Verify before re-submitting
&lt;/h2&gt;

&lt;p&gt;Before uploading the new build, double-check the manifest is in the bundle:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="c"&gt;# After archiving&lt;/span&gt;
&lt;span class="nv"&gt;ARCHIVE&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"/path/to/Archives/YYYY-MM-DD/YourApp.xcarchive"&lt;/span&gt;
unzip -l &lt;span class="s2"&gt;"$ARCHIVE/Products/Applications/YourApp.app"&lt;/span&gt; &lt;span class="o"&gt;|&lt;/span&gt; grep PrivacyInfo
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;You should see &lt;code&gt;PrivacyInfo.xcprivacy&lt;/code&gt; listed at the root of the &lt;code&gt;.app&lt;/code&gt;. If you don't, the file isn't in the &lt;em&gt;Copy Bundle Resources&lt;/em&gt; phase — go back to step 4.&lt;/p&gt;

&lt;p&gt;You can also validate the file syntactically before submitting:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;plutil -lint PrivacyInfo.xcprivacy
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;code&gt;plutil&lt;/code&gt; only checks XML syntax, not Apple's enum values — so it'll happily approve a manifest with bogus reason codes. For semantic validation against Apple's allowlists, use a tool that knows the enums.&lt;/p&gt;

&lt;h2&gt;
  
  
  The fix that doesn't work: declaring everything
&lt;/h2&gt;

&lt;p&gt;A common temptation when stuck: declare every category with every reason code, hoping that "more declarations" makes the rejection go away. &lt;strong&gt;This produces &lt;code&gt;ITMS-91055&lt;/code&gt; (invalid declarations) instead of &lt;code&gt;ITMS-91053&lt;/code&gt; (missing).&lt;/strong&gt; Apple checks that:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Every category your binary uses is declared.&lt;/li&gt;
&lt;li&gt;Every category you declare is one of the five valid categories.&lt;/li&gt;
&lt;li&gt;Every reason code you declare is valid for its category.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Over-declaration with mismatched codes flips you from one error to another. Be precise.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where third-party SDKs fit in
&lt;/h2&gt;

&lt;p&gt;If you ship an SDK or include one that's been updated for privacy manifests, the SDK has its own &lt;code&gt;PrivacyInfo.xcprivacy&lt;/code&gt; inside its framework bundle. Apple aggregates the host app's manifest with all SDK manifests for the static analysis. So:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Your manifest declares what &lt;em&gt;your code&lt;/em&gt; does.&lt;/li&gt;
&lt;li&gt;Each SDK's manifest declares what &lt;em&gt;that SDK's code&lt;/em&gt; does.&lt;/li&gt;
&lt;li&gt;They don't overlap; together they cover the whole binary.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If your bundle still gets &lt;code&gt;ITMS-91053&lt;/code&gt; after you've declared everything from your own code, an old SDK version is the most likely culprit. Update SDKs before adding fake declarations to cover their gaps.&lt;/p&gt;

&lt;h2&gt;
  
  
  Apple references
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://developer.apple.com/documentation/bundleresources/privacy-manifest-files" rel="noopener noreferrer"&gt;Apple — Privacy manifest files&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://developer.apple.com/documentation/bundleresources/adding-a-privacy-manifest-to-your-app-or-third-party-sdk" rel="noopener noreferrer"&gt;Apple — Adding a privacy manifest to your app or third-party SDK&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://developer.apple.com/documentation/technotes/tn3183-adding-required-reason-api-entries-to-your-privacy-manifest" rel="noopener noreferrer"&gt;Apple — TN3183: Required Reason API entries&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://developer.apple.com/documentation/technotes/tn3184-adding-data-collection-details-to-your-privacy-manifest" rel="noopener noreferrer"&gt;Apple — TN3184: Data collection details&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;&lt;em&gt;I run &lt;a href="https://orbitkit.io/privacy-manifest-generator/" rel="noopener noreferrer"&gt;OrbitKit&lt;/a&gt;, which generates a validated &lt;code&gt;PrivacyInfo.xcprivacy&lt;/code&gt; (and the rest of Apple's required web URLs) from a structured config — it checks every reason code against its category at save time so you can't ship &lt;code&gt;ITMS-91055&lt;/code&gt;-bait by accident. This post was &lt;a href="https://orbitkit.io/blog/resolving-itms-91053-privacy-manifest-guide/" rel="noopener noreferrer"&gt;originally published on the OrbitKit blog&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ios</category>
      <category>swift</category>
      <category>appstore</category>
      <category>privacy</category>
    </item>
  </channel>
</rss>
