Wrong item opens when edit login
When selecting edit in a log-in item, the wrong item opens. The item that opens appears to be random. Once I close the item, it brings me back to the original item I desired to edit. Then if I select edit again, it goes to the edit item finally that o originally tried to edit.
1Password Version: 8.10.28
Extension Version: Not Provided
OS Version: iOS
Browser: Not Provided
Comments
-
Bump?
0 -
Hello @MGOBLUE!
I'm sorry that you're seeing the wrong item open when editing using 1Password for iOS. Our developers recently included a fix in the latest version of 1Password. I see that you're already running this version and it's possible that you might just need to clear a couple of stuck drafts. When you see the wrong item open, tap on Cancel and then tap on Discard Changes.
If you continue to see the wrong item being opened for editing when using 1Password for iOS then are you able to share steps that I can follow to reproduce the issue on my end? For example, does the wrong draft appear automatically when you first open the 1Password app? Or do you see the wrong draft only when you deliberately edit a different item?
This information will allow me to confirm whether you're running into a different issue and to investigate this further on my end.
-Dave
0 -
Thank you. At this point, there appears to be a new issue, which is that the draft of one item continues to open up when I open the app. I have to discard changes before I can access the vault. Is this know issue being worked on or is there a solution?
I don’t appear to have the original issue anymore after the update.
0 -
Thank you for the reply. It does sound like you're running into a different issue that our developers are also investigating and that a fix is not available for yet. The next time that you run into the issue can you try these steps as a workaround:
- Tap Cancel on the item draft that appears.
- Wait 2 seconds.
- Fully close the 1Password app: Close an app on your iPhone or iPod touch – Apple Support (UK)
- Open and unlock the 1Password app.
- If you see another draft, repeat steps 1-4 again.
The results will tell me more about the situation so that I can advise further. I look forward to hearing from you.
-Dave
ref: dev/core/core#28720
0 -
After closing the app about four or five times, it stopped coming up. Thanks.
0 -
I also have this problem. Multiple times. This is a CRITICAL problem because if the user does not notice that they are editing the wrong login item (LoginY) after clicking edit on LoginX, they can get themselves locked out of both LoginX (because now has wrong password) and LoginY (because password was not updated). Huge, huge problem.
Because I have already been bitten by this more than once with 1Password, I now try to triple-check the item that is showing as being edited in 1Password but this is a RIDICULOUS BUG TO PERSIST and has been happening for several months now and still happened to me just now, on 05/18/2024.
TOTALLY UNACCEPTABLE! Please contact me if you need more information. Clearly this is affecting multiple users. As you know, of course, passwords and credentials are not something to be trifled with!!
0 -
I'm sorry for the frustration that the issue is causing. I agree that this is something that needs to be fixed as soon as possible and the team is currently testing a fix in the latest beta version of 1Password for iOS.
As soon as we're able to verify that the fix works, and doesn't introduce new issues, then it'll be included in a future update to the stable version of 1Password as well.
For the time being, try these steps to workaround the issue:
- Tap Cancel on the item draft that appears.
- Wait 2 seconds.
- Fully close the 1Password app: Close an app on your iPhone or iPod touch – Apple Support (UK)
- Open and unlock the 1Password app.
- If you see another draft, repeat steps 1-4 again.
-Dave
0 -
Thank you for your patience. Our developers have released a fix for an issue where if you discarded a draft, it could still appear when you opened the app. If you haven't already, please update to version 8.10.34:
Let me know if you still see the issue after updating and I'll let our development team know.
-Dave
0