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

2passwords

Thank you for the report. Please see my post here for the latest update. I'm sorry for the noise.

-Dave

Also seeing this on the stable channel, latest Chrome.

Looking forward to an official fix... the error is popping up everywhere.

happycappie

Thank you for reporting the issue as well, hopefully a fix will make it to the beta and stable versions soon.

-Dave

ref: dev/core/core#28962

Yes we are also seeing it in stable versions across a range of browsers. It's pretty much on every web page including cnn.com :)

PaidUser0011 and hcreative

I'm sorry for the noise and for disruption to your workflows. A fix is being tested in the nightly version of 1Password in the browser and the team hopes to release the fix to the beta and stable versions as soon as possible.

-Dave

I can confirm as well. Chrome Version 123.0.x. Deactivating and reactivating the extension confirms the error is related to the OnePassword Chrome extension.

Retrieving "b5x-stateful-inline-icon" flag errored: timed out - falling back
injected.js:4

Looking forward to the update. Thank you.

This caused me a little lost time in the browser console today as well!

Was wondering what injected.js was (common for hot module reloading and other tooling) and needed to track it down.

Was suprised to see this was caused by 1Password which I expect to be always very polished as it's dealing with some very critical data.

1P_Dave thank you so much for the fast reply and for the details provided, they're much appreciated! I'll be looking forward to the fix, and please send my kind regards and thanks to the dev team! :)

Roenfeldt

I'm sorry that the issue is causing disruption to your workflow. Our developers have finished coding a fix for the issue and are currently testing that fix in the nightly version  of 1Password in the browser.

Once the team's testing verifies that the fix fully resolves the issue, and doesn't introduce new issues, the fix will make it's way into future updates to the beta and then stable versions. Thank you for your patience.

-Dave

I am aware of the fact that the dev team are working hard on fixing this issue, but I would appreciate an update on their progress, or at least an estimate on how long this is going to take until it gets fixed, because I'm a web developer, and this annoying error message keeps on polluting my browsers' consoles, even on the very well optimized local projects I'm working on, thus heavily disrupting my workflow. Thank you!