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: Yeah, I didn't notice that when I first generated the data. I noticed it when I tried to work with it subsequently. After I select the file, it doesn't show as selected. This is just using the system picker. However, when I use the current play store version of the app, I don't have any trouble selecting a key file, and I've been using this app for many months with a key file in the same location. I keep it on my sdcard, but I also tried copying it to internal storage and accessing it from there. The version of the app linked to this issue does not enable me to select it. I don't really want to try copying my key file to a cloud service. Anyway, that seems unrelated to the original issue since I am able to select the keyfile on the play store version. We're probably seeing two different issues.
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: Yeah, I didn't notice that when I first generated the data. I noticed it when I tried to work with it subsequently. After I select the file, it doesn't show as selected. This is just using the system picker. However, when I use the current play store version of the app, I don't have any trouble selecting a key file, and I've been using this app for many months with a key file in the same location. I keep it on my sdcard, but I also tried copying it to internal storage and accessing it from there. The version of the app linked to this issue does not enable me to select it. I don't really want to try copying my key file to a cloud service. Anyway, that seems unrelated to the original issue since I am able to select the keyfile on the play store version. We're probably seeing two different issues.