-
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: ITMS-91061: Missing privacy manifest #3389
Comments
We have the manifest added for quite some time and even had a fix recently specifically for MacOS. Please show your pubspec yaml and lock file content to be sure that you really use the latest version. |
Here are pubspec.yaml and pubspec.lock:
|
I think I know what the issue may be, the line of the privacy info refers only to
should be duplicated and be as well:
or remove the
|
I will prepare a PR |
7 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Platform
macOS
Plugin
connectivity_plus
Version
6.1.0
Flutter SDK
3.24.5
Steps to reproduce
I distributed macOS to the App Store. However, I received the following response to the Apple review email:
ITMS-91061: Missing privacy manifest - Your app includes “Contents/Frameworks/connectivity_plus.framework/Versions/A/connectivity_plus”, which includes connectivity_plus, an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements.
Code Sample
No response
Logs
Flutter Doctor
Checklist before submitting a bug
flutter pub upgrade
flutter clean
The text was updated successfully, but these errors were encountered: