Errors in Safari on Mac
Hello Community,
My first post.
I have just installed the 1Password extension for Safari on a Mac running MacOS 15.0. Safari Version 18.0 (20619.1.26.31.6).
The extension manager shows the following errors for the 1 Password extension.
Errors for "1Password for Safari":
x Unable to find "lib/react.js" in the extension's resources. x Unable to find "lib/react-dom.js" in the extension's resources.
× Unable to find "lib/react.js" in the extension's resources.
× Unable to find "lib/react-dom.js" in the extension's resources. x Unable to find "lib/react.js" in the extension's resources. x Unable to find "lib/react-dom.js" in the extension's resources.
& Unable to find "lib/react.js" in the extension's resources.
& Unable to find "lib/react-dom.js" in the extension's resources. x Unable to find "lib/react.js" in the extension's resources.
× Unable to find "lib/react-dom.js" in the extension's resources.
× Unable to find "lib/react.js" in the extension's resources.
& Unable to find "lib/react-dom.js" in the extension's resources.
Is this a serious issue and if so how can it be fixed?
Comments
-
Hello, @rockoyster. Thank you for writing in.
Our development team is tracking an issue with 1Password for Safari showing the errors you mentioned running MacOS 15. Are you experiencing app integration or Autofill issues with 1Password for Safari?
-Evon
ref: dev/core/core#32589
0 -
Hi @EvonG1P
Thanks for your reply. Good to know the issue is under investigation.
I am only new to 1Password so just finding my way around. So far everything appears to be working as it should despite the errors noted above.
rockoyster
0 -
I wanted to add that it's not limited to MacOS 15. I'm also experiencing it on Safari Version 18.0 (19619.1.26.111.10, 19619), but MacOS 14.7. No auto-fill issues with this mix either.
1 -
Thank you for your reply. I appreciate the additional details.
So that I can take a closer look at the issue you’re experiencing, I’d like to request that you send me some information to support+forum@1Password.com. With your email, please include the following:
- A link to this thread: https://1password.community/discussion/148412
- Your forum usernames.
- A diagnostics report from 1Password for Safari: How to send a 1Password diagnostics report.
You should receive an automated reply from our BitBot assistant with a Support ID number. Please post that number here, and I will be able to locate your message and ensure it has reached the right place. Thank you!
-Evon
0 -
Hi Evon,
Not sure if you wanted diagnostics for only MacOS 14.7 or for my report. Anyway I have lodged diagnostics and Your support ticket ID is HQY-66173-964.
HTH.
rockoyster
0 -
I've tried three times and have not received any BitBot response to any of them. I'll keep an eye out, but know that I've tried and not been able to get this submitted.
0 -
Hi hamfam7,
Probably not much help to you but I got a BitBot response in about 2 minutes. Have you checked your spam folder?
rockoyster
0 -
Thank you for sending the reports! I located both tickets and shared them with our development team for further investigation. To prevent duplication of effort, please continue the conversation via email. 🙂
-Evon
ref: HQY-66173-964
ref: XYK-61714-3740 -
I am having the exact same issue. I'm on an M1 MacBook Pro 16", Sequoia 15.0 and 1Password 8.10.46. I first noticed the problem when trying to investigate why 1Password was not showing up in the Privacy & Security->Automation settings. I was investigating this because autofill isn't working properly on my MBP.
I uninstalled and reinstalled the 1Password for Safari app but sill have the same errors.
I also have a 2018 (Intel-based) Mac mini with the same versions of OS and 1Password. When I look at the 1Password for Safari extension on that Mac I don't have those errors.
0 -
My support ticket ID is ECQ-56431-658.
0 -
Thank you for posting the Support ID. I see that my colleague investigated this and was able to verify that you're running into a known issue that our development team is aware of. Hopefully it's resolved in the future soon. I'm sorry for the inconvenience.
-Dave
ref: dev/core/core#32589
0