The new codes do not get saved to KeePass2Android

[alensiljak]

Hi!

• I click + to create a new entry,
• take a photo of the QR code from the app,
• enter the name and click the Save icon
• unlock the database with KeePass2Android
• perform a search, and
• select an entry

at which point nothing really happens. I go back to the Fidelity app and the entry is there and the list is on the same screen (looks like a bug).
If I exit and reopen the app, the new entry is there.
But, if I look into the KeePass database, there is no additional record in the previously selected entry, where the code is stored.
I already have several such records and would really like to make sure that the codes are kept in my KeePass database. I don't always carry the original card or paper and, besides, I would want to know that I have a safe copy.

Is there a way to confirm this?
If the records are not linked, would it be possible to have an option to link a code to an existing entry in KeePass?

Thanks again, I find this an indispensable app. It is already replacing 7-8 cards and printouts of different sizes and significantly reduces time and stress levels before and at the scanners.

[choelzl]

I fixed the issue where you saw old screens under new ones.

In relation to the issue concerning "search and edit", unfortunately you need to create a new entry and merge it with an existing one. The keepass2android plugin interface does not seem to support "adding fields to existing entries" only "create new entries".

[alensiljak]

Thank you for the work that you're doing and the clarifications here.
It seems, however, that some entries were not created in KeePass but are shown in the app. I thought only the entries found in a KeePass database would be displayed.

If I search for "fidelity", I only find two entries in KeePass. But the Fidelity app shows five. Is there any way to re-sync?
Cheers

[choelzl]

Since I don't get any information back when the "create task completes" (user left without doing anything , user added entry,...) I by default store them in the app.
The alternative would be that it only stores them when searching/querying so that after adding you would need to search it to be added to the list.
The best approach would be to request on the keepass2android git a way for plugins to edit entries and to return success/failure information