Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

iOS parameterized input remains in native XCTest diagnostic logs

Aperta
  • Qualcosa non va?
#3,261 3 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
36/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
ios, typescript
Ambito
mobile-dev, security

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
TypeScript
Stelle
4.9k
Fork
328
Merge medio
12h 13m
PR unite (30g)
541

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di callstack/agent-device

Tutte le issue di callstack/agent-device

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.