Jump to content

en4789234809384user

Members
  • Content Count

    3
  • Joined

  • Last visited

Community Reputation

0 Neutral

About en4789234809384user

  • Rank
    Newbie
  1. Thanks for the workaround Vinod. I applied it successfully and could use the program again. Meanwhile the .240 update is installed as well and the environment variables could be removed. It still works fine. One thing however about the .240 update. When it was installed the program asked me to setup a new vault or something. I was shown the option to choose a sync service. I quickly backed out of the program by pressing Ctrl+Q and started it again. Then the expected Master Password entry page was shown. Now I'm all good again. Have a nice weekend!
  2. Same here. Version 6 was usable and looked fine until the update I received today. I run Windows 10 Version 1803 on a laptop with Full HD resolution (1920*1080). I never changed the default scaling and will not mess with it now. Enpass, please release a quick bug fix update! And while you're at it, please give us an option to use the program in English language. Since some UI elements don't have labels I suspect the German localization is at least partially broken too. Really, I don't need loc and would love to be able to use English without switching the whole computer to English. Which is something that Microsoft makes deliberately harder from release to release so I won't even bother with it. This is also true for the mobile client. Forcing the user to use a language version that was guessed to be the desired one just because the OS is using it is bad form. In Android for example you really can't switch the language if you care for app reviews from people of your country because as soon as you switch the phone to English USA as an example, all reviews are shown from Americans and are posted to the American review database. And I really don't want American app reviews on my Android phone. (Cultural issue; Americans are usually very shy to call out problems and rather prefer to sugar coat everything. Whereas my fellow Germans are brutally honest in their reviews and this is what I need, what helps me make decisions on what apps to use.)
  3. Hello I used to be a happy Enpass user with a Samsung A5 2017. I configured Autofill on it and used it quite a few times to create Autofill log ins in the app for logging into apps. Those can be identified by a "Autofill Info" field in Enpass desktop software. Now that I changed the phone to a Moto X4 (also running Android 8.0 but with almost no OEM customization) I can't get Autofill to work. The app is installed and accessibility services are enabled for Enpass. Also I put Enpass into the "not optimized" group within battery settings of the phone. Basically everything that I did on the Samsung as well. But the Moto never shows the Enpass touch target when I tap a password field in an app for which it should display this. It's as if the accessibility service either doesn't work although it's enabled (toggling doesn't help), or that Enpass can't identify that I'm running apps for which it has stored logins. What can you suggest I do to fix this? Thanks!
×
×
  • Create New...