perusjamppa 1 Report post Posted September 30, 2020 I have older install on MacBookPro (2019) that does not have this issue but newer install on MacBook Air (2019) that has this annoying issue. I have checked that that settings are the same on Enpass on both. MacOS is the same (Mojave multiple versions) and Chrome version is the same (using Chrome extension). Thanks for checking this issue! 1 Quote Share this post Link to post Share on other sites
someenpassuser 0 Report post Posted November 7, 2020 I sent a video via PN Quote Share this post Link to post Share on other sites
Pratyush Sharma 82 Report post Posted November 9, 2020 Hi @someenpassuser, We have taken note of this and our team is now analyzing into the issue. Quote Share this post Link to post Share on other sites
BerndD 0 Report post Posted November 19, 2020 (edited) . Edited November 21, 2020 by BerndD Quote Share this post Link to post Share on other sites
BerndD 0 Report post Posted November 19, 2020 Same here: MacBook Air 13" Late 2013 / tryed on Cataline and Big Sur / version 6.5.2 (726) from AppStore / preferences are the same as postet on image before / problem starts suddenly under Catalina, but i changed nothing. After updating on Big Sur same problem. Every Start Enpass starts with the LockIn Screen. I must stop running it in the foreground. Then i can use it by clicking the Icon in the Menubar. Quote Share this post Link to post Share on other sites
Garima Singh 80 Report post Posted November 20, 2020 Hey @BerndD Apologies for the trouble. We are looking into this issue. Your co-operation will be highly appreciated. Quote Share this post Link to post Share on other sites
erikrojo 0 Report post Posted November 26, 2020 Same issue here. I have an MacBook Air M1 with Fingerprint and Big Sur. I did not have this issue on my Intel MacBook Air with PIN, though. It happens after rebooting the machine. A fix would be appreciated. Quote Share this post Link to post Share on other sites
Pratyush Sharma 82 Report post Posted November 27, 2020 Hi @erikrojo, Sorry for the inconvenience caused to you. Our team is working on it. Hopefully, fix will be available in the future updates. Till then, we will request you to please co-operate with us. Quote Share this post Link to post Share on other sites
