The 1Password Community forums are in read-only mode from Jan 28th - Feb 4th, 2025. Find out more.

Issues with 1Password and Chrome

AGAlumB
AGAlumB
1Password Alumni
This discussion was created from comments split from: Problem with Chrome extension on El Capitan.

Comments

  • zozowine
    zozowine
    Community Member

    Hello, I am also having problems using 1password with El Capitain. It is not working at all. Please help. I have downloaded a new copy but still no use. Help. Thank you

  • AGAlumB
    AGAlumB
    1Password Alumni

    @zozowine: While many are having success with 1Password on 10.11, it isn't yet supported, as it is a beta operating system, so your mileage may vary. We appreciate the feedback, but ultimately we depend on Apple to bring their new OS X to a usable state in the coming months. :)

  • zozowine
    zozowine
    Community Member

    Thanks for the reply. Sorry for taking so long to post. Had to dump el cap anyway, back to yosemite, but still having problems after 10.10.5 update.

  • AGAlumB
    AGAlumB
    1Password Alumni
    edited August 2015

    Thanks for the reply. Sorry for taking so long to post. Had to dump el cap anyway, back to yosemite, but still having problems after 10.10.5 update.

    @zozowine: Hey, no problem. I'm sorry to hear that! I hope you don't mind, but I've split this off into a separate (non-10.11) discussion in the Mac category so we can address your issue separately.

    Can you tell me which 1Password, Chrome, and extension versions you're using there? Also, please tell me the exact steps you're taking, and what is (or is not) happening the way you expect so we can figure out the best plan of action. We've had reports that 1Password is working even in the latest Canary release (v47), so we should be able to get this sorted out for you. :)

  • zozowine
    zozowine
    Community Member

    Ciao brenty, thanks for checking back, here's what's recorded in the error log;
    Library not loaded: @rpath/OnePasswordUI-Mac.framework/Versions/A/OnePasswordUI-Mac
    Referenced from: /Applications/1Password 5.app/Contents/MacOS/1Password 5
    Reason: no suitable image found. Did find:
    /Applications/1Password 5.app/Contents/MacOS/../Frameworks/OnePasswordUI-Mac.framework/Versions/A/OnePasswordUI-Mac: code signature invalid for '/Applications/1Password 5.app/Contents/MacOS/../Frameworks/OnePasswordUI-Mac.framework/Versions/A/OnePasswordUI-Mac'
    That's the gist of it. It can't find the library... It happened after update to Yosemite 10.10.5, so right now I can't use 1password on my computer. Help, if you can, would be greatly appreciated.

  • littlebobbytables
    littlebobbytables
    1Password Alumni

    Hi @zozowine,

    It sounds like something is damaged so I would suggest the following.

    1. Drag the 1Password application from your /Applications/ folder to the Trash. Please don't use an app cleaner.
    2. Reboot your Mac.
    3. Download 1Password again from the same place you purchased it. As you reference 1Password 5 it sounds like you're a AgileBits Store user so you will want to download from our AgileBits Download page.

    If that doesn't resolve it please do let us know.

  • littlebobbytables
    littlebobbytables
    1Password Alumni

    Hi @zozowine,

    If that doesn't work this post may be something else worth trying. I don't know if it will help but it could be worth trying.

  • zozowine
    zozowine
    Community Member

    Ciao All, Thank you for trying to solve my problem. Turns out it is a hardware issue with my MacBook Pro. I'm at Apple Store now waiting for the verdict. Probably SATA cable. Seems they degrade with age and my 5.5 year old MacBook is just about that old.
    Thanks again for all of your efforts.

  • AGAlumB
    AGAlumB
    1Password Alumni

    Turns out it is a hardware issue with my MacBook Pro. I'm at Apple Store now waiting for the verdict. Probably SATA cable.

    @zozowine: Oh dear... Of all things it could have been! :dizzy:

    But it certainly makes sense that things wouldn't work right if data is being either read or written incorrectly — or both. I'm glad to hear that Apple is on the case, and I wish you and your poor Mac a speedy recovery. We're here if we can be of further assistance!

This discussion has been closed.