Broad Storage Access Issue (requestLegacyExternalStorage flag)

You must target Android 10 not eleven

Friend has same problem, he's targeting android 10 api 29

This message seems like out of timing, android 11 haven't reached OTA for many devices, so this message must be a warning, also they mention that developer need to clarify why they need full control for files in a form they mention is available, (don't know all details).

Quote from tk22

I have received this on all my the apps created with Clickteam fusion 2.5 and was wondering what is the correct way to solve this? and not have our apps removed! What do you suggest Fernando?

Hi!
Have you solved the issue? What permissions do your applications use?
(READ_EXTERNAL_STORAGE and/or WRITE_EXTERNAL_STORAGE)

I am just examining the contents of an apk file exported by Fusion.

AndroidManifest.xml unfortunately is impossible to read clearly or edit after exporting because some encoding.

Line four reads that the manifest requires permission "requestLegacyExternalStorage". Apparently the basic user can do nothing about it. I would fix the same problem by deleting the line if i were working with Android Studio project now.

The gaze turns to Clickteam. What are you going to do? Why is such permission used at all and can you remove that permission from the manifest with an emergency update to Fusion?

Please login to see this attachment.
Btw. Is Fusion Android Exporter AndroidManifest possible to customize by user?

requestLegacyExternalStorage is not a permission, this is a compatibility option.

AFAIK this option was required for Android 10 in order to continue using some file access API (I'm not Android developer, just what I quickly read, I could be wrong). If it was added in the Android runtime, then there is probably a valid reason.

Fernando is looking at the issue, more info soon.

If the changes are too important for the next build, perhaps we can remove this flag when it's not needed and keep it only when some features are needed. Just guessing. Again just wait for Fernando's input.

Fernando's answer: the code will be updated and this option will be removed in the next update, we'll have to drop support for Android 4.3 (not a problem). The next update will be released asap, the rest of the changes are almost ready.

Same nonsense here from google.

Actual info:
"We've detected that your app contains the requestLegacyExternalStorage flag in the manifest file of 1 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 May 5th, 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 May 5th

• 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."

This changes require a full android 11 device, now permission must be in manifest but define until a maxsdkwhich of course end before android 11 or minsdk in case of manage_storage , but old code will be read as it is in runtime, changes that developer must consider

An application can't use root folders and can't use defined folder, all data must be inside a scope that will be removed when uninstalling, side note if you are planning to keep information in user device must be kept in regular public folders.

Get folder or file exist as before can be unpredicted in some case when used for root files or folder in root folders

Any prediction of when the update comes out? Is there a possibility to release the update (even for Steam) before the 5th?

I'm getting this message too . We need to get the update at least 2 or 3 days before the deadline to have à minimum time to test and fix our apps.

hi all, I was just wondering the same thing in Discord and saw this thread.

any instructions on how to fix this? should we take 5th of may deadline serious?

a lot of people are confused about this messsage. Here is a thread on reddit (Please login to see this link.).

Answers from google seems to say that if you target api 29 it's ok... But i'm still woried about this deadline of the 5 may.

We are working on these changes BUT this message is just a warning, please note that you can find and read the new areas where you can save information to external storage. It is highly recommended if your application used external areas to implement a new version using API 29 where you move the information stored in the external storage to public directories or move it to the internal data storage. Remember also, that all data is deleted if the user uninstalls the application/game, so in this case, if you need to keep the data you should save it in a public directory or save it in the cloud.

I also received such a letter for all my games, although I have 29 APIs. Let's find a solution to this problem as soon as possible! I would not want any problems!