1Password incorrectly reports Wavebox is out of date

Thanks @Thomas8520 . I'll try out the new Windows beta. I thought I had the latest but didn't apparently. If the problem continues to reoccur, I'll update here. I do wonder, however, why this can't be fixed permanently in production since Wavebox supports Chrome extensions.

I had the same problem with version 8.9.12. The update channel is still set to beta, but it downloaded the production build again. I checked for updates, it updated to version 8.10.0 beta and it works again.

mbdiener this might work for you on Windows too.

What do you need from the Wavebox team to avoid this recurring issue? We already have URLs that we publish with the latest Wavebox versions for each platform...

https://download.wavebox.app/stable/win/latest.json
https://download.wavebox.app/stable/linux/latest.json
https://download.wavebox.app/stable/mac/latest.json

Do you need the corresponding Chromium version to go along with these? We keep pretty up-to-date with the Google Chrome release cycle so this shouldn't be an issue. We track it really closely... i.e. our beta channel went to M109 on 20/12/22 and stable went to 109.0.5414.87 on 11/01/23 the day after Chrome.

I know some smaller browsers just bump and spoof the version number, but this isn't the case for us, we work really hard to make sure we're up to date with Chromium and secure. We keep the open source https://chromiumchecker.com/ up to date, which uses feature detection to check which milestone the visiting Chromium browser is using. It can't detect the minor version but gives great confidence on which milestone the browser is using.

Let me know what you need from our end because we're more than happy to help. This isn't just joint Wavebox & 1Password users that are affected, I'm an avid 1Password user myself, so seeing these recurring bugs is disheartening.

Related to the thread, since a recent update, the 1Password Chrome extension running in Wavebox and the Windows desktop version do not synch their sign-in states or, in other words, if I'm signed in on the desktop, the extension no longer will be signed in. I am using the beta version in both the extension and desktop. The extension is v. 2.6.1 and Windows v. 8.9.12 (80912004). Is there a fix for this situation? Note that the synch was working until recently.

Hi @Thomas8520,

Thanks for your message. I appreciate you reporting that the release channel is set to Beta but no updates were available.

With regard to Mac alone, there was a small update that took place on December 15, 2022. This version you mentioned (80911019), is a Production release that has surpassed the latest Beta version number 80911014 causing this issue.

I have no news to share on a date, but once a Beta with a version number that is newer than 80911019, releases everything should be back on track with updates as long as the Release Channel remains on Beta.

I'm sorry for any inconvenience this has caused.

This has happened once again with version 1Password for Mac 8.9.11 (80911019).

The release channel under advanced is set to beta and hitting check for updates reports no new updates are available.

It's really grating having to manually re-download the latest beta and re-install every time this happens...

Hello @Thomas8520,

I'm sorry to hear that you are getting reports of this again.

1Password 8.9.8 (80908009) is the latest production version. Wavebox requires a beta or nightly version of the 1Password app. Could you let us know if troubles continue after updating to a beta? As of writing this message, version 8.9.9 (80909006) is the latest: Use 1Password beta releases

Thanks!

We're gettings reports this is happening again with 1Password 8.9.8 80908009. Checking for updates, reports that everything is up to date

Hey @Thomas8520, thanks for reaching out. This change to Production is currently expected due to a known limitation. As long as you remain on the Beta channel, you will advance to the new Beta as soon as it's available.

Ali

This has presented itself again. A Windows beta install has moved onto version 8.9.5 (80905042) on the production channel and shows the warning.

If I check for updates, 1Password reports that everything is up to date

Hi @Thomas8520,

We appreciate you reporting this behaviour with the Beta release channel active and not updating past Production 80800203. I've been able to reproduce behaviour and reached out to the team for some more details.

This is happening due to this particular Production 80800203 being released on the same day, but later than Beta 80800215. We look for the newest entry in the changelog file, which includes all channels and it's seeing that Production 80800203 as the newest entry between those two channels.

I hope this helps explain the cause, but I'm happy to hear that you were able to resolve this by redownloading the latest Beta version. I'm sorry for any frustration this causes, but this is the best workaround for this Beta release.

Please let us know if you have any further questions.

ref: dev/core/core#16529