Oops, something went wrong when loading (Safari)
Comments
-
Is there an update on this? I'm still having issues with profiles and 1Password. I'm using the workarounds but it's tiring having to do so when it used to work so well. Not having TouchID usable is also a pain. Most recently, on macOS Sequoia, the browser extension keeps saying that there's been an issue:
Would really like to get back to the place where 1Password was actually seamless. Any updates?
0 -
Hello @dpkonofa! 👋
I'm sorry that you're running into the "Oops, something went wrong while loading" error message when using 1Password for Safari. Our developers have released a potential fix for the issue in a previous update but we're still seeing reports from a small number of customers that the issue persists in certain cases. So that I can investigate further can you tell me the following:
- Which version of 1Password for Safari and of the desktop app are you using?
- Find the version numbers for 1Password and your operating system
- How to keep 1Password up to date in your browser
- Are you using more than one Safari browser profile? If you are then how many profiles are you using?
I look forward to hearing from you.
-Dave
ref: dev/core/core#32166
0 -
Hi, @Dave_1P:
Thanks for responding. This is getting frustrating as I have a ticket open for this issue and the replies are just rehashing things I've already done, told them about, and referenced from here. I even sent 3 diagnostic logs to try and give some additional technical info and no one has even referenced them.
1) 8.10.52 (81052025) - for 1Password for Safari, 1Password for Mac 8.10.54 (81054013) (On the Beta channel since it was recommended here and suggested that the workaround would show up here before an official release)
2) Yes. I am using 2 profiles - a Personal profile and a Work profile.
0 -
So what do we do if we sent in Diagnostic Reports and didn't receive any replies based on them?
0 -
WDM-27243-482
0 -
Thank you for posting the Support ID. It sounds like you're running into a known issue that is currently open with our development team. There is no fix available at this time for this known issue which is why my colleagues might have been suggesting some workarounds that might help in the meantime while we wait for a fix from our development team.
If our development team does request any more information from your end to further investigate the issue then the team will reach out, however I can see that we've been able to reproduce the issue on our end so more information isn't necessary at this time.
I'm sorry again for the inconvenience. If you have any other questions then please reply to my colleague's last email. Since we have a communications channel open via email, I'll close this thread.
-Dave
ref: dev/core/core#32166
1