Skip to main content
Sep 22, 2026 10:52 AM UTC
Question

Firefox: related-origin passkeys silently fall back to the browser (FetcherError in related-origins-fetcher)

Setup

Firefox 155.0.1 on Linux, 1Password in the browser 8.12.32.33 (current AMO build). Firefox on any OS is affected. Chrome is not.

Symptom

On a site that uses WebAuthn related origins, 1Password takes over navigator.credentials.get() and then hands it back to Firefox without showing anything. The user gets Firefox's native prompt; on Linux that is only "Touch your security key". Our case: page origin https://app.example.com, rpId auth.example.com, https://auth.example.com/.well-known/webauthn served with 200, application/json, access-control-allow-origin: *, and https://app.example.com listed in origins.

Background console:

[Webauthn] Failed to core.webAuthnRPValidate: ⛔ Core error code: {"type":"FetcherError"}
[Webauthn] Failed to _handleGetCredential: bad-rp-id
[Webauthn] Failed to _handleGetCredential while unlocked: bad-rp-id

No Related-origins fetch failed warning is logged.

Cause

background/webauthn/related-origins-fetcher.ts, around lines 75 to 87. The fetcher wraps the content-script fetch in a DNR session rule:

await chrome.declarativeNetRequest.updateSessionRules({ addRules: [rule] });
try { return await fetchViaContentScript(url); }
finally { await chrome.declarativeNetRequest.updateSessionRules({ removeRuleIds: [id] }).catch(warn); }

In Firefox, the MV2 chrome.* namespace is callback-only and returns undefined for these calls. The await on the add call passes, the fetch succeeds, then the finally block does .catch on undefined:

TypeError: can't access property "catch", t.updateSessionRules(...) is undefined

That rejection replaces the successful result. Core maps it to FetcherError, the sign-in handler maps that to bad-rp-id, and the page shim falls back to the browser. The only warning in that path is inside the .catch that never runs.

Verified separately: the content-script fetch returns the document (200, application/json), and browser.declarativeNetRequest.updateSessionRules accepts the same rule.

Repro (temporary add-on via about:debugging)

manifest.json:

{ "manifest_version": 2, "name": "dnr-repro", "version": "0.1",
"permissions": ["<all_urls>", "declarativeNetRequestWithHostAccess"],
"background": { "scripts": ["bg.js"] } }

bg.js:

const rule = { id: 1, priority: 1,
action: { type: "modifyHeaders", requestHeaders: [{ header: "sec-fetch-site", operation: "set", value: "none" }] },
condition: { requestDomains: ["auth.example.com"], urlFilter: "/.well-known/webauthn", resourceTypes: ["xmlhttprequest"] } };

console.log(typeof chrome.declarativeNetRequest.updateSessionRules({ addRules: [rule] }));
// Firefox: "undefined" Chrome: "object"

browser.declarativeNetRequest.updateSessionRules({ removeRuleIds: [1] })
.then(() => console.log("browser.* returns a promise and accepts the rule"));

Fix

Use browser.declarativeNetRequest (or the polyfill) in the fetcher, or guard the return value before calling .catch.

Impact

Every related-origin site, get and create, Firefox only. Because the fallback is silent, users read it as "1Password did not show up" and blame the site or Firefox.

5 replies

1P_ChrisBurgin
1Password Employee
1Password Employee
Sep 28, 2026 6:40 PM UTC

​@thunkar Thanks for reporting this! I am a developer on the browser extension team. I wanted to let you know that we just merged a fix for this and it should be available in the next release.

 

Please do reach out if you have any other issues!

Oct 6, 2026 1:46 PM UTC

I’m also affected on macOS with Firefox 157.0 and 1Password extension 8.12.32.33 (1Password for Mac 8.12.40). Passkey sign-in to my Microsoft work account fails with “1Password encountered a problem.” It used to work, and restarting the Mac didn’t help.

 

Local diagnostics reproduced the same FetcherError and bad-rp-id errors described here. Thanks for confirming that a fix has been merged. Is there an ETA or version number for the stable Firefox extension release containing the fix?

1P_ChrisBurgin
1Password Employee
1Password Employee
Oct 6, 2026 1:59 PM UTC

​@higordeus22 Thanks for the extra info! 

The fix will go out with 8.12.42, which will ship later this month. The exact day varies as Mozilla has to review each new release.

The beta hasn’t been shipped yet but it should in the next several days, pending any issues. If you want you can install the beta channel of the extension at the link below and you should get the update as soon as its released. Just note that if you do install the beta you will stay on the beta channel until you reinstall the stable release from the Mozilla add-on store.

 

https://support.1password.com/betas/?mac#install-a-prerelease-version-of-the-1password-browser-extension

 

I’ll keep an eye on this thread. Let me know if you still have problems after the 8.12.42 update!

 

thunkarAuthor
Sep 28, 2026 8:08 PM UTC

​@1P_ChrisBurgin Awesome, thanks for the quick fix!