New android permissions appeared after update to 2022.3.38f1

Hello!
After updating to the version 2022.3.38f1 and changing target SDK to 34, the android build naw has permissions that weren’t there before:

android.permission.READ_EXTERNAL_STORAGE
android.permission.READ_PHONE_STATE

I did not update the plugins in the project, so these permissions were almost likely added by built-in packages. So I would like to know:

  1. what are these permissions needed for?
  2. is it safe to remove these permissions?

Thank you!

1 Like

User can prefer to save app or app data to external memory instead of built-in, for example screenshot that is initiated by the game — android.permission.WRITE_EXTERNAL_STORAGE.

But the user can also choose an external file to import it into the game — i.e. photo from gallery — android.permission.READ_EXTERNAL_STORAGE.

These 2 permissions I use in my AR Masker, but I can’t see here android.permission.READ_PHONE_STATE.

If I recall correctly, there were some changes in the SDK related to these permissions. Possibly, your external permission is mandatory now.


On the other side, there is an asset that called Native Gallery, and there is information about this:

C. Runtime Permissions

Beginning with 6.0 Marshmallow, Android apps must request runtime permissions before accessing certain services, similar to iOS. Note that NativeGallery doesn’t require any permissions for picking images/videos from Photos on iOS 11+, picking images/videos from Gallery on Android 34+ and saving images/videos to Gallery on Android 29+, so no permission dialog will be shown in these cases and the permission functions will return Permission.Granted.

2 Likes

I think I have not explained my questions in enough detail.
I have read the documentation and I understand that these permissions are needed for in a general sense.
What I would like to know is what they do for the functionality of the built-in components (analytics, IAP, etc.) of the engine and whether they can be removed.

1 Like

This isn’t caused by IAP, but I found this which seems similar:

If this is the same issue, it would be fixed by updating to 2022.3.48f1.
Could you try updating your editor to see if that helps?

2 Likes

Thank you!
I removed there permissions via the manifest. If after this there are problems with the app functionality I will try to update the editor.

Hello,
Did you encounter any errors using the manifest method? Leonid
We don’t want to update our editor unless necessary.