Passkeys not working on Nintendo.com in Firefox

Created a passkey in 1password w ith firefox, can not authenticate with it. I opened Chrome and it's able to login just fine. So the issue is still present on firefox

OS: Tahoe 26.4.1
Browser: 
Firefox 149.0.2
Chrome 147.0.7727.102
1Password for Mac 8.12.10 (81210036)

Just confirming in January 2026 that this is still a problem. Firefox cannot successfully use the passkey on nintendo.com. The same passkey works fine for both login and purchase authentication when using the Edge browser. 

• Windows 11
  • Edition: Windows 11 Pro
  • Version: 25H2
  • OS Build: 26200.7623
  • Experience: 1000.26100.275.0
• Firefox: 147.0.1 64-bit
• Edge: 144.0.3719.82
• 1password extension: 8.11.27.2
• 1password: 81200013 production channel

1P_Evon​ I ran into this issue as well yesterday. I'd previously created a passkey for this account back in September 2023, and as far as I recall, the passkey worked then. I always do a test sign in after creating a passkey, that's why I'm quite sure that it worked when I created it.

Yesterday, I tried signing in with the passkey and ran into the same issue as everybody else is mentioning in this thread. I deleted the passkey and created a new one, but the issue remains.

This is in Firefox. I'll sign in with username and password while waiting for a fix for this issue.

11 months later and Passkey's still don't work to authenticate with Nintendo on Firefox.

 - I have not noticed this on other pages
 - Pass key prompt appears, clicking it makes Nintendo's webpage display an error within the webpage.
 - Just the in-page error.
 - Works in Safari.  Don't have Chrome.  (Want to use Firefox.)

I've also experienced a persistent passkey failure on Nintendo.com on Mac, and see it consistently in Safari, Firefox, and Chrome. Firefox fails to login at all, but Chrome and Safari pass regular login and fail only on the "reauthenticate" page when confirming a purchase. reauthenticate also fails in Safari on iOS. All seem to fail with an invalid character error. 

• Are you running into this problem on any other websites?

No, only Nintendo.com so far. Has been consistently failing for at least a month or two.

• Does the 1Password passkey prompt appear when you navigate to Nintendo's sign-in page?

Yes, for the regular login page, all browsers. In Safari and Chrome, the reauthenticate page doesn't show a prompt, only an error.

• Do you receive any error messages?

 The error in the js console in Firefox:

[Exception... "Component returned failure code: 0x80070057 (NS_ERROR_ILLEGAL_VALUE) [nsIDOMWindowUtils.addSheet]" nsresult: "0x80070057 (NS_ERROR_ILLEGAL_VALUE)" location: "JS frame :: resource://gre/modules/ExtensionCommon.sys.mjs :: runSafeSyncWithoutClone :: line 70" data: no] 5 ExtensionCommon.sys.mjs:70:12 runSafeSyncWithoutClone resource://gre/modules/ExtensionCommon.sys.mjs:70 inject resource://gre/modules/ExtensionContent.sys.mjs:646 injectInto resource://gre/modules/ExtensionContent.sys.mjs:519 executeInWin resource://gre/modules/ExtensionContent.sys.mjs:1481 map self-hosted:175 handleActorExecute resource://gre/modules/ExtensionContent.sys.mjs:1486 AsyncFunctionNext self-hosted:800

• Could you check whether the problem occurs in a different browser?

Firefox cannot login at all, while Safari, Chrome, and iOS Safari can login with a passkey. However, all 3 of those fail at the "reauthenticate" page when clicking a purchase button, with similar Invalid Character errors:

In Safari:

InvalidCharacterError: The string contains invalid characters. atob D — common.js:2:2437483 (anonymous function) — common.js:2:2423428 map (anonymous function) — common.js:2:2423396

and Chrome:

common.js?t=1754983712:340 InvalidCharacterError: Failed to execute 'atob' on 'Window': The string to be decoded is not correctly encoded. at D (common.js?t=1754983712:2:2437478) at common.js?t=1754983712:2:2423427 at Array.map (<anonymous>) at e.convertFromOptionResponse (common.js?t=1754983712:2:2423392) at common.js?t=1754983712:2:2422598 at d (common.js?t=1754983712:335:33027) at Generator._invoke (common.js?t=1754983712:335:32815) at Generator.next (common.js?t=1754983712:335:33452) at l (common.js?t=1754983712:2:2416868) at o (common.js?t=1754983712:2:2417071)

Notably, this page does not show a 1password passkey prompt, only an error.

Not sure if useful: passkey from Apple Passwords works fine in Safari on the pages where 1password fails.

Info:

• OS: macOS 15.6
• Safari: 18.6
• Firefox: 141.0.3
• Chrome: 139.0.7258.128
• 1password: 8.11.4
• 1password for Safari: 8.10.82
• 1password for Chrome: 8.11.4.27
• 1password for Firefox: 8.11.4.27

Any update on this 1P_Evon​ ? I have the same problem as OP.

You're welcome, idkicarus. Thank you for sharing the open bug report!

Let me know if there's anything else I can assist you with. 🙂

-Evon

Thanks for logging the issue, 1P_Evon. If it helps, I stumbled across an open bug report for Firefox from another user who is having trouble with passkeys for Nintendo: https://bugzilla.mozilla.org/show_bug.cgi?id=1870436.

idkicarus,

Thank you for your reply. Based on the details, you are running into the same issue. I've added you as an affected user to the reporting I filed. In the meantime, I recommend signing in with your username and password on Firefox. I apologize for the inconvenience.

Let me know if you have any questions.

-Evon

Thanks for the reply.

• No, I haven't run into this issue with any other websites where I use passkeys.
• Yes, the 1Password passkey prompt appears for me on Nintendo's sign-in page on both mobile and desktop.
• I don't get an error message from 1Password after a failed login via passkey. However, Nintendo's site displays the following message: "Couldn't complete passkey sign-in. Please use password sign-in instead. Tap on Can't use passkey sign-in? for details."
• I checked Chrome on mobile and desktop and the passkey works as intended. Regardless of which device creates the passkey, any device with 1Password installed is able to use the passkey to sign in.

On a side note, even with every extension besides 1Password disabled in Firefox, the passkey login still fails, so it doesn't seem another extension is interfering with the login process.