Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto Apto para principiantes
  • ¿Algo no está bien?
#3,627 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
62/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
ios, swift
Área
mobile, testing

Línea de trabajo

El error está en chooseAlertButton en apple/runner/AgentDeviceRunner/AgentDeviceRunnerUITests/RunnerTests+Alert.swift, donde el respaldo de dismiss devuelve buttons.last. Empieza por la lista de etiquetas de isDismissButton y la rama dismiss, y compáralas con la guarda que ya existe en la rama accept. Se considera resuelto cuando "Ask App Not to Track" se reconoce como etiqueta de descarte o cuando el respaldo de dismiss nunca elige un botón de estilo accept, y el aviso ATT deja el seguimiento como denied en una ejecución en simulador.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
TypeScript
Estrellas
5k
Forks
334
Merge medio
13 h 19 min
PR fusionados (30 d)
630

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de callstack/agent-device

Todos los issues de callstack/agent-device

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.