How do you choose files from ASD and export them?

[Anke]

@Sirous_Nekooei

Could you pls write the exact way to write in the "Documents" directory with a subdirectory named "ECG_Save"

To save an image with the Canvas component in one of the Shared folders directly you must set DefaultFileScope to Shared or Legacy.

Otherwise set it to App, save the image in the ASD and then move it to one of the Shared folder using the File component or one of the File extensions from @Taifun or @vknow360.

[Sirous_Nekooei]

@Anke

To save an image with the Canvas component in one of the Shared folders directly you must set DefaultFileScope to Shared or Legacy.

save_test.aia (105.4 KB)

Access to shared folder (writing) is not permitted at all.
Lets try a simple code here:

[Anke]

@Sirous_Nekooei

In this way the application creates a folder named "Documents" in the ASD, then writes inside it!

Correct, the DefaultFileScope is essentially responsible for two things:

1. Where are files, created with components that can save something (ie e.g. Canvas), stored.
2. Which permissions are declared on which Android versions in the Manifest.

To store files directly in the Shared folder /Documents with the Canvas component, DefaultFileScope must be set to Legacy, as this is the only way to declare both storage permissions in the Manifest. On Android < 11 both permissions are required. Unfortunately with AI2 also incorrectly on Android 11+.
I've mentioned this bug countless times.

@Sirous_Nekooei

Access to shared folder is not permitted at all.

Yes, this is another bug with the File component, that I also mentioned some times. But anyway, you need to set the DefaultFileScope to Legacy as I said before.

[Sirous_Nekooei]

@Anke

you need to set the DefaultFileScope to Legacy

Sorry, but I have tested "legacy" without success.
Let's check everything:
Screen1 properties : DefaultFileScope :Legacy

File1 Properties: DefaultScope; Legacy
ReadPermission TICKED
WritePermission TICKED

Blocks:

When the app is launched:
upon clicking the save button, askes for Permission:

Then this error pops up:

When I go to settings.......permissions:

But altogether, nothing is saved.

[Anke]

Try this one: save_test_2.aia (105.9 KB)

[Taifun]

@Sirous_Nekooei

Lets try a simple code here:

Your question was to save something using the canvas... so you should use the canvas for your tests... sorry, my previous answer about the default file scope was wrong, I corrected it meanwhile...

testing the file component to save some text will not help for your purposes...

Taifun

[Sirous_Nekooei]

@Anke

Try this one: save_test_2.aia

Thank you so much. It worked. But I am totally confused.
At 1st installation, it saved without difficulty. but at later times, it could not save. Tried several times, looks like randomly working.
I am very close to give up!

[TIMAI2]

I believe you have to delete an existing file in the Shared area before you can save it again. You cannot overwrite.

[Sirous_Nekooei]

Tried that, no success...

[Anke]

@Sirous_Nekooei

At 1st installation, it saved without difficulty. but at later times, it could not save.

@TIMAI2

you have to delete an existing file in the Shared area before you can save it again

As I wrote, you must delete the file before testing with the APK and vice versa.
Because if you first saves the (non-media) file with Companion, the compiled app (APK) cannot overwrite this file because it was created by another app (Companion).

That's why I added this (delete) button:

[Anke]

Otherwise (to avoid this prior deletion) you must append a timestamp to the filename.

[Sirous_Nekooei]

I don't use companion. I test on my phone. I uninstall the app, delete the file and folder already is created, delete the downloaded apk, then again compile the project...

[Anke]

Ok, I understand. Then try this one:
save_test_3.aia (106.8 KB)

It will work always regardless of Companion, APK, un-/reinstallation, removing files, dirs etc.

Blocks

[Sirous_Nekooei]

@Anke

It will work always regardless of Companion, APK, un-/reinstallation, removing files, dirs etc.

Hurrah....
It works
Now I am going to test it in my own app

[Anke]

@Sirous_Nekooei

Hurrah....
It works

And if want to avoid storage permissions on Android 11+ use my MFile extension, which does not require storage permissions (READ/WRITE) on Android 11+ for the Shared folder (like /Documents or /Download).

MFile - a modified version of Sunny's `EFile` extension - Shared folders - storage permissions - Android 11+

Here is a modified version of Sunny's EFile extension, which added some methods that are needed (among others things) for testing purposes with Companion & AKP. Because if you try to save in one of the Shared folders (/Documents or /Download) first with Companion it is not possible to do this without deleting the saved text file before testing with the APK and vice versa (at least on Android 11+). So the Delete & FileExists & API level methods are needed. The Delete method exists with the File …

[Sirous_Nekooei]

@Taifun

Your question was to save something using the canvas... so you should use the canvas for your tests

My project has csv file save, canvas save, and screenshot save (with Taifun screenshot extension).
How can I determine the "scope" for canvas save and screenshot save?

[Anke]

@Sirous_Nekooei

How can I determine the "scope" for canvas save and screenshot save?

I already answered this question here:

@Anke

the DefaultFileScope is essentially responsible for two things:

1. Where are files, created with components that can save something (ie e.g. Canvas), stored.
2. Which permissions are declared on which Android versions in the Manifest.

The TaifunScreenshot ext. saves screenshot.jpg in the ASD.

[Sirous_Nekooei]

@Anke

The TaifunScreenshot ext. saves screenshot.jpg in the ASD.

Is there any way to save screenshot in the shared folders? Other extensions for example?

[Anke]

@Sirous_Nekooei

Is there any way to save screenshot in the shared folders?

Move it from the ASD to one of the Shared folders using the File comp. or the TaifunFile ext.