Chromium 110.0.5481.177.1: Possible Code-signing Mismatch

[scrutinizer11]

After installing 110.0.5481.177.1 on Mavericks, Chromium went into a log-out frenzy forcing me to sign into my Google Account over and over again. Resetting it to smouldering bones by trashing its support folder didn't rectify the problem bringing me to square 1 with every launch.

The cue that showed me the way was the Chrome Safe Storage keychain. Upon glancing through it in Keychain Access, I saw many duplicates, each referencing the _Chromium binary. This suggested that each session prompted the app to treat every start as a new instance. I deleted the Chromium Safe Storage and re-signed the Chromium bundle with a third-party tool adding an ad hoc signature. After that, the issue was gone, and it finally stopped causing me a headache.

In Lion, the story repeated, however this time the outcome was quite different. Deleting its support folder, Chrome Safe Storage (containing a heap of duplicate references), and code-signing it via codesign --sign - --force --deep made no difference. I ended up with the previous version (110.0.5481.100.1), and voila - the problem disappeared there too.

I don't know what you'll make of it. It could, probably, be related to the discussion about Chromium showing repeated prompts to accept the location reading, particularly the linked reply below. The actions mentioned there may have spurred the snowball rolling until it developed into this defect, but that's just my theory. The impression is that 110.0.5481.177.1 broke something.
#93 (comment)