Thanks for your reply. I’ll try to to help narrow this down and make it reproducible.
you can break this cycle of notifications by accepting the changes and saving your database
Yes, separately for each entry, one by one. This is not an insignificant feat for a typical database of several hundreds of entries, and it’s a daunting task for a large one. I don’t think anyone would consider spending many months reorganizing their workflow and muscle memory until all entries have been touched on-the-fly, or potentially spending days going through each entry manually just to open+save them all.
I can’t reproduce this problem. I have tried again with different databases, including a brand new one that has no existing KPRPC data within it.
The issue with with:
a) old databases with existing entries that were added before KPRPC was upgraded to version 2 or installed in the first place. To reproduce, you could try disabling the plugin, adding a couple entries to the database, then enabling the plugin again. Those entries should now lack the new field (since the plugin wasn’t active) and KeePass will prompt to save upon closing an entry.
The issue isn’t with new databases, or with new entries that are added to a database while KPRPC is installed and activated.
b) any database that is used by other apps (e.g. KeyPassDroid) or plugins on devices that don’t have KPRPC installed. When you add an entry to the database on such a system, it won’t have the new field either.
This is a common usage pattern that I believe many people follow (with the mentioned app or another) to synchronize the database across devices, including devices that KPRPC doesn’t support.
I hope this information will help you reproduce the issue.
permissions requests
I understand the nature of KPRPC as an add-on. My comment was not about rewriting the application, but about responsibly making KPRPC get the user’s permission before it adds its own metadata to each entry in the first place. I’ll accept that that’s the topic of a different discussion though.