Quitting 1Password reverts sidebar to 'All items' [Known issue, working on a fix]

jcraven
jcraven
Community Member
edited January 2015 in Mac

For the last few months when ever I open 1Password it shows all items. Whereas previously it always opened to the Logins list. Is there any way to revert to the Logins list when opening 1Password. This would be more convenient if possible.

Comments

  • hawkmoth
    hawkmoth
    Community Member
    edited January 2015

    Doesn't it show the past category you had open?

  • Megan
    Megan
    1Password Alumni

    Hi @jcraven,

    Could you please let us know the version number of 1Password that you are currently using? I've just tested with 1Password 5 and the main app will unlock to the category that I was previously viewing, which seems to make sense to me. :)

  • jcraven
    jcraven
    Community Member

    Hi Megan

    1Password
    Version 5.0.2 (502006)
    Mac App Store
    Just before leaving this reply I selected the Logins Category in the sidebar, I locked 1pw, and closed the App. Then I reopened the App and entered my password. When it unlocked it had again selected All Items in the sidebar. If it would revert to the last category I used it would be very helpful.

  • Megan
    Megan
    1Password Alumni

    Hi @jcraven,

    Thanks for confirming your steps for me! When I had tested earlier, I simply locked 1Password without closing the window. Turns out that's the key step. 1Password will remember your previous selection while locked, but quitting the app does revert to the 'All items' state. I've checked our issue tracker, and this is something that our developers are already working to solve! I've let them know that you'd love to see a fix for this as soon as possible.

    ref: OPM-2536

  • jcraven
    jcraven
    Community Member

    Thank you for looking into this for me. Looking forward to an update sometime in the future.
    Keep up the good work.
    John Craven

  • Megan
    Megan
    1Password Alumni

    Hi John ( @jcraven‌ ),

    Great news - it appears our developers have managed to squash this bug! You should see an update soon that has things behaving properly for you. Thanks for your patience. :)

This discussion has been closed.