Search the Community

Hi, Samsung released an update to their android browser which states they have improved 3rd party autofillers. It seems bitwarden got it to work. Will Enpass further improve on autofill and Samsung internet as well?

Enpass on Android supports autofill through the following three methods. For the best experience, please ensure all of them are enabled. If they’re already active, try toggling them off and back on: Using Autofill on Android Android Autofill Framework Android Accessibility Enpass Keyboard Enpass works seamlessly with most major browsers that support Android’s Autofill Framework, including: Google Chrome Mozilla Firefox (Android version) Microsoft Edge Other mainstream Android browsers that support the standard autofill service

I've been using Kiwi browser for a long time, but it isn't being updated anymore. Now I'm looking for a new browser on my android phone. Quite some browsers I've tested so far (smaller, more obscure ones) don't work with autofill. Therefor I thought to turn the search around and look at android browsers that do work with autofill. I've now spend quite some time searching for a list of compatible browsers, but I can't seem to find one. Which android browsers work with Enpass autofill?

Is it possible to show the usernames of the accounts that can be autofilled to this website before needing to do a biometric verification? I found it much more straightforward when it's possible, like how Apple is offering with KeyChain, and Microsoft Authenticator on Android. Here's what I'm expecting (like Microsoft Authenticator): If this account is what we are looking for, we can select it, do a verification and it's auto filled. If it is not, press the button on the top right corner to open the app itself to choose another one. Here's what we have right now As you can see, it is not very "inline" as it still requires the pop up to be opened every single time, then we can choose an entry.

Enpass iOS seems to default to the Primary vault for the autofill widget in Safari. I have four vaults and want to default to 'All vaults'. I have to manually select all vaults every time the autofill opens. If I open Enpass app then all vaults is the default. Enpass iOS 6.11.12 (1002) iOS 18.5

Hi! Enpass was always working on my Galaxy S8 with Android 9. Yesterday, I installed enpass on my new S21 with Android 11, and suddenly the accessibility autofill service is no longer working. This happens with any site, for instance whe logging in to amazon.com in Chrome. I see the the Touch to Autofill notification in the adressbar, I can click it, and select Amazon, but it doesn't autofill. This happens on any site, and any app. I can see the notification, but the credentials are never filled. It only applies to the accessibility service, the regular autofill for apps that support it works. But for those that don't have this api, such as spotify, it doesn't work. I tried disabling enabling it tens of times. I reinstalled the app a few times. Also, I ensured that enpass was not part of any battery saving measures on the device. Tdlr; autofill by accessibility is working on older Android versions, but for the same sites and apps, doesn't work on Android 11 (OneUi 3.1)

I have installed Enpass on a new Macbook Air with MacOS 15.4. I also have installed the Safari extension. Everything seems to be OK. I also synced all my passwords. However, the autofill popup menu won't appear when I want to enter username/password on a website. I looked in the support files (https://support.enpass.io/app/extension/take_a_look_at_browser_extension_settings.htm#autofill-popup-menu) but I can't find the settings screen which is described there. Am I overlooking something? Note: I have Enpass running on my Mac Mini (with MacOS 15.4) and before that on my iMac without problems. On these machines the autofill popup menu appears always.

When I performed the autofill in Android Devices is not working, Enpass put the password on every single field. The username is fill with password, email is fill with password, everyting is filled with password. Any way to solved this? I already tried to unistall, erase data and nothig works.

Hi, with enabled autofill (enpass 6.11.5.2 in firefox 140.0) some websites are broken. https://kundenportal.ewe-netz.de/ reports this error in console: with disabled enpass extension, the page load without errors.

Hi! Recently chrome started overlayering the enpass autofill popup, Enpass is setup to be default pwd manager in Chrome settings and I've tried reinstalling the extension, so far no go. Anyone else with this issue?

I often use Duplicate to create new similar cards for other services, but now see that they ALL have carried across the application autofill settings from the Android app. There really needs to be a simple way to clear "app autofill" information from existing cards... and duplicate card should probably "throw away" any autofill mapping information. Is there something I am missing in the app, or is this a (pretty significant) limitation that really needs to be addressed in an update.

Recently, whenever I click on the autofill icon, the android app immediately crashes the android app.. This happens 100% of the time. The following are the info. Machine: Lenovo IP Flex 5 Chrome 13ITL6 (intel i3) ChromeOS version 1140.0.7339.229 Chrome Enpass extension 6.11.8 Android Enpass 6.11.15.1190

I use a chromebook. I cannot get the app to work in a reasonable way. The chrome extension shows ENABLE AUTOFILL SERVICE! and it is asking me for ip address and port. What on earth does that mean? I have installed the app for Chromebook, but I guess the extension and the app are not talking to each other? This is really a horrible first start. Help?

Just a curiosity: I have several logins for the same site and I have named them 1, 2, 3, etc. When Enpass suggests me the logins, it orders them in another way... look at the attached image. Is there any way to get them in the correct order? Thank you

Saving the login data to Enpass and autofill does not work on https://meine.norisbank.de/#/login. Webform does not work here either.

Please fix this: https://banking.dkb.de/login MacOS: 13.5.2 Firefox: 130 Enpass Extension: 6.9.4.2

In my phone I have accessibilty for enpass set to "ON" but in the enpass settings it's disabled. When I enable it, i get sent to the accessibility settings to turn it on but it's already on. If I turn it of, it switches right back on again and when I go back to settings, it's still disabled in enpass settings. So no matter what I try I can not get enpass to autofill on android. This happened after I updated my pixel to android 14. It worked fine before this. I have uninstalled and reinstalled enpass to set it up from scratch but the issue remains after every reinstall. This means autofill does not work ever on my android device.

I am using a Google Pixel 8 with Android 15 and noticed on multiple websites that Autofill Using Accessibility stopped working. I tried the usual steps disabling/re-enabling mentioned here https://discussion.enpass.io/index.php?/topic/31539-autofill-using-accessibility-is-broken-in-android-14/#findComment-91299 It was working before, but stopped working recently. Any ideas?

Came across the following article from another tech news reader: DOM-based Extension Clickjacking: Your Password Manager Data at Risk | Marek Tóth Looks like Enpass is one of the many password manager extensions affected: Mitigation Browser extension developers should focus on the following parts. The missing fix of one method leads to the extension remaining vulnerable. Extension Element • styles cannot be changed (MutationObserver) • using "Closed Shadow-Root" Parent Element • BODY/HTML opacity detection • using Popover API for extension should protect this method Extension Overlay • last DOM element detection (z-index conflict) • popover elements listing - when the autofill menu is opened, check if any other "top layer" elements exist → if another element exists the autofill menu should close → or just don't show extension UI if exist "popover" element • elementsFromPoint() can be used for partial overlay but cannot be used for popover elements (pointer-events:none are ignored) → The content script can temporarily remove pointer-events:none from all popover elements before filling in data, then check the "top layer" state using elementsFromPoint() and fill the data accordingly. Doesn't exist simple protection.⚠️ Some platform-level support should be created - new browser API protection for this clickjacking technique.⚠️ The proposed solutions are still handled through javascript and conflicts may occur between exploit code and extension content script (extension white-box analysis can be made). The safest solution is to display a new popup window - but that will be very inconvenient for users. Alternatively, a context menu or a system dialog for autofill may then be displayed. Consider addressing this issue ASAP Enpass team.

We understand the inconvenience and want to assure you that our team is aware of the Safari issue and working on a fix. Your data remains fully encrypted and secure, only certain Safari functionality is affected. The Safari autofill extension is part of the macOS app bundle and will be released by the end of the month. Until then, you can disable the inline autofill popup in Safari Extension Settings ▶︎ “Show Inline Autofill Popup Menu” ▶︎ Off. Thanks for your patience, we’ll update this thread once the fix is out.

I am having some difficulty with using Enpass with ChromeOS. I have the android app Enpass install and the Enpass extension installed in Chrome. In the android app, I attempted to do the following: 1. In the android app's settings -> Autofill -> Android Autofill Service. I toggle it and it and tries to set enpass as the android app. When I tried this, it display a dialogbox saying "Make sure you trust this app". When I press OK, the checkbox is not checked. It only gets check if I set the autofill service to none. 2. Toggle "autofill in chrome browser". This connects to the chrome extension. The problem is that connection keeps being loss. what am I doing wrong and why doesn't step #1 work?

Please ensure Android Autofill Service and Autofill using Accessibility are enabled. You can also check the Enpass support page for details on using Autofill on Android: https://support.enpass.io/app/autofill/using_autofill_on_android.htm?rhhlterm=autofill&rhsearch=autofill If the issue persists, share your device's OS and Enpass app version.

Suggestion Idea: The inline autofill integration is amazing. The one way it will be more convenient is to have a setting which lets us keep the inline icon enabled, but the inline popup only starts when the icon is clicked within the field, instead of it showing up when the field is focused. This would allow the user to easily decide if they want to use the autofill menu or just type within the field manually.

Thanks for reporting this issue. As we investigate further and seek assistance from our Technical team, could you please share the following details to help us troubleshoot more effectively: Enpass version and Device OS version When exactly does the app crash? (e.g., during installation, while unlocking, while using the app, when editing/adding an item, during sync, or during browser autofill) Do you receive the Enpass Crash Reporter notification when it crashes? Also, please mention this topic link when you send the report to us so we can easily identify your case. Looking forward to your reply so we can assist you better.

Earlier this year, we learned about a browser extension vulnerability that could have exposed users to clickjacking. We acted promptly to investigate, patch, and ultimately release a complete fix. Here's what happened On April 7, 2025, security researcher Marek Tóth contacted Enpass to responsibly disclose a clickjacking vulnerability in the Enpass browser extension. Clickjacking is a web-based attack where a malicious site tricks users into clicking something unintended. In this case, a malicious webpage could exploit the vulnerability to trick a user into stealing a credential stored in Enpass by altering the attributes such as transparency of the inline autofill menu. How We Responded Promptly As soon as we were notified, the Enpass team immediately acknowledged and began working on a fix. May 12, 2025 - We issued a partial fix in Enpass Browser Extension v6.11.4, which addressed cases where a malicious page or script could manipulate the transparency of input fields and the inline autofill menu. Thorough mitigation required additional efforts and hence, our engineers continued to work on a permanent fix. August 13, 2025 - We rolled out the releases for all supported browsers via extension version 6.11.6 and later. The reporter has acknowledged that the fix works (check the related blog post). What You Should Do To stay protected, make sure you’ve updated to the latest version (6.11.6) of the Enpass browser extension. We extend our sincere appreciation to Marek Tóth who reported this issue responsibly.