### Description
Burrow continues to report that Full Disk Access is disabled even though it is enabled under:
System Settings → Privacy & Security → Full Disk Access
The app is running from the expected location:
`/Applications/Burrow.app`
### Environment
- Burrow: 0.8.1 (build 12)
- Bundle ID: `dev.caezium.Burrow`
- macOS: 27.0
- Architecture: Apple Silicon
### Steps to reproduce
1. Install Burrow 0.8.1 in `/Applications`.
2. Add Burrow to Full Disk Access.
3. Enable the permission.
4. Completely quit and reopen Burrow.
5. Burrow still reports: “Full Disk Access is off.”
Removing the existing privacy entry, adding `/Applications/Burrow.app` again, and relaunching does not resolve the issue.
### Diagnostic findings
The running process is the correct application:
```text
/Applications/Burrow.app/Contents/MacOS/Burrow
The release uses an ad-hoc signature without a Team ID:
Identifier=dev.caezium.Burrow
Signature=adhoc
TeamIdentifier=not set
Strict signature verification also fails inside the bundled Sentry framework:
Burrow.app: code has no resources but signature indicates they must be present
In subcomponent: Burrow.app/Contents/Frameworks/Sentry.framework
I downloaded the official Burrow-0.8.1.zip release again and obtained the same verification failure, so this does not appear to be local file corruption.
Possible cause
The ad-hoc application identity may cause the TCC/Full Disk Access authorization to become invalid after an update. The malformed Sentry framework signature may also affect macOS’s identity validation.
Could the macOS release be signed with a stable Developer ID and have its nested framework signatures corrected?
The release uses an ad-hoc signature without a Team ID:
Strict signature verification also fails inside the bundled Sentry framework:
I downloaded the official
Burrow-0.8.1.ziprelease again and obtained the same verification failure, so this does not appear to be local file corruption.Possible cause
The ad-hoc application identity may cause the TCC/Full Disk Access authorization to become invalid after an update. The malformed Sentry framework signature may also affect macOS’s identity validation.
Could the macOS release be signed with a stable Developer ID and have its nested framework signatures corrected?