Search the Community

Hi there, recently (few months ago) I noticed that navigating on web pages with TAB (which should normaly "jump" over active elements like links, buttons and form inputs) is not working properly. It works normally until it jumps on a form elements (e.g. search, which has many sites), then it cycles up on them. Even this page (Create new topic) is suffering with this issue. I found out that if I turn off the Enpass extension its started to behave as expected. My setup: Enpass 6.8.5 (1256) (Mac App Store) macOS Ventura 13.3 (22E252) primary browser Firefox 112.0 (but behaves the same in Safari and Chrome) Thanks for looking into it.

I'm a new user, and since installing recently, I've been very happy with the Enpass feature set and value offering. One major gripe, however, is its CPU use on Android. I'm on a Samsung Galaxy S9 running Pie (April security patch level, recent kernel), with what I believe are quite common Enpass settings. As long as Enpass is running (which I prefer it to be so I can enter my PIN, not always my rather long master code), it will continually gobble up more or less all available CPU (at least >1 full core), to the point that my phone gets hot, and maintenance tools find it necessary to warn me about the anomaly taking place in my system. Needless to say, this also has a very adverse effect on battery life, which has dropped drastically since I set up Enpass. Clearly there's a bug here. Is it known? What help can I offer to isolate and pin it down? And until such time, what workarounds should I be looking at, apart from stopping Enpass from running in the background? I've seen scattered posts alluding to the accessibility service, so that's where I'll start experimenting first. Any help would be greatly appreciated, be it from staff, subject matter experts, or even just a "me too" from anyone who's seen anything similar to this. Thanks.

After upgrading my One Plus 5 to the latest Android Pie build, I've encountered an issue when enabling the accessibility option for enpass. When enabled, the multi tasking windows gets extremely laggy and slow. As soon as I disabled the accessibility option, it works normal. Is this some kind of unintended bug?

Android 9 on Pixel. Two major issues made me regret purchasing Enpass since the issues are not new yet are not being resolved: 1. 9 out of 10 times in browsers, Enpass does not appear when I need to login on a website. When I test the same site with Lastpass, also using the Accessibility Service, it works. 2. When Enpass appears below a login field, it covers my keyboard and also the next field (password) making it impossible for me to logon. If Enpass does not have the credentials this means in such cases I am blocked from logging it completely and have to disable Enpass to continue. Fix: the notification should always appear above such fields (1 out of 2 times it does). Development team of Enpass, please confirm you are aware of these issues. When can we expect this to be solved?

Hi, Firstly, thank you for the great apps (I use it on various devices). Now on to my problem, I am an android developer and I am using the Enpass android app on my main phone, because that is where one would need a password manager. I happened to install an app that I am developing on my main phone to test while I was away from my desk and I got a crash in said app. I have tracked down the cause of the crash to the Enpass autofill accessibility setting. If I disable Enpass in the accessibility settings then the crash no longer occurs. Essentially, in order to cause the crash I tap on an item in a recycler view list to switch to another activity (a detail view of the tapped item) and then push the device's back button to return to the recycler view list. In order for the crash to occur this needs to happen at least twice and in quick succession. So, tap item, tap back, tap item, tap back (not allowing the loading on each activity to finish). Device: LG G5 (H850) Android 7.0 Enpass 5.4.8 Enpass Autofill Service and Notification are enabled. Enpass Keyboard is not enabled. The Enpass notification does not show while I am switching between the views mentioned above. It does show when I am on the app's login screen though. Below is the stack trace of the crash in my app: E/AndroidRuntime: FATAL EXCEPTION: main Process: [My App's Package Name], PID: 1318 java.lang.NullPointerException: Attempt to invoke interface method 'boolean android.view.ViewParent.requestSendAccessibilityEvent(android.view.View, android.view.accessibility.AccessibilityEvent)' on a null object reference at android.view.View.sendAccessibilityEventUncheckedInternal(View.java:6309) at android.view.View.sendAccessibilityEventUnchecked(View.java:6288) at android.view.View$SendViewStateChangedAccessibilityEvent.run(View.java:23713) at android.os.Handler.handleCallback(Handler.java:751) at android.os.Handler.dispatchMessage(Handler.java:95) at android.os.Looper.loop(Looper.java:154) at android.app.ActivityThread.main(ActivityThread.java:6247) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:872) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:762) I had a look at the source code for the View class and the method that is throwing the exception is requestSendAccessibilityEvent() The below code is from the API 25 source code, View.java: public void announceForAccessibility(CharSequence text) { if (AccessibilityManager.getInstance(mContext).isEnabled() && mParent != null) { AccessibilityEvent event = AccessibilityEvent.obtain( AccessibilityEvent.TYPE_ANNOUNCEMENT); onInitializeAccessibilityEvent(event); event.getText().add(text); event.setContentDescription(null); mParent.requestSendAccessibilityEvent(this, event); } } The exception happens because mParent is null, and that code should not run/execute if the mParent object is null. So something is changing the mParent object to null after the if statement has done the check. Now because the exception occurs in the android system code, there is not much I can do to catch the error. Perhaps there is an update you guys can make to your app? Are you guys calling the announceForAccessibility() method in the Enpass android app anywhere?