[Bug]: Android pending-answers card's Submit button is hidden behind the 3-button navigation bar (Samsung One UI)

Abierto
#39,263 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
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
68/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
android, react-native, typescript
Área
frontend, mobile

Línea de trabajo

Start in the apps/mobile thread screen and trace how the pending-answers card is laid out alongside Android system insets. Reproduce on Android with 3-button navigation, then compare the card and composer behavior. Done when the Submit button remains visible and tappable above the navigation bar; check the related thread-screen issue #19345 for context.

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

Descripción

Before submitting
  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.
Area

apps/mobile

Steps to reproduce
  1. On a Samsung Galaxy S21 Ultra (One UI 7.x, 3-button navigation), open the T3 Code Android app (Google Play build).
  2. Open a thread where the agent asks a question, so the "USER INPUT NEEDED · Fill in the pending answers" card is shown.
  3. Scroll to the bottom of the card, past the options and the "Or type a custom answer" field.
Expected behavior

The card's Submit button sits above the Android navigation bar and can be seen and tapped.

Actual behavior

The pending-answers card runs past the bottom of the visible area. Its Submit button ends up in the system navigation-bar area, level with or under the 3-button navigation, so it is hidden behind the system buttons and cut off in screenshots. The bottom inset does not seem to be applied below this card.

The composer's send button may be affected the same way (it was first reported as sitting in line with the system buttons), but the question card's Submit button is the clear case.

Possibly related: #19345 (thread screen pushed below the nav bar after starting a new chat), closed as fixed. This is a different screen state, so it may be a separate path or a regression.

Impact

Minor bug or occasional failure

Version or commit

2.3.0 (Google Play)

Environment

Samsung Galaxy S21 Ultra, One UI 7.x (exact version unknown), 3-button navigation, T3 Code 2.3.0 (Google Play).

Logs or stack traces

No response

Screenshots, recordings, or supporting files

Pending-answers card running off the bottom of the screen

Cropped to the card. The screenshot ends at the "Or type a custom answer" field: the card continues past the bottom edge, and the Submit button below it is hidden in the navigation-bar area, so it does not appear in the capture.

Workaround

No response

Lenguaje dominante
TypeScript
Estrellas
24.8k
Forks
6.4k
Merge medio
4 h 29 min
PR fusionados (30 d)
488

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

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 pingdotgg/t3code

Todos los issues de pingdotgg/t3code

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.