Which extension should I use?
@hammerhai Does my app work for you? Yes or no?
I’ll answer this, but first: did you test my app? If so, does it work?
No it doesn’t work, it asks a permission before “copying” whatever file is to be copied… I got to the permission part and closed your application because I was scared of such dialog.
Yes it works, I can see the picture in the file
It works definitely!
Where could be the problem to ask for WRITE permission at Screen.Initialize 
Thankfully I have the right one for you!
To see instructions on how the storage extension works with paths, view this post…
To download the storage extension, view the following post and open the “Original reply (includes v3.0.1 and v3.1.1)”…
No, when doing anything with files, the File component will ask for permissions REGARDLESS of it’s path.
Can you share aia for my reference
No, for the save method you need the relative path.
Here are my blocks for saving a text file and copy an image from the /Download folder to the ASD:
Again @kentleow1496, there is no need to feel rushed to pick which method best suits you, however, I definitely think your application would be better off not needing a pesky permission :)
i try to do now
Which permission does not have much impact on my application, the most important thing is that I can make the application work normally, because tomorrow I will have to conduct related tests with the government department
The File component will ask for the READ and WRITE permissions which aren’t needed for the external directories. If you don’t want to ask for the READ and WRITE permissions, you can relook over my previous response referencing the extension I recommended!
I know that, but that’s not the subject of our considerations here, only the question of whether it is possible to save to the ASD with the File component. And it does.
So you were wrong in your claim:
It is well known that the READ/WRITE permission problem can be avoided with the EFile extension. But this was not the question.
I already provided an extension that can be used.
Back then I would’ve been correct, but I do remember at one point being unable to save files to certain paths.
I love you, my application can save files normally
1 Like
I am really not a fan of the File component for these reasons:
- The really disturbing thing is the constant alternation between relative and absolute path.
- Copying from the assets does not work
- Permissions are also requested for the ASD (but this applies to many components, but I’m sure this will be fixed when Kodular targets Android 11, Aug 2021).
1 Like
Here are all blocks, where you can see that for the SaveFile method a relative path is needed, but for the Copy method you must set an absolute path. 
I hope that this (and the other points) will be adjusted / fixed with the next Kodular update.
→ @Kodular
1 Like
