Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

iOS parameterized input remains in native XCTest diagnostic logs

未关闭
  • 哪里不对？
#3,261 3 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
36/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
ios, typescript
领域
mobile-dev, security

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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.

主要语言
TypeScript
星标
4.9k
派生
328
平均合并
12 小时 19 分钟
30 天内合并 PR
549

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

callstack/agent-device 的其他 Issue

查看 callstack/agent-device 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。