KeePassdroid won't accept master password

[GoogleCodeExporter]

What steps will reproduce the problem?
1. I have KeePass on my desktop which accepts the Master Password
2. I synchronize using DropBox (desktop and Droid app)
3. I open up KeePassdroid, enter the same Master password and get the message 
"invalid password or keyfile"
4. I don't use a keyfile in addition to the PW

What is the expected output? I would expect that it would open the database 
which was created on the desktop

What do you see instead? the error message noted above in 3

What version of the product are you using? On what operating system?  Latest 
versions of KeePass for Windows XP and Droid

Please provide any additional information below.

Original issue reported on code.google.com by mcfallg...@gmail.com on 19 Jul 2011 at 9:22

[GoogleCodeExporter]

I've seen occasional reports like this, but I've never been able to track it 
down.

Can you try to create another database that doesn't contain sensitive 
information that has the same problem? Then send me the database and password.

Original comment by bpel...@gmail.com on 21 Jul 2011 at 12:02

[GoogleCodeExporter]

I just installed KeepassX and KeepassDroid, and am getting this issue also.

KeePassX 0.4.3
KeePassDroid 1.9.5

I created my password file in KeePassX and after copying over to my Nexus S, 
KeePassDroid opened it up on the first try. Yay! Every successive try since I 
get "Invalid password or key file." Nay!

Upon clicking OK to attempt the open, I see "Creating xxxxxxxx", then 
"Decrypting database contents", then the "Invalid password or key file". The 
xxxxxx means I can't read it because it changes so fast.

Yes, I'm typing the correct password - the file still works fine with KeePassX.

HTH.

Original comment by dsteckb...@gmail.com on 6 Aug 2011 at 6:55

[GoogleCodeExporter]

Ok, I finally had a chance to investigate further. My attempts at creating a 
sample file for you failed. I couldn't get it to replicate the problem. So, I 
next tried an export/import.

1. I opened my 'broken' password file in KeePassX
2. exported to XML
3. closed the file
4. imported from XML to a new file
5. saved the same DB with a different file name but used the same password and 
key file
6. copied over to my Android phone
7. opened successfully ?!?

The new file is bytesize identical, but does differ in md5. Visually inspecting 
in vim, the magic values are the same, but then differences are indeed visible.

Original comment by dsteckb...@gmail.com on 7 Sep 2011 at 4:52

[GoogleCodeExporter]

Same exact problem, same workaround resolved it.  Very weird.

Original comment by m...@subfocal.net on 28 Oct 2011 at 6:21

[GoogleCodeExporter]

Same trick did it for me. have no clue what got wrong...

Original comment by Markus.h...@gmail.com on 9 May 2012 at 6:26

[GoogleCodeExporter]

did some investigation further.
Problem seems to stick in manner of file saving or opening by using Ubuntu One.
My *.kdb file is absolutely functional with following systems:
Windows XP with KeePass 1.20 using a  file download over Ubuntu One, Sky Drive, 
Google Drive.
The same file will open on my SGS 2 with Android 4.0.3 and KPD while using G 
Drive or Sky Drive.
But using the file synced over Ubuntu One will lead to "Invalid password or key 
file".
is there a problem with the path? maybe the space ine path /Ubuntu One/ causes 
the problem on opening?

Original comment by Markus.h...@gmail.com on 16 May 2012 at 7:23

[GoogleCodeExporter]

dived deeper into the problem:
after copying a file from skydrive folder to the ubunut one folder KDP opens 
the database without any hassle.
So my conclusion is: Ubuntu one does something with the file that dosen't keep 
the file correct.

Original comment by Markus.h...@gmail.com on 16 May 2012 at 8:24

[GoogleCodeExporter]

The conclusion from the previous post seems to be the right hint - I have the 
same problem while opening the database from Ubuntu One.

Original comment by niw...@gmail.com on 9 Jun 2012 at 6:05

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I'm having the same problem with a file saved by KeePassX on Ubuntu and saved 
in Dropbox.

Original comment by IanMLe...@gmail.com on 29 Jun 2012 at 8:36

[GoogleCodeExporter]

I'm having the same problem with saving by KeePassX on saved in Dropbox.

it seems that dropbox solved this problem only not on my Samsun Gs III

Original comment by willem.k...@gmail.com on 3 Jul 2012 at 10:43

[GoogleCodeExporter]

I found that clearing the data via settings (Settings-->Application 
Manager-->App Info-->Clear data) and then downloading your keyfile from 
whatever cloud service you might use clears the problem up for me. 

Original comment by mrobbel...@gmail.com on 30 Jan 2013 at 2:17

[GoogleCodeExporter]

So why not just update keepass to work with the file that is obviously modified 
in an inconsequential manner?

Original comment by pmug...@gmail.com on 7 Feb 2013 at 4:49

[GoogleCodeExporter]

I resolved this issue by switching my USB connection mode from MTP to MSC 
before copying the file from my phone to my PC.  Otherwise, after doing the 
copy then copying from PC to Nexus 7, KeePass Droid couldn't open the file and 
displayed this error.  I've had a number of problems with MTP copies on my 
phone (Sony XPeria Arc with Android 4.0.4) and decided that the MTP 
implementation is broken.

Original comment by Paul.1.A...@gmail.com on 30 Mar 2013 at 6:38