weird behaviour report (storage permissions)

[barbiefan]

device: Huawei p40 lite
os: EMUI 10.1

I believe that android (or EMUI specifically, don't have any other flavor to test on) automatically removes empty folders which results in unexpected behaviour:

File operations (I've tested only Move) within folders which don't exist result in macrodroid asking for a permission for a root folder. I don't think that should happen. I get that it's trying to create the folder (probably), but asking for a root directory read+write permissions is a bit too much...
BUT! I wouldn't mind it since I trust macrodroid, but giving it rw permissions of root directory results.... in nothing. It just continuously asks for it.

any thoughts?

I was trying to organise a system that includes a TEMP folder, but when it flushes it disappears and macrodroid can't Move anything to it since it doesn't exist. And yes this is a thread specifically about the resulting situation (unnecessary permissions) and not about me trying to create a temporary folder

 

[MacroDroidDev]

I will fully confess the file related functionality is not exactly great, I have put off looking at it for some time as Google have been plotting to ruin Android further with more changes that meant any work I done could of been wasted. I will soon be forced to tackle another Android permissions nightmare where they are restricting the way files are accessed using the horrendous Android Storage Access Framework. When I am forced into this unwanted work I shall try and take a look at issues such as this and make it work better but it's well known that some vendors have weird implementations of file handling which can cause undesirable effects when using the supposedly universal Android Storage Access Framework.

 

[barbiefan]

I will fully confess the file related functionality is not exactly great, I have put off looking at it for some time as Google have been plotting to ruin Android further with more changes that meant any work I done could of been wasted. I will soon be forced to tackle another Android permissions nightmare where they are restricting the way files are accessed using the horrendous Android Storage Access Framework. When I am forced into this unwanted work I shall try and take a look at issues such as this and make it work better but it's well known that some vendors have weird implementations of file handling which can cause undesirable effects when using the supposedly universal Android Storage Access Framework.

oh, I see now
I feel for you, Google has been up to some weird stuff lately.
Thanks for the reply
nice work btw, keep up!