Forum Discussion

patrick227's avatar
patrick227
New Contributor
4 hours ago

MacOS - Keep reverting from Beta to Production: After doing everything suggested

Keep reverting from Beta to Production: Did everything suggested including deleting info with Apple Keychain, Finder files, etc. I have sent an email with the Diagnostics file for 1Password Desktop for Mac

Hello!

I am a bit frustrated, since I have followed all the steps suggested to others and also to me and have been reverted back to 1Password's PRODUCTION channel twice over the past year after being on BETA. I am referring to my Mac and the Desktop app.

Just today, I was checking the status of Mac's auto-fill only to see things seemed to have been shifted, and I saw that PRODUCTION was once again my product.

Even the 1Password for Mac Desktop settings still have BETA set as the release channel right now.

I previously deleted every single reference in Keychain to 1Password, and this keeps happening. I use 1Password BETA for my Chrome browser, and also use 1Password CLI with Claude as well as other sensitive things, so I really cannot have this keep occurring.

I have followed the instructions with care and have used my Emergency Kit too. I have generated a Diagnostics file which I will email.

I am just continually frustrated at 1Password for this occurrence. There is something going on here beyond just deleting every reference to 1Password using Finder to navigate those specific files on both my MacBook Pro and iMac, and then also completely deleting my account references on my computer so that I use my 1Password Emergency Kit.

I deleted the 1Password DATA folder, after first compressing it, to see if that would prevent it.

It seemed to hold for a week or so the last time I did all of this.


This is frustrating, and I need this to not occur in order for me to trust 1Password, especially with the new features the Beta is bringing forth for Macs. In addition, in using the CLI and the SSH agent, it disrupts my process as I can't trust that things will still work properly if I re-install the app. I have to double-check all of that, and it is time-consuming.

I actually just sent an email:

"

Hello!

I'm feeling a bit exhausted in 1Password's inability to keep me on the BETA channel for more than seemingly a few weeks, as it reverts me back to production, despite my:

 

1) Ensuring BETA is selected as the Channel

2) Deleting all references in Apple Keychain

3) Deleting all application files and references in multiple threads through Finder --> Go, including the DATA file: after first compressing it as per the suggestions.

4) Being at the stage where I use 1Password Emergency Kit

 

I have included the diagnostics file for the desktop app - it's been sent as a Google Drive link by Gmail because of its size, which is now:

1Password for Mac 8.12.22 (81222017) on the PRODUCTION channel.


The Chrome beta browser extension is version: 8.12.24.24 (81224024) on BETA channel (and it would be nice to be able to copy/paste this as you can with the 1Password desktop app for Mac as it's even hard to copy/paste it, so I manually have to enter it here.

 

I'm using Chrome version Version 149.0.7827.54 (Official Build) (arm64)

It keeps automatically updating by the way, as per my preference. But I doubt it's the issue anyway.

 

I'm using MacOS Tahoe 26.5.1.

 

Doing all this really interferes with my process, as I am using the CLI with Claude and also have the SSH agent turned on. And I'm using MacOS Autofill which then gets disrupted when I am reverted back to PRODUCTION which doesn't support it even though my preferences in the app still say BETA.

 

So it really disrupts my confidence in the flow of 1Password to repetitively do this. On my MacBook Pro, which uses the same Apple cloud account, I have no issues staying on Beta, and Keychain syncs between the two systems.

 

Normally, at this point, I'd do the following before submitting a diagnostics report, just so you can see what steps I do follow:

1) Double-check Release Channel, which is still Beta for me.

 

2) Open Finder, click the Go menu > Go to Folder..., and in the box that appears, copy and paste the following exactly: ~/Library/Group Containers/2BUA8C4S2C.com.1password/Library/Application Support/1Password

 

Compress the DATA folder and then delete the original DATA folder. Sometimes I've deleted the compressed file too, to see if that prevents future unwanted transitions back to the Production channel.

 

3) Completely delete the desktop version of 1Password, and ensure every process is closed, including the Chrome browser as it has the 1Password BETA extension. This has meant printing out instructions so I don't rely on any browser's instructions while it remains open to follow the instructions. I also ensure the 1Password app is closed via the Apple menu bar in the top right before deleting the desktop app.

 

4) I open "Keychain Access" and delete any 1Password Preferences as well as anything that references 1Password. I delete b5credentials from Keychain Access, which stores the encryption details within this entry; more specifically: 

 

"com.agilebits.onepassword.b5Credentials"

 

The preferences include things such as "1Password:device-unlock-ask-again-after" which don't actually store any account data, but I have deleted them in case they might be causing the issue, as I'm tired of being reverted back to production.

 

5) I make sure to download the 1Password beta from: https://releases.1password.com/mac/beta/, and prior to doing so, I delete all older 1Password installation files in Downloads just to be sure. And I regularly empty the Trash bin.

 

-

I REALLY HOPE the diagnostics can clarify the issue, as I already have spent significant time on this process before and hope not to have to redo everything once again.

 

Please let me know what the next steps are, as it has been a week perhaps or maybe slightly longer since I completed this lengthy process - as described above, and am surprised to be back on the PRODUCTION channel."

I hope this works. Has anyone else experienced this even after following the above referenced steps?

Thank you!

1 Reply

Replies have been turned off for this discussion
  • Hello patrick227​! 👋

    I'm sorry that you were unexpectedly moved to the production version. I've replied to the support ticket that you opened, let's continue the conversation there. 

    To avoid having the same conversation in two places at once, I've closed this thread. 

    -Dave