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

iOS fill can report TEXT_ENTRY_MISMATCH before the confirmation deadline

Abierto
  • ¿Algo no está bien?
#3,952 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@shamilovtim ya está trabajando en esto.

Desde el 25/10/2026.

  • #3953 de @shamilovtim — abierto

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
35/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Estancado
Stack tecnológico
ios, testing-qa, typescript
Área
mobile, testing

Línea de trabajo

Read RunnerTests+TextEntryConfirmation.swift and inspect the ReplacementTextEntryConfirmation polling rule. Run or add the synthetic regression described in the issue for transient partial text, a moved empty field, later exact success, and persistent mismatch. Done means negative observations keep polling within the existing deadline while the stated early success, identity, and mismatch behaviors remain intact; linked pull request #3953 is already open.

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

Descripción

Bug

On the iOS accessibility-driven fill route, replacement confirmation can return verified: false before its existing confirmation deadline. The caller then reports TEXT_ENTRY_MISMATCH, even though a subsequent read within that deadline can contain the requested text.

This is a source-level, synthetic reproduction against 45125d717b207736dd47bc7969edbff7807a6e6d; it does not depend on a particular application.

Deterministic reproduction

Exercise ReplacementTextEntryConfirmation with requested text 123456, an empty baseline, and timestamps relative to initialization:

Time Observation Expected
0.10 s 123 on the same identified input Pending
0.31 s 123 on that input Pending
0.50 s 123456 on that input Pending while settling
0.71 s 123456 on that input Verified

Currently the second observation returns verified: false, so the caller stops before the later correct observation. The same early rejection occurs for an empty, focused, unidentified field whose frame changed from its baseline.

Cause

In RunnerTests+TextEntryConfirmation.swift, settled && (moved || result.verified != false || sampledAt >= deadline) permits a settled negative result whenever the observation differs from its baseline. A changed partial value or changed field frame satisfies moved; neither proves that a negative observation is final.

Required behavior

  • Keep polling negative replacement observations within the existing bounded confirmation budget.
  • Preserve early settled exact/unconfirmed results and identity protections.
  • Preserve rejection when a mismatch persists through the deadline.
  • Type once; do not clear, retype, or add mutation retries.

Completion: a synthetic regression must fail on the current rule and pass after correction, including transient partial text, a moved empty field, later exact success, and persistent mismatch rejection. No public API change or new dependency is needed.

Lenguaje dominante
TypeScript
Estrellas
5.1k
Forks
339
Merge medio
12 h 57 min
PR fusionados (30 d)
653

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.