Extension to download file(s) to ASD (app-specific directory) without WRITE permission

Yes, I guess so.

After downloading some images to ASD, when I try to set the source of image to the downloaded image path, it is asking for accessing permission.

The Image component requires READ permission. (→ Shouldn’t be like that .)
Therefore you must ask for READ permission (in this case).

See also here:

Blocks

1 Like

Okay, I see.
Thanks! :smiley:

Hello @bodymindpower
I used version 2 of you extension, download is ok and file is in the directory but when download completed get this error: Error 701: Unable to load /storage/emulated/0/Android/data/io.makeroid.companion/files/MyVideos/join.mp4

my block :point_down: :point_down: Thank you :hugs:

See here:

1 Like

This is what happens with path like mine

I copy to another path and It works perfect, I have to report something ? Thanks for the help

But I couldn’t test it because the Beta server doesn’t work at the moment. @pavi2410

2 Likes

Thanks for your time. :hugs: I have a question for you. So this error changes with the device? My app could work perfect or not according to the device which runs the app?
So I have to change method or I have to create a procedure to change the path if app get error? I’m right? Thanks

Use the EFile extension grom @vknow360 instead of the File component.

1 Like

Is it a problem to do similar extension but with acces to internal storage instead of external storage?

Not clear. What do you mean?

Ok I will take a look . :+1:t2: Thanks

From Android documentation:

Internal storage directories: These directories include both a dedicated location for storing persistent files, and another location for storing cache data. The system prevents other apps from accessing these locations, and on Android 10 (API level 29) and higher, these locations are encrypted. These characteristics make these locations a good place to store sensitive data that only your app itself can access.

I know that, but what does it have to do with this topic?

I just thought it’s a good place to ask about it as you dealt with the similar problem. Everyone is concerned about the external storage but the internal storage is missed in action.

I know that, but what does it have to do with this topic?

A lot of things. Is there any better place to ask about the internal storage? I would like to know if internal storage extension is hard to implement or there are other circumstances why you didn’t make it.

Yes, of course.

The assets (→ Internal Storage) are read-only.
The app package is saved in:

/data/data/<packageName>/

The only component that can write to the Private directory (→ internal storage, see here)

/data/user/0/<packageName>/files/

is the File component.
There is also no extension that does it.

I opend my android folder today and i saw this…
I have some doubt
Will the file component and your extension still work in Android 11.

→ Post #16

1 Like

The content of this dir is no longer visible with Android 11+ on the device:

/storage/emulated/0/Android/data/

So also the ASD is no longer visible with Android 11+, but the dir and files are there and accessible through your app.