DioxusLabs/dioxus · error · anyhow::Error
No valid signing identity found in keychain {}. Output: {}
Error message
No valid signing identity found in keychain {}.
Output: {} What it means
Raised by find_identity_in_keychain during macOS code-signing setup (called from setup_keychain) when the `security find-identity` command succeeds but its output yields no parsable signing identity: no quoted identity name between double quotes and no whitespace-delimited second token of 40 hex characters (a SHA-1 fingerprint). This means the keychain named in the message contains no valid 'Developer ID' or 'Apple Development' certificate, so signing cannot proceed and the input at fault is the keychain's certificate contents.
Source
Thrown at packages/cli/src/bundler/macos.rs:797
if line.starts_with("1)")
|| line.contains("Developer ID")
|| line.contains("Apple Development")
{
if let Some(start) = line.find('"') {
if let Some(end) = line.rfind('"') {
if end > start {
return Ok(line[start + 1..end].to_string());
}
}
}
let parts: Vec<&str> = line.split_whitespace().collect();
if parts.len() >= 2 && parts[1].len() == 40 {
return Ok(parts[1].to_string());
}
}
}
bail!(
"No valid signing identity found in keychain {}.\nOutput: {}",
keychain_path.display(),
stdout
)
}
/// Sign a list of paths with the given identity.
async fn sign_paths(
identity: &SigningIdentity,
targets: Vec<SignTarget>,
settings: &MacOsSettings,
) -> Result<()> {
for target in &targets {
sign_path(identity, target, settings).await?;
}
Ok(())
}
View on GitHub (pinned to 24f6a829df)
Solutions
- No valid signing identity exists in the keychain. Install a Developer ID certificate and retry.
Defensive patterns
Strategy: validation
When it happens
Trigger: Thrown at packages/cli/src/bundler/macos.rs:797 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of DioxusLabs/dioxus@24f6a829df (2026-08-23).
Data as JSON: /api/errors/ecb7f850c61c369d.
Report an issue: GitHub.