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
Does plugin require NSPhotoLibraryUsage ? #36
Comments
@pamir72 Can you provide a complete warning? Thanks |
ITMS-90683: Missing Purpose String in Info.plist - Your app's code references one or more APIs that access sensitive user data. The app's Info.plist file should contain a NSPhotoLibraryUsageDescription key with a user-facing purpose string explaining clearly and completely why your app needs the data. Starting Spring 2019, all apps submitted to the App Store that access user data are required to include a purpose string. If you're using external libraries or SDKs, they may reference APIs that require a purpose string. While your app might not use these APIs, a purpose string is still required. You can contact the developer of the library or SDK and request they release a version of their code that doesn't contain the APIs. Learn moreIt is strange, but the warning appeared after plug-in connected |
It's strange. Possible reasons for this
Can you provide your plist file and the pubspec file (If possible)? |
I didn't have NSPhotoLibraryUsageDescription in the info.plist and the code But without the plugin NSPhotoLibraryUsageDescription was not required |
pubspec: environment: dependencies: flutter_webview_plugin: ^0.3.8 |
@pamir72 |
I've set NSPhotoLibrariUsageDescription as Apple recommended and then never returned to this question. |
Did the app was deployed successfully after adding the permission? |
Yes |
Ok, thanks for the confirmation. Unfortunately, you faced this issue. |
Closing this issue as it is resolved |
When I uploaded my app into AppStore I got the refusal with warning NSPhotoLibraryUsageDescription is absent. Does plugin require NSPhotoLibraryUsage ?
The text was updated successfully, but these errors were encountered: