Repository navigation
|
My app was flagged or rejected on App Store (flutter) for this. Flutter plugin touches required-reason APIs with no PrivacyInfo.xcprivacy. Which guideline is this, how do I find it in my project, and how do I fix it before I resubmit? |
Replies: 1 comment
|
Guideline. 5.1.1 (App Store) Severity in the playbook. critical What triggers it. pubspec.yaml present, a plugin known to touch required-reason APIs (permission_handler, image_picker, geolocator, device_info_plus, package_info_plus, shared_preferences, sqflite, firebase_*) is a dependency, and no PrivacyInfo.xcprivacy exists anywhere in the project. What to search your code for. How to fix it. Add an app-level PrivacyInfo.xcprivacy and confirm each Flutter plugin ships its own (Flutter 3.19+ plugins mostly do). A missing plugin-level manifest is invisible to Apple unless the app manifest also declares that plugin reason code. The guard reports this as This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submission guard for App Store and Google Play review. Run |
Guideline. 5.1.1 (App Store)
Severity in the playbook. critical
What triggers it. pubspec.yaml present, a plugin known to touch required-reason APIs (permission_handler, image_picker, geolocator, device_info_plus, package_info_plus, shared_preferences, sqflite, firebase_*) is a dependency, and no PrivacyInfo.xcprivacy exists anywhere in the project.
What to search your code for.
pubspec.yaml,permission_handler,image_picker,firebase_How to fix it. Add an app-level PrivacyInfo.xcprivacy and confirm each Flutter plugin ships its own (Flutter 3.19+ plugins mostly do). A missing plugin-level manifest is invisible to Apple unless the app manifest also declares that plugin reason code.
The g…