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

iOS parameterized input remains in native XCTest diagnostic logs

Abierto
  • ¿Algo no está bien?
#3,261 3 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
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
36/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
ios, typescript
Área
mobile-dev, security

Línea de trabajo

Start by tracing the Node API entry point client.interactions.fill and how input reaches the stock XCTest runner; inspect the .xcresult diagnostic log behavior described in the reproduction. Done means establishing whether a supported stock path prevents sensitive values from appearing there, or documenting the limitation if it cannot.

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

Descripción

Observed behavior

On unmodified [email protected], a harmless value supplied through the Node API with fill({ text, recordAs }) was correctly absent from the fill response, subsequent predicate/error responses, and the inspected Agent Device session artifacts, but remained verbatim in the native XCTest .xcresult diagnostic log.

We are trying to use the official release for iOS login automation without carrying a downstream patch. Is there a supported way to prevent sensitive visible input from being retained by this native diagnostic channel? If this is outside the parameterization guarantee, documenting that boundary would also help.

Environment

  • Official npm release 0.21.22; source tag commit 202585240f0c1289642885b5df645cbc25114272
  • macOS host, Xcode 27.0 (27A266a), iOS Simulator
  • Stock signed XCTest runner; no modified upstream code
  • Script recording armed for recordAs; no screen recording, trace, or app-log capture requested
  • Only inert test strings were used, never a real credential

Reproduction outline

  1. Boot an owned iOS simulator and open Settings with the stock CLI in a fresh state directory/session:

    agent-device open com.apple.Preferences --platform ios --udid "$SIM_UDID" \
  --session stock-canary --save-script --foreground --timeout 120000 --json

  2. Use the official Node client for that same session. Take a fresh snapshot and select the unique Settings SearchField with label Search. Then execute:

    const options = { platform: 'ios', udid: process.env.SIM_UDID };
const client = createAgentDeviceClient({ session: 'stock-canary', cwd: process.cwd() });
// searchRef comes from the fresh Settings snapshot.
await client.interactions.fill({
  ...options, ref: searchRef,
  text: 'INERT_STOCK_PRIVATE_CANARY_20261006',
  recordAs: 'PRIVATE_CANARY',
});
await client.interactions.is({ ...options, predicate: 'exists', selector: 'label="Settings"' });
try { await client.interactions.press({ ...options, ref: '@e999999' }); } catch {}

  3. Inspect the exact runner's .xcresult Staging/1_Test/Diagnostics/.../Session-AgentDeviceRunnerUITests-*.log for the inert marker. Our observed excerpt:

    SearchField, label: 'Search', Keyboard Focused ... faulted in {
    "XC_kAXXCAttributeValue" = "INERT_STOCK_PRIVATE_CANARY_20261006";
}: (no error) for value using XC_kAXXCAttributeValue

A second run using another inert marker and fill({ ..., verify: false }) also retained its marker in the native diagnostic log. The stock XCTest plan already sets system/user attachment lifetime to keepNever; that did not prevent this diagnostic text.

This establishes persistence during the sequence, not that the deliberately failed press alone caused it. We have not yet established the behavior on a physical iPhone or a masked password field. The visible Settings input was a control for a visible OTP field.

Expected / requested guidance

A documented stock path for sensitive visible input that avoids retaining its literal value in native diagnostics, or an explicit documented limitation so callers can stop before supplying credentials. We are not asking to disable ordinary observations globally.

Related: #1348 and #1398 provide useful recording/response redaction, and those protections worked in the checks above. #3260 separately concerns CLI input transport; it would not by itself address native diagnostics.

Lenguaje dominante
TypeScript
Estrellas
4.9k
Forks
328
Merge medio
12 h 19 min
PR fusionados (30 d)
549

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.