From 395e4a189be90ac5ce276153b570d4b143a8451a Mon Sep 17 00:00:00 2001
From: airkjw <airkjw@gmail.com>
Date: Mon, 15 Jun 2026 13:06:16 +0900
Subject: [PATCH] =?UTF-8?q?ios:=20fix=20ITMS-91064=20=E2=80=94=20set=20NSP?=
 =?UTF-8?q?rivacyTracking=3Dfalse,=20drop=20empty=20domains?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Apple rejected build 2: NSPrivacyTracking was true with an empty
NSPrivacyTrackingDomains. Listing AdMob's ad-serving domains would block
ads before ATT consent (same domains serve non-personalized ads), so we
set NSPrivacyTracking=false and remove the domains key — mirroring
Google's own AdMob SDK manifest (DeviceID data type stays tracking=true,
no top-level tracking/domains). Bump to build 3.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
---
 ios/Runner/PrivacyInfo.xcprivacy | 18 +++++++++++-------
 pubspec.yaml                     |  2 +-
 2 files changed, 12 insertions(+), 8 deletions(-)

diff --git a/ios/Runner/PrivacyInfo.xcprivacy b/ios/Runner/PrivacyInfo.xcprivacy
index 36a3c0e..5b0eb1b 100644
--- a/ios/Runner/PrivacyInfo.xcprivacy
+++ b/ios/Runner/PrivacyInfo.xcprivacy
@@ -2,14 +2,18 @@
 <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
 <plist version="1.0">
 <dict>
-	<!-- The app uses data for tracking (personalized ads, gated by the ATT
-	     prompt). Google's AdMob/Firebase SDKs ship their own privacy manifests
-	     that declare the tracking domains; this app-level manifest declares the
-	     app's own collected data and required-reason API usage. -->
+	<!-- NSPrivacyTracking is false at the app level and no tracking domains are
+	     listed. AdMob's ad-serving domains serve BOTH personalized and
+	     non-personalized ads, so listing them in NSPrivacyTrackingDomains would
+	     make iOS block ad requests before ATT consent (breaking ads for users
+	     who decline). This mirrors Google's own AdMob SDK privacy manifest,
+	     which marks the DeviceID data type tracking=true (below) yet sets no
+	     top-level NSPrivacyTracking and no domains. ATT consent is still
+	     requested at runtime via NSUserTrackingUsageDescription (Info.plist).
+	     Apple ITMS-91064 requires: if NSPrivacyTracking is true, the domains
+	     list must be non-empty — so we keep it false. -->
 	<key>NSPrivacyTracking</key>
-	<true/>
-	<key>NSPrivacyTrackingDomains</key>
-	<array/>
+	<false/>
 	<key>NSPrivacyCollectedDataTypes</key>
 	<array>
 		<dict>
diff --git a/pubspec.yaml b/pubspec.yaml
index b409fe3..64c2892 100644
--- a/pubspec.yaml
+++ b/pubspec.yaml
@@ -16,7 +16,7 @@ publish_to: 'none' # Remove this line if you wish to publish to pub.dev
 # https://developer.apple.com/library/archive/documentation/General/Reference/InfoPlistKeyReference/Articles/CoreFoundationKeys.html
 # In Windows, build-name is used as the major, minor, and patch parts
 # of the product and file versions while build-number is used as the build suffix.
-version: 1.0.0+2
+version: 1.0.0+3
 
 environment:
   sdk: ^3.9.2