Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

iOS: alert dismiss taps "Allow" on the App Tracking Transparency prompt

Open Beginner friendly
  • Is something wrong?
#3,627 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
62/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
ios, swift
Domain
mobile, testing

Research direction

The bug is in chooseAlertButton in apple/runner/AgentDeviceRunner/AgentDeviceRunnerUITests/RunnerTests+Alert.swift, where the dismiss fallback returns buttons.last. Start with the isDismissButton label list and the dismiss branch, comparing them with the guard already in the accept branch. Done when "Ask App Not to Track" is recognized as a dismiss label or the dismiss fallback never picks an accept-style button, and the ATT prompt leaves tracking denied on a simulator run.

Written by the indexing model from the issue text.

Description

bug ready-for-agent

Problem

On an iOS simulator, alert dismiss on the App Tracking Transparency prompt (buttons "Ask App Not to Track" and "Allow") taps "Allow". The command prints dismissed and exits 0, but iOS records an authorization, exactly as after alert accept.

Nothing in the output reveals it: a test that dismisses the prompt to decline tracking silently runs the app with tracking authorized.

Environment

  • agent-device 0.21.24 (code unchanged in 0.21.27, 0.21.28-nightly.20261014.57 and main at 542fb77, see Cause)
  • macOS 26.6.2, Xcode 27.0, Node 24.21.0
  • Simulator: iPhone 17, iOS 27.0, English locale
  • Target app: an Expo development build that calls requestTrackingAuthorization on launch

Reproduction

xcrun simctl privacy "$SIM" reset all <bundle id>        # ATT status back to notDetermined
npx agent-device open <bundle id> --platform ios --udid "$SIM" --relaunch
npx agent-device alert wait 15000                         # "Allow “<app>” to track your activity across other companies’ apps and websites?"
npx agent-device alert dismiss                            # "dismissed", exit code 0
sqlite3 ~/Library/Developer/CoreSimulator/Devices/"$SIM"/data/Library/TCC/TCC.db \
  "select auth_value from access where service='kTCCServiceUserTracking' and client='<bundle id>'"

The development build was opened with --launch-url and its dev-client deep link; any app that requests tracking authorization on launch shows the same prompt. auth_value is 0 when tracking is denied and 2 when it is authorized.

Response to the prompt Runs auth_value
alert dismiss 4 2 (authorized), 4 of 4
alert accept — 2 (authorized)
find text "Ask App Not to Track" click, or click on the button ref 4 0 (denied), 4 of 4

Cause

chooseAlertButton in RunnerTests+Alert.swift:

return buttons.first(where: { isDismissButton($0.label) }) ?? buttons.last

"Ask App Not to Track" is not in the isDismissButton list (cancel, close, dismiss, don't allow, not now, no, keep browsing, later), so dismiss falls back to buttons.last, which is "Allow" on this prompt.

The accept branch already guards against the symmetric mistake: when no accept label matches, it only taps a lone button that is not a dismiss button. The dismiss branch has no such guard and can tap a button that isAcceptButton recognizes ("allow").

Suggested fix

Either or both:

  • add "ask app not to track" to the dismiss labels;
  • in the dismiss fallback, never pick a button that isAcceptButton matches (e.g. the last button that is not an accept button), and fail when every button is an accept button, rather than tap one.

The second keeps dismiss from authorizing on any prompt whose decline label is unknown, including localized ones.

Expected behavior

alert dismiss on the App Tracking Transparency prompt taps "Ask App Not to Track", or fails without tapping, and never records an authorization.

Dominant language
TypeScript
Stars
5k
Forks
334
Avg merge
12h 29m
Merged PRs (30d)
663

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from callstack/agent-device

All issues in callstack/agent-device

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.