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 https://1password.community/discussion/129049/warning-popup-on-launch 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! Corentin 1Password Version: 8.10.3-1.BETA Extension Version: 2.8.1 OS Version: 12.6.3 Browser:_ Safari

cortig 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 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? Corentin

"You’ve used a newer version of 1Password on this device"

29 Replies

1P_Tommy
Moderator
3 years ago
UXJedi

No worries. If you continue to have trouble on the Mac please email us using support+forum@1password.com. Be sure to use the email address tied to the account in question.
UXJedi
Occasional Contributor
3 years ago
Terribly sorry! I misspoke… er, mistyped… missed something! I meant to only say macOS.
1P_Dave
Moderator
3 years ago
UXJedi

I don't believe that we've received reports of the "You’ve used a newer version of 1Password on this device" error on either iOS or iPadOS, can you post a screenshot of the error message that you're seeing on your iPhone and iPad?

-Dave
1P_Dave
Moderator
3 years ago
@kshuey73

I'm sorry that you're running into the issue on your Windows PC. So that we can investigate further, I'd like to ask you to send in a diagnostics report:

Press the Start button on your keyboard (it may have a Windows icon on it). This will bring up your Windows search bar.

Copy and paste this into your Windows search bar: %localappdata%\1Password\logs

Press Enter.

Select everything in this folder, and then right-click and choose Send to > Compressed (zipped) folder.

Attach the zipped diagnostics to an email message addressed to support+forum@1password.com.

With your email please include:

A link to this thread: https://1password.community/discussion/comment/683586/#Comment_683586

Your forum username: kshuey73

Please do not post your diagnostic report to the forum. This is for your privacy and security.

The report will be in zip format. Please send the entire file.

You should receive an automated reply from our BitBot assistant with a Support ID number. Please post that number here. Thanks very much!

-Dave
UXJedi
Occasional Contributor
3 years ago
Still happens to me. MacOS, iOS, iPadOS
Former Member
3 years ago
I've still been getting issues with this on my Windows PC - each time I restart my computer I'm getting the error coming up.

Is there a fix/solution for Windows?
1P_Dave
Moderator
3 years ago
Our developers are aware of the issue and are looking into making improvements to the update process in the future so that it's easier for users of nightly builds to recover from this if it occurs again. The team is also looking into making changes to the updater to avoid the issue entirely.

In the meantime, using just the beta or production builds will result in a more stable experience as those are QA tested.

I'm sorry for the inconvenience and I've passed along all of your comments to the team. If anyone else is still running into the issue then please let me know so that we can help get you back up and running. 🙂

-Dave

ref: dev/core/core#15096
ref: PB-32038641
cortig
Super Contributor
3 years ago
1P_Tommy I understand what you meant (and I indeed thought you were talking about the data, not the app).
Just so you know, I tried various builds of the app with the idea that 1) restoring the build I was on might get me back on my feet or 2) installing a later build might bypass the issue where this process seems to think my data is coming from a “later” build.
Clearly, letting the app auto-update after restoring an old build was putting me at risk of seeing the warning again.

It seems that wiping out all my user data to redownload it off the 1Password servers is the easiest option, but it’s not great for troubleshooting the issue at hand here and confirm it has been fixed…
1P_Tommy
Moderator
3 years ago

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.

I took this to mean you restored the app from the backup. Apologies if I erred.

Me:

Because you restored from a backup you may have accidentally updated into the problem again.

Apologies for not being clearer this was in reference to the app.
cortig
Super Contributor
3 years ago
1P_Tommy I haven't restored anything from backups.
I tried reinstalling various versions of the app itself (from other Mac around that had not updated) and it got me back on my feet usually, but update after update the issue kept on coming back.
Yesterday I reset the data completely on the affected Mac and everything was redownloaded of the 1Password servers.
I hope the issue is now fixed so that the warning won't popup again. Time (and future updates) will tell!

Corentin