Changing an existing login password fails to sync (Dropbox) until I add a new field to the item

whenney

Last night, I changed the password of a login item on my iPhone. This morning on my Mac I was surprised to see that 1Password still showed the previous password. I checked my iPad and it had the same problem. So, to check if sync was working I added a new item on my iPhone, and that appeared straight away on my Mac and my iPad. So far, so good ... but the password change still did not sync.

Next, I looked at the modification times on the files in the 1Password.agilekeychain/data/default folder and it appeared that the <long hash code>.1password file for the login item in question had not been recently changed. So that gave me the idea of adding a new field to that login item, to try and force it to sync. I added a Text field on my iPhone and it worked: the change was synced immediately to my other devices, including the new password that I set last night.

On the one hand, this is not such a serious problem since I have found a workaround. On the other hand, it is a bit of a pain to have to add a new field every time I want a password change to sync, and this is surely not the way things are supposed to work.

---

1Password Version: 6.5.4 on iOS, 6.7.1 on macOS
Extension Version: Not Provided
OS Version: iOS 10.3.1, macOS 10.12.4
Sync Type: Dropbox

Ben

Hey @whenney,

Thanks for taking the time to write in. If changes are not being properly synced that is certainly concerning. Are you able to reproduce this issue? e.x. If you create a new login item > save it > make sure it synced to the Mac > change the password on iOS > see if the change synced.

Please let me know how it turns out.

Ben

whenney

Hi Ben - thanks for getting back to me.

Yesterday, I did manage to reproduce the issue on a different login item (albeit not one created from scratch).

But, today I can't reproduce the issue at all! That is, I followed your advice to make a new login item and every time I changed the password on iOS, it synced very quickly to the Mac. Then I went back to one of the login items that showed the issue yesterday and that too is syncing password changes perfectly today.

So, I seem to have found a heisenbug :(

The only thing I can think of is that it might somehow be related to the age of the item. The items that showed the issue yesterday were originally created on July 3 2008 and Aug 17 2013, so presumably have gone through several database migrations. Anyhow, feel free to close the issue. I'll just keep an eye out in case it happens again.

By the way, I have using 1Password since January 2008 and this is literally the first time I have had need to report an issue (and then it turns out to be non-reproducible ...). So, not bad going!

Cheers, Will

Ben

Thanks for the update and the feedback, Will! If you run into it again please do let us know!

Ben