Skip to main content
snozdop
March 22, 2024
Question

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

  • March 22, 2024
  • 56 replies
  • 22781 views

Using Safari Extension v2.22.1 (22200103) beta I get the following console error on every page load from the injected.js:


Retrieving "b5x-stateful-inline-icon" flag errored: timed out - falling back

clicking the error highlights line 19578 of injected.js


1Password Version: 8.10.30
Extension Version: 2.22.1
OS Version: macOS 14.4
Browser: Safari 17.4

56 replies

Roenfeldt
April 4, 2024

Identical situation here to @mmaass above. Any word on the update/fix?

1P_Dave
1Password Employee
April 4, 2024

@mmaass and @Roenfeldt

Thank you for the reports and I'm sorry for the trouble. The team hopes to get this fixed as soon as possible and you'll see the fix noted in our release note when it's available: 1Password Releases

-Dave

April 4, 2024

Same in Firefox 124.0.1 (64-bit)

mmaass
April 4, 2024

Thank you for the confirmation, Dave_1P
Good to know the issue has been identified. So I am not imagining things ... ;-)
I am sure it will be solved.

1P_Tommy
1Password Employee
April 5, 2024

On behalf of Dave, you're welcome.

April 6, 2024

Me too - same in safari 17.4.1

Roenfeldt
April 8, 2024

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!

1P_Dave
1Password Employee
April 8, 2024

@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

Roenfeldt
April 8, 2024

@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! :)

April 9, 2024

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.