Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Starting 5 May, you must let us know why your app requires broad storage access (message from google play store) #48003

Closed
anisc opened this issue Apr 18, 2021 · 4 comments

Comments

@anisc
Copy link

anisc commented Apr 18, 2021

Godot version:
3.2.3

OS/device including version:
Android

Issue description:
I recieved a message from GooglePlay that I need to provide a reason why app contains the 'request Legacy External Storage" flag.

But it doesn't.

The only permission I have selected for export is "Internet".
What can cause this? and where can I find the "requestLegacyExternalStorage" flag ?

The full message from google play store:
`We've detected that your app contains the requestLegacyExternalStorage flag in the manifest file of one or more of your app bundles or APKs.

Developers with apps on devices running Android 11+ must use scoped storage to give users better access control over their device storage. To release your app on Android 11 or newer after 5 May, you must either:

Update your app to use more privacy-friendly best practices, such as the storage access framework or Media Store API
Update your app to declare the All files access (MANAGE_EXTERNAL_STORAGE) permission in the manifest file, and complete the All files access permission declaration in Play Console from 5 May
Remove the All files access permission from your app entirely

For apps targeting Android 11, the requestLegacyExternalStorage flag will be ignored. You must use the All files access permission to retain broad access.

Apps requesting access to the All files access permission without a permitted use will be removed from Google Play, and you won't be able to publish updates.`

@mortarroad
Copy link
Contributor

Duplicate of #47910. This should already be fixed.

@anisc
Copy link
Author

anisc commented Apr 18, 2021

@mortarroad is there a way to fix this with 3.2.3 ?
Do I have to build it by my self ?
does this means that releasing a game on android using the 3.2.3 is not recommended even tho it is the stable one ?
This seems to be fixed with 3.3

@mortarroad
Copy link
Contributor

mortarroad commented Apr 18, 2021

None that I know of.
The release of 3.3 will be very soon, and it should be backward compatible.
You can already try the release candidate: https://godotengine.org/article/release-candidate-godot-3-3-rc-9

Edit: I suppose that specific fix is not yet in the RC, never mind. I recommend waiting a few days for the next RC.
You can theoretically download the build with the fix already here: https://github.com/godotengine/godot/pull/47954/checks

@madmiraal
Copy link
Contributor

Closing as duplicate of #47910 and fixed in 3.3.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants