Andotp: Export data generate a blank file

[uranio-235]

After export data, result is a 0 bytes length file...

[flocke]

Do you export to any cloud storage or to your phones internal storage?

[guyfw]

Here the same. It happens when I export to my internal storage.

[flocke]

Which export are you using? Password protected, PGP, Plain-text?

[guyfw]

I tried both with plain and password-protected. I noticed that this could be solved waiting approximately 15s after the beginning of the export procedure.

[beerisgood]

15s? Sound you try to save the file to a slow sd card or you use a "security" solution
It's only few Kb.

[guyfw]

Yeah, I saved on my SD card (60 MB/s in writing) since it's the only path available to me.

[beerisgood]

Yeah, I saved on my SD card (60 MB/s in writing) since it's the only path available to me.

Why? Every phone has internal storage.
Also are you sure that your sd card isn't corrupt? With 60MB/s you wouldn't get any trouble

[guyfw]

I'm sorry, I though the Download folder was located on my SD. I tried to save on it and I had no issues. However, I still do not comprehend why there's such difference since I checked my SD for integrity without reporting errors.

[alexbakker]

We're getting similar reports: https://github.com/beemdevelopment/Aegis/issues/362. It appears that no exception is thrown when writing the file, but it ends up being 0 bytes in size somehow. Could it be that the Storage Access Framework is buggy on some devices?

[beerisgood]

We're getting similar reports: beemdevelopment/Aegis#362. It appears that no exception is thrown when writing the file, but it ends up being 0 bytes in size somehow. Could it be that the Storage Access Framework is buggy on some devices?

I would say the error is on app side. Also with upcomming Android 11 the actually storage permission get changed, so apps now need to change that as well.
Read: https://www.reddit.com/r/GrapheneOS/comments/fre3vz/storage_permissions/flvqzhi/

[alexbakker]

I would say the error is on app side.

What makes you draw this conclusion? The (little) evidence we have so far suggests otherwise. I hope to be proven wrong though.

Also with upcomming Android 11 the actually storage permission get changed, so apps now need to change that as well.

Indeed. Aegis doesn't request the legacy storage permissions anymore.

[alexbakker]

FYI: One of our users reported the following:

the issue is solved, it was not caused of aegis. had the same problem just now when exporting my contacts and was also a 0 Byte empty file, so i searched in settings and found in the developer options the point "allow external storage usage of apps" since activating , everything works as desired.

[flocke]

FYI: One of our users reported the following: ...

I will put this issue on hold until after the storage rework that is planed for version 0.8.0, which should fix most of the storage-related problems.

[skobkin]

Same here with GPG (OpenKeychain) export.

UPD:

Tested different ways to export AFTER enabling suggested "allow external storage usage of apps":

OpenKeychain: Don't work, 0 bytes
Password, AES: Works
Plaintext: Works

When such option disabled I'm getting the same results.