Authentication failures and Allow access notifications despite the plugin working

[Whitechapel-1888]

I set up keepassxc-mail and KeePassXC on Windows following the guide outlined in the readme (I should add that initially, I failed to enable the Firefox browser extension until I was kindly notified by one of the devs). I am using Thunderbird 145.0 and have multiple gmail accounts connected. peepass-mail uses default options.
After booting my computer, I always open KeePassXC first, then start Thunderbird. Both are configured to remain open/run minimized in the background.

As soon as I open Thunderbird, I get these "Allow access" confirmation windows. I get multiple of these, in total 4 each time I open Thunderbird in a new session:

The other type of "Allow access" dialogue:

Usually a few seconds after allowing the first (few) access requests, I get Authentication failure notifications:

Nothing happens when clicking on these. However, despite all of these messages, Thunderbird succeeds in accessing my KeePassXC storage and proceeds to download messages. I assume there're two issues, the "Allow access" problem seems to be cookie related, and the authentication failures seem to be due to some sort of timeout. Can somebody help me fix these problems, please?

[ecoutinho]

This works for me on version 1.12. On Settings > Config Editor, create a boolean:

keepassxc-mail.offline_control=true

The next time, Thunderbird will start in offline mode, which will allow it to load the keepassxc-mail extension, before it tries to connect to Gmail. I still have to close an offline connection warning window, though.

[Whitechapel-1888]

I didn't try that, yet. But to me it seems enabling this option trades the Authentication failure for a offline connection window that I have to interact with.

For the time being, I must stop using this plugin. Each time the Allow Access windows pop up, I get multiple security alert mails on my gmail accounts. The overall experience is not good.

[kkapsner]

This is a timing issue that KPM is not able to solve entirely. The solution @ecoutinho pointed out is the only way to get rid of the security alert mails. They will not be present if you "deal" with the offline window. And the interaction is quite minimal as you simply have to close the window.

For this offline message it could be feasible to open a bug request at Mozilla. I consider this to be a bug that the oauth token is even checked when being offline.