1Password 8 not working in some Mac user accounts

Same issue for two of my family members on their shared iMac.

Support ID #WAL-23788-774 refers

I have the same problem. My account works just swell , but my wife’s account (same machine [catalina 10.15.7] ) no joy there.

Crash report:
Process: 1Password [3586]
Path: /Applications/1Password.app/Contents/MacOS/1Password
Identifier: 1Password
Version: 8.9.4 (8.9.4.125339)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: 1Password [3586]
User ID: 503

Date/Time: 2022-09-12 09:51:13.072 -0600
OS Version: Mac OS X 10.15.7 (19H2026)
Report Version: 12
Anonymous UUID: 74C840C2-DA4A-CD41-70BC-09979F810689

Time Awake Since Boot: 1200 seconds

System Integrity Protection: enabled

Crashed Thread: 0

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Termination Reason: DYLD, [0x1] Library missing

Application Specific Information:
dyld: launch, loading dependent libraries

Dyld Error Message:
Library not loaded: @rpath/libffmpeg.dylib
Referenced from: /Applications/1Password.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework
Reason: image not found

Roger

Hi @fl6nders:

My colleague Alvin has recently replied to you, can you please continue the conversation there?

ref: QKY-28757-457

@FragileBits:

I was able to locate your conversation, so we'll be in touch soon.

ref: WAL-23788-774

@lasllcap:

Can you please share the crash report with us? Include it as an attachment to an email addressed to support+forum@1password.com, and include your username: lasllcap. After emailing in, you'll receive a support ID that looks something like [#ABC-12345-678]. Post that here, and I'll be able to make sure your message has gotten to the right place. Thanks!

Jack

When might I expect to hear back with a solution, please?

It's been over 24 hours since I submitted the crash report and confirmed the support reference here.

My elderly father, who followed my recommendation to rely on 1Password and who followed the prompt in version 7 to upgrade to 8, remains unable to access the program. He is, understandably, feeling very confused, upset and frustrated.

Hi @FragileBits:

I'll follow up shortly to your email. Thanks for your patience on this!

Jack

ref: WAL-23788-774

Thank you @Jack_P_1P :)

@FragileBits

Thanks again for your patience. I'm happy that Jack was able to help over email. 😊

@Jack_P_1P Hello and hope this message finds you doing well. Long time 1Password Family user here and recently upgraded from 1Password 7 to version 8 and oh boy do I regret it. I have this same issue as listed here where one user on my iMac works with 1Password and my wife's user doesn't work. It sounds like there is a solution available so I'm genuinely curious why you just wouldn't post the solution here but instead make each individual user open a new ticket?

Hi @bruceg11,

Sorry to hear you're experiencing something similar. We generally want to confirm what the issue is before making suggestions, lest we send anyone down the wrong path. That said, what some users in this thread have experienced has since been addressed in our nightly build. If you're open to trying that, you can change your release channel in 1Password 8's preferences:

If you have automatic updates turned on, you'll be updated to the new version within 24 hours of making this change. Alternatively, or if the issue persists, you can also send a crash report to support+forum@1password.com and we can take a closer look.

Let me know and we can figure out our next steps from there. 🙂

ref: dev/core/core#14740

Sorry to say this problem recurs with each update. I'm in my third go-round.

This is the fix -- it still works -- given by the 1Password Support Community:

Open Terminal.app from an administrative account, and enter the following commands.

cd /Applications/1Password.app/Contents/Frameworks/Electron\ Framework.framework
sudo chmod -h 755 ./Electron\ Framework ./Helpers ./Libraries ./Resources
cd Versions
sudo chmod -h 755 ./Current

Although I'm grateful for the fix, it is most perplexing why the issue persists.