# fix\(desktop\): tell Safari's Full Disk Access apart at listing time · pingdotgg/t3code

[View on GitCafe](https://git.cafe/pingdotgg/t3code/commit/35f4dcdd21a047d41ae0e6924452de5d4eb1d680)

Repository: [pingdotgg/t3code](https://git.cafe/pingdotgg/t3code)

Visibility: public

Requested revision: 35f4dcdd21a047d41ae0e6924452de5d4eb1d680

Requested commit: 35f4dcdd21a047d41ae0e6924452de5d4eb1d680

Commit: 35f4dcdd21a047d41ae0e6924452de5d4eb1d680

Tree: f3bd00071c05676dbe22d6006428e365d6b6c37e

Author: Julius Marminge

Committer: Julius Marminge

## Message

```
fix(desktop): tell Safari's Full Disk Access apart at listing time

The listing found Safari's jar with `stat`, which TCC permits without Full
Disk Access, so Safari always listed as ready and the wizard opened on the
configure step — the permission-first flow, the "still required" recheck and
its `resume: "configure"` path could never run, and a refresh could not tell
granted from denied. `unavailableReason` now probes the jar by opening it for
read; TCC's EPERM reports `needsFullDiskAccess`, while a readable jar or any
other failure does not.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

```

## Parents

- [3a8fcf706d04c8fb284b77dddeab0e8ed9c93176](https://git.cafe/pingdotgg/t3code/commit/3a8fcf706d04c8fb284b77dddeab0e8ed9c93176?format=markdown)

[Source at this commit](https://git.cafe/pingdotgg/t3code/tree/35f4dcdd21a047d41ae0e6924452de5d4eb1d680?format=markdown)