In 1Password app, I am trying to enable MFA for a site I select the "Scan QR Code" button and I get this message Note that I have allowed screen recording permissions 1Password Version: 1Password for Mac 8.9.8 (80908009) Extension Version: 2.4.1 OS Version: macOS Monterey 12.6.1 Browser:_ Safari

I am very interested to know if this feature is functional under any circumstance. I haven't found a way to make it work as expected. My suspicion is that the mechanism expects the QR code to be an image within a web browser that has the 1Password extension enabled. If that's the case, I don't understand why permission for screen recording is required. I guess I could spend a few more hours troubleshooting this defect.

I received a response from 1Password Support via email after I sent the diagnostics information, which is weird, because I suspect most 1Password.Community members don't have access to my email. It offered a tip about adjusting my screen brightness, which suggests that I need to provide more context. For background, I have been using OTP Auth for several years. It is good, but limited. I have, until recently, resisted adding TOTP secrets to 1Password because it violated my conception of separate factors. I have since given up this position, since my emergency recovery codes are already in 1Password, so the TOTP authorizer app isn't necessary when performing an attack. If somebody gets into my 1Password vault, the game is over. To enjoy the significant benefits that come from having TOTP in 1Password, I want to transfer all 72 secrets. I have tried multiple exfiltration methods. One method is to copy the secret in Base32 out of OTP Auth for Mac. Unfortunately, the Catalyst app is buggy as hell and the context menu fails to activate and present the copy option. This is not 1Password's fault, but it does mean that I can't use the least error-prone method. The other method for extracting secrets is to have OTP Auth for Mac show the QR code as an image. I assumed that 1Password for Mac would be able to tap into the displayed pixels and grab the currently visible image inside OTP Auth for Mac. These are the things I have tried: * Display QR code in OTP Auth Catalyst app, then click the "Scan QR code from clipboard or screen" button in 1Password. Result: "QR code detection failed" * Thinking that perhaps the issue was with an OS secure overlay feature, I grabbed the QR code image content and saved it as a file to display in Preview. Also fail. * I attempted to copy the image data into the clipboard from Preview. I inspected the clipboard with Keyboard Maestro to verify the content existed. Still, no import to 1Password. * I opened the saved QR code image in Google® Chrome® with the 1Password extension activated, thinking that perhaps the expected customer use case is to import an image from some web page leveraging the extension's ability to inspect the DOM and media. Nope. * I opened the target website and injected an image tag into the page to load my saved QR code, thinking that perhaps 1Password would perform a document.location.origin match on the record being edited in 1Password, because, let's be honest, that's the sort of over-engineering I would subject my customers to. Still nope. The application log is splattered with lines like this: WARN 2023-02-03T08:08:45.492 op_executor:invocation_loop(ThreadId(17)) [1P:op-app/src/app/backend.rs:220] operation blocking event loop invoke Invocation(External(ProcessQrCode(<QrCodeProcessRequest>))) took more than 50 ms (70 ms) I'm running macOS 13.1 22C65 on a Mac Studio. The 1Password for Mac 8.9.15 (80915001) application has been granted Privacy & Security permission for the following: * Location Services * Camera * Accessibility * Screen Recording I will note that running 1Password on iOS and aiming my phone's camera at my ridiculous Apple Studio Display to import what OTP Auth for Mac is showing works flawlessly. It's just not the procedure I was hoping to use. I'm on the production release channel. I am willing to switch to beta, but haven't yet.

1P_Dave I came to the forums to resolve this product issue so that others may benefit. I'm not super interested in having secret email correspondence. The diagnostics output was not necessary in order to tell me whether this product feature is claimed to function currently or not.

@timheilman Thank you for sending in the diagnostics report. I can confirm that the team has received it and that you'll receive another reply via email as soon as possible. Is there a bug status page where I can track the status of this bug? I provided a report as described, but no response. When, and if, the issue is resolved you'll see the bug fix noted in our release notes: 1Password Releases For the time being the best workaround, if you're unable to use the desktop app to scan the QR code on a particular website, is to use the browser extension instead: Use 1Password as an authenticator for sites with two-factor authentication -Dave ref: LDX-94585-796

@Olliecampbell I'm sorry that you ran into the issue as well, thanks for confirming that the workaround also helps on a Windows PC. I've added your report regarding the Sony website to our internal work item for the issue. -Dave ref: dev/core/core#19783

"QR code Detection Failed" message attempting to scan QR

oschrenk
Occasional Contributor
8 months ago
Same issue still on obsidian.md

1Password for Mac 8.10.36
81036049, on PRODUCTION channel

macOS 14.5 (23F79)
Kindsaber
New Contributor
8 months ago
Hi, I want o share I'm experiencing the same issue as well with my Atlassian account (https://id.atlassian.com/2step/enrollment/2-configure-app), 1Password kept failing to detect the QR code on screen and show a rather unhelpful message "QR code detection failed." without any suggestion how to fix it. I'm on Sonoma 14.5, 1Password version:

1Password for Mac 8.10.36 81036049, on PRODUCTION channel
I tried restarting 1Password, screenshot the QR and open it in Preview, no dice. The site offers a way to input without using a QR code but it doesn't seem like 1Password supports this method:
1P_Tommy
Moderator
9 months ago
guhebisavy

The community is open to anyone interested in talking about 1Password. It's not just for those who are already using it. This is a family community for users of any age. I have tweaked your comment to make it more appropriate for our user base here in the community.

We inform here in the community. As needed, we request that folks submit diagnostic information. We offered suggestions that may help anyone encountering it work around it until a resolution can be implemented. The only option we have in the community is to report and help users like yourself with potential workarounds. Things like diagnostic reports are not available here in the community to protect your privacy.

We appreciate your understanding as we work to make the 1Password the best it can be.
guhebisavy
New Contributor
9 months ago
By the way, thanks to @the_actual_jlamoree for keeping the discussion open to the community. That’s how I found out about the Beta fix, 1P_Dave.

Actually, your whole approach in this topic is pretty questionable - I’ll note it, though I doubt you’ll consider it:

The policy should be to keep discussions as public as possible. It speeds up diagnosis, collaboration, and solutions.

This is a space for your customers. Defending yourself instead of collaborating doesn’t add any value to 1Password. Remember, only established users access this forum. The sale is already made.

And, of course, as users, we can see through any excuses. After all, we got here googling about that bug that is right in front of us. It's a bug, and i*t really upsets me* how you tried to say otherwise. moderation action: change the term used

This bug has been around for over a year and still isn’t fixed in the Production version. It goes beyond the purpose of this comment, but it’s a bad sign.
guhebisavy
New Contributor
9 months ago
I can confirm the bug exists.
Additionally, I can confirm that today’s Beta version fixes it. (as 1P_Dave previous mentioned)

1Password for Mac 8.10.34 81034039, on BETA channel
1P_Dave
Moderator
10 months ago
oschrenk

I'm sorry that you ran into the same issue. Our developers are currently testing a fix in the beta version of 1Password, if you're willing to give that a try then you can find instructions here: Use 1Password beta releases

If you're happy with using the browser extension for now then hopefully the fix will make it to the stable version of the desktop app soon.

-Dave
oschrenk
Occasional Contributor
10 months ago
Same issue for https://app.hellosign.com using

1Password for Mac 8.10.33 (81033001)

Using the browser extension finally solved the issue.
1P_Dave
Moderator
10 months ago
I'm sorry for the continued frustration. The team is currently testing a fix in the latest beta version of 1Password for Mac. If you're willing to help us test the fix, you can switch the beta by following this guide:

Use 1Password beta releases

Once updated, try to reproduce the issue again. If you do see the same issue then let me know what website you're seeing the issue on and whether scanning the QR code using the browser extension instead works.

-Dave

ref: dev/core/core#19783
WalterMusings
New Contributor
10 months ago
May 19th, 2024, and the macOS 1Password client is having issues with this feature. 🥺
cterry
New Contributor
10 months ago
I am also having this problem. It fails to scan via 1Password from Mac but I can use 1Password on my iPhone to scan the exact same QR code (from MacOS screen) without issue. QR code scanning used to work for me on MacOS but no longer works. If it helps, the broken QR code was for Streamlabs MFA.