Skip to main content

Troubleshoot partial extension compatibility

An extension can verify, install, and start while one optional feature reaches a Chrome-only API. Crest reports what it can observe without treating one error as proof that every extension feature failed.

Read the status first​

  • Running means the enabled WebKit context loaded without an observed runtime error. It does not certify every workflow.
  • Needs attention means the context failed to load or reported a runtime problem. Expand the row for Crest's plain-language explanation.
  • Blocked means Crest identified an unsafe or unavailable requirement before installation.
  • Off keeps the installation and Space-local configuration but does not run it.

Try the smallest recovery​

  1. Open Crest Settings → Extensions.
  2. Choose the Space and device where the problem occurs.
  3. Expand the extension and read the status explanation.
  4. Turn the extension off and back on.
  5. Update or reinstall the signed Chrome Web Store package.
  6. Review Permissions and Website Access for a blocked rule.
  7. Open the extension's Options page when it provides one and review feature-specific settings.

Read Technical Details without overgeneralizing​

Open Technical Details to see the JavaScript errors and unsupported APIs reported by WebKit. Include those details, the extension version, Crest build, Space, device, and failing workflow in a bug report.

Common measured limitations include notification-click events, managed storage, isolated scripting execution worlds, and tabs.onUpdated registration. Another feature in the same extension may still work.

Check the native-companion boundary​

If the extension needs a desktop app, confirm you are using Crest Direct and a verified Chrome Web Store package. App Store Crest cannot launch companion helpers, unpacked extensions are ineligible, and a Safari app's native handler is not portable.

See Direct build, App Store, and native companions and the current compatibility matrix.