Hi

Enpass didn't work on the newest macOS Mojave Public Beta released yesterday (18E215a). I got only an empty window and if i try to start the browser extension I only get a non responding window (no possibility to enter something). I

Any solution/idea to fix it?

 

For all: Don't update to the newest public beta if you need Enpass.

regards

Lukas

 

same problem, please help us ;)
Im', stuked 

Same problem here. Hope there will be a fix/workaround. Found no other impactes apps on my Mac with this latest MacOS beta.

Hey guys,

Thanks for reporting this issue.

Our dev team is already looking into it. Meanwhile please run this command in the Terminal and then run Enpass.

• launchctl setenv QMLSCENE_DEVICE "softwarecontext"

Hope this helps!

Edited March 13, 20197 yr by Anshu kumar
Added a workaround

Same problem here....

21 hours ago, Anshu kumar said:

Hey guys,

Thanks for reporting this issue.

Our dev team is already looking into it. Meanwhile please run this command in the Terminal and then run Enpass.

• launchctl setenv QMLSCENE_DEVICE "softwarecontext"

Hope this helps!

Thank's. It's working. 

I'm really sorry but it doesn't work for me.
I have darkmode enabled, so I switched in lightmode (just to be sure), but it still not works...
I also launched the command with "sudo" before... but nothing..... 

I have this version of the app. 6.0.6 (361)

Edited March 13, 20197 yr by davide_s
add info

It works for me. 
I have a 2nd Mac at home, will try it later today I give a feedback if it's working there also.

 

 

Het werkt niet om met launchctl setenv QMLSCENE_DEVICE "softwarecontext" in terminal om de app opnieuw te laten werken.

 

It doesn't work with the workaround.

Edited March 13, 20197 yr by Berry

The workaround doesn't work for me either.

Same issue here. The workaround doesn't work either.

Enpass version 6.0.6

MacOS 10.14.4 Beta (18E215a)

The workaround does not work for me either.

2 hours ago, ZeusRico said:

The workaround does not work for me either.

It didn't work for me either, however launching it from the Terminal with the below command worked alright:

QMLSCENE_DEVICE=softwarecontext open /Applications/Enpass.app

 

Same issue here. Non of the suggestions is working. App remains white paged or locked down. Immediate spt requested.

4 hours ago, Zach said:

QMLSCENE_DEVICE=softwarecontext open /Applications/Enpass.app

 

That solution did work for me.  It's a temporary fix at least.

Quote

• launchctl setenv QMLSCENE_DEVICE "softwarecontext"

Worked for me. Many thanks!

7 hours ago, Zach said:

QMLSCENE_DEVICE=softwarecontext open /Applications/Enpass.app

This also worked for me.  If you are running the Enpass Beta, the path is

/Applications/Enpass.localized/Enpass.app

Out of curiosity, what does this do?

 

thanks RHPT, it works 

12 hours ago, Zach said:

QMLSCENE_DEVICE=softwarecontext open /Applications/Enpass.app

Sadly this new workaround also doesn't work for me....

Thanks. Works fine for me. Hope for a final solution in short terms.

8 hours ago, Mark923 said:

Sadly this new workaround also doesn't work for me....

I had also tried the other option with the launchctl setenv QMLSCENE_DEVICE  "softwarecontext" command and restarted my Mac before I tried that, might want to try that if you haven't already

My workaround: uninstall the app entirely, reboot the system and download from store again. Run

QMLSCENE_DEVICE=softwarecontext open /Applications/Enpass.app

in the terminal and open Enpass. Reconfigure cloud-access and apply known master-password. Soon the cloud stored date will be loaded. 

It starts but that's all 

The workaround by Anshu did not, but the one by Zach did on both of my Macbook Pro

Edited March 15, 20197 yr by European

22 hours ago, TechMac said:

My workaround: uninstall the app entirely, reboot the system and download from store again. Run

QMLSCENE_DEVICE=softwarecontext open /Applications/Enpass.app

in the terminal and open Enpass. Reconfigure cloud-access and apply known master-password. Soon the cloud stored date will be loaded. 

I tried this approach (uninstall/reboot/install and then run the command from the terminal) and I have found that the workaround works. In my case the reboot was the key additional step to get it working.