Anthony

Interestingly, it seems that Enpass is treating Edge Beta as an app, rather than a browser. Every time I go to login to a site, Enpass isn't seeing a website domain in a browser. When I search for a card to use for username and password,, it always asks if I want to associate that card with "Edge Beta". I.e. it is treating it as an app.

Thanks @Abhishek Dewan I'm finding that using accessibility services autofill is working on my Samsung S5e tablet (Android 11) but not on my Samsung S22 phone (Android 13). On my tablet I get the Enpass popup when I give focus to a username or password field, but nothing on my S22 phone.

Oh, when it does work, its never able to match the website domain. I always have to search for the card in Enpass and confirm the match.

I was just wondering if Enpass on Android is expected to work with Microsoft Edge beta browser? I've just been using it for a few things and I've noticed that Enpass is almost never appearing an an option on the keyboard when I'm clicking in username and password fields on websites. This obviously all works fine with the 'release' version of Edge on Android. I'm seeing this same behaviour on multiple devices: Samsung Galaxy S22 phone (Android 13) and Samsung Galaxy Tab S5e (Android 11), with Enpass 6.9.1.844 I am specifically referring to the beta version of Edge which is available here - https://play.google.com/store/apps/details?id=com.microsoft.emmx.beta - as opposed to Dev or Canary versions. I completely understand if the position is that Enpass isn't tested with beta versions of browsers. Still, I wanted to ask the question and raise the point in case you wanted to investigate why it isn't working in case you need to prepare for a future release.

I'm seeing more and more websites implementing a "phased logjn" type approach where you are initially only presented with a username field. When you enter this, some even go for a firm of 2FA (usually SMS or email) that needs to be successful before you are presented with a password field. Other sites might reverse this 2 last steps. Sites I'm seeing this include Adobe (sites and apps using Adobe ID login), Apple, PayPal. Enpass does not currently work seamlessly with these types of authentication workflows, occurrence requiring me to go back into Enpass multiple times to login. I hope Enpass can be improved to handle these variations to more classic single form username/password followed by 2FA type logins.

One piece of feedback for the coin wallet template is that in addition to a recovery key or phrase, you pictured need to store a seed phrase, usually 12 words where you need to store them in the exact same order so that you can identify word 5 or word 8. I've generally favoured a multiline field to store this in Enpass currently, but you might have better ideas.

Well, at least it's nice to see that it's not just me getting this error... sigh. Enpass really should gift us some additional free lifetime licenses (or similar) for this debacle.

6.8.0.648 on both phone (Android 12) and tablet (Android 11) will autofill username just fine, but not password. App - https://play.google.com/store/apps/details?id=de.heinemann

This seems to be an old problem: ..but as I've just started using Home Assistant, I'm re-reporting it. I'm finding that Enpass won't autofill the username or password on either the webpage (using Edge on Windows 10 with Enpass 6.8.0 (1002)) or on my multiple Android devices using the Home Assistant app and Enpass 6.7.1.572. Login also includes TOTP so having Enpass not working is quite cumbersome. Home Assistant is a home automation system (https://www.home-assistant.io/) that you install and run. They do have a demo environment here (https://demo.home-assistant.io/) but you can't access the login page. If required, I could setup a port forward on my router and PM a link to my environment to help troubleshoot.

Thanks @Manish Chokwal I tried setting up onedrive sync with Firefox (98.1.1) and got same result as before. I checked the linked article about disable tab queue in Firefox but I did not find any such setting. I also tried setting up sync using Google drive and this worked fine.

I am setting up Enpass on a new Microsoft Surface Duo 2 (Android 11, Enpass 6.7.1.572) and running into problems enabling OneDrive sync. When I select OneDrive from the Sync with list Enpass immediately produces a dialog with "The sync with OneDrive was canceled by the user". It does also launch the default browser and go through the Microsoft Account login authorization on the other screen, but even when I get to the Enpass page (auth.enpass.io/onedrive/?code=<long string>) with Authorization Finished! and the Redirect button, Enpass doesn't respond and so I'm left with no OneDrive sync. I've tried this process with both Edge and Chrome as the default browser, but I get the same result. Any ideas on how I can proceed here?

ShareX - https://www.microsoft.com/store/productId/9NBLGGH4Z1SP

I have never seen that behaviour. I'm not sure you understand the problem I've outlined. The problem is that after every update of Enpass, it always reverts to a hidden icon in the system tray. I then have to: Go to system tray Click 'show hidden icons' Drag Enpass icon out onto the taskbar It will then persist as a visible icon whenever launched, until the next time there is an app update when it reverts again. I have other applications that do not display this behaviour. If I choose to make icon visible in system tray, they persist forever. Across updates, reboots, etc. This is why I have raised this issue as I believe it is possible for Enpass to behave 'correctly' and respect the setting across updates.

After receiving the option below, I decided to try letting Enpass be the default autofill password manager in Edge. However, I don't like the experience. How do I revert this to go back to Edge being the default autofill password manager as I'm not able to find the option in Enpass or Edge?

I've managed to "fix" the issue, but I'm not convinced that what I did really fixed the problem. However, worth sharing in case it helps someone else. I found this thread ( ) ..and one of the instructions was "Log in to the site https://account.live.com/consent/Manage with the same Microsoft account and delete all the permissions for Enpass." I went and took a look and found multiple sets of Enpass apps with associated permissions so I revoked/removed all the 'old' ones. I worked on the theory that the one with the matching icon and a 'most recently used' date in the previous 24 hours was the one to retain. After doing that, I disconnected sync on my phone and was able to successfully re-establish sync without any error.