When I try to open my keepass database, I get the error: "An error occurred: the file is corrupted." The file is stored on dropbox using a password and a key file. The key file is local. I can open the file with the regular desktop keepass2 application. Until recently, I could open the file with keepass2android as well. I tried clearing application data and cache and re-initializing, but it didn't help.
Other relevant details: desktop version of keepass2: 2.25. I run it under Linux with mono. Specifically I use the Ubuntu 14.04 package.
I have a Samsung Galaxy S4 from Verizon running Android 5.0.1.
My Keepass2Android version is the latest version available from play store as of the time of this report. It appears to be version 0.9.9b. I noticed the problem for the first time on the version BEFORE the one with the new UI.
I have not gone back through my old versions to see if there was a point in time at which this broke, but I can do that if necessary.
I obviously can't attach my keepass database, but please let me know if there's other information I can provide that could assist in debugging this.
I am a software developer but I don't know C# and I don't do Android development. However, I am sufficiently well-versed in android tools that it is possible for me to do something like using adb to grab a log file or something.
Not that it should matter, but I have previously donated to Keepass2Android. :-)
Right now, I am unable to access my keys on my phone at all, so I will need to find a solution or workaround or else I'll have to find some alternative way to store my keys.
Comments: Using the desktop version of keepass2, I generated a new key file and then copied that over to my phone. With the new key file, I was able to open the database. I'm not sure why the old key file doesn't work and the new one does. I definitely verified that the key files are identical. So, for now, my immediate problem is resolved since I am once again able to use my keepass database on my phone. I am saving a copy of my old database and old key file in case I am able to provide additional information that may help with debugging this problem. I am quite certain that I didn't change or damage the key file and that the same key file that worked on the desktop program did not work in keepass2android starting sometime recently, but I had previously been using that key file without an issue.
Other relevant details: desktop version of keepass2: 2.25. I run it under Linux with mono. Specifically I use the Ubuntu 14.04 package.
I have a Samsung Galaxy S4 from Verizon running Android 5.0.1.
My Keepass2Android version is the latest version available from play store as of the time of this report. It appears to be version 0.9.9b. I noticed the problem for the first time on the version BEFORE the one with the new UI.
I have not gone back through my old versions to see if there was a point in time at which this broke, but I can do that if necessary.
I obviously can't attach my keepass database, but please let me know if there's other information I can provide that could assist in debugging this.
I am a software developer but I don't know C# and I don't do Android development. However, I am sufficiently well-versed in android tools that it is possible for me to do something like using adb to grab a log file or something.
Not that it should matter, but I have previously donated to Keepass2Android. :-)
Right now, I am unable to access my keys on my phone at all, so I will need to find a solution or workaround or else I'll have to find some alternative way to store my keys.
Comments: Using the desktop version of keepass2, I generated a new key file and then copied that over to my phone. With the new key file, I was able to open the database. I'm not sure why the old key file doesn't work and the new one does. I definitely verified that the key files are identical. So, for now, my immediate problem is resolved since I am once again able to use my keepass database on my phone. I am saving a copy of my old database and old key file in case I am able to provide additional information that may help with debugging this problem. I am quite certain that I didn't change or damage the key file and that the same key file that worked on the desktop program did not work in keepass2android starting sometime recently, but I had previously been using that key file without an issue.