Getting started with 1Password for your growing team, or refining your setup? Our Secured Success quickstart guide is for you.
Forum Discussion
btaroli
8 months agoOccasional Contributor
TypeError: Illegal invocation in Chrome Browser
This happens on all the platforms I've tried: Windows, Linux, and Mac. I find multiple reports of this behavior online, including notes on how it should be fixed... and yet it isn't. Is there a timeframe for when this will be addressed? Or is there a workaround users can apply for the time being?
1Password Version: 8.10.56
Extension Version: 8.10.56.28
OS Version: Windows, Linux, macOS
Browser: Chrome
17 Replies
- btaroliOccasional Contributor
I guess you could consider my case, the one I reported here, as Oracle Cloud as well, since our internal SSO is based on OCI IDCS. I have some other passkey sites that aren't Oracle, so I could try those with Chrome to confirm they aren't affected. Please add me to the Oracle affected list as well. I'd like to have some idea when I might be able to use it again, though I fall back on a Yubikey in Chrome for now.
- 1P_Evon
1Password Team
Thank you for writing in. Our development team is tracking a known issue when using a passkey on Oracle Cloud. I've added you as an affected user to our internal reporting.
In the meantime, I recommend using an alternative login method. I understand that this may not be ideal, and I apologize for the interruption to your workflow caused by this.
Let me know if you have any questions.
-Evon
ref: dev/core/core#33167
- khaosspawnDedicated Contributor
Can I be added also?
- PauliehedronNew Contributor
I'm having the same problem on 7.0.3495.29 (Stable channel) (arm64) when trying to login to Oracle Cloud with a passkey. Here's another which looked into the issue.
https://github.com/bitwarden/clients/issues/12060. - 1P_Dave
Moderator
Hello btaroli! 👋
I'm sorry that you're running into an error message when using 1Password in Chrome. So that I can better understand the situation can you tell me the following:
- Where are you seeing the error message that you mentioned? Does it appear on the page? Or in the console log? Can you provide a screenshot of the error message?
- Are there specific steps that you can share that I can follow to reproduce the issue?
- Does the issue happen on a specific website or when performing a specific action?
- Can you link to the other reports that you mentioned?
I look forward to hearing from you.
-Dave