Read this entire topic, and the links provided. Try out some of the examples, then maybe you will learn and understand how SAF works.
If you have a specific issue, then post your relevant blocks and explain the problem.
It is a complicated subject, necessitating a complex solution, and wording is there to avoid confusion with existing terms used elsewhere in AI2.
You may also want to research the subject; search the web for "android storage access framework" to learn more...
Can anyone make youtube videos about this extension in a way that any newbies can use it without spending too much time to learn the techniqal side of the extension?
okay. I can understand. But, there must be shortcut to understand this extension easily. Okay, I shall search on Google as well.
Is it necessary to use SAF blocks in app to upload files using FilePicker and to put it in GoogleSheet?
No, it all depends where your files are stored and if your app created them as to how you can access them.
Okay, leave me but think of upcoming newbies. It will be good if there is a precise article/tutorial-post in the below format.
TO GET BLOCKS TO LOAD FILES - CLICK THIS LINK.
TO GET BLOCKS TO DO XXXXXXX - CLICK THIS LINK.
TO GET BLOCKS TO DO YYYYYYYY - CLICK THIS LINK
TO GET BLOCKS TO DO ZZZZZZZZ - CLICK THIS LINK,
etc. etc.
If you or mit ai2 team provide precise blocks in the above format (in links), then new users don't need to understand what the SAF is, they simple use the right blocks in their project.
it is important users understand what they are doing, and why
You could be the one who prepares that tutorial for the community
Taifun
huhh , it took me 1 hour to find the right topic and get the link of .aix file finally. Thanks. I bookmarked it! 
Have you managed to upload files from phone using SAF extension? What is that .aix file?
Can the Author, update the extension with new words on the block so ordinary lay man can guess the flow of the blocks on SAF projects? It doesn't matter even if there are large text on the blocks.
Read this thread carefully and you will understand...
I know that. But, some one who understand this extension can definitely simplify it like any other extension.
I am planning to dedicate some time to understand this extension but later, not now.
So tell us what your problem exactly is.
And also read this:
Hi,
I have been all day long trying to understand this and finally got it working but I'd like to know if I can avoid the need to select the file URI by selecting the folder/file when the read/write operation will be done (OpenSingleDocument).
At some point it was mentioned that this can't be avoided but I would like to double check this in case I missed something (believe me, processing the whole post with 3 years of activity in just one day is a lot when you are not a developer).
I need to read/write a backup file, I know the name and the location beforehand and it will never change (Download/Backup.csv).
I know some of you will mention SAF is not needed but it is since when I upgrade the App it no longers opens the file and also the customer can get this backup file from the cloud and not using my App, so I do need SAF.
Can this need to select the file to get its URI be avoided?.
Thanks!.
Unfortunately, the answer is no. The user will have to select the file.
It may be possible to only have to do this once, after which you can store the uri string to tinydb for reuse, but this relies on the uri not changing when any changes are made to the file either by your app or other means. If the read fails, then fall back to file selection, and start again.
Thanks! I will implement that workaround.
is there anyone who can post the blocks to save a txt file to local storage having Android 12 and using SAF extension.?
