Kunzisoft / KeePassDX

Lightweight vault and password manager for Android, KeePassDX allows editing encrypted data in a single file in KeePass format and fill in the forms in a secure way.
https://www.keepassdx.com/
GNU General Public License v3.0
4.57k stars 269 forks source link

Auto-save information problem in auto-fill #1001

Closed Vstory closed 3 years ago

Vstory commented 3 years ago

Describe the bug After using auto-fill, searching for items and selecting them, if saving information is enabled, there are some problems when writing data. It will not merge with the existing field values, but instead add a new custom field. For example, the original field is: AndroidApp, then add AndroidApp_1

To Reproduce

  1. Prepare an entry, and create a field AndroidApp, and write the value.
  2. Turn on the data saving options of auto-fill and magic keyboard.
  3. Try to autofill, trigger the selection of entries, and then try to reproduce the problem.

Expected behavior Merged with existing custom field values.

KeePass Database

KeePassDX (please complete the following information):

Android (please complete the following information):

J-Jamet commented 3 years ago

This is not a bug, it's the behavior we defined to register several applicationId to be consistent with other KeePass applications. Why do you want it to be in the same field?

Vstory commented 3 years ago

Why do you want it to be in the same field?

For some applications (A, B, C), they use the same account. And I don't like to append "_1", "_2" after the field. Like AndroidApp, AndroidApp_1, AndroidApp_2.

J-Jamet commented 3 years ago

What are the other applications? This was decided in the KeePassXC thread with other KeePass creators. https://github.com/keepassxreboot/keepassxc/discussions/6229#discussioncomment-432102

Vstory commented 3 years ago

This was decided in the KeePassXC thread with other KeePass creators. keepassxreboot/keepassxc#6229 (comment)

Thank you. I have read and understood. But I will not use this method, I prefer my current usage. ApplicationId [n], when there are too many custom fields, it will not be "concise" enough.

What are the other applications?

I have quite a few applications that require the same account.