browserpass/browserpass-extension

This extension may soon no longer be supported because it doesn't follow best practices for Chrome extensions.

Opened this issue · 5 comments

Warning from Google Chrome Extensions

Anybody seeing this?

Firefox is still working OK. In my Dev version of Chrome it outright prevent me from running it anymore. Regular chrome at the moment is letting me still run it for the time being.

Without knowing for sure, it might be caused by #320. cc @erayd do you know more about this?

@maximbaz That is precisely what it is. I had entirely forgotten that deadline was coming up!

For the moment, Chrome / Google will just moan about it, but will continue to let you use it. But we do need to get it migrated.

30 Dec 2024 now - and I am still seeing this.
Does this mean I can't use browserpass (and therefore can't use pass?!) I just #&$&%@ installed it! :(

It works so far - we are tracking progress in #320, feel free to subscribe. Help is also very welcome, just keep discussions open as someone is already working on this, to avoid duplicate work.

Talking about coincidences... about the same time I posted the above https://github.com/patgmiller/browserpass-extension.git did commit a "first attempt" at fixing this on the branch 320-migrate-v3-manifest - which for some reason I found 8 minutes after he committed it. I tested that extension and it works, although it gives me this error:
https://gyazo.com/49a79db443a32c46d35d82b38b3e6dce