Beta 2016.6.204d broken for local vaults [Fixed]

zendnez

I have a local vault (DropBox synced) that has 567 items. I've been using this with earlier desktop betas. The beta self updated today.

Category headers are displaying incorrectly as are items.

I closed and re-opened the vault. No change.

This is an agile key chain vault. The attached image illustrates the issue.

Thanks.

---

1Password Version: 2016.6.204d
Extension Version: Not Provided
OS Version: Win10
Sync Type: Dropbox

MikeT

Hi @zendnez,

Thanks for reporting this, we are investigating this and shipped an update that may help.

Please restart the desktop app to install the latest update and let us know if it is better.

zendnez

The app updated to 205d. The problem is still present. I've quit and re-launched several times to reduce the likelihood that issues with ux refresh are involved. I have not attempted to remove and re-open the vault or removing and re-adding the account. Let me know if you'd like me to try either of those.

MikeT

Hi @zendnez,

Could you email us your 1Password logs. To do this, unlock 1Password, reproduce the issue by switching to that local vault and then enter /log in the search field. It'll open up 1Password's log window, please click on Save, and save it to your desktop.

Could you email that log file to us at support+windowsbeta@agilebits.com and in the email, include your forum username as well as the link to this thread, so we can connect the email to this thread.

Let us know here when you sent the email, so we can confirm we got it.

Thanks!

zendnez

Mail sent.

AGAlumB

@zendnez: Thanks! I see that we've received your email, so we can continue the conversation there. We'll take a look at the diagnostics and get back to you shortly! :)

ref: TVZ-13543-539

zendnez

Sergey requested that I delete the sqlite db. I did so, set up the account/vault again, and the problem did not repro.

MikeT

Hi @zendnez,

Thanks, in that case, it was a known bug we immediately fixed in the next beta update. Unfortunately, some got affected and need the db to be reset to fix this correctly.