MAS 1PW 5.4 First Launch

Community Member
edited October 2015 in Mac

A rocky start to a new version. Both my Macs exhibited this symptom. I am running 10.11

After the upgrade to 5.4 from MAS, 1st launch of 1PW is broken. All I have is 1Password in the menubar upper left, but no ability to get the window open. On my MacBook, I did briefly see "failed to connect to 1PW mini".

Quitting 1PW normally doesn't work, so had to force quit the app. Second time I open 1PW, it works normally. Of course I have the window issue where an unlocked 1PW exhibits the graphic jitters, on both of my Macs.

Is this really what we should expect from AgileBits??

1Password Version:MAS 5.4
_Extension Version:
Not Provided
_OS Version:10.11
_Sync Type:DropBox


  • MikeT
    edited October 2015

    Hi @VirgilBoy,

    These are El Capitan related bugs that doesn't pop up for all users, just specific Macs. We're trying to work around these bugs but no progress yet. The initial app launch didn't right work off the bat for some users because of how the Mac App Store incorrectly flag the file after installing it. If you're still seeing that problem, please try this suggestion and see if it will work.

    For the jitter issue, try to drag the window below the search field, it will then move around smoothly. We're working on a fix and it should be available soon.

  • VirgilBoy
    Community Member

    Hi Mike

    So far, it seems only the very first startup of 5.4. I have not had any reoccurrence. At this point...working normally, as is the beta Safari extension

  • littlebobbytables
    1Password Alumni

    Greetings @VirgilBoy,

    Do please keep us updated but hopefully things run smoothly now.

  • Drew_AG
    1Password Alumni

    Hi @sashk,

    Yep, very first start up of 5.4 on multiple systems.

    I'm hoping that means 1Password launches correctly for you now, and if so, yay! :lol:

    But if you're still having any trouble trying to open the 1Password app, please let us know. Thanks!

  • AGAlumB
    1Password Alumni

    @sashk: I'm sorry to hear that. It sounds like maybe OS X is having trouble punching mini for some reason (or there's some delay). Would you be willing to try the beta to see if that resolves the issue?

This discussion has been closed.