Skip to content
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

Closed
pamir72 opened this issue Sep 25, 2019 · 11 comments
Closed

Does plugin require NSPhotoLibraryUsage ? #36

pamir72 opened this issue Sep 25, 2019 · 11 comments
Labels
app-deployment Some issues faced while deploying app to PlayStore or AppStore resolved The issue has been addressed in latest release.

Comments

@pamir72
Copy link

pamir72 commented Sep 25, 2019

When I uploaded my app into AppStore I got the refusal with warning NSPhotoLibraryUsageDescription is absent. Does plugin require NSPhotoLibraryUsage ?

@pamir72 pamir72 changed the title Is plugin requires NSPhotoLibraryUsage ? Does plugin require NSPhotoLibraryUsage ? Sep 25, 2019
@AmolGangadhare
Copy link
Owner

@pamir72
The plugin doesn't require NSPhotoLibraryUsageDescription.
Only NSCameraUsageDescription is required here.

Can you provide a complete warning?

Thanks

@pamir72
Copy link
Author

pamir72 commented Sep 25, 2019

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 more


It is strange, but the warning appeared after plug-in connected

@AmolGangadhare
Copy link
Owner

It's strange. Possible reasons for this

  1. Used NSPhotoLibraryUsageDescription in code but not added in info.plist
  2. Added in plist but the description is unclear or not sufficient.

Can you provide your plist file and the pubspec file (If possible)?
After that, we can figure it out.

@pamir72
Copy link
Author

pamir72 commented Sep 25, 2019

I didn't have NSPhotoLibraryUsageDescription in the info.plist and the code
After rejecting, I added a description into info.plist and uploaded app successfully

But without the plugin NSPhotoLibraryUsageDescription was not required

@pamir72
Copy link
Author

pamir72 commented Sep 25, 2019

pubspec:

environment:
sdk: ">=2.3.0 <3.0.0"

dependencies:
flutter:
sdk: flutter

flutter_webview_plugin: ^0.3.8
cupertino_icons: ^0.1.2
firebase_messaging: ^5.1.6
flutter_barcode_scanner: ^0.1.6
provider: ^3.1.0

@AmolGangadhare
Copy link
Owner

@pamir72
Did the issue is resolved?
I have gone through it several times and I was able to make it work without NSPhotoLibraryUsageDescription.

@pamir72
Copy link
Author

pamir72 commented Oct 6, 2019

I've set NSPhotoLibrariUsageDescription as Apple recommended and then never returned to this question.

@AmolGangadhare
Copy link
Owner

Did the app was deployed successfully after adding the permission?

@pamir72
Copy link
Author

pamir72 commented Oct 6, 2019

Yes

@AmolGangadhare
Copy link
Owner

Ok, thanks for the confirmation. Unfortunately, you faced this issue.
I'm marking this issue as resolved.

@AmolGangadhare AmolGangadhare added resolved The issue has been addressed in latest release. app-deployment Some issues faced while deploying app to PlayStore or AppStore labels Oct 6, 2019
@AmolGangadhare
Copy link
Owner

Closing this issue as it is resolved

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
app-deployment Some issues faced while deploying app to PlayStore or AppStore resolved The issue has been addressed in latest release.
Projects
None yet
Development

No branches or pull requests

2 participants