Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

fill: a sensitive value can still come back in an altered form (iOS read-back)

Offen
  • Stimmt etwas nicht?
#3,392 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Anfängerfreundlichkeit
45/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
swift, typescript
Bereich
mobile, security

Rechercherichtung

Start with the TEXT_ENTRY_MISMATCH message in RunnerTests+TypeExecution.swift around line 111, which quotes the observed read-back value, and with FillUnconfirmedVerification in packages/contracts/src/fill-evidence.ts, which carries before and after. Check how #3351 redacts the expected and requested values for sensitive fills, then apply the same treatment to observed, before and after. Done means a sensitive fill that fails or settles on a different value returns no read-back text in the error or the response, while the error code and verification status remain. A device run is not required to verify the change, but the design of the placeholder should be agreed first.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

bug ready-for-agent

Follow-up from #3351, as suggested in review.

#3351 keeps the exact text of a sensitive fill (--text-stdin, --record-as) out of responses and errors. Two places can still carry a changed form of that text, which no literal match catches:

  • Error: the iOS runner's TEXT_ENTRY_MISMATCH message quotes both sides: text entry read-back did not match: expected "…", observed "…" (RunnerTests+TypeExecution.swift:111). expected is the exact value and is now redacted. observed is what the field read back. Per the fill help this error covers dropped characters, so it can be the value with a character or two missing.
  • Success: a fill that settles on a different value returns verification: "unconfirmed" with requested, before and after (FillUnconfirmedVerification in packages/contracts/src/fill-evidence.ts). requested is the exact value, but after can be a formatted form of it, like the help's "00 062 91 77" for "000629177".

I found these by reading the code and have not reproduced them on a device, since that needs a field that alters its input.

A possible direction: for a sensitive fill, drop the read-back values instead of matching them. For example, keep the error code with a generic message, and replace before/after with the placeholder. Related: #3261 (the same value in native XCTest logs).

Vorherrschende Sprache
TypeScript
Sterne
5.1k
Forks
339
Ø Merge
12 Std. 57 Min.
Gemergte PRs (30 T.)
653

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus callstack/agent-device

Alle Issues in callstack/agent-device

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.