Hi,
I'm using Keepass2Android (version 1.0.0-d) on Nexus 5x (android 6.0.1) with a keepass.kdbx file locally on the phone. I was adding a few new entries to my database (protected with just a password, not a key file), and after 3 new entries, it said something about the local file differed from the in-memory one. I canceled adding the newest entry, closed the db, and when I tried to reopen it, it said the file is corrupted. I don't think any other app would have touched the file so think maybe keepass2android corrupted the file when saving it?
How can I recover the file? I had some hard-to-recover data in the newest entries. If someone understood what bug might have corrupted the data, maybe I can reverse the bug and write a quick script to un-corrupt it?
It'd even help if there were a way to get some debug corruption information on what exactly was corrupted.
Thanks for any suggestions!
Josh
I'm using Keepass2Android (version 1.0.0-d) on Nexus 5x (android 6.0.1) with a keepass.kdbx file locally on the phone. I was adding a few new entries to my database (protected with just a password, not a key file), and after 3 new entries, it said something about the local file differed from the in-memory one. I canceled adding the newest entry, closed the db, and when I tried to reopen it, it said the file is corrupted. I don't think any other app would have touched the file so think maybe keepass2android corrupted the file when saving it?
How can I recover the file? I had some hard-to-recover data in the newest entries. If someone understood what bug might have corrupted the data, maybe I can reverse the bug and write a quick script to un-corrupt it?
It'd even help if there were a way to get some debug corruption information on what exactly was corrupted.
Thanks for any suggestions!
Josh