Forum Discussion

bwadm's avatar
bwadm
Dedicated Contributor
2 months ago

The Advanced setting "Release channel" is not respected

Hi!

I did set my 1Password 8 App to the "nightly" builds channel a few weeks ago. At present, I am running:

1Password for Mac 8.11.22 / 81122010, on NIGHTLY channel
My advanced setting for the channel is: PRODUCTION / install updates automatically

When I click the "Check for updates" button in the About panel, always a new nightly build is installed. I just got 81122010 a few minutes ago.
I also tried to set to BETA, but no new beta build has been installed for weeks, although new beta versions were announced on the website.

How can I make sure that 1P does really install builds from the correct (selected) update channel?

4 Replies

  • Hello bwadm​! 👋

    I'm sorry that you're running into issues when switching between release channels. I'll respond to both of the issue that you've reported below: 

    Unable to switch to the production/beta release channel when using the nightly

    If you've tried the nightly version and want to switch to either the production or beta version then you'll need to follow the steps in this article, just switching the release channel won't be enough: Stop using a prerelease version of the app or browser extension

    This is due to the nightly version always having a higher version number than the beta or nightly version. 

    Unable to update to the beta version when using the production version

    This is a recent issue that we've been able to reproduce on our end as well and an internal work item is open to get this fixed in the future. For the time being, you can manually install the beta version from our release notes page: 1Password for Mac Beta

    I'm sorry for the inconvenience. Let me know if you run into any further issues. 

    -Dave

    Issue=PA-864

    • bwadm's avatar
      bwadm
      Dedicated Contributor

      Thanks, Dave!

      However ... when I do not update the Nightly for a while, the build number should stay the same on my machine. Once a new production version is out and a new beta cycle has been initiated, the beta build number on your (the 1P/AgileBits) server must be higher than the "old" nightly build number on my Mac. 
      Therefore: If the update logic is implemented correctly, and if the Release Channel setting is respected correctly, the Update function should solve the "problem" without reset.
      Right?

      • 1P_Dave's avatar
        1P_Dave
        Icon for Moderator rankModerator

        bwadm​ 

        There's currently an issue with the update login that our team is aware of and hopes to improve in the future. For the time being, if you're currently using the nightly version, switching to the beta version manually using the steps in the article that I linked to is the best workaround. 

        -Dave

        Issue=PA-596

  • bwadm's avatar
    bwadm
    Dedicated Contributor

    Additional observation: The initial report comes from a MBP16 (M1) running 15.7.2.

    Now, I am tested on an iMac24 that has just been set up with macOS 26.1 using a clean install. I dowloaded the production version of 1Password 8 (via the zipped installer) and got v8111836.
    My advanced setting for the release channel is: BETA / DO NOT install updates automatically

    The "Check for Updates" reports that I am up to date, but the 1P website tells that there is v8112031 from November 12th.

    Why is the new Beta not installed?