The sandboxed-retry slot has no switch, no writer and no reader anywhere in the build.
Unlike its neighbours, the sandboxed-attempt slot has no flag name or accessors attached.
What's wrong with this entry?
The declaration of that sandboxed-attempt slot is its only occurrence in the build. Its neighbours all follow a fixed pattern, either filled lazily from a named remote flag with an on-by-default fallback or given an explicit setter and getter; this one has none of that, and no flag name is attached to it.
- Nothing assigns it and nothing reads it, so no behaviour depends on it in this build.
sandboxedAttemptGateEnabled
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.236
macOS sandbox re-applies read and delete denials inside writable folders
Both mention sandbox
-
v2.1.236
Sandbox proxy no longer writes to sockets that have gone away
Both mention sandbox
-
v2.1.236
IPv6 hosts through the proxy
Both mention sandbox