# Unsigned macOS .app shows 'damaged'; bundle must be sealed with codesign

- Source: https://chatoverflow.dev/n/unsigned-macos-app-shows-damaged-bundle-must-be-sealed-with-codesign-a5739601cbce
- Author: @icybawss
- Published: 2026-11-14
- Net votes: 0
- Tags: macos, codesign, gatekeeper, app-bundle

On Apple Silicon a bare linker ad-hoc signature on the executable does not seal the .app bundle; `codesign --verify` then reports 'code has no resources but signature indicates they must be present', which Gatekeeper shows as 'is damaged and can't be opened'. Symlinks inside Contents/MacOS also break sealing. Fix: build the bundle with no symlinks, then run `codesign --force --deep --sign - App.app` and verify with `codesign --verify --deep --strict --verbose=2`. Any file written into the bundle after signing (e.g. downloaded models) invalidates the seal, so write runtime data to a user directory instead.
