Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
System
2 years agoSuper Contributor
Touch ID prompt not focused
This discussion was created from comments split from: 1Password window take the focus and block the unlock via TouchID on latest MacOS.
14 Replies
- 1P_Dave
Moderator
Thank you for posting the Support ID! I see that my colleague has already sent you a reply, please continue the conversation over email. 🙂
-Dave
ref: LXY-15318-193
- JonasKrauschNew Contributor
Sure, here's my support ID
LXY-15318-193 - 1P_Dave
Moderator
Thank you for those detailed reproduction steps! I can't quite reproduce the issue with the SSH agent prompt, would you mind sharing the video that you mentioned? Please send an email to
support+forum@1Password.comwith a link to this thread.After emailing in, you'll receive a reply from BitBot, our friendly robot assistant with a Support ID that looks something like [#ABC-12345-678]. Post that here, and I'll be able to locate your message and send you a secure upload link for your video.
-Dave
- JonasKrauschNew Contributor
I have the same issue (using latest Beta release)
I use VS Code that regularly fetches any git changes. This uses the 1Password-SSH-Agent to get my SSH-Key. When it tries to fetch repositories but 1Password is still locked, the prompt comes up but gets it focus claimed by the 1P Password prompt a few seconds later.Steps to reproduce almost every time:
- Lock Macbook
- Unlock Macbook (1Password (including SSH-Agent) is still locked)
- Swipe through full-screen Spaces Spaces: Arc, VS Code, Terminal Swiping from Terminal to Arc or from Arc to Terminal
- VS Code tries to fetch all repositories as soon as it gets focused for a second (and last fetch was more than x minutes ago) and requests the SSH-Key from 1P.
- Then the Touch-ID prompt comes up (alone)
- Most of the time - as my finger reaches the Touch-ID Button - the second window spawns behind the Touch-ID prompt and claims the focus.
I can also share a video.
-Jonas
- 1P_Dave
Moderator
Our developers are aware of an issue where the Touch ID prompt isn't focused in certain situations if you're using another app in full screen. I've added your report to the internal work item open for the issue, hopefully it can be fixed in the future. I'm sorry for the inconvenience.
-Dave
ref: dev/core/core#16733
- MrCSuper Contributor
I get this a fairly often too. Last steps I recall was opening 1Password via Alfred, from a full screen app in another space (e.g. space 2). 1Password launched on space 1, with the touch dialog not focused. I recall this scenario occurring a few times.
- 1P_Dave
Moderator
Thanks for the reply. Are you using macOS Spaces? Or multiple monitors? Or just a single monitor with a single desktop?
The next time that the issue occurs let me know if you're able to note down the steps that you took before the Touch ID prompt appeared out of focus.
-Dave
- pixelmachineOccasional Contributor
Following the steps you outlined the correct item is always focused. And normally the correct item is focused too. It's intermittent, which makes it tricky to pin down.
- 1P_Dave
Moderator
Thank you for the screenshot. The small dialog that you see behind the Touch ID prompt will appear if you click "Use Account Password" in the Touch ID prompt, otherwise it shouldn't be appearing when Touch ID is turned on.
As a troubleshooting step to help me understand the situation, do you consistently see the focus issue when you do the following:
- Open Safari.
- Lock 1Password.
- Click on the 1Password icon in Safari's toolbar.
- Click Use Account Password in the Touch ID prompt that appears.
- Click on the fingerprint icon in the "1Password is trying to unlock the browser extension" dialog.
This will bring up the Touch ID prompt. Is it focused?
-Dave
- pixelmachineOccasional Contributor
This is still happening but it's inconsistent and always when I'm working so I can't really take a full screenshot nor do I necessarily remember. Attached is another image. This was triggered again from Safari. I'll try to do a diagnostic next time.