I came back to my Mac today and launched 1Password.
I immediately got the following warning:
I had not changed from nightly to another channel, I sure had not reinstalled 1Password. It seemed that it happened after the app auto-updated itself.
1Passwrd was in version 8.10.3. I tried deleting the app and using the installer to reinstall: and indeed it installed an apparently different version of 1Password (8.10.3-1.BETA), but still, the problem remains and I get the same warning at every launch.
I can use the same approach described here to get back on my feet, but I thought I had to report this since I clearly don’t understand how it happened in the first place!
1Password Version: 8.10.3-1.BETA
Extension Version: 2.8.1
OS Version: 12.6.3
Sorry for the trouble. I've not seen any tother reports like yours but I'll keep a look out. Correction one other. The post you mentioned from Ben would be the correct approach.
I just ran into this as well. I switched to the beta channel a couple of months ago to get a bug fix, then switched my setting back to stable a few weeks ago, expecting that I'd still be getting betas for a while until the relevant stable version came out. I've received a few beta updates since then.
This morning, I had the notice in 1P that it wanted to restart after an update, so I did that. Upon restart, it was on a newer beta version and had another restart message. I hit the button again, and this time, I got the message above about having used a newer version. So 1P must have switched to a stable version that's behind the beta version. Again, this is all driven by the built-in update mechanism; I did no manual updates/installs using versions off the web site.
I think the version I started on today was 8.10.1 beta per the about box, and Finder now shows I'm on version 8.10.3 after the two restarts.
I'll go through the process to nuke things and get operational again, but as a suggestion, it'd be great to have a built-in way to handle this. Two ideas:
Isn't simply switching to the latest beta always a way back to a working app? If so, consider adding a button to the dialog to do just that, without making the user do the job of finding, downloading, and installing the beta.
Add functionality to check for a keyboard modifier (e.g., probably shift or option) during startup and offer to reset the database. Basically, an automation of the manual procedure. You could add another button to the dialog as an alternate route to the feature in case people forget it's there. Note that this feature is useful to any user beyond this situation.
Oh, boy. I just found this problem. Oh boy, the dangers of beta waters. Now, I'm freaking out. I'm unsure of what the correct "approach" it is to fix it now. Can someone lend a hand? @cortig ?
(There is a bit of irony here! 1Password provided me the correct password to login to this forum!)
@BobW I like your ideas, btw.
@BobW I thought about your option 1), which is why I attempted to reinstall the latest beta through the installer, but in my case it didn’t work.
I still don’t understand how I ended up in that situation on that Mac.
If the installer installs the latest beta instead of the latest nightly, is there a way to manually install the latest nightly?
@cortig LOVE your avatar! I meant to mention @BobW for assistance on what option I should do, not the other way around. I'm sorry, I'm getting you all confused! So, what is my best route right now?
@cortig Good point on betas v. nightlies. I don't see a reason why the button couldn't compare the installed version with the latest beta and nightly versions to automatically determine the right version to download.
@UXJedi I got back in operation by removing the directory at ~/Library/Group Containers/2BUA8C4S2C.com.1password/Library/Application Support/1Password.
To do it, first quit 1P. Then, open a new Finder window, hit cmd-shift-G (or select the "Go to Folder…" command from the "Go" menu), and paste this into the dialog that pops up:
Hit return, and you should be taken to that path. There, you should see a folder called
1Password. Drag the
1Passwordfolder to the trash. Finally, fire up 1P and you should be prompted to sign back into your accounts. In my case, I also had to reset all my preferences -- not sure if that's normal, but it's definitely worth checking.
@BobW Easy! Thank you.
I apologize for the trouble folks. If anyone continues to have trouble please let me know and I'll be happy to jump in.
I tried to use a second computer to download the latest nightly (and not have to delete all my data).
The other computer was on the beta channel, but told me it in the About box that the version installed was the production build 8.10.3.
I switched this build from beta to nightly and searched for updates. It found and installed 8.10.3-14.NIGHTLY, and when I launched it I got the warning about "You’ve used a newer version of 1Password on this device” again!
There is something wrong with the beta/nightly builds……
I had kept a backup of the 8.10.3 build I had before and was able to restore it and this one opened fine on that second Mac.
@UXJedi I'm glad you like my avatar :-) I've been using it for as long as I can remember :-)
Nice that a community member came up with a solution for "You’ve used a newer version of 1Password on this device" what is 1password doing to fix this?
I had this with the last beta as well as today's. I contacted support a few days ago [#ARQ-15886-117] but solved it on my own by
But if you then stay on the Beta build, it will recur, as it did for me today.
@ag_tommy so yeah, it happened to me again today after updating to the latest beta. I'm going to delete everything yet again and reinstall but not bother with the betas.
Never saw this issue before this week. Glad I'm not the only one but sheesh-seems like I've had waay more issues in the past year with 1PW on the Mac than ever. I miss the stability (and yes, I was on betas in the past-they were typically smooth sailing).
I just followed up on your ticket via email.
…and the problem remains with the new 8.10.4-8.NIGHTLY. 1Password updated and gave me the warning again.
Weirdly enough, it gave me the warning on one computer, but not another.
Could something be done about this? There is a way to get back on our feet, but it's not a correction of the issue… (and prevents you from using the new builds in any case).