Signing back into the Community for the first time? You'll need to reset your password to access your account. Find out more.
Forum Discussion
Former Member
3 years agoBUG: cli auth prompt immediately dismissed with Apple Watch [macOS]
Hiya,
I'm having an issue as of this morning using the 1password cli integration with the 1p8 mac beta.
It launches the prompt for me to authorise an action, but its immediately dismissed (i see it flicker), and I get the following error:
authorization prompt dismissed, please try again
1Password Version: 80700002
Extension Version: Not Provided
OS Version: 12.3
- Former Member
Hey all! The latest nightly release of the 1Password app contain the major update to the authorization prompts I talked about earlier this week. The new prompts not only look prettier (if you ask me), but I expect them to solve the reported issue as well.
You can try out the nightly release by following these steps, but selecting "Nightly" instead of "Beta" as the release channel. Alternatively, these will be available in the beta release sometime soon.
If you give it a try, let me know if this resolves the issue!
- 1P_Rob
1Password Team
Hey, @maxcbc! I'm sorry for the huge delay here. Are you still having this issue? I've reached out to the right team to see if we can get you an answer if so.
- Former Member
Hey!
We have made a few improvements to the authorization process recently. So if you are still having this issue, could you try out the latest beta release? You can read here how you can switch.
Let me know if that resolves it.
Joris
- Former Member
Hi, I have the same error, the version that I'm using for 1password-cli is 2.0.2, and for 1password 8.7.0~90.BETA
In the console shows the follow messages
INFO 2022-04-22T10:33:34.432 tokio-runtime-worker(ThreadId(5)) [1P:native-messaging/op-native-core-integration/src/lib.rs:307] Extension connection accepted.
WARN 2022-04-22T10:33:34.448 op_executor:invocation_loop(ThreadId(14)) [1P:foundation/op-sys-info/src/process_information/linux.rs:394] no top-level parent was found for pid 172170
ERROR 2022-04-22T10:33:34.464 tokio-runtime-worker(ThreadId(5)) [1P:native-messaging/op-native-core-integration/src/connection_handler.rs:60] message from b5x was None: EndConnection
ERROR 2022-04-22T10:33:34.464 tokio-runtime-worker(ThreadId(5)) [1P:native-messaging/op-native-core-integration/src/connection_handler.rs:31] Dropping connection with b5x due to error handling incoming message: EndConnection
ERROR 2022-04-22T10:33:34.464 tokio-runtime-worker(ThreadId(5)) [1P:native-messaging/op-native-core-integration/src/connection_handler.rs:63] failed to receive message from b5x: Io(Os { code: 104, kind: ConnectionReset, message: "Connection reset by peer" })
ERROR 2022-04-22T10:33:34.464 tokio-runtime-worker(ThreadId(5)) [1P:native-messaging/op-native-core-integration/src/connection_handler.rs:31] Dropping connection with b5x due to error handling incoming message: EndConnection
ERROR 2022-04-22T10:33:34.464 tokio-runtime-worker(ThreadId(4)) [1P:native-messaging/op-native-core-integration/src/connection_handler.rs:63] failed to receive message from b5x: Io(Os { code: 104, kind: ConnectionReset, message: "Connection reset by peer" })
ERROR 2022-04-22T10:33:34.464 tokio-runtime-worker(ThreadId(4)) [1P:native-messaging/op-native-core-integration/src/connection_handler.rs:31] Dropping connection with b5x due to error handling incoming message: EndConnection
- Former Member
Hey! That does not look right. Could you tell which OS/distribution you are using?
- Former Member
Same problem here. Happens when biometric unlock is enabled. If I disable biometric unlock, I instead get "You are not currently signed in".
1Password for Mac 8.7.1
1Password CLI 2.4.1
MacBook Pro, Intel i9
macOS 12.3.1 - Former Member
I'm not sure what changed, but for some reason it seems to be working now, at least for the moment. Here's what I've done since my previous post, as best I can recall:
- Disabled biometric unlock and signed in manually with
eval $(op signin)
. - Successfully ran a couple of
op
commands. - Tried turning biometric unlock back on after having successfully signed in the old-school way, but it didn't seem to work right away.
- Turned biometric unlock off again.
- Closed the terminal where I had tested manual sign-in and went back to other tasks.
- A few hours later, I decided to give it one more try before closing up shop for the day, so I turned biometric unlock back on one more time.
It was at this point that I ran an authenticated
op
command and the authentication prompt actually stayed on-screen and allowed me to unlock with my Apple Watch. I then went to the 1Password app, explicitly locked it from the menu, then closed the 1Password window. When I went back to the terminal window and tried the command again, it prompted again for authentication as expected, and again the prompt remained on-screen and allowed me to unlock. - Disabled biometric unlock and signed in manually with
- Former Member
Hi,
I'm also experiencing the same thing. For me my Apple Watch auth prompt closes itself. I'f I'm not wearing my watch, it won't ask via fingerprint (when available) will instead just take a password or give me a "allow" option for ssh access.
Happy to post a log in here, if someone can let me know that's no sensitive information in it, and that it'll be useful.
Here's a gif:
- Former Member
Thank you both for reporting back with more details. We have seen some similar reports when using Apple Watch. To see if these cases are indeed similar:
- When you are running into this problem, is your Mac in clamshell mode by any chance?
- And when you run into this problem, are you still able to unlock macOS itself with the Apple Watch?
@jamesstidard, logs are definitely helpful! The logs do not contain any secrets like your account password and we go out of our way to make sure there is as little sensitive information in there as possible.
About 1Password diagnostics information
You can send a diagnostics report by following these instructions:
Sending Diagnostics Reports (Mac)
Attach the diagnostics to an email message addressed to
support+forum@1password.com
.With your email please include:
- A link to this thread:
https://1password.community/discussion/128135/bug-cli-auth-prompt-immediately-dismissed
- Your forum username
You should receive an automated reply from our BitBot assistant with a Support ID number. Please post that number here. Thanks very much!
- Former Member
I've not been wearing my watch while working because of this, just put it on to try and get you the details love, but it's working again now. Will report back with stuff above if it breaks again.
Thanks.