mrc247

I can confirm that your workaround also works on macOS. It seems all versions (Windows/macOS/Linux) have the same bug. Thanks again for sharing this simple but effective tip!!! It's even more ridiculous that as a customer you can't get this information from the official Enpass support or that this simple error is finally fixed.

Hi Abhishek Dewan, I just installed the new version 6.9.1 and guess what, the error hasn't been fixed. It's really starting to get ridiculous. This is only the fourth update in 2023. You might think Enpass will soon be out of support. How can it be that errors that were reported 10 months ago and are quite simple cannot be fixed?

Many thanks to everyone who shares with us here in the thread that they have the same problem! Thank you for sharing this workaround with us. Before I try it myself I have a question: If I remove the key file and add it back, is it a new file so I have to replace it on all my other devices as well? or does it remain the same file during the process?

Hi Abhishek Dewan, I just installed the new Enpass version (6.9.0) and I can't believe the bug hasn't been fixed yet. WTF It's been 7 months since I reported the bug. I'm lost for words..

Unfortunately not, I already had the same idea. ;-)

Thanks for the information. Then let's hope it doesn't take another four months.

You are not serious, are you???

The problem you describe has existed for months, among many other problems... but nobody at Enpass seems to care about the Mac version's problems. I'm sorry to say this so harshly, but all these issues were reported by several users months ago.

maybe we should switch to another password DB provider.. unfortunately the state of the Enpass Mac version is no longer sustainable and the speed of bug fixes is certainly not

What is the status of this issue? Unfortunately it still exists.

What is the status of this issue? Unfortunately it still exists.

What is the status of this issue? Unfortunately it still exists. in the meantime the thread and the problem had its 3 year old birthday. So happy birthday!

When will the problem I described be fixed??? It annoys me to death having to manually select the key file every time Enpass starts on the Mac. I already opened a support case and this thread in mid-December 2022 and have not received an answer... four months later..

should I open a support case for this?

As I mentioned in the other thread, I have the same problem: It first appeared after updating to Enpass 6.8.3 in early October. (The same update also destroyed the Dropbox Sync for me) I use Safari on macOS. it seems to help to quit and restart the Enpass app, then the problem goes away until it occurs again at some point. My Setup: Intel based iMac macOS 13.1 Safari 16.2 Enpass 6.8.4 (1166)

Today I had the problem again and it seems to help to quit and restart the Enpass app, then the problem goes away until it occurs again at some point. My Setup: Intel based iMac macOS 13.1 Safari 16.2 Enpass 6.8.4 (1166)

latest GA version (of course) macOS 13.1 Safari 16.2 Enpass 6.8.4 (1166)

Yes, this time I got a response from support. It wasn't my fault that the Dropbox problem resulted in a total of 3 cases. After I hadn't received an answer to the first case for more than three weeks, I responded to the automatic answer because I wanted to know what the status was and this automatically opened case no. 2. When I hadn't heard from Case No. 2 for two weeks, I asked again and since Case No. 2 was apparently simply closed without a solution, Case No. 3 was automatically generated. But I didn't get any reaction to Case No. 3 either. That was one of the worst support experiences of my life. And I make my money as a system administrator who constantly has to open cases with companies like VMware, NetApp or HPE. Thank you for your understanding that I'm a little annoyed that I also have to analyze problems caused by an Enpass update in the evening.

Yes, the steps you suggested helped. It's a pity that the official Enpass support still hasn't responded to my case. Unfortunately, I have a new problem with the Enpass Reset you suggested:

I have the exact same problem, but it doesn't always happen. It first appeared after updating to Enpass 6.8.3 in early October. (The same update also destroyed the Dropbox Sync for me) I use Safari on macOS.

Unfortunately, to solve the Dropbox sync problem, I had to completely delete Enpass and set it up again with a backup. I also have to reset all the settings in the application. Since then, the option "Remember the location of the last used key file" no longer works. Before my Enpass reset, I always only have to enter the master password at Enpass start, the key file was already selected. Now after the reset, in addition to the master password, I have to click on "Select key file" every time and then select the file. I would open a case with Enpass Support, but unfortunately the cases I open, for example because of the Dropbox Sync. Problem, either not answered at all or they are simply closed unresolved. So please, can someone help me to solve the problem and restore the state before my Enpass reset. Many greetings macOS 13.1 Enpass 6.8.4 (1166)

I upgraded my iMac to macOS 13.1 (Ventura) and you can guess... ...that's right, the problem that has existed for almost 3 years now, that Enpass jumps to the foreground at system start, is unfortunately back. I would open a case with Enpass Support, but unfortunately the cases I open, for example because of the Dropbox Sync. Problem, either not answered at all or they are simply closed unresolved. Therefore, here again the impressive request to the moderators to forward the problem to the development team. The problem was first reported in January 2020 in this thread. The problem was only fixed by Enpass in September 2021. However, as I pointed out in 2021, this was obviously just a dirty workaround rather than a real fix because you saw the Enpass window flash briefly at every start. I hereby ask Enpass to solve the problem with a real fix. I have a number of software in the autostart and all of them start without jumping to the foreground, e.g. Dropbox, HueSync, LuLu, AltTab, etc. For example, you can also configure apps like Safari in the login objects and even start them minimized in the background if you want. Please Enpass Team, it can't be that hard if other developers can do it too.

Unfortunately, the new Enpass updates (6.8.5 for iOS and 6.8.4 for macOS) do not fix the sync problem caused by 6.8.3. The Dropbox sync feature is still broken on my iPhone and Mac. And the worst thing about it is that I opened an official case with support more than 3 weeks ago and have not received an answer until today. That's pathetic for a software development company.

Unfortunately, the new Enpass updates (6.8.5 for iOS and 6.8.4 for macOS) do not fix the sync problem caused by 6.8.3. The Dropbox sync feature is still broken on my iPhone and Mac.

It's now 8 days since I reported the problem to Enpass Support and opened a ticket, unfortunately there hasn't been any response so far. Unfortunately, this coincides with my experiences in the past, when Enpass works everything is great, but if there is a new bug due to an update, it takes months to fix it. I hope that this problem will not become another 2.5 year story like the autostart problem of the desktop version under macOS.