You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 8eaefa3
Browse filesBrowse the repository at this point in the historyBrowse files
feat(settings): let permission and iOS location target an explicit app
`settings permission` and the iOS-simulator `settings location on|off` privacy change acted only on
the app the session had open, so setting a permission before an app's first launch meant opening the
app first just to bind it. `simctl privacy` and Android's `pm` need only the bundle id or package, so
the requirement was the daemon never being handed one.
The named app now rides the request's input payload the way a gesture payload does: `app` is no CLI
flag key, and permission's positionals already carry the target and mode. The CLI reaches it through
the `--app` option `doctor` already owns, and the client and MCP surfaces through their `app` field,
which is now documented. `clear-app-state` keeps carrying its app positionally, unchanged.
Where a mutation cannot consume an app at all the request is refused rather than silently dropped:
Android's `location on|off` writes the device's `location_mode`, and a macOS permission is a TCC grant
to the host process. `settingsAppScope` is that one table, and the refusal carries
`setting_app_not_consumed` with `dispatched: no` so a driver branches on the reason and knows no
device was touched.
No permission is set on a device that never held the app installed differently: the owner resolves the
id as it always has, and the Android rule that revoking a granted permission kills the app (#1796) is
unchanged.
usageDescription: 'Doctor: verify an installed target app without opening a session',
88
+
usageDescription:
89
+
'Target an app without opening it: doctor verifies an installed app by id or name; settings applies an app-scoped change (permission, iOS location) to a bundle id or package',
message: `settings ${described} applies to the target itself, not to an app: ${app} names nothing it can grant or revoke.`,
250
+
details: {
251
+
reason: SETTINGS_APP_NOT_CONSUMED_REASON,
252
+
dispatched: 'no',
253
+
setting: described,
254
+
app,
255
+
},
256
+
hint: `Drop the --app option and run \`settings ${described}\`, or aim the app at an app-scoped setting such as \`settings permission grant location --app ${app}\`.`,
0 commit comments