Console error: "Retrieving "b5x-stateful-inline-icon" flag errored: timed out" [Fixed in the beta]

notnotjake

Thank you for confirming that you're no longer seeing the issue. 🙂

-Dave

I am not seeing it anymore

Hello notnotjake, thank you for reaching out.

We've recently updated 1Password in the browser, and this error message should no longer appear. May I ask if you're still encountering this in your browser's console log?

-Evon

oh my god, I didn't realize this was 1Password. nice to know why I am constantly seeing this

mmaass and dealtek

Thank you for confirming that the beta version has resolved the issue for you both. 🙂

thijs

The fix is currently being tested in the beta version of 1Password in the browser. If testing goes well, the team is hoping to include the fix in the stable version as soon as possible. But I'm not able to provide an ETA on when that will be. For now, I recommend that you use the beta version if you'd like to benefit from the fix today.

-Dave

1P_Dave When will this fix go to the stable version? This year it appears there is a release to stable once a month, so we can expect this to be fixed in 1 week?

update - the chrome beta did fix this - thanks

1P_Dave Yes! I installed the beta add-on for Firefox and the error is gone. :-)
That is a relief! Thank you

By the way: This page here shows several errors in the Console ... but, apparently, none of them is caused by my 1Password beta add-on ... ;-)

mmaass, kwyld, nciiis, dilenio

I'm sorry that the issue is affecting your workflows, our team is aware of the impact to customers and a fix has been developed and is currently being tested before it's included in a future update to the stable version of 1Password in the browser.

If you're willing, please try the beta version and let me know if you still see the issue there: Install a beta release of the 1Password browser extension

-Dave

prathers :

I'm amazed by the number of people complaining about this.
Does anyone give the devs a chance? Or read the posts above their own?

When it comes to support for a widely used piece of software, things are often prioritized based on user satisfaction. User dissatisfaction == less $$$. Without evidence of dis/satisfaction, it's a guess.

While ultimately this is a trivial bug (a missing icon), this thread is abundant evidence that the way the error presents is interrupting 1P's customers' work in various ways. What may have, at first, been considered a low-priority bug now has all this evidence 1P Support can bring to 1P Devs to boost its priority.

On one hand, I understand your call for "giving the devs a chance". Though, many of us here are kindly requesting updates on this.

On the other hand, 1Password is a security tool, and a bug that presents as an error being left this long, especially one that appears to require a simple fix (reference the icon properly), is not a good look for a security tool. Errors in password management software, no matter how trivial they may be or appear, are anxiety-inducing, and validly IMO.