Closed ippocratis closed 5 months ago
I don't know why this would happen. What type of storage are you saving to (internal, external, cloud)? Does the file manager show 0 bytes for manually exported JSON as well, or only scheduled exports?
Happenss both on manual and sheduled exports Files are saved in internal memory under /storage/emulated/0 I'm suspecting that maybe the custom rom I'm running is handling storage permission improperly android 13 is strange in app permissions anyway
Happenss both on manual and sheduled exports Files are saved in internal memory under /storage/emulated/0 I'm suspecting that maybe the custom rom I'm running is handling storage permission improperly android 13 is strange in app permissions anyway
Happenss both on manual and sheduled exports Files are saved in internal memory under /storage/emulated/0 I'm suspecting that maybe the custom rom I'm running is handling storage permission improperly android 13 is strange in app permissions anyway
Thanks for the additional details. If you can test whether the problem occurs on a more standard version of Android, that would certainly be helpful. The app does work on Android 13 (tested on LineageOS), but it's certainly possible that a custom ROM could cause storage access problems.
I'm closing this issue due to inactivity and the fact that I cannot reproduce the problem; feel to free to reopen it if the problem persists.
The truth is I forgot about it. In the meantime I'm not having this problem on A14 on another rom, in a diferent device though. Thanks for the great app
You'll welcom! Thanks for the update.
I have the sheduled export enabled and syncing the export folder to my home server The syncing app (foldersync) throws error Expected * bytes but received **
But also file managers like material files displays the exported json(s) as zero byte If I open the files with a text editor they display contents
So maybe the export is not finalising the files properly?