tinyhumansai/openhuman · error
Unsupported auth profile schema version {} (max supported: {
Error message
Unsupported auth profile schema version {} (max supported: {}) What it means
Raised while loading the persisted auth-profile store when its schema_version is newer than the maximum this build supports (CURorent max). It means the profiles file was written by a newer OpenHuman version; the loader refuses to interpret unknown schema rather than misreading or dropping credentials.
Source
Thrown at src/openhuman/security/credentials/profiles.rs:999
.file_name()
.and_then(|s| s.to_str())
.unwrap_or("auth-profiles.corrupt");
tracing::warn!(
path_file = PROFILES_FILENAME,
quarantined_file = quarantined_file,
error = %err,
"[credentials] auth profile store unparseable; quarantined and reset to empty"
);
return Ok(PersistedAuthProfiles::default());
}
};
if persisted.schema_version == 0 {
persisted.schema_version = CURRENT_SCHEMA_VERSION;
}
if persisted.schema_version > CURRENT_SCHEMA_VERSION {
anyhow::bail!(
"Unsupported auth profile schema version {} (max supported: {})",
persisted.schema_version,
CURRENT_SCHEMA_VERSION
);
}
Ok(persisted)
}
fn write_persisted_locked(&self, persisted: &PersistedAuthProfiles) -> Result<()> {
if let Some(parent) = self.path.parent() {
fs::create_dir_all(parent).with_context(|| {
format!(
"Failed to create auth profile directory at {}",
parent.display()
)
})?;
}View on GitHub (pinned to 7491200858)
Solutions
- Upgrade OpenHuman to a build that supports the newer schema version.
- Restore a profiles file from a backup taken with a compatible version.
- If downgrade is intentional, re-authenticate to rebuild the store in the old format.
Defensive patterns
Strategy: validation
When it happens
Trigger: Thrown at src/openhuman/security/credentials/profiles.rs:999 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of tinyhumansai/openhuman@7491200858 (2026-08-17).
Data as JSON: /api/errors/ed32f70d9a95ea6b.
Report an issue: GitHub.