为何在Safari中注册WebAuthn凭证时会返回"The operation cannot be completed"错误？

I’ve run into this exact Safari-specific WebAuthn issue a few times, and it almost always boils down to Safari being stricter about adhering to the WebAuthn spec than other browsers. Let’s break down the most common causes and fixes to get your registration flow working:

Common Causes & Fixes #

1. Invalid Relying Party (RP) ID #

Safari has zero tolerance for RP ID mismatches or invalid formats—this is the #1 culprit I see. Make sure your rp.id meets these rules:

• It must be a registered domain suffix of your page’s URL. For example, if your app runs on app.yourdomain.com, valid RP IDs are yourdomain.com or app.yourdomain.com—but not sub.app.yourdomain.com.
• IP addresses aren’t allowed; use a proper domain name.
• Drop any port numbers (even if your local dev server uses :3000, the RP ID should omit it).

Check your request payload to fix this:

// Correct example for app.yourdomain.com
const publicKeyOptions = {
  rp: {
    id: "app.yourdomain.com",
    name: "Your Application"
  },
  // Rest of your options...
};

2. Overly Strict userVerification Setting #

If you’ve set userVerification: "required" but the user’s device doesn’t support mandatory verification (e.g., a security key without a PIN), Safari will throw this error immediately. Try loosening it to preferred or discouraged first to test:

const publicKeyOptions = {
  // Rest of your options...
  userVerification: "preferred", // Swap this for "required" to debug
  // Rest of your options...
};

3. HTTPS is Non-Negotiable (Even Locally) #

Unlike Chrome, Safari won’t let WebAuthn run over plain HTTP—even for localhost. You’ll need to set up HTTPS for local development:

• Generate a self-signed SSL certificate and add it to Safari’s trusted certificates list.
• Use tools that auto-provision local HTTPS to avoid manual setup headaches.

4. Attestation Conveyance Preference Conflicts #

Setting attestation: "direct" can cause issues on Safari if the user’s authenticator doesn’t support returning direct attestation data. Try switching to none or indirect to bypass this:

const publicKeyOptions = {
  // Rest of your options...
  attestation: "none",
  // Rest of your options...
};

5. Outdated Safari Version #

Older Safari builds (pre-15.4) have known WebAuthn bugs that cause vague errors like this. Ensure both you and your users are running the latest stable version of Safari.

Debugging Pro Tips #

• Open Safari’s Dev Tools (Cmd + Opt + I), go to the Console tab, and look for hidden error logs—sometimes Safari will spit out a more specific message about what’s wrong (even if the modal only shows the generic "cannot be completed" text).
• Use Safari’s built-in WebAuthn simulator (under Dev Tools > More Tools > WebAuthn) to test your request parameters without a physical device.

Final Check #

If none of the above works, cross-reference your publicKey request against the official WebAuthn spec. Safari is a stickler for spec compliance, so a tiny parameter oversight that Chrome ignores will break things here.

内容的提问来源于stack exchange，提问作者Logan Carmody