Error 2103 File component can't create file in ASD in Android12 (but the same app works in previous Android version)

Hi all.
I made a litle modification in my app, renaming the version, and I begun experiencing trouble with it when installed in a mobile phone with Android12 (Installing the same app in another older phone with Android 4.4.4, it works well).
It looks like neither File component can write in the ASD, nor can I download files there from FireBase Storage, and I get Error 2103 (The file could not be created).
Scope is set to App. And I don't think I need to request permission to read or write on the ASD.
To make sure I wasn't doing something else wrong, I used a simple app proposed by Anke to check File component (in other topic, now closed).
And the problem remains (only in the new mobile, not in the old one).
What can the problem be?


FileASD.aia (2.1 KB)

Post a screenshot of your device (-> Settings: device name, Android version).

There you are.

In case it helps, I just checked there is no problem when scope is set to Private (both in app and File component).

Try to use a full path: file:///storage/...

FileASD_2.aia (24.3 KB)

... or this:

Sorry I can't find such .GetApplicationSpecificDirPath block in the File component of my app inventor.

MFile extension. I also posted the aia.

I Can't make your second option work with Scope (2x) set to App.
When I set Scope (2x) to Private, this one works the same as before.

Look at my blocks:

I have more than 20 test devices (Android 4.4 - 15) and it works on all Android versions. Period.

Sorry, Anke. I didn't realize you programmatically changed the file scope to "Legacy."
I already did that, but it doesn't work on my phone. I still get error 2103 when I press the button. Do I also need to change the DefaultFileScope to "Legacy" in the project properties?

Thanks a lot.
In any case, I think I prefer using the "Private" scope.
Based on what you've pointed out in other threads, it seems more secure, since this way most users wouldn't be able to access sensitive information in the files, even if they set debug mode on their phone and connect their computer via USB.

No.

I would like to see that with my one eyes. So please try this app and post a screenshot:

Correct.
But I've never seen that the ASD doesn't work (on any Android version).

Did you check the .aia of my first post?

There you are

Hmm, that's really strange. Test this blocks to see if the ASD even exists/was created.

FileASD_3.aia (25.2 KB)

Blocks

Maybe the ASD is not created on your device. It should work with Companion & APK on any Android version.

If it still doesn't work on your device, the device is damaged and should be reset to factory settings.

1 Like

I believe the ASD/files folder should be created at the download of the first app remote configuration file from Firebase Storage, or else later when writing the first line in the debug .csv File.
But both tings fail, and I checked via USB that ASD/files folder it's not created at all.
I'll follow your recomendation, and report back.

...and...?

It's not that easy. Because it's the phone I use every day. I'll lose everything.