You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The native image picker built into iOS allows app developers to access the full image library, with all its metadata
On iOS11 this has changed.
UIImagePickerController runs as a separate process and does not require Photos permission at all. Only the assets user selects on UIImagePickerController gets delivered to the app, in a one-time read-only way.
Selecting a photo (e.g. you want to upload an existing picture to a social network)
Granting full access to the photo library (e.g. Dropbox or Google Photos to backup your complete library)
The new behaviour on iOS11 is kind of what you (and we all :) ) want.
For Selecting a photo there is no permission at all, as I mentioned above.
From now on, Apple should enforce the use of UIImagePickerController instead of custom image picker UIs.
For Granting full access to the photo library, it still works as before.
So, an extra permission layer to access the metadata, as you suggested, would be good.
Activity
KrauseFx commentedon Dec 14, 2017
That's awesome, thanks for letting me know 👍 I'll update the post accordingly
KrauseFx commentedon Dec 14, 2017
Just pushed an update, thanks again 🚀 35e1b6e
bjornworldwide commentedon Jan 4, 2019
An app shouldn't need permissions to save photos from an app to your photo library (and if it does, it should be specifically just for that).
It's insanely irresponsible on Apple's part that iOS still works this way.