📂Photo Library
Grant your app persistent access to the user's entire photo library.
What is Photo Library?
The Photo Library feature gives your app broad, persistent access to the user's entire photo library on both iOS and Android - including the Android READ_MEDIA_IMAGES and READ_MEDIA_VIDEO permissions, and the iOS NSPhotoLibraryUsageDescription (Photos) permission.
Enable it only if your app has a core function that requires this - a photo editor or gallery management app, for example (e.g. Instagram).
Google Play has been rejecting apps that request these permissions without this kind of core use case - including marketplace or classifieds apps that only need users to upload a few photos.
The device's standard system picker is always available to your app regardless of this setting. If you only need to let users upload a photo - a profile picture, a listing image, an attachment - you don't need to enable this feature at all; the system picker handles that without requiring broad permissions.
Natively Dashboard Setup
Open your Natively app dashboard and navigate to Features > Photo Library.
Toggle the feature to Enabled.
Select which Android permissions your app needs:
READ_MEDIA_IMAGES,READ_MEDIA_VIDEO, or both - only check the ones your app actually uses.Enter the Permission Description.
Click Save.
Rebuild your app(s).
You must rebuild your app for these changes to take effect.
How to use
Default to the system picker
For most apps - profile pictures, listing photos, message attachments - the standard file input picker covers it without needing this feature enabled at all. Only enable Photo Library if your app's core purpose depends on browsing or managing the user's full photo library.
Enable it for gallery and editing apps
If your app lets users browse their camera roll, select multiple photos at once, or manage albums, Photo Library is the right choice - the system picker isn't built for that kind of bulk or repeated access.
Only check the Android permissions your app actually uses
If your app only works with photos and never handles video, check READ_MEDIA_IMAGES alone rather than both - requesting permissions you don't use increases rejection risk.
Write a Permission Description that matches the actual use case
Since this permission grants broad access on both iOS and Android, be specific about why - vague descriptions like "to improve your experience" are a common cause of rejection. Explain the real feature, e.g. "We use your photo library to let you browse and select multiple images for your gallery".
Troubleshooting
Last updated