BroadcastChannel Channel is closed errors after upgrading okta-auth-js to 6.4.0 (fixed in 6.7)

TL;DR

Nothing in the app had changed besides the SDK version bump, which pointed at the 6.4.0 release itself. Fixed in @okta/okta-auth-js 6.7.0; the reporter confirmed upgrading to 6.7.0 removed the BroadcastChannel errors.

Steps

1. Fixed in @okta/okta-auth-js 6.7.0; the reporter confirmed upgrading to 6.7.0 removed the BroadcastChannel errors. Upgrade past 6.7. The Okta team also recommends reading tokens from the tokenManager directly rather than authState, as they observed related token staleness issues around the same upgrade.

When to use

You are seeing this: Upgrading an Angular app from @okta/okta-auth-js 6.2.0 to 6.4.0 produced Unhandled Promise rejection: Failed to execute 'postMessage' on 'BroadcastChannel': Channel is closed during npm test (and in the console at runtime). Use this skill when you run into "BroadcastChannel Channel is closed errors after upgrading okta-auth-js to 6.4.0 (fixed in 6.7)".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: oktaokta-auth-js 6.2.0, 6.4.0, oktaokta-auth-js 6.7.0. If you are on something much newer or older, the details may have shifted.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Sources

• https://github.com/okta/okta-auth-js/issues/1174

Someone asked: Upgrading an Angular app from @okta/okta-auth-js 6.2.0 to 6.4.0 produced Unhandled Promise rejection: Failed to execute 'postMessage' on 'BroadcastChannel': Channel is closed during npm test (and in the console at runtime). The SDK's cross-tab communication channel was being used after it was closed. Nothing in the app had changed besides the SDK version bump, which pointed at the 6.4.0 release itself. The verified resolution: Fixed in @okta/okta-auth-js 6.7.0; the reporter confirmed upgrading to 6.7.0 removed the BroadcastChannel errors. Upgrade past 6.7. The Okta team also recommends reading tokens from the tokenManager directly rather than authState, as they observed related token staleness issues around the same upgrade. Thread: https://vectle.com/threads/thrVThhxNRrN2E6vKBvGp_2Q