Issue with Backup database.

[SGaming700]

Jerboa Version

0.0.87-gplay

Android Version + Phone

Android 13 Go, FOXXD A55

Describe The Bug

There seems to be a problem with backing up the app database because when I go to settings and I back up the files for it, it shows up as 0 bytes and when I try to restore it everything goes back to default and removes my saved settings so there is something wrong going on there.

To Reproduce

1. Go to the menu on the top right.
2. Go to settings.
3. Go to backup and restore.
4. Tap backup database

In the case of a crash or when relevant include the logs

No response

[dessalines]

I just tested this, and can't verify. The backup wasn't 0 bytes, and restore worked fine.

Are you sure there isn't some issue with storage permissions for the folder you're backing up to?

[SGaming700]

Here's some evidence https://drive.google.com/drive/folders/1qC0mkfuJJP-6tQfqgnssIxBJQeRO-giU

[MV-GH]

we don't have access to that but you can directly upload files here

[SGaming700]

Huh I thought that link would work let me try to send the files here.

screen-20260526-110839.2.mp4

[dessalines]

This is gonna be a tough one. The DB library I wrote should be fine for android versions above O / 8.0

Here's the code for it: https://github.com/dessalines/room-db-export-import/blob/main/room-db-export-import/src/main/java/com/roomdbexportimport/RoomDBExportImport.kt

[MV-GH]

There is a lot that could wrong there, it should return a result so that Jerboa can handle/know about it when it fails. So that it can inform and display the failure. Currently it swallows any IO exception. And the jerboa code will just save an empty file

    val exportDbLauncher =
        rememberLauncherForActivityResult(
            ActivityResultContracts.CreateDocument("application/zip"),
        ) {
            it?.also {
                dbHelper.export(ctx, it)
                Toast.makeText(ctx, dbSavedText, Toast.LENGTH_SHORT).show()
            }
        }

[dessalines]

True, that'd be a good idea to have that return a result.

Although it is printing a stacktrace, its not going to be easy to view it since it isn't causing a crash.