Skip to main content
August 26, 2023
Question

Mac Beta reverted itself to Production channel and won’t change back

  • August 26, 2023
  • 16 replies
  • 492 views

My macOS version of 1Password updated itself to the Production channel version, despite specifically being set to use the Beta channel in the advanced settings.

Checking for a new version does nothing, it just stays on Production even though it is supposed to be the Beta.


1Password Version: 8.10.13
Extension Version: Not Provided
OS Version: macOS 13.5.1
Browser: Not Provided

16 replies

1P_Tommy
1Password Employee
September 1, 2023

If you create a new Beta, does that always have a version number equal to (or higher than) the current Nightly?

It seems like you might be thinking the nightly sits above production and below beta. That is not the case in the numbering system. Nightly always has a higher numbering scheme than any production or beta.

Real world examples:

Current production is 8.10.13
Current beta is 8.10.16-15
Current nightly is 8.10.16-18

If not, will you downgrade the 1Password App for people that selected Beta, but are still getting Nightly updates because of their previous channel choice?

You are never downgraded you always move forward. To change channels you would need to take manual intervention. You always go forward never backward.

XIII
September 1, 2023

It seems like you might be thinking the nightly sits above production and below beta. That is not the case in the numbering system. Nightly always has a higher numbering scheme than any production or beta.

That is exactly what I expected.

But this also means that I still don’t understand: if 1Password keeps installing newer Nightly builds, changing from the Nightly to the Beta channel is futile, since 1Password will never install another Beta (without manual interaction).

What am I (and possible @bwadm as well) missing all this time?

bwadm
September 1, 2023

I agree on "never downgrade".
But:
When I set the Release channel to BETA, I was on 8.10.16-9 NIGHTLY
The current BETA is 8.10.16-15 (from August 31 2023).
Do we agree that 8.10.16-15 is higher than 8.10.16-9?

A consistent behaviour of 1P would be to NOT update to the next NIGHTLY if BETA is selected as Release channel.
The next update must be the next BETA with a build number that is higher than the running NIGHTLY.

1P_Tommy
1Password Employee
September 2, 2023

@XIII @bwadm

If you wish to be rid of the nightlies please take the following steps. They should get you on the beta train and keep you there.

  1. Make sure you have your 🚒 Emergency Kit and know your account password and all data is contained on 1Password.com.

  2. Quit 1Password and all browsers for good measure. Right-click 1Password in the menu bar (If it's there) and click Quit.

  3. Open Finder, and click the Go menu > Go to Folder...
    In the box that appears, copy and paste the following exactly:


~/Library/Group Containers/2BUA8C4S2C.com.1password/Library/Application Support/1Password

  1. Press Return.
  2. You'll see a folder called Data – right-click on the folder and select Compress "Data".
  3. Drag the original Data folder to the Trash.
  4. Drag 1Password from the Applications folder to the Trash.
  5. Download a new copy of 1Password from here and install it - https://downloads.1password.com/mac/1Password.zip
  6. Wait a few moments and then open 1Password 8. You'll be taken through the setup process.
  7. Update to the Beta. * if desired.

--

I also went digging and found an issue that Ben filed about the updater logic not working as intended. This sounds exactly like what you've encountered. My apologies for that. I can't say I have encountered it. It sure sounds like you have. I've add the both of you to the open issue.

ref: dev/core/core#16674

XIII
September 2, 2023

Thanks. I already did something similar a few days ago and am running Production now (and can still use passkeys 🎉).

Nevertheless I would still like to understand (which I still don’t 😢).

1P_Dave
1Password Employee
September 6, 2023

@XIII

I'm happy that you were able to switch release channels. I'm sorry for the confusion, I see that Tommy has added you to an internal issue that we have open where 1Password's update logic can sometimes be broken after switching release channels, hopefully this can be fixed in the future.

-Dave