-
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bitwarden userscript gives "mac failed" error when another session is started somewhere else #7607
Comments
There actually seems to be a cleaner way , Still, I wonder if it's a good idea to check if the stderr contained something like BTW, thanks a lot for digging into this, I was having this error pop-up from time to time and never once thought it could be some kind of session invalidation behind the scenes. |
I used |
@georgettica Please take a look at the attached MR, the userscript requires adding the noninteractive flag and also an if check |
I will test it in the future, didn't see the MR returns early if the issue is detected |
Version info:
latest master
Does the bug happen if you start with
--temp-basedir
?:yes
Description
As in the title.
How to reproduce
bw unlock
.Thinking about it a quick hack is
speaking of which, in this situation the returncode is still 0, so checking returncode doesn't work and it will give JSON decode error later on. (but the returncode might be changed to something nonzero later...?)
The text was updated successfully, but these errors were encountered: