Error: "Oops, something went wrong while loading" [SEE APPROVED ANSWER]

I'm sorry for the delay, folks. The team has been working on your reports. You should be able to use 1Password in the browser version 2.14. We appreciate your patience while we continue to investigate the issue.

• Please try turning off the extension and turning it on again:

1. Right-click the 1Password icon in your browser's toolbar and click "Manage Extension."
2. Turn off the 1Password extension and then turn it back on again.
3. Click on the 1Password extension in your browser's toolbar.

If the above steps do not work, follow these steps to get 1Password working in your browser again:

The actions below would necessitate you using your account password to unlock the 1Password in the browser until an update can be released. After releasing a new build, you can turn on the shared lock state and return to using biometrics for unlocking.

• Turning off the shared lock state:

1. Right-click on the browser toolbar icon.
2. Select settings.
3. Turn off the General section's Integrate with 1Password app setting.

• Turning on the shared lock state: (Only after a new release is issued)

1. Right-click on the browser toolbar icon.
2. Select settings.
3. Turn on the General section's Integrate with 1Password app setting.

We will follow up here in the community when a resolution occurs. You have our apologies for the disruption.

I'll get onto the suggested fixes shortly, but just wanted to float an idea here.
It seems we've got a 'friendly' crowd here, 1Password. Perhaps consider something like an 'insiders' release. That way, us friendlies can do a first round real world test for you before releasing into the wild. I've got a family subscription and 1Password is my elderly mother's lifeline. When things like this happens, it takes a lot of effort to get her processes aligned again, including having to explain why the known process doesn't work anymore.
Just a thought...

Someone in another thread found a fix, at least for Chrome. Uninstall the extension from Chrome, then close Chrome, open 1Password app, go to Settings>Browser, click on "Get 1Password for your browser." This will take you to the Chrome webstore's page for the extension, where you can reinstall it. The extension should work properly after that.

As above reporting using Chrome browser, extension autofill doesnt work at all. Also extension and bottom of screen full app are not in sync anymore. I.e. locking extension and app worked in unison, locking one would lock the other and vice versa. Getting OOPS message. tried rebooting and pretty well what has already been listed before. Quickly losing confidence.

I also have this problem (and have emailed 1Password support about it (#QMC-74326-711). I have since tested the suggested workaround above (thanks Solos for letting us know here), and I can confirm that it does work in Safari, besides the inconvenience of needing to log in again every time the browser is newly launched.

For the sake of others, these are the settings to look for. In the 1Password app:

And in the 1Password settings in the browser:

Restart the browser, and then you should be able to log in to 1Password from the browser and then have access to your vault.

Now if I can just remember to undo these settings when the fix is released.

Went looking around for similar threads and found that this has a temporary fix that can be implemented until a proper patched version of the browser extension can be released. See https://1password.community/discussion/comment/693695/#Comment_693695

Hello everyone,

I'm sorry for the inconvenience that the issue is causing. Our developers are working on releasing a hotfix as soon as possible. The team has identified the cause of the issue and hope to be able to share more soon.

For now, we've published documentation on how to get things working again on our website based on Tommy's instructions from earlier in the thread: If you see “Oops, something went wrong while loading”

Thank you for your patience.

-Dave

Thanks steph_giles but this is apparently not an issue related to her Mac. I just now installed 1Password on a new M2 Pro MacBook Pro and I'm seeing the exact same problem as on my wife's new M2 Pro Mac mini. That's not possibly a coincidence. I'll just go back to Keychain and wait for the problems to be resolved in the next update. I don't say this with any malice at all...but I've experienced more problems with v8 than I've had with all versions during the past 17 years using 1Password.

Adding more details, clicking Reload 1Password does not solve the problem. Restarting browsers as well as restarting the computer does not solve the problem either.

Have had the same issue in all my 4 browsers with the plugins.
For being able to reply here to this post, I created an account via the 1password application. Looks like creating an item fixed the issue in all the browsers :-D.
Really strange behavior.

Edit: Sorry, was to fast. The described solution worked for me in Edge, Chrome and Firefox under Windows. Brave still had the issue. I had to go the way @scottfulmar described. Uninstall plugin, restart browser, install plugin. After that, Brave plugin also works again.