react / react/react-native

Android: Keyboard.addListener returns incorrect height when switching between different keyboard types

Aperta
#52,600 8 commenti 2 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

API: Keyboard Component: Switch Needs: Attention Needs: Repro Needs: Version Info Platform: Android
Lingua principale
C++
Stelle
127k
Fork
25.3k
Merge medio
1g 23h
PR unite (30g)
4

Descrizione

Description

When switching between different keyboard types on Android, Keyboard.addListener events and Keyboard.metrics()?.height return the height of the previous keyboard instead of the current one. This issue occurs consistently when the previous and current keyboards have different heights (e.g., switching from numeric keyboard to password keyboard, or from system security keyboard to regular keyboard). The problem affects both event callback heights and the static Keyboard.metrics()?.height value. The issue resolves itself on the next keyboard opening, but can be stably reproduced by switching between different keyboard types.

Steps to reproduce

Steps to reproduce the behavior:

  1. Open an app with text inputs on Android device
  2. Focus on a text input with keyboardType: 'numeric'
  3. Note the keyboard height (e.g., 300px)
  4. Switch to another text input with keyboardType: 'visible-password'
  5. Observe that both Keyboard.addListener events and Keyboard.metrics()?.height return the previous keyboard's height (300px) instead of the current keyboard's height
  6. Close and reopen the keyboard - the issue resolves and correct height is returned
React Native Version

0.78

Affected Platforms

Runtime - Android

Output of npx @react-native-community/cli info
System:
  OS: macOS 15.3.1
  CPU: (10) arm64 Apple M4
  Memory: 153.83 MB / 16.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 23.11.0
    path: /opt/homebrew/bin/node
  Yarn:
    version: 1.22.22
    path: ~/app/Systech_HX_App/node_modules/.bin/yarn
  npm:
    version: 10.9.2
    path: /opt/homebrew/bin/npm
  Watchman:
    version: 2025.04.28.00
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.16.2
    path: /opt/homebrew/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 24.4
      - iOS 18.4
      - macOS 15.4
      - tvOS 18.4
      - visionOS 2.4
      - watchOS 11.4
  Android SDK: Not Found
IDEs:
  Android Studio: 2024.3 AI-243.25659.59.2432.13423653
  Xcode:
    version: 16.3/16E140
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 17.0.15
    path: /usr/bin/javac
  Ruby:
    version: 2.6.10
    path: /usr/bin/ruby
npmPackages:
  "@react-native-community/cli":
    installed: 15.0.1
    wanted: 15.0.1
  react:
    installed: 19.0.0
    wanted: 19.0.0
  react-native:
    installed: 0.78.0
    wanted: 0.78.0
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: true
iOS:
  hermesEnabled: true
  newArchEnabled: true
Stacktrace or Logs
..
MANDATORY Reproducer

https://github.com/facebook/react-native/

Screenshots and Videos

No response

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Direzione di ricerca

Inizia riproducendo il problema su Android usando input con i tipi di tastiera numeric e visible-password, quindi esamina l’implementazione alla base di Keyboard.addListener e Keyboard.metrics(). Verifica l’altezza riportata quando si cambia tastiera e quando si riapre la tastiera; il lavoro è completato quando sia le callback degli eventi sia le metriche riportano l’altezza attuale della tastiera.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Valutazione

Stack tecnologico
android
Ambito
mobile
Tipo di issue
Bug
Difficoltà
4/5
Tempo stimato
3-5 giorni
Stato di attività
Tranquilla
Chiarezza
Abbastanza chiara
Idoneità per principianti
45/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.