READ_MEDIA_IMAGES and READ_MEDIA_VIDEO permissions in the app manifest

[Maiko_Herrmann]

I can no longer update my app on the Play Store; I receive this message:
Invalid use of photo and video access permissions
Apps that access photos only once or infrequently cannot include the READ_MEDIA_IMAGES and READ_MEDIA_VIDEO permissions in the app manifest. Instead, they need to migrate to a system photo picker.

If the app's core functionality requires broad access to these permissions, update the photo and video access permissions declaration.

---

But I don't use any kind of sharing, nor file access, much less images...
I've already removed extensions and nothing solves it... Could someone give me a tip on how to change these permissions? Because I don't use them...

[TIMAI2]

Possibly this ?

Help test nb202

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 [grafik], all storage permissions are declared in the M…

[Taifun]

@Maiko_Herrmann

But I don't use any kind of sharing, nor file access, much less images...

Which components and extensions are you using? For extensions always use the latest versions

Upload your app to https://unchive.kodular.io to get some statistics of your project and post the statistics overview

Taifun

[Maiko_Herrmann]

These two extensions appear in the report, but it's strange because I removed them from the project and apparently they're still there...

[Anke]

Did you read the post that @TimAi2 referred to carefully?

I have already pointed out several times—and not just in this post—that the FileScope = Shared block automatically declares all storage permissions in the Manifest. And this happens even when this block is disabled.

<uses-permission android:name="android.permission.READ_MEDIA_AUDIO"/>
<uses-permission android:name="android.permission.READ_MEDIA_VIDEO"/>
<uses-permission android:name="android.permission.INTERNET"/>
<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"/>

@ewpatton

---

If you don't use the File component, send me your aia via PM. I can take a look.

[Taifun]

@Taifun

Which components and extensions are you using?

@Taifun

Upload your app to https://unchive.kodular.io to get some statistics of your project and post the statistics overview

You forgot to post the statistics overview of your project
This would show us the components you are using

EDIT: the 2 extensions you are using don't seem to be the issue

Taifun

[Maiko_Herrmann]

Yes Anke, I read the post and from my understanding the problem would occur if I had the block declared in the project, but I don't have the "fileScope" block.

And also in the Project properties, "DefaultFileScope" is already set to Legacy.

[Maiko_Herrmann]

Sorry, I misunderstood. I thought the problem was only with the extensions.

[Anke]

These are the permissions of your app declared in the Manifest:

    <uses-permission android:name="android.permission.BLUETOOTH_SCAN"/>
    <uses-permission android:name="android.permission.INTERNET"/>
    <uses-permission android:name="android.permission.BLUETOOTH_ADMIN"/>
    <uses-permission android:name="android.permission.BLUETOOTH"/>
    <uses-permission android:name="android.permission.BLUETOOTH_CONNECT"/>
    <uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE"/>
    <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"/>

Since you have set DefaultFileScope = Legacy (for whatever reason), WRITE_EXTERNAL_STORAGE permission is being declared in this strange way. It should be:
<uses-permission android:maxSdkVersion="29" android:name="android.permission.WRITE_EXTERNAL_STORAGE"/>

---

So READ_MEDIA_IMAGES and READ_MEDIA_VIDEO is not declared in the Manifest. Are you absolutely sure that it is the same app you uploaded to the Play Developer Console? I don't think so.

[Taifun]

@Anke

So READ_MEDIA_IMAGES and READ_MEDIA_VIDEO is not declared in the Manifest.

@Maiko_Herrmann
Also we can see some Bluetooth permissions in the manifest
Did you drag a Bluetooth component into the working area without using it?
For unused components, remove those from the working area

Taifun

[Anke]

@Taifun

Did you drag a Bluetooth component into the working area without using it?
For unused components, remove those from the working area

[Maiko_Herrmann]

Bluetooth is used in the application; I believe the cause of the error is something related to the project properties.

[Maiko_Herrmann]

Anke, after reading your message, I decided to try changing the DefaultFileScope properties again and testing as: APP
The error persisted when trying to publish again.

Then I changed it back to: Legacy
And now the publication was accepted.

I believe something prevented the previous manifest from being updated.
Now it worked. Thank you all for your attention.

[Anke]

@Maiko_Herrmann

DefaultFileScope

I took a look at your app. DefaultFileScope plays no role in this.

[Maiko_Herrmann]

I can't tell you what else it could be, as that was the only change I made for the publication to be accepted.

[Anke]

Hmm, strange.