App fails to launch on macOS 26.3 beta - "Launchd job spawn failed" (error 163)

[zetsuchan]

Description:

Environment

• RepoBar version: 0.2.0
• macOS version: 26.3 (Build 25D5101c) - Tahoe beta
• Architecture: Apple Silicon (arm64)

Problem

RepoBar fails to launch with the generic "The application 'RepoBar' can't be opened" dialog.

Diagnostics

The app is properly signed and notarized:
spctl -a -t exec -vv /Applications/RepoBar.app
/Applications/RepoBar.app: accepted
source=Notarized Developer ID

Launching via open -a RepoBar reveals the actual error:
error=Error Domain=RBSRequestErrorDomain Code=5 "Launch failed."
UserInfo={NSLocalizedFailureReason=Launch failed.,
NSUnderlyingError=0xbef014a50 {Error Domain=NSPOSIXErrorDomain Code=163
"Unknown error: 163" UserInfo={NSLocalizedDescription=Launchd job spawn failed}}}

Attempted fixes (did not help)

• xattr -cr /Applications/RepoBar.app
• Right-click → Open
• Re-extracting the ZIP

Notes

This may be a macOS 26.3 beta regression. The app was built with SDK 26.2.0. Happy to provide
additional logs or test builds

[objectiveous]

RepoBar fails to launch on macOS 26 beta - AMFI code signature rejection

Environment:

• macOS: 26.3 (25D5101c)
• Hardware: MacBook Air M4, 32GB RAM
• RepoBar: 0.2.0
• Xcode: 26.0 (17A5241e)

Issue:
RepoBar fails to launch with AMFI code signature validation error. The app is properly signed with Developer ID and notarized, but macOS 26
rejects it due to "no eligible provisioning profiles found."

Console errors:
taskgated-helper: Disallowing com.steipete.repobar because no eligible provisioning profiles found
amfid: AppleMobileFileIntegrityError Code=-413 "No matching profile found"
AMFI: Code has restricted entitlements, but the validation of its code signature failed.

Analysis:
The app uses keychain-access-groups entitlement (Y5PE65HELJ.com.steipete.repobar.shared) which requires a provisioning profile. This worked
on macOS 15 but fails on macOS 26 beta.

Signature info:

• Authority: Developer ID Application: Peter Steinberger (Y5PE65HELJ)
• Notarization: Stapled
• Runtime Version: 26.2.0

Likely cause:
Either macOS 26 has stricter provisioning profile requirements, or the embedded profile needs to be regenerated for macOS 26 compatibility.

---

This appears to be either:

1. A macOS 26 beta regression in AMFI profile validation
2. The app needs a new provisioning profile generated against macOS 26 SDK

Peter Steinberger (the developer) would need to re-export the provisioning profile from Apple Developer portal and re-sign the app.