That lead me to think that it was not detecting existing instance. After trying multiple times I have realised that browser extension attempts to start new instance of Bitwarden even though one is already running. The workaround with tmp directory creation did not help. In the meantime manually creating the tmp directory inside ~/Library/Containers//Data should resolve the issue.įWIW I had exactly same problem. I've opened a PR which should fix this issue. ![]() If there is, chances are that the newest version is the cause. Btw this is my case, I don't know if anybody else has a similar experience like me. Potentially, but I haven't found a downgrade option in the Mac App Store, so I cannot test it out. I also run the Mac App Store version btw.Ĭheck to see if the directory exists ~/Library/Application\ do have the NativeMessagingHosts directory, with a file inside of it. So you're saying that solution worked for you on the previous version (should be 1.24.1) the newest 1.25.0 broke it again? Then nothing happened for a few days, until recently (4 days before my last post), I confirmed that there was an update which went silently in the background (In order to use fingerprint auth, we have to use the Bitwarden Desktop App from the Mac App Store, and I didn't turn off auto-update in my macOS system preferences), update information in the Mac App Store shows that Bitwarden Desktop updated 4 days ago, which corresponds with the time when the same issue came up again. At that time, my guess was that macOS does this permission stuff to enhance security, creating their so-called "Containers" to limit system resource accessibility, or at least the Chrome sandbox environment does that. ![]() ![]() When I first set up Bitwarden browser extension, I ran into the same issue like the OP posted above, but solved by enabling Allow access to file URLs thanks to the link that I mentioned above. Worth noting: I saw that this option in Chrome Extensions was set to be a solution for others reporting this issue, but it doesn't solve it for me I got same issue, have the same environment as except for using Browser Extension version 1.49.1
0 Comments
Leave a Reply. |