In case you want to install previous versions of nightlies and betas....

AganArya007

You can visit this (unfortunately hidden) site:
https://app-updates.agilebits.com/product_history/OPW8 (for Windows)
https://app-updates.agilebits.com/product_history/OPM8 (for Mac)

Note: if you press download on Mac page, it will contain this $ARCH in the address. Replace $ARCH with x86-64 (for Intel) and aarch64 (for ARM Mac), and then the download will proceed.

Note 2: Replace OPW8 or OPM8 with OPW7 or OPM7 for 1Password 7.

I hope 1Password team can expose this site a little bit more on the official download page, because sometimes there's this really stable and perfect nightly or beta, but then the next one is buggy again, so maybe someone out there, like me, wants to downgrade while still can.

Thank you!

---

1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided

James.Dressel_1P

Hello @AganArya007 ,

For your awareness, we don't consider https://app-updates.agilebits.com/product_history/OPW8 or https://app-updates.agilebits.com/product_history/OPM8 as part of our "public API". Those pages may be changed or removed without warning. We also don't recommend staying on specific old beta or nightly releases. Beta and nightly releases expire after 90 days, if you need to stay on a frozen version for longer, we recommend using the stable "production" releases. It is likely that the OPW8 page will return URLs containing $ARCH in the future.

I’ll take this request to the team to consider. I believe the main thing you’re looking for is an exposed method to download previous versions, as opposed to specifically using https://app-updates.agilebits.com to get those versions. Is that correct?

I'd also like to provide you with some background on why the update servers are setup this way, and why we're hesitant to make changes. App-updates is one of our legacy services. It’s difficult and time consuming to change for a few reasons, and it needs to support several generations of 1Password applications.

App-updates provides endpoints that are used in different contexts. For example, in the 1Password for Mac 4-6 days, people would visit https://app-updates.agilebits.com/product_history/OPM4 to see release notes intended for consumption by humans. The 1Password desktop client would visit another endpoint (the "check" endpoint), intended for use by it's auto-update code. 0 in the url would be replaced by the actual OPM4 build number in the example below:

$ curl -sS https://app-updates.agilebits.com/check/1/12.3.1/OPM4/en/0/YES | jq
{
  "available": "1",
  "version": "4.4.3",
  "relnotes": "https://app-updates.agilebits.com/relnotes/OPM4/en/0/443000/Y?os_version=12.3.1",
  "sources": [
    {
      "name": "Amazon CloudFront",
      "url": "https://c.1password.com/dist/1P/mac4/1Password-4.4.3.zip"
    },
    {
      "name": "CacheFly",
      "url": "https://cache.agilebits.com/dist/1P/mac4/1Password-4.4.3.zip"
    },
    {
      "name": "AgileBits",
      "url": "https://cdn.agilebits.com/dist/1P/mac4/1Password-4.4.3.zip"
    }
  ]
}

The updater then sees that there is an update available with a newer version. It also sees that there are three places to download the file from, which correspond to different CDNs we use to make the file available.

Earlier 1Password releases were mostly on a single CPU architecture. We knew that we wanted to support Apple Silicon ("M1") processors with 1Password 8 for Mac. We didn't want to ship a universal .app file, since it would double the size of the download. As a result, we build two zipfiles for each release, one for Intel processors, the other for Apple processors. The 1Password 8 Mac updater includes the CPU architecture when it requests available updates. To support updating single-architecture builds, I modified the output of the check endpoint to insert the architecture that's provided by the updater code. In the below example, the arch is aarch64 for Apple Silicon.

$ curl -sS https://app-updates.agilebits.com/check/2/12.3.1/aarch64/OPM8/en/0/A1/nightly | jq
{
  "available": "1",
  "version": "8.7.0-63.NIGHTLY",
  "sources": [
    {
      "name": "Amazon CloudFront",
      "url": "https://c.1password.com/dist/1P/mac8/1Password-8.7.0-63.NIGHTLY-aarch64.zip"
    },
    {
      "name": "CacheFly",
      "url": "https://cache.agilebits.com/dist/1P/mac8/1Password-8.7.0-63.NIGHTLY-aarch64.zip"
    },
    {
      "name": "AgileBits",
      "url": "https://cdn.agilebits.com/dist/1P/mac8/1Password-8.7.0-63.NIGHTLY-aarch64.zip"
    }
  ]
}

For technical reasons, it was pretty quick and easy to add architecture support to the check endpoint. It would take a larger effort to either display multiple links with the architectures inserted on the product history endpoint. We also have a newer site https://releases.1password.com/ that lets us include more detailed information and screenshots on our releases notes.

On macOS in particular, we want users to use our installer. It will ensure that the correct architecture is downloaded. It also will take some steps to ensure smooth operation, such as making sure 1Password.app is run from /Applications/1Password.app and that the macOS quarantine attribute is removed. Skipping these steps can lead to performance issues and difficult to troubleshoot interactions between 1Password and the browser extensions.

Thanks,

James Dressel
Senior Build Engineer

AganArya007

Hi.

Thank you very much for a very detailed answer.

Yes, that's my goal, to have an easier method to downgrade, via a more publicly shown link. And of course, I'm aware that Beta and Nightly can expire soon, but in 90 days, there has to be a newer version that is clearly as stable, if not more, than the one someone is still using now.

And it's not that I encourage people to downgrade willy nilly to way older versions. It's more like hey, there's a new update, but ah, it's somehow way buggier, so I'll downgrade one version earlier and I'll wait for a week or two for newer betas and nightlies. More like, just in case. Like oh macOS 12.3 is buggier, so I'll downgrade to 12.2 for now and wait.

But if it's not even a public API in the first place, and the link could be changed or even gone forever, well I hope you would consider putting a more permanent method or heck, maybe I'll accept my fate, turn off auto update, and be more careful about updating the beta and nightly (but 1Password 8 isn't full version yet on Mac... so... beta and nightly it is for now) :D

Once again, thank you very much! Looking forward to discuss it further.