reqable
[bug] Imported collections vanish after restart
Describe the bug
Imported collections vanish after application restart
To Reproduce Steps to reproduce the behavior:
- Import some collections from Postman
- Close the application. It usually does not happen on the first time, and I am not sure what exactly triggers it.
- Open Requable again
- All imported collections are replaced with "Untitled (0)"
Expected behavior
Imported collections should not be corrupted between restarts
Screenshots
Information
- Platform: Linux
- OS: Kubuntu 25.10
- Arch: x86-64
- App Version: 3.0.22 but it happened on earlier 2.xx versions as well
I am not 100% sure yet, but I think history also gets deleted at the same time when collections are corrupted
@qbast Hello, this issue occurred because you upgraded to version 3.x and then downgraded to version 2.x, causing data loss. If you haven't done this multiple times, it's possible to recover your data from backups. Copy the two files from ~/.local/share/reqable/box.bak and overwrite the existing files in ~/.local/share/reqable/box, and restart the app.
If data recovery fails, check the size of the backup file under box.bak. If the file is less than 1MB, it means the backup has been refreshed and cannot be recovered.
Hello. I don't think this is caused by version changes. I had the same problem on version 2 before any upgrades. Then I upgraded to version 3, hoping it will fix the problem, but it does not. I never downgraded.
I managed to reproduce it right now: start reqable, import all my collections from postman, verify that box.data size is 208KB. Then I closed reqable, restarted it and collections were emptied again. I tried to restore from backup (it shows multiple possible date/times I could restore from), but it also does not bring back anything.
One thing I forgot to mention in the report: reqable is installed via flatpak. Could it be the issue? I will retest on requable installed from .deb
Hello. I don't think this is caused by version changes. I had the same problem on version 2 before any upgrades. Then I upgraded to version 3, hoping it will fix the problem, but it does not. I never downgraded.
I managed to reproduce it right now: start reqable, import all my collections from postman, verify that box.data size is 208KB. Then I closed reqable, restarted it and collections were emptied again. I tried to restore from backup (it shows multiple possible date/times I could restore from), but it also does not bring back anything.
One thing I forgot to mention in the report: reqable is installed via flatpak. Could it be the issue? I will retest on requable installed from .deb
Okay, thank you for your reply. Could you please provide the log files(~/.local/share/reqable/log), compressed into a zip file, and send it to my email address [email protected] ?
Sure, done.
But no email received in my message box. Also you can attach it here, the log contains no sensitive information.
Maybe it got stuck in spam inbox? Anyway, here is the logs:
It increasingly looks like this bugs is specific to flatpak-packaged reqable. After installing version from .deb, i restarted it multiple times and my collections are still there.
Thanks very much. I think I know the reason: you started multiple instances, causing the database to fail to open, see https://github.com/objectbox/objectbox-dart/issues/288 . On Linux, we did not prevent multiple instances from starting, which can cause some problems.
That's quite probable. Flatpak version does not show bird icon in taskbar (instead just empty rectangle), so it is easy to overlook already started instance. However I also tested it on .deb version - opened multiple instances, closed some of them, etc. - it still works. So the .deb version is rock solid for me. Flatpak does have some sandboxing, maybe this interferes with multiple running instances