Direct access to media files (except audio files) using READ_MEDIA_IMAGES and/or READ_MEDIA_VIDEO (on Android 13+) will no longer be permitted for apps in the Play Store starting May 28, 2025 (at least not without an explicit review of the app and its core functionality by Google).
This issue, which should be another nail in Google's coffin, can only be circumvented with the help of SAF.
BTW, if your app contains this block somewhere
, all storage permissions are declared in the Manifest. @ewpatton
<uses-permission android:name="android.permission.READ_MEDIA_AUDIO"/>
<uses-permission android:name="android.permission.READ_MEDIA_VIDEO"/>
<uses-permission android:name="android.permission.READ_MEDIA_IMAGES"/>
<uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE"/>
<uses-permission android:maxSdkVersion="29" android:name="android.permission.WRITE_EXTERNAL_STORAGE"/>
At least READ_MEDIA_VIDEO and READ_MEDIA_IMAGES should not be declared automatically in the Manifest, but only when they are explicitly requested.
Note: If you use this block instead
only these storage permissions are declared:
<uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE"/>
<uses-permission android:maxSdkVersion="29" android:name="android.permission.WRITE_EXTERNAL_STORAGE"/>
I would of course prefer the latter and then request special storage permissions individually if necessary.
I will also add this part to my guide Some basics on Android storage system in due course.