blacs30 / bitwarden-alfred-workflow

Simple Bitwarden Workflow for Alfred
MIT License
448 stars 31 forks source link

Unlock results in "No Password returned." error #194

Open rodrigobdz opened 7 months ago

rodrigobdz commented 7 months ago

I followed the installation instructions in the readme but encountered an error which is not documented in the troubleshooting section.

What could be causing this error and how could I fix it?

image
shreyasgm commented 6 months ago

I'm facing the same issue. For now, I've had to switch to this newer extension, which is working well so far: https://github.com/ajrosen/Bitwarden-Accelerator

blacs30 commented 6 months ago

@shreyasgm was it working for you in the past? I wonder how the two workflows compare? Great that there is an alternative for all Alfred users.

shreyasgm commented 6 months ago

It was indeed working great for me in the past - thank you for this wonderful workflow @blacs30 . I recently decided to do a fresh reinstall of some of my workflows, which is when it stopped working for me. I tried troubleshooting for a bit and eventually landed on this inscrutable issue and decided to look for an alternative. The two workflows are almost exactly identical in functionality (at least to the extent that I use bitwarden with Alfred). I'd actually prefer to stay with this extension since it's more widely used (and hence probably more secure / battle-tested). Thanks again!

kelbyers commented 5 months ago

I'm having a similar issue, but getting a different error. Whenever I try to sync my cache, I get an error saying that bitwarden needs to be unlocked. I enter my master password. It doesn't display any errors, but every attempt to sync the cache tells me that it needs to be unlocked.

I've also tried using the cli integration, and logging in with bw login. I am able to run cli commands, such as bw get successfully. Then I use bwauth_save_to_Alfred. That prompts for my password again, and doesn't show any errors, but I still get the error in the workflow saying that my account needs to be unlocked.

This seemed to start happening after I updated the cli to version 2024.4.0 about a week and half ago.