What OSStatus Error 47 Means
OSStatus error 47 is a macOS and iOS system error code indicating a security or authorization failure. In Apple frameworks, OSStatus values represent the result of operations, where error 47 corresponds to errSecAuthFailed. This status typically surfaces when an app or process cannot prove the required authentication context to access protected resources such as keychain items, secure preferences, or file system items protected by Access Control Lists (ACLs). It is a verifiable system-level response rather than an application-specific message, and it belongs to the Security and Common Error status domain used across Apple platforms.
Core Technical Context
OSStatus is a signed 32-bit integer used across Apple’s CoreFoundation, Security, and Application Services APIs to communicate operation results. Each code maps to a four-character code and a numeric value; error 47 maps to the symbolic constant errSecAuthFailed. This error belongs to the Common and Security status families and is not tied to a single product version, making it an enduring interface behavior that developers should handle through robust authentication, credential verification, and user prompts rather than treating it as a transient glitch.
Primary Causes of OSStatus 47
The most common triggers involve missing or invalid credentials when accessing protected data. In keychain scenarios, a mismatch between requested access rights and stored item access rules produces this result. File system operations may encounter error 47 when an item has ACLs or extended attributes that deny the current user or process, even if the user owns the file. Other causes include incorrect keychain access groups, absent or revoked certificates in authentication dialogs, sandbox restrictions, and expired or improperly installed user or developer certificates.
Scenario Breakdown by Platform Context
| Platform/Context | Verified Detail | Source Type |
|---|---|---|
| macOS keychain access | errSecAuthFailed when access control or user authentication fails | Apple Security framework reference |
| File operations with ACLs | Operation not permitted due to ACL or ownership mismatch | POSIX and HFS+/APFS behavior |
| Sandboxed apps | Entitlement or container permission mismatch | App Sandbox design |
| Code signing and auth | Invalid or expired certificate/identity assertion | Code Signing and Trust Evaluation |
How to Diagnose OSStatus 47 on macOS
Diagnosis begins by reproducing the action and noting the exact context: which API, file, keychain item, or system function triggered the failure. Consult the system console for related messages, inspect the keychain access UI for denied prompts, and verify that the calling process holds the required entitlements or file permissions. Use command-line tools to review ACLs and ownership, and verify code signing identities to narrow the cause. These steps form a repeatable methodology to isolate whether the issue is credential, configuration, or entitlement related.
Diagnostic Checklist
- Reproduce the operation and capture surrounding logs
- Check Console.app for Security and system messages
- Confirm keychain item access controls and sharing settings
- Verify file ownership and ACLs with ls -le or xattr
- Ensure app sandbox entitlements match required access
- Validate code signing identities and trust settings
Verified Fixes and Remediation Paths
Resolution depends on the root cause. For keychain issues, ensure the keychain is unlocked, the item’s access control matches the requesting app, and any access groups are correctly set. For file system problems, correct ownership and ACLs using chown and chmod utilities or the Get Info panel. In sandboxed apps, confirm that entitlements and container permissions allow the requested operation. For certificate-based auth, reinstall or reissue the relevant identity. Always back up sensitive data before making permission changes, and test changes in a non-production environment when possible.
Resolution Workflow
- Identify the operation and OSStatus 47 context from logs
- Check keychain access controls and user prompts
- Inspect file ownership, ACLs, and extended attributes
- Review entitlements and sandbox settings for sandboxed apps
- Verify code signing certificates and trust settings
- Apply corrective permissions or reissue credentials as needed
Prevention and Best Practices
Reduce the likelihood of errSecAuthFailed by designing apps to request access only when needed, handling user prompts gracefully, and clearly communicating why elevated permissions are required. Use standard Apple APIs for keychain and file access, and validate entitlements during development. Keep system certificates and identities up to date, and test permission changes on a development machine before deploying widely. These practices improve reliability and reduce user-facing authentication failures across OS versions.
FAQ
Reader questions
Is OSStatus error 47 a virus or malware indicator?
No, error 47 is a standard OSStatus code for authentication failure and does not itself indicate malware. However, unexpected occurrences may warrant a full security check if they follow suspicious activities.
Can third-party security tools interfere and cause error 47?
Yes, some endpoint protection or parental control tools can modify access rules or inject policy checks that trigger auth failures; consider temporary exclusion testing if the behavior started after installing such software.
Does this error only happen on macOS or also on iOS?
It can occur on both platforms when an app or system component fails to satisfy the required authentication or authorization checks, though user-facing frequency is lower on iOS due to stricter app sandboxing and controlled prompts.
Should I reset my keychain to fix OSStatus 47?
Not as a first step; targeted actions like unlocking the keychain, ensuring correct sharing settings, and repairing permissions usually suffice. A keychain reset is a more invasive step that should be considered only after other methods fail and after proper backups.
Are there known macOS versions where errSecAuthFailed is more common?
No specific version is universally associated with high rates of this status; it is tied to app configurations, permissions, and user workflows rather than OS releases, though behavior can evolve with major security updates.
When should I contact Apple Support regarding this error?
Contact Apple Support if the error persists after verifying permissions, entitlements, and certificates, especially when built-in macOS apps are affected or when remediation steps lead to broader system issues.