jonasoreland
[BUG] importing Backup
it seems like the folder where a backup is created is not accessible anymore, as it is a system folder.
Any way to have a file picker integrated to choose which backup should be loaded? Could also be used to export the database to a specific directory.
Its been a long time since I have worked on an Android App.
Can someone give me an estimate of the complexity of this? If it is an easy fix I could try fixing this, but the Devtool setup will take me some time.
The biggest problems in changing this is the Google requirements: https://developer.android.com/training/data-storage#scoped-storage Storage is therefore in app private storage for newer Android versions.
One way to implement export without changing storage is to implement sharing and use something like Solid/Amaze file manager to store the file.
I think it is is a serious bug, because ultimately breaks the whole purpose of bugs. Please prioritise
The file is stored in the app private storage, it does not have privileges to store it somewhere else. This follows Googles requirements, how they want it to work. You can move the file after exporting.
Thank you, I appreciate the response. I can confirm that it works fine for me to move the exported file freely. Export works.
Unsolved issue:
On my new phone, I didn't find any possibility to write the existing backup file to the private storage of the app.
An idea to work around this is having an activity launcher in the app (not sure if the wording is correct), where the existing backup file can be 'shared with' and then with RunnerUp app.
Or another idea is to declare in Android manifest (again guessed wording) that RunnerUp is able to open the filetype of the backup file. So that the file moved to new phone can be 'open with RunnerUp'.
Is the issue which I am facing clear?
Backups are restored with Google backups when you restore a backup. If you install in some other way, settings and activities are not included.
A share could be used, then you need some Solid Explorer Save to "receiver". Not too hard, but requires users to actually have a relevant way to share installed.
Restoring is harder, there are too many "interested" receivers by default already.
What about including the full path to the restore/export path?