New entry not saving Password/Username depending on which entered first
Am I missing something?
Here is my process of entering a new item. Latest version of iOS 1Password and iOS 7.1
- Goto Login Items
- Tap +
- Enter Name of item in Logins box
- Enter username
- Enter password without using password generator
- Scroll down and enter a note
- Tap Done
Now screen shows my saved entry but the password is not saved. Will show the same thing with username not saved if I switch steps 4 and 5 around.
I am able to get it to save everything if I tap into username and or password boxes back and forth again before saving but I don't always remember to do this and if in a hurry can not realize I didn't save a password I just made up. (Doh!)
Comments
-
Hi @iceout,
I'm sorry to hear that you're having trouble here. Thanks so much for including such detailed description of the steps that you took, it makes it a lot easier to test things out on our end.
Now, I'm not able to reproduce this issue. Could you please tell me the version number of 1Password that you are currently using? You can find this by going to 1Password > Settings and looking in the 'Recommend 1Password' area. Does this happen every time you create a new Login in this manner?
0 -
Hi @Megan,
I am using version 4.3.2 and yes this happens every time I create a new login item in this manner. I have updated my steps to be as specific as possible.
Here is my process of entering a new item. Version 4.3.2 of iOS 1Password and iOS 7.1 on an iPhone 4s
- Goto Login Items
- Tap +
- Tap into Login box and enter name of item
- Tap into username box and enter a username
- Tap into password box and manually enter a password
- Scroll down to notes section without tapping into any other boxes and tap into notes section and enter a note
- Tap Done
Just did another test and scrolling down to enter a note was a necessary step to recreate this issue. If I don't scroll down and enter a note the password is saved properly.
0 -
Hi @iceout,
Well, that did it. The "do not touch any other fields" seems to be the key to this. I can now reproduce what you're seeing. I sincerely apologize for the trouble here. I've filed an issue in our tracker and we'll do our best to get this fixed ASAP. Not saving a password is not cool.
Thanks so much for bringing this to our attention!
0