[RESOLVED] [Incident] Browser extension fails to initialize after sign-out on Chrome 147

Announcements
1

We are investigating an issue where the Passbolt browser extension does not start when navigating to the Passbolt API URL after signing out. This issue has been confirmed on Chrome 147.

The issue is reproducible across browser extension versions 5.10 and 5.11 and does not appear to be related to a specific extension version.

Workaround: Toggling the extension off and on, or restarting the browser, resolves the issue temporarily.

Our engineering team is actively investigating the root cause. We will keep you informed with further updates as we progress.

1 Like
3

Hi everyone,

Update on this issue.

tldr; We’ve identified the root cause and a fix is on its way. Chrome/Edge extensions (in review) & API should be available on 9th morning.

Chromium 147 introduced a change in how it handles page caching (BFCache) that affects the browser extension. The impact turned out to be broader than the sign out scenario initially reported, it can also cause the extension to become unresponsive when navigating within the application, especially in the administration workspace.

Because the issue surfaces in different ways, we’ve addressed it on two fronts:

The browser extension 5.11.1 is currently in review on the store and will be available shortly. On its own, it fully fixes the sign out issue and should resolve the navigation issues for most users. If you can’t update the API right away, the extension update alone still ensures you retain access to your credentials.

The API 5.11.0 will be available on April 9th. Because Chrome is rolling out this BFCache change progressively, some users may still experience navigation issues with the extension update alone. Updating the API completes the fix and covers all cases.

Please let us know in this thread if you’re still experiencing issues after updating.

Thank you to everyone who reported the problem and helped us investigate.

1 Like
Account recovery email is sent at each login
4

Hi everyone,

The incident is now resolved. The fix is included in browser extension 5.11.1, which is live on the Chrome, and Edge stores. The extension should update automatically, but if you’re still experiencing the issue, make sure you’re running the latest version. If the problem persists after updating the extension, the API 5.11.0 is also available and fully resolves it.

If you’re still running into issues after updating both, don’t hesitate to let us know in this thread.

2 Likes
5

@cedric Would you mind please sharing more about this fix? Our organization is experiencing the same problem in our Chrome Extension.

Pasting the diff if it is small would be beneficial to others finding this via search engines.

6

Hello,

Here is our bug report to chrome, describes where the problem lies:

The one being worked on by Chrome that rollback the changes

Not sure if our solution that applies exactly to everyone, but there you go:

3 Likes