migration Intel Mac -> Apple Silicon hangup because Beta

niceoldguy
niceoldguy
Community Member

Just setup a MacMini M4. Used migration assistant to transfer from 2018 Intel Mac.

On startup on the M4, 1Password asked to install Rosetta. I didn't want this, and followed instructions found here to delete the migrated app, close all browsers, restart, download and install.

Got the message fail because my data was from a newer version of 1Password than the installer. Rinse repeat fail.

Finally remembered I'd signed up for the beta program years ago and was still on it. Compared the version on the old machine 8.10.58 with the version downloaded from the main download page (8.10.56 as of this posting) and got a clue.

Went to the release notes page and downloaded the current beta (8.10.58) and all went smoothly.

This may be an edge case, but since the installer looks up the version that stored the data, couldn't there be a flag that the data was made with a beta version--then perhaps a useful error message could be displayed?


1Password Version: 8.10.58
Extension Version: 8.10.56.28
OS Version: macOS 15.2
Browser: Safari

Comments

  • Hello @niceoldguy! 👋

    I'm sorry that you ran into issues when migrating from your old Mac to your new Mac. To provide some background: our installer will automatically download and install the right build for your Mac whether you have an Intel Mac or an Apple Silicon Mac. If you've migrated from an Intel Mac and are seeing a message about Rosetta, then it means that you migrated the Intel build of the app from your old Mac and you'll need to reinstall 1Password.

    In addition, we do sometimes update the database schema which can result in the beta or nightly version of 1Password using a newer schema than the production version. To move from the beta/nightly to the production version you'll need to fully remove 1Password's data and then install the production version: Use 1Password beta releases - To stop using the beta

    That all being said, I'm glad that you were able to resolve both issues by installing the latest beta version of 1Password.

    This may be an edge case, but since the installer looks up the version that stored the data, couldn't there be a flag that the data was made with a beta version--then perhaps a useful error message could be displayed?

    I think that this is a great suggestion and I've passed it along to the team. Thank you for the feedback! 🙂

    -Dave

    ref: PB-45522629