Skip to content

fix: prevent failed signing artifacts from entering Signed - #720

Closed
mvanhorn wants to merge 1 commit into
claration:mainfrom
mvanhorn:fix/704-feather-signing-failure-persistence
Closed

mvanhorn wants to merge 1 commit into
claration:mainfrom
mvanhorn:fix/704-feather-signing-failure-persistence

Conversation

@mvanhorn

Copy link
Copy Markdown

Move the existing handler.hadError check in SigningHandler.modify() immediately before move() and addToDatabase(), after the signing-option branch, so any recorded signing failure throws before either persistence operation. Issue #704 reports that custom-entitlement signing can fail inside zsign while Feather saves an invalid app as signed; the stated acceptable outcome includes reporting the signing failure.

On the pre-fix revision, stop in SigningHandler.modify() immediately before move(), set handler.hadError to SigningFileHandlerError.signFailed, and continue: verify that an error is reported but a new Signed directory and database record are incorrectly created. Repeat after the fix with the breakpoint before the relocated error check: require an error, no new Signed directory or record, temporary work-directory cleanup, and retention of the imported source. Use a disposable app/certificate and record baseline directory and library contents before each run; Repeat the failure case with automatic installation and delete-source-after-sign enabled: neither success action may run. Previously signed unrelated apps must remain intact.

Fixes #704

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

2 participants