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

Aberta
#39,263 3 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
3/5
Tempo estimado
1-2 dias
Facilidade para iniciantes
68/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
android, react-native, typescript
Domínio
frontend, mobile

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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

Linguagem predominante
TypeScript
Estrelas
24.8k
Forks
6.4k
Merge médio
4h 29min
PRs com merge (30d)
488

Preparar o ambiente

Abrir no Codespaces

Inicia o contêiner de desenvolvimento do projeto no navegador, com a sua própria conta do GitHub.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de pingdotgg/t3code

Todas as issues de pingdotgg/t3code

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.