1Password incorrectly reports Wavebox is out of date

This happens to me with some frequency on Windows and macOS. I think that technically there is a newer version of Chromium that Wavebox hasn't had a chance to incorporate and push out. The problem usually just lasts a day or so (on the beta channel), maybe a little longer if the Chromium release cycle and the Wavebox team had a schedule conflict (like during the weekend). 😜

I do the ULTRA secure of copying the password from 1P and pasting it into the Extension in Wavebox. It'll stay unlocked and functional for a good portion of the day, depending on the 1P settings and computer usage.

It hasn't bothered me enough to track down the version of Chromium used in the build of Wavebox I'm using and see what the latest Chromium build is. I'm assuming it isn't always the same as one of the Chrome builds, and even if it were the same, I have stable and Dev installed but not beta, so there are a bunch of variables (does the Wavebox team beta build pull from a specific Chromium release channel, is the version of any of the Chrome versions.

I do always check to see if there's an update to Wavebox, the 1P extension, and the 1P app, but that's the extent of my troubleshooting. Most of the time, there isn't an update.

I'm still happy that 1P "finally" works with other browses, like Wavebox, so I'm OK with this relatively minor inconvenience.