crashes when adding new data

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Adding a new group or item
2.
3.

What is the expected output? What do you see instead?

forced closure of app

What version of the product are you using? On what operating system?
I deleted the app and loaded new from market with the same result. 

Please provide any additional information below.

Original issue reported on code.google.com by lynnkid...@gmail.com on 11 Aug 2011 at 11:05

[GoogleCodeExporter]

It happens when I change an existing entry, too.  Only when the file is opened 
from Dropbox.  If I copy the file to my SD card outside of the Dropbox folder, 
no problem.  It has only recently started doing this.

Original comment by bclag...@gmail.com on 5 Sep 2011 at 3:58

[GoogleCodeExporter]

Issue 228 has been merged into this issue.

Original comment by bpel...@gmail.com on 5 Sep 2011 at 5:51

[GoogleCodeExporter]

I'm not able to reproduce this error with the steps described. When version of 
Android are you running.

Could someone who sees this provide me with a log trace with 'adb logcat', or 
with the Log Collector application?

Original comment by bpel...@gmail.com on 5 Sep 2011 at 5:53

[GoogleCodeExporter]

I've used the log info sender many times when this issue has happened. You 
should see them from my email address.

Original comment by chuckp...@carefreeservices.org on 5 Sep 2011 at 1:42

[GoogleCodeExporter]

I have this issue. 
Whenever I try to save a change or edit to the existing database in kbd-format, 
the application returns 'sorry. process has stopped unexpectedly (force close / 
report)'
It doesn't matter if I open the database file from the Dropbox folder or if I 
copy it to another folder on the sim card and open it from there. Both options 
end in the same fail state.
The process in more detail:
1. open Dropbox (ver. 1.2.4) (I have tried copying the kbd to another folder on 
the sim car and open it from there, but it produces the same result as below)
2. select database file (.kbd)
3. KeePassDroid (ver 1.9.5) opens
4. Log in
5. Any action that tries to save changes to the file exits with the above fail 
state (process stopped unexpectedly)
Repeated on two handsets (Xperia Neo and Samsung Galaxy S2).
I am currently using the Samsung S2, and on that one I am running KeePassDroid 
version 1.9.5
I am running Android version 2.3.4 (Gingerbread)

Original comment by martin.d...@gmail.com on 25 Nov 2011 at 8:12

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I´ve got a similar problem.
If i´m adding a new item, my database is completely mixed up.
In most fields, where were empty before, afterwards there is some information 
from other fields in...

If in one entry the URL field is empty, 
after adding an new entry, there is some information
from any other entry in it.
Not from the new entry, from an random other entry...

For example:
Before:
Name, URL, Password, comment
A, , asdf, foranything
B, www.google.de, fdsa, somethingelse
C, 123, fds,

Now adding a new field:
A, 123, asdf, foranything
B, www.google.de, fdsa, somethingelse
C, 123, fds, somethingelse

Now the comment from field B is in field C and the URL from field C is in field 
A...

But it´s nearly random... i see now scheme in it...

I hope you understand what i mean...

I am running a Motorola Defy, Android Version 2.3.7
KeepassDroid Version 1.9.8

Original comment by Hubert.F...@gmail.com on 12 Feb 2012 at 9:33

[GoogleCodeExporter]

I´ve tested it again, and the problem is definitely by keepassdroid :(
If i am adding a new entry it mixes up the fields.

Might it will help you:
In the new added entries, the Field URL has got the value: $
the field Name has got the value: SYSTEM
and the field comment has got the value: KPX_GROUP_TREE_STATE

but only, if the field was empty.

Deleting the data and new installation of keepassdroid hasn´t helped.

Greetings

Original comment by Hubert.F...@gmail.com on 13 Feb 2012 at 2:39

[GoogleCodeExporter]

I just had this happen tonight. The comments and URL fields of dozens of 
entries were copied from other entries. The password and user names appear to 
be okay. I traced it back to a new entry made via KeePassDroid yesterday.

What I observed is described exactly by the previous comment (#8)

Original comment by wdunca...@gmail.com on 22 Feb 2012 at 4:21

[GoogleCodeExporter]

The source of corruption was fixed in 1.9.7.

Original comment by bpel...@gmail.com on 30 Jul 2012 at 12:25

• Changed state: Fixed