You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 10, 2024. It is now read-only.
I'm having an issue where the workflow seems to think my vault is always locked. The workflow worked great for me months ago and I'm not exactly sure what changed... Homebrew has updated my cli version to 2024.2.0, but I'm still using version 2.4.7 of the workflow as I'm using Alfred 4. Here are logs showing the workflow saying the vault is locked, me unlocking it (appears successful from the logs), and then saying that it's locked again.
Via the CLI unlocking seems to work fine, although I get a punycode warning that has been mentioned in some other tickets.
➜ ~ bw unlock
(node:24729) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
? Master password: [hidden]
Your vault is now unlocked!
To unlock your vault, set your session key to the `BW_SESSION` environment variable. ex:
$ export BW_SESSION="<redacted>"
> $env:BW_SESSION="<redacted>"
You can also pass the session key to any command with the `--session` option. ex:
$ bw list items --session <redacted>
➜ ~ export BW_SESSION="<redacted>"
➜ ~ bw status
(node:24867) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
{"serverUrl":null,"lastSync":"2024-02-29T17:33:30.531Z","userEmail":"<redacted>","userId":"<redacted>","status":"unlocked"}
The text was updated successfully, but these errors were encountered:
Hey @mckennajones
just noticed now that you're using a very old version.
See the first item in release 3.0.0 that is probably causing your issue. The data structure changed and the workflow always thinks it's not logged in because it can't find some field in the json file.
Have you tried using a new version?
Hi @blacs30 thanks for the response. I'm using 2.4.7 of the workflow based on this comment in the readme:
If you are using Alfred 4, the latest supported version is 2.4.7.
I'm still on Alfred 4 because I have no strong reason to pay the upgrade fee to get version 5. Do I need to be using an older version of the BW CLI potentially?
Hey @blacs30. I installed an older version of the CLI and I'm back up and running. I went with 2023.1.0. Not sure which version breaks things when using 2.4.7 of the workflow. Probably best to add a note to the Readme then we could close this one out.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm having an issue where the workflow seems to think my vault is always locked. The workflow worked great for me months ago and I'm not exactly sure what changed... Homebrew has updated my cli version to
2024.2.0
, but I'm still using version2.4.7
of the workflow as I'm using Alfred 4. Here are logs showing the workflow saying the vault is locked, me unlocking it (appears successful from the logs), and then saying that it's locked again.Via the CLI unlocking seems to work fine, although I get a punycode warning that has been mentioned in some other tickets.
The text was updated successfully, but these errors were encountered: