Google rejected my request to get all file access.

[dsnz]

Wait, why not just do what they asked?

Literally this could be a simple fix - edit the description for macrodroid in the play store, add a sentence or two at the very beginning about being able to move files or write to files on a schedule, OR SOMETHING like that, you know what i'm trying to say right??

Just try giving them EXACTLY & LITERALLY what they asked for, as stupid and patronizing as it is to have to do it, it would be worth the effort to try once more but with your app description updated to reflect how file operations are one of the core features of your app.

For example, here is the current macrodroid description in the app store but edited to include the information google is asking you to put in - you can literally copy and paste this into your app description on the playstore and then try resubmitting it because at that point, it will have met the requirements they're asking you to meet. Also be very polite as much as you can, bite your tongue, it's honestly worth a shot:


MacroDroid is the easiest way to automate tasks on your Android smartphone or tablet. Via the straightforward user interface MacroDroid makes it possible to build fully automated tasks that can run on schedules, within IF/THEN conditional statements, any number of constraints, and most importantly, the ability to automatically move & sort your files into folders of your choice -either whenever you want, or on a recurring schedule,automating the backing up of your most important files to multiple locations can give you peace of mind in case something should ever happen to your device.

A few examples of how MacroDroid can help you to get automated:

# Optimize your daily workflow on your phone; switch on bluetooth and start playing music when you enter your car. Or switch on WiFi when you are near your house.
# Reduce battery drain (like dimming your screen and switching Wifi off)
# Saving on roaming costs (automatically switch off your Data)
# Increasing safety during commuting by reading your incoming notifications (via Text to Speech) and sending automated responses via email or SMS
# Make custom sound and notification profiles.
# Remind you to do certain tasks using timers and stopwatches.

These are just a few examples out of limitless scenarios where MacroDroid can make your Android life a little easier. With only 3 simple steps this is how it works:

1. Select a Trigger.

The trigger is the cue for the macro to start. MacroDroid offers over 70 triggers to start your macro, i.e. location based triggers (like GPS, cell towers, etc), device status triggers (like battery level, app starting/closing), sensor triggers (like shaking, light levels, etc) and connectivity triggers (like Bluetooth, Wifi and Notifications).
Macros can be triggered automatically, but it is also possible to create a shortcut on the homescreen of your device or start using the unique and customizable Macrodroid sidebar.

2. Select the Actions you like to automate.

MacroDroid can perform over 100 different actions, that you typically would do by hand. Connect to your Bluetooth or Wifi device, select volume levels, speak text (like your incoming notifications or current time), start a timer, dim your screen, run Tasker plugin and many more.

3. Optionally: Configure Constraints.

Constraints help you to let the macro fire only when you want it to.
Living near your work, but only want to connect to your company's Wifi during work days? With a constraint you can select specific times or days that the macro can be invoked. MacroDroid offers 50 constraint types like: battery level, connected devices, time and day constraints, headphones inserted and many more.

MacroDroid is even compatible with Tasker and Locale plugins to expand the range of possibilities even further.

For beginners
===========

MacroDroid's unique interface offers a Wizard that guides step by step through the configuration of your first macros.
It is also possible to use an existing template from the template section and customize it to your needs.
The built-in forum allows you to get help from other users, allowing you to easy learn the ins and outs of MacroDroid.

For more experienced users
=======================

MacroDroid offers more comprehensive solutions like the use of Tasker and Locale plugins, system/user defined variables, scripts, intents, advance routing like IF, THEN, ELSE clauses, use of AND + ORs

The free version of MacroDroid allows you to configure up to 5 macros. The Pro version (a small one time fee) unleashes the full power of MacroDroid and lets you create an unlimited amount of macros.

Running in background
===================

If you have issues with the app not staying alive in the background please see http://dontkillmyapp.com

Wear OS
=======

MacroDroid includes a basic Wear OS companion app allowing you to launch macros from you watch.

Support
=======

Please use the in-app forum for all usage questions and feature requests, or access the forums via www.macrodroid.com.

To report bugs please use the built in 'Report a bug' option available via the settings.

Notices
======

This app uses the Device Administrator permission (BIND_DEVICE_ADMIN). This permission is used by the failed login trigger (nothing else) and will only be enabled if you explicitly give MacroDroid device admin access from within the app.

great and so complete my friend

just wondering.. are you a lawyer ? or your profession is law-related ?

 

[tenduramax2]

Fu©|{ Google....

Why not just keep a bare bones 'non-pro' version on the Playstore to comply with Google's never-ending bag of bullshit and yank the pro version and have it available for purchase right here on the website.

Now you make the G-machine happy (the permissions issue was probably denied by AI anyhow) while simultaneously making the app exactly how you want with no G-prick in the middle.

 

[MacroDroidDev]

Fu©|{ Google....

Why not just keep a bare bones 'non-pro' version on the Playstore to comply with Google's never-ending bag of bullshit and yank the pro version and have it available for purchase right here on the website.

Now you make the G-machine happy (the permissions issue was probably denied by AI anyhow) while simultaneously making the app exactly how you want with no G-prick in the middle.

Multiple reasons, but mainly because the Play Store is everything on Google and most users won't install apps from elsewhere. Also maintaining two different versions with significant differences in functionality will be a big overhead that I don't want to waste my time on.

 

[Qarboz]

I try to say my idea.
I don't know if it is feasible and how complicated it can be to create: create separate modules to be downloaded separately to integrate specific functions into Macrodroid. For example, the "MDFM" (Macrodroid File Manager) module has the purpose of navigating through directories and copying/moving/deleting files. It is unlikely that they will not grant the necessary permissions.
But maybe there would be a lot of rewriting work to be done...

 

[Volmark]

Multiple reasons, but mainly because the Play Store is everything on Google and most users won't install apps from elsewhere. Also maintaining two different versions with significant differences in functionality will be a big overhead that I don't want to waste my time on.

Why don't you want to implement a donating system to collect money for development of an extended version of MD? The most users will support you.

 

[MacroDroidDev]

I want to implement many, many things but the bounds of time force me to prioritize accordingly. I am grateful for the many users here who I'm sure would support me, but I won't ever ask for someone to pay twice and the amount of income from the hardcore users will be orders of magnitude smaller than the income from regular sales to the 99% of users who never do anything other than visit the Play Store.

 

[Volmark]

I want to implement many, many things but the bounds of time force me to prioritize accordingly. I am grateful for the many users here who I'm sure would support me, but I won't ever ask for someone to pay twice and the amount of income from the hardcore users will be orders of magnitude smaller than the income from regular sales to the 99% of users who never do anything other than visit the Play Store.

We are not talking about demanding additional amounts from users. We are talking about raising funds for those projects for which you do not have enough time and which you are forced to prioritize low.
MacroDroid is such a well thought and professionally developed system that many users perceive it not just as a tool for automating their gadgets, but as an interesting intellectual activity. In combination with a well-functioning forum where you are literally taken care of by more experienced users, it turns into an exciting intellectual exercise.
In comparison with the rubbish heap of Facebook and Google that has lost its boundaries, MacroDroid looks like a well balanced opportunity to play Lego and do something useful.
The method of collecting donations that is now more like asking for alms. I donated something impulsively, because I was charmed with how everything works, but if there was an opportunity to give funds to a certain project, I would feel like I was not a donor, but a participant of the development process. The main thing is that the project is well understood for me and I can see the process of collection of funds (some kind of visual counter that shows progress of accumulation of funds). If funds are accumulated you can hire developers who can do this work under your supervision.
Moreover, you can develop your highly prioritised projects as usual.
I recently tried a few plugins for Tasker by developer Marco Stornelli. Very interesting functionality that greatly expands the possibilities of MacroDroid. I would like them to be more integrated with the UI of MacroDroidand and to get them updated more often. Such kinds of projects I am ready to support economically. I believe that the majority of users agree with this concept

 

[Hemal Mondal]

After November MacroDroid must target sdk 30 to be allowed to update on the Play Store. I tried my best to get permission, but my request has been rejected because the file operation "is not a core feature of the app".

I think they would argue that any one feature of MacroDroid is not a core feature so it's pretty much impossible to win against that argument.

This is an annoying setback and will effect other features as well that take liberties with file storage permissions. It means I will have to spend a ton of time fixing any features that access files in any way (e.g record microphone, write to file etc.) and the locations these features can access will be extremely limited (basically only MacroDroid's data space). This is going to take my attention away for some time I'm afraid just to keep the app working as well as I can make it.

I will see if it's possible to keep the file operation action alive using the helper file, but it's quite a lot more complicated and lots of additional work.

Information about scoped storage is here:

Storage updates in Android 11 | Android Developers

developer.android.com

My rejection is below:

=================================================

Issue: Not a core feature


The feature you identified that is dependent on this permission does not appear to be critical to the core functionality of your app.

Core functionality is defined as the main purpose of the app. Without this core functionality, the app is "broken" or rendered unusable. The core functionality, as well as any core features that comprise this core functionality, must all be prominently documented and promoted in the app's description.

Please update your app so that the feature does not use this permission or ensure that the core functionality is prominently documented and promoted in the app's description and resubmit your app on Play Developer console.

Policy: All Files Access Permission

Files and directory attributes on a user's device are regarded as personal and sensitive user data subject to the Personal and Sensitive Information policy and the following requirements:

Apps should only request access to device storage which is critical for the app to function, and may not request access to device storage on behalf of any third-party for any purpose that is unrelated to critical user-facing app functionality.
Android devices running Android "R" (Android 11) or later, will require the MANAGE_EXTERNAL_STORAGE permission in order to manage access in shared storage. All apps that target R or later and request broad access to shared storage ("All files access") must successfully pass an appropriate access review prior to publishing. Apps allowed to use this permission must clearly prompt users to enable "All files access" for their app under "Special app access" settings. For more information on the R requirements, please see this help article.

• Read more about Use of All Files Access Permission
• See Android storage use cases and best practices
• Address this issue in the Play Console.

Bro iam useing marshmellow android 6.0.1 Samsung.

 

[FrameXX]

Bro iam useing marshmellow android 6.0.1 Samsung.

Target SDK doesn't mean lowest supported Android. MacroDroid supports lollipop 5.0 and higher so you are still in bounds and because you are on Android 6 this new Android limitation won't propably have affect on you.

 

[Jacob L]

Why don't you want to implement a donating system to collect money for development of an extended version of MD? The most users will support you.

It is already possible to donate from the side menu

 

[Jacob L]

Are we any nearer to all files?

 

[AhmedZ]

Why is Google such a **** about file permission? Makes no sense that an app needs permission to ask for permission.
Anyway, clear description and bullets should work... Else have to rebrand MacroDroid as MacroDroid Files or something..

 

[MacroDroidDev]

I have once again been trying to get all file access permission and once again keep getting the usual automated bot rejections. I have provided clear examples of how MacroDroid can be used to backup data and clean up data that is not accessible without all file permission.​

The rejection stupidly claims I can use the MediaStore API when my example youtube video that I sent them demonstrates clearing the files from the downloads folder.

I have appealed via the Google Play appeal process once more, so I await a further rejection from that. It seems clear to me that Google's arbitrary policy enforcement is detrimental to app developers and can favour one app over another. The fact that both Tasker and Automate have been granted this permission and MacroDroid has not is clear evidence of this. If I don't get any satisfaction from Google I hope to start making noise on whatever Android/tech sites I can to highlight this injustice.

With this in mind if people have any suggestions of sites to contact or channels that can get this issue noticed I would welcome your suggestions.

The generic rejection is below for your amusement:

Hi Developers at ArloSoft,​

After a recent review, we found that your app MacroDroid - Device Automation (com.arlosoft.macrodroid) is not compliant with one or more of our Developer Program Policies. See below for more information about your app's status and how to correct the issue.

App Status: Rejected​ Your app has been rejected and wasn't published due to the policy issue(s) listed below. If you submitted an update, the previous version of your app is still available on Google Play.

Issue found: Not a core feature​ The feature you identified that is dependent on this permission does not appear to be critical to the core functionality of your app. Core functionality is defined as the main purpose of the app. Without this core functionality, the app is "broken" or rendered unusable. The core functionality, as well as any core features that comprise this core functionality, must all be prominently documented and promoted in the app's description. Please update your app so that the feature does not use this permission or ensure that the core functionality is prominently documented and promoted in the app's description and resubmit your app on Play Developer console. Additionally, follow these steps to bring your app into compliance: Read more about Use of All Files Access Permission See Android storage use cases and best practices About the All Files Access Permission Policy​ Files and directory attributes on a user's device are regarded as personal and sensitive user data subject to the Personal and Sensitive User Data policy and the following requirements: Apps should only request access to device storage which is critical for the app to function, and may not request access to device storage on behalf of any third-party for any purpose that is unrelated to critical user-facing app functionality. Android devices running Android "R" (Android 11) or later, will require the MANAGE_EXTERNAL_STORAGE permission in order to manage access in shared storage. All apps that target R or later and request broad access to shared storage ("All files access") must successfully pass an appropriate access review prior to publishing. Apps allowed to use this permission must clearly prompt users to enable "All files access" for their app under "Special app access" settings. For more information on the R requirements, please see this help article.

Issue found: Need to use Media Store API or No Access to Files​ You have requested access to All Files Access permission but it appears that your app's core feature requires access to only Media Files or does not need access to any Files. In case your app needs access to Media Files, with the MediaStore API, apps can contribute and access media that's available on an external storage volume without the need for the access all files permission. Please update your app so that the feature uses Media Store APIs and remove All Files Access (MANAGE_EXTERNAL_STORAGE) permission. Additionally, follow these steps to bring your app into compliance: Read more about Use of All Files Access Permission See Android storage use cases and best practices and how to access media files from shared storage About the All Files Access Permission Policy​ Files and directory attributes on a user's device are regarded as personal and sensitive user data subject to the Personal and Sensitive User Data policy and the following requirements: Apps should only request access to device storage which is critical for the app to function, and may not request access to device storage on behalf of any third-party for any purpose that is unrelated to critical user-facing app functionality. Android devices running Android "R" (Android 11) or later, will require the MANAGE_EXTERNAL_STORAGE permission in order to manage access in shared storage. All apps that target R or later and request broad access to shared storage ("All files access") must successfully pass an appropriate access review prior to publishing. Apps allowed to use this permission must clearly prompt users to enable "All files access" for their app under "Special app access" settings. For more information on the R requirements, please see this help article.

 

[FrameXX]

Did you try to follow this proposal?

Google rejected my request to get all file access.

After November MacroDroid must target sdk 30 to be allowed to update on the Play Store. I tried my best to get permission, but my request has been rejected because the file operation "is not a core feature of the app". I think they would argue that any one feature of MacroDroid is not a core...

www.macrodroidforum.com

If I look on Play store description of Automate, I can clearly see that the file management is prominently mentioned in the description even though it's really not something that would be more important than other app features and deserve such a place in description, but it's here so Google doesn't complain.

EDIT: Read the MacroDroid description in English and it also contains mention about Automatic file backup, so it really seems to be some kind of other problem.

Automate


Tasker

MacroDroid

 

[Qarboz]

I have once again been trying to get all file access permission and once again keep getting the usual automated bot rejections. I have provided clear examples of how MacroDroid can be used to backup data and clean up data that is not accessible without all file permission.​

The rejection stupidly claims I can use the MediaStore API when my example youtube video that I sent them demonstrates clearing the files from the downloads folder.

I have appealed via the Google Play appeal process once more, so I await a further rejection from that. It seems clear to me that Google's arbitrary policy enforcement is detrimental to app developers and can favour one app over another. The fact that both Tasker and Automate have been granted this permission and MacroDroid has not is clear evidence of this. If I don't get any satisfaction from Google I hope to start making noise on whatever Android/tech sites I can to highlight this injustice.

With this in mind if people have any suggestions of sites to contact or channels that can get this issue noticed I would welcome your suggestions.

The generic rejection is below for your amusement:

Hi Developers at ArloSoft,​

After a recent review, we found that your app MacroDroid - Device Automation (com.arlosoft.macrodroid) is not compliant with one or more of our Developer Program Policies. See below for more information about your app's status and how to correct the issue.

App Status: Rejected​ Your app has been rejected and wasn't published due to the policy issue(s) listed below. If you submitted an update, the previous version of your app is still available on Google Play.

Issue found: Not a core feature​ The feature you identified that is dependent on this permission does not appear to be critical to the core functionality of your app. Core functionality is defined as the main purpose of the app. Without this core functionality, the app is "broken" or rendered unusable. The core functionality, as well as any core features that comprise this core functionality, must all be prominently documented and promoted in the app's description. Please update your app so that the feature does not use this permission or ensure that the core functionality is prominently documented and promoted in the app's description and resubmit your app on Play Developer console. Additionally, follow these steps to bring your app into compliance: Read more about Use of All Files Access Permission See Android storage use cases and best practices About the All Files Access Permission Policy​ Files and directory attributes on a user's device are regarded as personal and sensitive user data subject to the Personal and Sensitive User Data policy and the following requirements: Apps should only request access to device storage which is critical for the app to function, and may not request access to device storage on behalf of any third-party for any purpose that is unrelated to critical user-facing app functionality. Android devices running Android "R" (Android 11) or later, will require the MANAGE_EXTERNAL_STORAGE permission in order to manage access in shared storage. All apps that target R or later and request broad access to shared storage ("All files access") must successfully pass an appropriate access review prior to publishing. Apps allowed to use this permission must clearly prompt users to enable "All files access" for their app under "Special app access" settings. For more information on the R requirements, please see this help article.

Issue found: Need to use Media Store API or No Access to Files​ You have requested access to All Files Access permission but it appears that your app's core feature requires access to only Media Files or does not need access to any Files. In case your app needs access to Media Files, with the MediaStore API, apps can contribute and access media that's available on an external storage volume without the need for the access all files permission. Please update your app so that the feature uses Media Store APIs and remove All Files Access (MANAGE_EXTERNAL_STORAGE) permission. Additionally, follow these steps to bring your app into compliance: Read more about Use of All Files Access Permission See Android storage use cases and best practices and how to access media files from shared storage About the All Files Access Permission Policy​ Files and directory attributes on a user's device are regarded as personal and sensitive user data subject to the Personal and Sensitive User Data policy and the following requirements: Apps should only request access to device storage which is critical for the app to function, and may not request access to device storage on behalf of any third-party for any purpose that is unrelated to critical user-facing app functionality. Android devices running Android "R" (Android 11) or later, will require the MANAGE_EXTERNAL_STORAGE permission in order to manage access in shared storage. All apps that target R or later and request broad access to shared storage ("All files access") must successfully pass an appropriate access review prior to publishing. Apps allowed to use this permission must clearly prompt users to enable "All files access" for their app under "Special app access" settings. For more information on the R requirements, please see this help article.

I propose the idea again.
Can you create an extension (or module, or plugin, or expansion, or...) that installs separately from Macrodroid (but integrates into it) that has the purpose of managing files? If it were possible, I believe that Google cannot reject this app

 

[FrameXX]

I propose the idea again.
Can you create an extension (or module, or plugin, or expansion, or...) that installs separately from Macrodroid (but integrates into it) that has the purpose of managing files? If it were possible, I believe that Google cannot reject this app

That scatters MacroDroid into 3 different apps. Even better than 2! We can already use MacroDroid Helper to handle this problem as it does now. The only thing this would solve is that the plugin could be on Play Store and wouldn't need to be sideloaded.

 

[Jacob L]

I hope to start making noise on whatever Android/tech sites I can to highlight this injustice

Android Central, Android Police, XDA developers, r/degoogle and any newspaper outlet will pay you for it. Change.org https://petition.parliament.uk

 

[MacroDroidDev]

It seems like every time I try to get the app through with the new permission and it gets rejected, subsequent releases seem to take much longer to get through reviews. It's like the app gets flagged as needing a more thorough review for a while or something similar. This is playing havoc with my ability to rollout release and fixes quickly. I feel like it's a slap on the wrist for daring to ask for this permission!

I will try and reach out to some of these sites and see if anyone will help to raise awareness of the issue.

I may ultimately have to end up putting something in the helper file because I can't keep trying and failing as it's effecting my ability to work on and release the app.

 

[Jacob L]

Simple gallery on the play store has full files access

 

[MacroDroidDev]

Yes there are many conflicting examples where apps have gained access that seems to be outside of the allowed use cases.

This is the main frustration of such stupid policies, they are arbitrarily enforced and it can be effected by luck of who looks at it or influenced by who you know in Google.