Closed GoogleCodeExporter closed 8 years ago
Correction: KeePassDroid Version 1.9.1
Original comment by thew.bur...@gmail.com
on 4 Feb 2011 at 4:08
I have keepassx on my Mac and keepass on my droid. I can't get them to work
together using Dropbox. I also want to use it on an iPad. All of my devices
are up to date. My error message is "database format not recognized." Is it
possible to sync all devices through Dropbox?
Original comment by hvbluegr...@gmail.com
on 6 Jun 2011 at 3:27
I have the same problem. I have keepassx on my Debian and latest KeePassDroid
on my samsung galaxy s. My error is also "database format not recognized." Why?
Original comment by ronny.ew...@gmail.com
on 16 Aug 2011 at 9:16
just copy the file via usb from your pc. that might solve the problem
Original comment by umit.kus...@gmail.com
on 18 Sep 2011 at 9:42
I have this problem as well. The file transfers happily via Dropbox between
KeepassX instances (on both Linux and Windows), but KeepassDroid fails to read
it with the database format error.
I just double checked that the affected database is indeed using AES
encryption, since KeePassDroid states explicitly that TwoFish isn't supported.
It's an old database though, so the number of encryption rounds is relatively
low compared to more recently created databases.
Original comment by ncoghlan
on 18 Jul 2012 at 5:18
Just ran into the same problem after the version of KeePass on my PC got
updated (I use KeePass portable on the desktop, which reports that it is
version 1.23 - i.e. the version released 18 days ago)
Original comment by RichardJFoster
on 18 Jul 2012 at 8:42
Can you provide an example database that exhibits this problem?
Original comment by bpel...@gmail.com
on 12 Sep 2012 at 5:23
It's working for me now, so either one of your recent updates fixed it, or else
it was just a Dropbox transfer glitch to my phone.
Original comment by ncoghlan
on 12 Sep 2012 at 6:55
Original comment by bpel...@gmail.com
on 13 Sep 2012 at 1:39
New SamSung Galaxy S III Data base format not recognized.
Original comment by bobpen...@gmail.com
on 18 Feb 2013 at 12:53
Original issue reported on code.google.com by
thew.bur...@gmail.com
on 2 Feb 2011 at 3:13