Getting started with 1Password for your growing team, or refining your setup? Our Secured Success quickstart guide is for you.
Forum Discussion
iOS: Tapping edit on an item will open a previously edited item in certain cases
Similar issue as this post (which was closed so I couldn't just reply):
https://1password.community/discussion/138397/1password-opened-to-edit-screen
I've been doing a lot of work with 1 password today, and everytime I choose 'edit' for an item on the iphone, it opens the edit window for the PREVIOUS item. In other words:
- I search for an amazon password
- I edited and save data for that entry
- I search for a google password
- I click edit on that google password
- The edit window opens, but it's for the AMAZON password
Actually lost a password to this today, and I'm kind of stunned. Was using both desktop and iphone versions (because I was transitioning from Authy to 1Password for 2fa and needed my phone's camera for the QR codes).
Saved password on desktop and iphone for 1 item. Edited it on desktop.
Switch to iPhone, searched a totally different item. Clicked edit, and it opened the PREVIOUS item. I couldn't choose to simply close. Had to "save" or "discard". Chose save, and it overwrite the edit on the desktop with the previous data which had not reached the iPhone via the cloud yet.
1Password Version: 8.10
Extension Version: Not Provided
OS Version: macOS 14 and iOS 17.2
Browser: mac App and iOS App
73 Replies
- 1P_Dave
Moderator
Thanks for the question. When you edit an item and the wrong item appears, tap on Cancel and then tap on Discard Changes. You might need to do this a couple times before all existing drafts are cleared.
The fix will prevent new drafts from becoming stuck but it won't automatically remove drafts that were stuck before you updated to 1Password for iOS version 8.10.28.
-Dave
Same question -- the solution to the bug is for users to keep enduring the error until it suddenly stops happening?
How do we clear out or see existing drafts? @dave
- 1P_Dave
elioa6, menditto, and accordionmelody
I'm sorry for the confusion. It's normal that you might see the issue a few more times after updating as existing drafts are cleared out from the app. As a data loss prevention measure, the fix in 1Password for iOS version 8.10.28 ensures that new drafts are not "stuck" moving forward but it doesn't automatically clear existing drafts.
Once you clear out those existing drafts the issue should no longer occur. Let me know if you have any questions.
-Dave
accordionmelody So far that's been my experience too -- it happened a bunch of times right after I updated. Now it seems to have stopped. Hopefully it stays that way -- I'll report back if it doesn't.
elioa6 menditto Is this the case after the initial time. I observed as well that after the update, the first time I wanted to edit an item, as before, a previously edited item came up. But after that (even after closing 1Password and reopening it) the issue never happened again and it always opened the item in edit mode that I clicked on.
Same for me every time.
Did not resolve the issue for me. Happened right away after updating. This time when I hit edit on an entry it opened a random different entry, not even one I had recently edited or used.
- 1P_Dave
Hello everyone,
Our developers have released an update to 1Password that includes a fix for the issue where a previously edited item would sometimes show up when you tried to edit a different item. Please update to 1Password for iOS version 8.10.28:
You might see the issue a couple more times after updating as existing drafts are cleared out from the app, this is a data loss prevention measure. Thank you all for your patience while our developers worked to resolve the issue. If you still see the issue with version 8.10.28 then let me know and I'll be here to help.
-Dave
- 1P_Dave
I've merged your thread into the larger thread that's discussing the same issue so that we can keep the conversation in one place. 🙂
I'm sorry that you're running into issues when editing an item using 1Password for iOS. This is a known issue that our development team is actively working on and the team is planning to release a fix as soon as possible.
-Dave
ref: dev/core/core#20148
