Google has begun to send out emails to developers whose applications demand broad access to device storage. The email tells engineers that, beginning May fifth, they should educate Google why their application demands broad storage access or they will not be permitted to distribute refreshes that target Android 11.
Before Android 11, applications could demand broad access to a device’s storage by announcing the READ_EXTERNAL_STORAGE permission in their Manifest and requesting that the client award it. Numerous applications that had no legitimate need to peruse every one of the files stored on the device’s storage were requesting this permission, making Google slender capacity access consents with Android 11’s “Scoped Storage” changes. Nonetheless, for applications that truly need broader storage access, for example, document supervisors, Google urged them to keep on focusing on Android 10 (API level 29) and to demand “legacy” storage access by proclaiming requestLegacyExternalStorage=true in their Manifest.
Heritage access permits applications to have broad access to the gadget’s storage without being exposed to Scoped Storage restrictions. In any case, all applications that target Android 11 (API level 30) or more are dependent upon Scoped Storage limitations and can’t demand inheritance admittance to gadget stockpiling. All things being equal, they should demand another consent called MANAGE_EXTERNAL_STORAGE (appeared to the client as “All Files Access”) to be given wide storage access (barring a modest bunch of catalogs like/Android/information or/Android/obb).
Beginning November of 2021, all applications and application updates submitted to Google Play should target Android 11, implying that file manager apps and other applications that need more extensive stockpiling access should ultimately change to the Scoped Storage model and solicitation the All Files Access authorization. The lone issue is that Google at present doesn’t permit designers to demand the “All Files Access” permission. Google prior said it needs engineers to sign a Declaration Form before the application will be permitted on Google Play. This Declaration Form is expected to permit Google to remove applications that have no requirement for “All Files Access”, similar as how Google restricts access to the SMS, Call Log, and the QUERY_ALL_PACKAGES consents.
Despite the fact that Google reported their intention to make designers sign a Declaration Form right back in November of 2019, they actually haven’t made those Declaration Forms really accessible. The organization refered to labor force difficulties originating from the COVID-19 pandemic with regards to why they were conceding permitting applications focusing on Android 11 and mentioning “All Files Access” to be uploaded to Google Play. Google set the unknown date of “early 2021” for when they would open up the Declaration Form.
Presently at last, Google has begun to advise engineers when applications can really demand the “All Files Access” permission. The email sent to developers is confusingly phrased, however a recently distributed help page adds some lucidity. As indicated by the help page, applications that target Android 11 and request “All Files Access” can finally be transferred to Google Play beginning May 2021, which is probably when the Declaration Form goes live. For a rundown of allowed uses, special cases, and invalid uses of “All Files Access”, just as recommended elective APIs, visit Google’s support page.