I waited a bit b/c I was busy and wanted to make sure it didn't fix itself. Old build passed and it narrowed down around July with 104 which aligns with experience. To try to and recreate that through regression testing I used the -profile-persistence=copy-first and logged in the first time and used that profile for each test.

But if I log in to my Firefox profile with just lastpass enabled it failed. So I did some tests and it was pretty confusing.įirst confusion bit, a clean profile with just lastpass I was able to log in cleanly. Tested on the latest Nightly (108.0a1/20221018213916) and Release (106.0/20221010110315) aas well as the latest available snap builds of Nightly (107.0a1/20221013022417 – canonical-002) and Release (106.0/20221014183137 – canonical-002).Īs for errors in the browser console, I only get a “ExtensionError: No such native application ”, on both the normal builds and the snap ones, but that does not hinder the login process or any other extension function it seems. So I cannot reproduce the issue even so, at least on what OS I have available. Of course, I accept and I’m logged in without any issues and not logged out.

On the authenticator app I get a prompt to either accept or reject the login request and a I think a 1 minute timer to do this. Now, each time, after I submit the email and password via the login form, I’m asked for a passcode. Firstly, I just want to point out that the only available Linux I have access to, is Ubuntu 16.04 LTS, without the possibility of an update unfortunately.Īs per Comment 9, I’ve set up MFA via the LastPass authenticator app on my phone.

Lastpass chrome extension not working