Anthony

I was surprised to see that I could not drag and drop a file that I wanted to attach to a card while in Edit mode. Add File -> Browse should not be the only way to add an attachment. Make the Attachments area a target area for drag and drop of files. Or even the entire card.

Given it has been 4 years since my original request, this is clearly not a priority (especially as they focus all efforts on their Business version product, which this would also benefit mind you) or simply beyond their dev person (I'm reluctant to say 'team' given the slow rate of updates and fixes) capabilities.

Agreed. I have over 1,100 entries and even after using Search to reduce the list, the extra spacing is just wasteful and adds time to find the card you want

Wow. Enpass has really turned to the 'bait and switch' model and screwing over loyal long-time customers. Nags in the Windows app but no pricing and no links to where to upgrade. Just a small note saying "Purchasing Premium plans within the app is not supported. We understand this isn't ideal". OK, but you've given me to links to WHERE to actually find out where, how, how much??? In the Android app I finally got a nag popup ad and then nearly choked when I saw the 40% discounted price of $104.99! Are you f'ing kidding?????? LOL. First you pivot to trying to become a business/enterprise solution, which I'm guessing didn't drive the revenue you were hoping for. Now you create a new subscription tier and charge an exorbitant upgrade cost to your existing customers? What a shake down. I will definitely NOT be upgrading at that price and you've provided yet another reason to trust/like/respect Enpass even less, so that when a new password management solution comes along, I will have less concerns about abandoning Enpass. Yes, I get it, if we don't need those features in Premium we can choose not to pay the price. That is entirely our choice. But from what I can see, a feature that I used to have (2FA supported), has now been taken and put into another tier. So, something I did have, has now been taken away. You really should respect your customers more. If you want to rectify this, you need to be offering a 90%+ discount on upgrade to existing customers given the insane price.

Almost 9 months on, this is still broken!! Also not working for me on Windows 11 with Edge browser and Enpass 6.11.6 (1828)

Thanks @Amandeep Kumar, will check those settings and browser flags and re-check.

In the same way the desktop browser extension can prompt to save new logins, I really miss not having this same feature on Android. I would love to see this functionality added.

Seeing same issue was other people here. Can get passkeys to work on Windows, like others, on my Android devices it only asked them to be loaded from Google password manager. It would be advisable for Enpass to clarify whether these feature doors actually work on Android or not.

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.