Closed Vstory closed 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?
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.
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
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.
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 addAndroidApp_1
To Reproduce
Expected behavior Merged with existing custom field values.
Such as URL: Original url:
A
, New url:B
After the merger:A,B
Such as AndroidApp: Original:
com.aaa
, New:com.bbb
After the merger:com.aaa,com.bbb
KeePass Database
KeePassDX (please complete the following information):
Android (please complete the following information):