[Android] Keyboard toolbar overlap
Personne n'a encore pris cette issue.
- Langage dominant
- C++
- Étoiles
- 127k
- Forks
- 25.3k
- Merge moyen
- 1 j 23 h
- PR mergées (30 j)
- 4
Description
Description
On Pixel, Vivo, and Xiaomi devices, the Gboard toolbar overlaps with the app's sticky button when entering generic text, making the button partially or completely inaccessible. This issue appears to be specific to certain input types and doesn't occur consistently across all text fields.
When using a street address field, the accessory bar appears, but when using a postal code field, the bar is hidden. The system doesn't trigger new keyboard events when it shows or hides this accessory bar, making it difficult to detect and adjust layouts accordingly.
The issue is reproducible when the form has fields with different input types. I.e. when the keyboard changes its height without actually hiding.
Hiding and showing the keyboard works as a workaround.
Workaround:
An ugly fix is triggering the "keyboardDidShow" event from the app approximately 400ms after focusing on the view. This means the system eventually provides the correct dimensions, but it doesn't provide them initially. There is probably no specific event for the toolbar.
Steps to reproduce
- Install the app
yarn android - Focus on the "Street Address" field
Expected result: the sticky button is on top of the keyboard toolbar
Result: the keyboard toolbar covers the sticky button
React Native Version
0.79.1
Affected Platforms
Runtime - Android
Output of npx @react-native-community/cli info
System:
OS: macOS 15.4.1
CPU: (12) arm64 Apple M2 Max
Memory: 129.13 MB / 32.00 GB
Shell:
version: "5.9"
path: /bin/zsh
Binaries:
Node:
version: 21.7.1
path: ~/.nvm/versions/node/v21.7.1/bin/node
Yarn:
version: 1.22.22
path: ~/.nvm/versions/node/v21.7.1/bin/yarn
npm:
version: 10.8.3
path: ~/.nvm/versions/node/v21.7.1/bin/npm
Watchman: Not Found
Managers:
CocoaPods:
version: 1.15.2
path: /Users/vlad/.rvm/gems/ruby-3.1.5/bin/pod
SDKs:
iOS SDK:
Platforms:
- DriverKit 24.0
- iOS 18.0
- macOS 15.0
- tvOS 18.0
- visionOS 2.0
- watchOS 11.0
Android SDK: Not Found
IDEs:
Android Studio: 2024.3 AI-243.24978.46.2431.13208083
Xcode:
version: 16.0/16A242d
path: /usr/bin/xcodebuild
Languages:
Java:
version: 17.0.15
path: /usr/bin/javac
Ruby:
version: 3.1.5
path: /Users/vlad/.rvm/rubies/ruby-3.1.5/bin/ruby
npmPackages:
"@react-native-community/cli": Not Found
react: Not Found
react-native: Not Found
react-native-macos: Not Found
npmGlobalPackages:
"*react-native*": Not Found
Android:
hermesEnabled: false
newArchEnabled: false
iOS:
hermesEnabled: true
newArchEnabled: false
Stacktrace or Logs
N/A
MANDATORY Reproducer
https://github.com/vladvlasov256/reproduce-android-keyboard-toolbar-issue
Screenshots and Videos
https://github.com/user-attachments/assets/48b075ff-2b84-43ec-99db-ff83388cb52f
Guide de contribution
Ouvrir le guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Piste de recherche
Commencez par exécuter le reproducteur obligatoire avec yarn android et comparez les champs Street Address et postal code lorsque la barre d’outils du clavier apparaît ou disparaît. Suivez la gestion du clavier et de la mise en page Android de React Native afin de déterminer pourquoi les dimensions ne sont pas mises à jour lorsque la hauteur du clavier change. Le travail est terminé lorsque le bouton fixe reste accessible lors du passage d’un type de champ de saisie concerné à l’autre.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- android, react-native
- Domaine
- mobile
- Type d'issue
- Bug
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Activité
- À l'abandon
- Clarté
- Plutôt claire
- Accessibilité débutants
- 38/100