1Password incorrectly reports Wavebox is out of date

Hello @Thomas8520 and @remo, I'm sorry to learn of this issue (and for the delay in response - we just launched 1Password 8 for Mac, which means things are busier than usual here).

We'll need to investigate this a bit on our end, so I have forwarded your reports of the problem to our development team so they can check it out. Thank you @thomas8520 for the details on reproducibility - this kind of thing is extremely helpful when we're trying to track down the source of the problem. I'll hope to have more for you soon.

ref: dev/core/core#15241

Excellent, thank you for the update @Thomas8520. And welcome to the latest Beta! 🙌

Hi @Thomas8520, thanks for your message and I'm sorry to learn of these newly reported troubles.

The version of 1Password mentioned, 80800203, has been promoted to Production on July 19, 2022. The latest Beta version 80800215 is required and can be found here: https://downloads.1password.com/win/1PasswordSetup-latest.BETA.exe

It sounds like the previous Beta may have been installed, but if 1Password is set to the Production channel, when this update happened, 1Password did not update to the latest Beta. I've included our guide here which explains how to set the release channel in 1Password 8 to ensure it stays up-to-date: Use 1Password beta releases

I hope this is helpful, but please let us know if you have any further questions.

Hi @Thomas8520, thanks for the update! I'm glad this worked!

Just keep an eye on the Beta channel in the settings:
1. Open and unlock 1Password.
2. Click your account or collection at the top of the sidebar and choose Settings (or Ctrl + Comma).
3. Click Advanced, then set “Release channel” to Beta.

Once this is set to Beta, you should get automatic updates as new betas are released. If you need to go back to Production for one reason or another, reverting that setting Production will keep you on the latest beta version downloaded, until the production version number surpasses that of the current build.

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

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

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!

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.

Hi @mbdiener! I'm sorry to hear that you ran into this issue again in recent days. I understand that you've been in communication with us about this already - if this was via email, could you provide your Support ID number here so we can connect the dots? Thanks!

I don't have any answers at the moment, however I've reached out to the team for more information, and we'll be back in touch as soon as we have any details to share.

Hi @mbdiener, thanks for letting me know 😄I can see that my colleague Jermaine has also reached out to our browser team for more information about this. To keep the conversation in one place, myself or one of my colleagues will continue the conversation with you via email as soon as we have news to share.

We do apologise for any inconvenience caused, and we appreciate your patience here!

ref: LQP-83416-892