keepasshttp attribute migration shows up every time I open db

[gabrielambuehl]

I am recently trying out latest stable release. I like what I see but it bothers me that keepassxc wants to migrate browser config everytime I open the DB. Even if I go to DB settings and tell it to forget all browser connections and remove site specific data, it still asks me to do the migration agqain next time I open the DB.

I could obviously set the checkbox to suppress the dialog but it is a bit worrying that the DB does not seem to be properly cleaned...

[droidmonkey]

Just do the migration, you can't use browser integration if you don't.

[gabrielambuehl]

I did the migration at least 5 times and the entries do show up in the DB settings. Unfortunately, the dialog still shows up every time I open the DB.

Browser integration itself works just fine.

[droidmonkey]

Ok well then that's a problem 😅

[varjolintu]

Check if your database have these:

• An entry named KeePassHttp Settings
• A group named KeePassHttp Passwords

[gabrielambuehl]

I had checked for that by searching even before opening the issue - did not find anything. Then it occurred to me to check the Recycle bin - bingo. Removed the entry and resolved.

So presumably the migration routine should also remove it from Recycle bin?

[varjolintu]

Or maybe it should not check the recycled stuff at all.

[gabrielambuehl]

Possibly cleaner still...

[droidmonkey]

Unintended bug for sure. We added move to recycle bin to prevent data loss on the operation!

[hackel]

I just got hit by this as well. I merged an old database from my phone that must have been from before I migrated the first time, and now every time it starts, it asks me to move browser settings into the database settings. Then when I hit yes, it says "The active database does not contain an entry with KeePassHTTP attributes." Indeed, I can find no KeePassHttp Settings / Passwords in my database, so I don't know what is triggering it.

[gabrielambuehl]

Did you check the Recycle bin (normal search does not so you have to go there manually!)? That's where they were hiding in my case. Occasionally I even got that error, too.