Apple's Privacy Manifest: 86 third-party SDKs Required to Add Privacy Manifest and Signature
Apple requires:
Apps uploaded to App Store Connect must be built with Xcode 15 for iOS 17, iPadOS 17, tvOS 17, or watchOS 10, starting April 29, 2024.
And adopts new requirements for some commonly used SDKs:
Starting in spring 2024, you must include the privacy manifest for any SDK listed below when you submit new apps in App Store Connect that include those SDKs, or when you submit an app update that adds one of the listed SDKs as part of the update.
Signatures are also required in these cases where the listed SDKs are used as binary dependencies.
Any version of a listed SDK, as well as any SDKs that repackage those on the list, are included in the requirement.
And the latest timeline for privacy manifests.
Starting May 1: You’ll need to include approved reasons for the listed APIs used by your app’s code to upload a new or updated app to App Store Connect. If you’re not using an API for an allowed reason, please find an alternative. And if you add a new third-party SDK that’s on the list of commonly used third-party SDKs, these API, privacy manifest, and signature requirements will apply to that SDK. Make sure to use a version of the SDK that includes its privacy manifest and note that signatures are also required when the SDK is added as a binary dependency.
This is the fourth part of a series on Privacy Manifests.
- What are Privacy Manifests
- How to Create a Privacy Manifest in Your iOS App
- How to Add a Privacy Manifest to SDK
- All 86 Requiring SDKs and Status in Supporting Privacy Manifest
- How to Generate Privacy Report and Update Privacy Nutrition Labels
All 86 Required SDKs and Status in Supporting Privacy Manifest
Apple provides a list of third-party SDKs that must include a privacy manifest and signature if they are used as binary dependencies.
This requirement applies if you want to submit new apps or an app update that adds those SDKs, starting from spring 2024.
There’s a lot of Facebook and Google SDKs here, including Firebase and Flutter.
Organizations or maintainers with the most SDKs on the list:
- Google: 24
- Flutter: 22
- Meta: 6
- OneSignal: 4
- Others: 30
Here is the list of all 86 third-party SDKs and their respective versions or status in supporting the privacy manifest.
Google SDKs
Flutter
SDK | Version or Status |
---|---|
Flutter image_picker_ios shared_preferences_ios path_provider path_provider_ios url_launcher url_launcher_ios video_player_avfoundation webview_flutter_wkwebview | Doing Determine how to handle privacy manifests in packages #131940 flutter/packages#5846 |
file_picker | Released on v8.0.0 iOS privacy manifest required #1418 |
flutter_inappwebview | Not Yet iOS privacy manifest required #1909 |
flutter_local_notification | Released on flutter_local_notifications-v16.3.1+1 iOS privacy manifest required #2177 [flutter_local_notifications] added privacy manifest #2221 |
fluttertoast | Doing iOS privacy manifest required #481 |
OrderedSet | No Repsonse from SDK Owner iOS privacy manifest required #41 |
connectivity_plus device_info_plus package_info package_info_plus share_plus | Released iOS privacy manifest required for several plugins #2447 |
geolocator_apple | Released on v2.3.7 Add privacy manifest for Apple #1360 |
sqflite | Released on v2.3.1 iOS privacy manifest required #1065 |
wakelock | No News |
Meta(Facebook)
SDK | Version or Status |
---|---|
FBAEMKit FBSDKCoreKit FBSDKCoreKit_Basics FBSDKLoginKit FBSDKShareKit | Released on v17.0.0 Feature Request: Support App Privacy Manifest #2264 |
hermes | Not Yet iOS App submission will require a privacy manifest and signature #1216 |
OneSignal SDKs
SDK | Version or Status |
---|---|
OneSignal OneSignalCore OneSignalExtension OneSignalOutcomes | Released on 5.0.5 Add 4 privacy manifests for the 4 importable targets #1334 |
Others SDKs
SDK | Version or Status |
---|---|
AFNetworking | deprecated project, wouldn't be added |
Alamofire | Released on v5.9.0 Add privacy manifest #3792 Fix Privacy Manifests, Add To Xcode Targets #3831 |
AppAuth | Released on v1.7.3 Add Privacy Manifest #807 Add privacy manifest #822 |
Capacitor | Released on v4.8.2,v5.7.3, v6.0.0-rc.1, but with wrong podspec file config feat: Add required Privacy Manifest file for iOS #7176 |
Charts | Released on v5.1.0 Add Privacy Manifest #5141 |
Cordova | Not Yet #1391 |
DKImagePickerController | Released on v4.3.7 Support App Privacy Manifests #718 |
DKPhotoGallery | No Response from SDK owner Support App Privacy Manifests #42 |
FMDB | Released on v2.7.8 |
grpcpp | Backport to v1.61.x [CocoaPods] Re-work how privacy manifests are exposed #35542 |
IQKeyboardManager IQKeyboardManagerSwift | Released on v7.0.0 & MR |
Kingfisher | Released on v7.10.0 |
Lottie | Released on v4.4.0 |
MBProgressHUD | Merged to master branch, but not released yet Apple Privacy Manifest #647 |
nanopb | Released on v0.3.9.10 Feature Request: Support App Privacy Manifest #910 |
OpenSSL | "I am sorry but we do not provide any binaries for iOS so we cannot provide these manifest files." OpenSSL iOS Privacy Manifest #23262 |
Reachability | Released on v5.2.0 Add Privacy Manifest #401 |
RealmSwift | Released on v10.46.0 Add a privacy manifest #8455 |
RxCocoa RxRelay RxSwift | Not Yet Any support/plan of Privacy Manifest? #2567 |
SDWebImage | Released on 5.18.7 |
SnapKit | Released on 5.7.1 Include privacy info for Cocoapods #798 |
Starscream | Released on v4.0.7 Privacy Manifest #993 |
SVProgressHUD | Add Privacy Manifest on 2.3.0 But with wrong cocoapods config PrivacyInfo.xcprivacy #1120 |
SwiftyGif | Released on v5.4.5 Adding privacy manifest #193 |
SwiftyJSON | Released on v5.0.2 Privacy manifest required by Apple #1143 |
Toast | Released on v4.1.1 |
UnityFramework | Apple’s privacy manifest policy requirements Release plan The solution to merge Privacy Manifests into a single file within Unity Framework (including relevant reasons from Unity Engine core) should be available in Unity 2021.3.35f1, 2022.3.18f1 and 2023.2.7f1 releases. The release notes will state "Add Apple Privacy Manifest support". |
Have any questions? Feel free to drop me a message on Twitter!