Android app rejected by Play Store for All Files Access when using MDM-deployed XML config filesSolved

Participant
Discussion
2 weeks ago May 27, 2026

Our Android app reads an XML configuration file that is deployed through MDM. The file is pushed to device storage, and the app currently requests All Files Access so it can read that XML file.

The public Play Store rejected the app because of the All Files Access permission. Is there a way to handle this with Hexnode without requesting that permission? Ideally, we would like the XML file to be pushed into the app-specific folder, for example: Android/data/<package>/files/…

That way, the app could read the file from its own directory instead of needing broad storage

Replies (1)

Marked SolutionPending Review
Hexnode Expert
2 weeks ago May 27, 2026
Marked SolutionPending Review

Hello @maatthew ,

For Android apps that are rejected by the public Play Store due to the All Files Access permission, there are two enterprise deployment options you can consider:

  1. Publish the app as a private app through Managed Google Play so it is available only to your managed organization.
  2. Upload the APK directly to Hexnode as an enterprise app and deploy it to devices using an app policy.

These approaches are commonly used for internal or enterprise apps that do not need to be distributed publicly through the Play Store.

Regarding the app-specific path under Android/data/<package>/files: on Android 11 and later, access to /Android/data and /Android/obb is restricted due to Google’s scoped storage changes. Hexnode cannot push files into /Android/data/<package>/files on Android 11+ because the restriction applies to third-party apps, including MDM agents.

MDM file deployment can still target accessible shared folders such as DCIM or Pictures, but it cannot bypass Android’s scoped storage restrictions for app-specific directories.

Regards,
Simon Scott
Hexnode UEM

Save