[Bitwarden Vault] Continuously errors with server URL preference changed

[lhjt]

Extension

https://www.raycast.com/jomifepe/bitwarden

Description

I recently updated this extension and noticed that it downloaded its own copy of the bitwarden CLI. I do have a custom URL for my instance.

Since the update, it now always greets me with this error:

l have configured the CLI and extension to use my custom instance URL but the error persists. My guess is that the extension has not updated the config for its own internally downloaded bitwarden CLI with the new server URL address.

I have reinstalled the extension and reconfigured everything, to no avail. I have also tried providing the path to my own bitwarden CLI binary, and the issue persists.

Steps To Reproduce

1. Install the extension
2. Configure a custom server URL
3. Try to run the "search vault" command

Current Behaviour

Explodes with the screenshot in the description

Expected Behaviour

Should not explode

[raycastbot]

Thank you for opening this issue!

🔔 @jomifepe @daniel-stoneuk @pomdtr @andreaselia @pernielsentikaer @eth-p @YamenSharaf @undefinedzack @anirudhganwal06 you might want to have a look.

💡 Author and Contributors commands

The author and contributors of jomifepe/bitwarden can trigger bot actions by commenting:

• @raycastbot close this issue Closes the issue.
• @raycastbot rename this issue to "Awesome new title" Renames the issue.
• @raycastbot reopen this issue Reopen the issue.

[Geezus42]

Related: #10977

[Geezus42]

I know you already tried specifying the path, but I just pointed the extension to /opt/homebrew/bin/bw, and now it's working better than ever.

[lhjt]

Unfortunately I am still experiencing the issue with that setting (I just restarted raycast as well):

[jomifepe]

Hey, thanks for reporting. I'm gonna look into this soon.

[lhjt]

Hey @jomifepe thanks for the update - I see that you updated the extension in #10977 (comment) and that seems to have solved the problem!

Things are working now. Shall I close this issue?

[jomifepe]

Great to hear, I gotta say that I wasn't expecting it to fix this issue, but it shouldn't have broken in the first place, so great 🙂

Thanks for the update!

@raycastbot close this issue