search

ismben / secrets-for-android

Automatically exported from code.google.com/p/secrets-for-android
0 stars 0 forks source link

Secrets accepts any master password but shows no data #50

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Enter any master password (including correct one).
2. Press "Enter" on soft keyboard.

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

If master password is correct one I expect to see my secrets and error 
message otherwise. Instead for any password I get error message "Uh oh: a 
problem was encountered while loading your secrets. Some data may be 
lost." and see empty list of secrets. It's strange that any password is 
actually unlocking the app.

What version of the product are you using? On what operating system?

Secrets 1.4.8
HTC Tattoo
Android 1.6

Please provide any additional information below.

Just before that problem I've manually entered about 20 secrets in a row 
and due to minute of inactivity my HTC Tattoo has locked. After unlocking 
the screen I found Secrets locked, it did not recognize master password 
for several times and finally had opened empty list.
I use Secrets 1.4.8 and I've tried to restore data but unsuccessful - it 
says wrong password. And app continues to make backups overwriting early 
versions :(

Original issue reported on code.google.com by denis.li...@gmail.com on 12 Jan 2010 at 8:54

GoogleCodeExporter commented 9 years ago 
I have rebooted HTC Tattoo and it seems that Secrets started working 
appropriately - 
it recognized my master password and does not allow me to unlock with random 
password. However, all backups were already overwritten. It was not good idea 
to 
keep trying and just reboot instead.

Original comment by denis.li...@gmail.com on 12 Jan 2010 at 9:09

GoogleCodeExporter commented 9 years ago 
Apparently this is a duplicate of #49

Original comment by tioerre on 13 Jan 2010 at 2:46

GoogleCodeExporter commented 9 years ago 
See duplicate bug for details.

Original comment by roge...@google.com on 13 Jan 2010 at 3:46