-
-
Notifications
You must be signed in to change notification settings - Fork 996
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
iOS privacy manifest required for several plugins #2447
Comments
@stuartmorgan does this affects me if I'm planning on using this plugin for developing an ios app? if yes, what workaround do you suggest? |
Hello! What is the status of the response to this matter? If an empty manifest is ok I may be able to create a PR for you too. |
Interesting that some of them are listed, but not all of them. I guess due to popularity. This PR from the Flutter team could be a good starting template for this: flutter/packages#5846 My understanding is that, since the plugins don't collect any data/send it anywhere, an empty manifest would be enough. Anyone else thinks the same? |
I am taking care of this, will open a separate PR per plugin. |
If any of the plugins in this repository use a Required Reason API, that would require a non-empty manifest even if the plugin doesn't have any data use to declare. |
Thanks @stuartmorgan Looking at the Flutter repo, the only plugin that used a Required Reason API was the Taking a quick look over the Required Reason API, I couldn't find any that is used here in the plus plugins:
In case we need to correct this in the future, the manifests will be in place, and can be updated accordingly. |
Privacy info has been added to all plugins. |
Has the new version not been released yet? |
There is some info regarding upcoming releases here: #2653 |
Plugin
Various
Use case
Several of this project's plugins are listed on on https://developer.apple.com/support/third-party-SDK-requirements/ as requiring a privacy manifest:
See flutter/flutter#131940 for context, but some kind of action will need to be taken.
If you've had any communication from Apple about what the expectations are for the plugins in terms of describing usage, that may be helpful as we work to understand the overall ecosystem impacts here.
Proposal
Add privacy manifests, and/or clarify with Apple about whether these plugins should actually be on the list.
The text was updated successfully, but these errors were encountered: