moderato_burrito

Or at least open it up, or provide instructions on how a user might implement.

I'm sad to see that I'm only the second person commenting here. +1! Give 1Password a run for their money, and create an Alfred integration!

Thanks. I should've searched harder for existing threads. Fingers crossed for a fix.

Same problem. I created my own post though, not finding this one:

I am experiencing the same issue described in this older post. What happens is: Enpass goes idle. I unlock it in the Chrome browser extension. It waits for a little while, and tells me that Enpass is empty. If I check the Enpass desktop app for MacOS, it also says it's empty. I can fix this temporarily but closing Enpass, and reopening it. However, this is annoying. I've had to do this twice this morning already, and many times over the past week. I'm running Enpass 6.6.0 (772), on an M1 MacBook Air, running MacOS 11.2.1 (20D74).

+1. This issue is almost 3 months old. This is a dramatic usability problem.

Hi @Anshu kumar, actually I've not had this problem since. Clearly there's some intermittency. Obviously something idiosyncratic going on here. I'm using Enpass 6.0.7 (336) for Mac with version 6.0.2 of the Chrome extension.

If it helps, from my end I work on a 2016 MacBook with a 12-inch screen (2304 x 1440) and that is plugged into a Dell SE2416H 23.8" Full HD (1920x1080) monitor. The resolution was completely wrong in the Dell monitor. However, the plot thickens. If I move a Chrome window to my MacBook screen and click reveal, the browser extension pop-up for Enpass, it renders properly. Now that my Chrome window is back on the Dell screen again, it is working again fine after moving it back and forth. So this seems to happen intermittently, when changing displays. I had the same issue a couple of weeks ago over a low-resolution projector (not sure of the resolution).

Guys, this is pretty crushing. Also having the same problem on Chrome, Safari and Firefox (all latest as of writing this), on MacOS 10.14.5. Your app is proving inconvenient at the moment. Tried reinstalling the extension here but the same thing is happening.