Xcode archive fails with errSecInternalComponent while signing a framework

I’m archiving an iOS app in Xcode 27.2 on my Mac, using Xcode’s GUI and Automatically manage signing. The archive fails during the [CP] Embed Pods Frameworks build phase, when codesign signs CapacitorAppLauncher.framework, with errSecInternalComponent.

Keychain Access shows my Apple Development certificate and its associated private key in the login keychain. I’m signed in to the Mac locally; this is not an SSH or CI build. Changing the Mac login password did not resolve the issue. I have not revoked or changed the Apple Distribution certificate.

What safe diagnostics can distinguish a login-keychain unlock problem, a private-key access-control issue, an untrusted certificate, or another cause? Is there a recommended GUI-session test to determine whether codesign can use the identity independently of the Xcode archive build?

I can provide redacted Xcode and system details if needed. I will not post passwords, private keys, account identifiers, or unredacted keychain screenshots.

Update: I followed the suggested test from Terminal.app in the logged-in GUI session. Signing a copy of /usr/bin/true fails with errSecInternalComponent for both active Apple Development identities.

The Xcode archive log selects one of those identities. It signs several Capacitor frameworks successfully, then fails while signing CapacitorBrowser.framework with errSecInternalComponent.

Keychain Access shows both active private keys with access allowed to all applications. Both user and admin trust-settings checks report that no trust settings were found. Xcode Manage Certificates shows two active Apple Development certificates and one previously revoked certificate.

A Keychain Access hang report also shows a prolonged stall in SecKeychainItemSetAccess while changing a key’s ACL. I don’t know whether that is related to the current signing failure.

Environment: macOS 27.2.1, Xcode 27.2. I have not revoked or replaced either active certificate during this investigation.

Given that the standalone signing test fails for both identities, what would you recommend as the next diagnostic step to distinguish a keychain/user issue from a system-wide issue?