Open jficz opened 6 years ago
I had some very similar issue, which I reported here: Issue #264
While I used some iOS client to get access to my vault on iOS, I was alerted that there were issues with duplicate names for some credentials in my vault. At first, I blamed the iOS client for using the credentials names for unique keys and since I knew, I had some and the password collector itself doesn't seem to care about that, I thought that these names needn't to be unique, but for the sake of the iOS client, I edited the duplicate credentials to satisfy the iOS client.
Then I checked in on my passman web-extension and suddenly two things changed:
So, maybe not only duplicate credential names cause these issue, if you are sure, that your creds are all named uniquely.
Not sure I understand. In my case, I have two separate and independent entries (accounts) set up in Passman, where only the URL field has the same value in both.
They both have a custom field named #account, which corresponds to a login form input with id "account". This login form has three fields - account, username and password. Both username and password are filled correctly when the desired entry is clicked on while the account field is not filled at all.
I'm not sure I see any relation to #264 here.
I see what you mean. When I encountered my issue, I only reported a very basic issue, since I didn't relate the issue to the duplicate names in my vault. It was only when I fired up the iOS simulator to check the iOS client, that the client complained about duplicate names.
In your case it's a duplicate custom field, but my assumption is, that the webextension has a general diasbility to deal with those in general.