-
Notifications
You must be signed in to change notification settings - Fork 31
error when logging in #147
Comments
Thanks for the kind words. Currently I don't have a donation address. Are you a long term user of Bitwarden? It will log you out of every device though. |
I see. Well, if you change your mind I would love to support your efforts.
reset and same error
|
I tried to login using the cli in term and it prompted me for my API client secret. I am wondering if the workflow app isn't handling this scenario. I am still testing but I think logging in via the cli in term fixed the workflow app. |
i tried to do an unlock and got this error:
On a side note, I am not seeing any of these errors except for when I open the debug window in the workflow. |
Thanks for the logs. This one now shows little bit more.
I see that you've set the path and probably you are not using plain brew to install node (and/or bitwarden) Which version of the Bitwarden CLI and Node do you run? If I google just for this error Regarding the Bitwarden workflow login you can set in the config Internally the workflow is still using the bw cli command. My dream is to one day use the API directly and also to have better automated testing against a vaultwarden instance. Anyway back tot he issue. Let me know if anything of the above helped. |
Correct. I use nvm.
bw --version node --version
Done. However, I am getting the same errors.
Seems like the login issue may be related to the error above. I think I am able to login but when I sync folders I have no secrets(passwords) in the folders. When I do a list search manually in terminal I can see that there are passwords and everything seems to work just not syncing in the workflow.
That would be pretty sweet. Though if the cli is fast and reliable it should be good right?
|
Do you really still have the same error with Could you check the path of the binaries of |
Dude this workflow is fucking amazing! Thank you for sharing it. Do you have a donation link?
I am getting the following error when trying to login:
The text was updated successfully, but these errors were encountered: