argent-settings-permissions

Name: argent-settings-permissions
Author: software-mansion

1.8kstars51forks

How to install argent-settings-permissions?

software-mansion/argent/argent-settings-permissions

$npx -y skills add software-mansion/argent --skill argent-settings-permissions

Installs into the current project.

Summary

Grant, deny, or reset an app's runtime permissions (camera, microphone, photos, contacts, notifications, calendar, location, location-always, media-library, motion, reminders) on an iOS simulator or Android device using the argent settings-permissions tool - without navigating

Files · 1

View on GitHub

SKILL.md

1	## What this tool is for
2
3	`settings-permissions` edits the platform's permission store directly - the iOS simulator's TCC database, or Android's package-manager permission flags. It replaces the manual Settings → Privacy dance during test setup: pre-authorize a service so the app never has to ask, deny it up front to test the refusal path, or reset it so the first-run dialog appears again on the next launch.
4
5	It is a test-setup / out-of-band tool, not a general permissions toggle. The default way to change a permission is still through the app - this tool is the exception for the cases the app can't reach.
6
7	## When to use it - and when NOT to
8
9	Decide with this order. The first matching row wins.
10
11	\| Situation \| Do this \| Why \|
12	\| ---------------------------------------------------------------------------------------------------------------- \| --------------------------------------------------------------------------------------------- \| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- \|
13	\| The app has an in-app control for the permission (a toggle in its own settings screen) \| Tap it in the app (`describe` → `gesture-tap`) - do NOT use this tool \| It's real user behavior and exercises the flow you're testing. See `argent-device-interact`. \|
14	\| The app is about to ask (or just asked) and the system permission dialog is on screen \| Tap the dialog (`Allow` / `Don't Allow` / `Allow While Using App`) - do NOT use this tool \| The app-triggered prompt is the natural path; answering it is what a user does. `describe` exposes the dialog buttons; fall back to `screenshot` only if it doesn't. \|
15	\| You need the permission already granted/denied before the app runs, so no dialog interrupts the flow \| Use this tool (`grant` / `deny`) before `launch-app` \| The app can't pre-set its own permission; a real user would do it in Settings. This is the core use case. (`deny` suppresses the prompt on iOS only - see Gotchas.) \|
16	\| The user already denied it and you need it on again \| Use this tool (`grant`) \| iOS never re-shows a dialog once denied - the only in-device path is the Settings app. This tool is the shortcut. \|
17	\| You need the first-run dialog to appear again (test the prompt itself, or reset dirty state) \| Use this tool (`reset`) \| Returns the permission to "not yet asked" so the app prompts on next use. \|
18	\| The permission is not one this tool supports on the target platform (see the support table) \| Do NOT use this tool \| It will return an "unsupported" error. Use the app dialog if the app triggers one, or navigate the real Settings app. \|
19	\| The setting isn't one of the 11 runtime permissions below (e.g. Wi-Fi, cellular data, dark mode, VPN, Focus) \| Do NOT use this tool \| Out of scope - drive the Settings app or the app's own UI instead. \|
20
21	Rule of thumb: if a human tester could flip it _inside the app_, do that. Reach for `settings-permissions` only for a change a human

People who liked this also viewed

6 picks

Type

argent-settings-permissions

1.8kstars51forks

View on GitHub

How to install argent-settings-permissions?

software-mansion/argent/argent-settings-permissions

$npx -y skills add software-mansion/argent --skill argent-settings-permissions

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	## What this tool is for
2
3	`settings-permissions` edits the platform's permission store directly - the iOS simulator's TCC database, or Android's package-manager permission flags. It replaces the manual Settings → Privacy dance during test setup: pre-authorize a service so the app never has to ask, deny it up front to test the refusal path, or reset it so the first-run dialog appears again on the next launch.
4
5	It is a test-setup / out-of-band tool, not a general permissions toggle. The default way to change a permission is still through the app - this tool is the exception for the cases the app can't reach.
6
7	## When to use it - and when NOT to
8
9	Decide with this order. The first matching row wins.
10
11	\| Situation \| Do this \| Why \|
12	\| ---------------------------------------------------------------------------------------------------------------- \| --------------------------------------------------------------------------------------------- \| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- \|
13	\| The app has an in-app control for the permission (a toggle in its own settings screen) \| Tap it in the app (`describe` → `gesture-tap`) - do NOT use this tool \| It's real user behavior and exercises the flow you're testing. See `argent-device-interact`. \|
14	\| The app is about to ask (or just asked) and the system permission dialog is on screen \| Tap the dialog (`Allow` / `Don't Allow` / `Allow While Using App`) - do NOT use this tool \| The app-triggered prompt is the natural path; answering it is what a user does. `describe` exposes the dialog buttons; fall back to `screenshot` only if it doesn't. \|
15	\| You need the permission already granted/denied before the app runs, so no dialog interrupts the flow \| Use this tool (`grant` / `deny`) before `launch-app` \| The app can't pre-set its own permission; a real user would do it in Settings. This is the core use case. (`deny` suppresses the prompt on iOS only - see Gotchas.) \|
16	\| The user already denied it and you need it on again \| Use this tool (`grant`) \| iOS never re-shows a dialog once denied - the only in-device path is the Settings app. This tool is the shortcut. \|
17	\| You need the first-run dialog to appear again (test the prompt itself, or reset dirty state) \| Use this tool (`reset`) \| Returns the permission to "not yet asked" so the app prompts on next use. \|
18	\| The permission is not one this tool supports on the target platform (see the support table) \| Do NOT use this tool \| It will return an "unsupported" error. Use the app dialog if the app triggers one, or navigate the real Settings app. \|
19	\| The setting isn't one of the 11 runtime permissions below (e.g. Wi-Fi, cellular data, dark mode, VPN, Focus) \| Do NOT use this tool \| Out of scope - drive the Settings app or the app's own UI instead. \|
20
21	Rule of thumb: if a human tester could flip it _inside the app_, do that. Reach for `settings-permissions` only for a change a human

People who liked this also viewed

6 picks

Type