KeyboardAvoidingView padding bug
See original GitHub issueIssue Description
KeyboardVoidingView has wrong padding on android.
Steps to Reproduce / Code Snippets
Create KeyboardAvoidingView with following view hierarchy
-> KeyboardAvoidingView
-> ScrollView
-> View (The one with this issue)
When keyboard is open last View has wrong padding
Attachments
iOS (Correct)
#### Android (Wrong) #### Expected ResultsPadding should be set correctly
Additional Information
- React Native version: 0.35.0
- Platform: Android
Issue Analytics
- State:
- Created 7 years ago
- Reactions:6
- Comments:11 (4 by maintainers)
Top Results From Across the Web
KeyboardAvoidingView padding bug - react native
I made an attempt to fix this problem using keyboardVerticalOffset. This is the render function of the view from the image, wich is...
Read more >[Solved]-KeyboardAvoidingView padding bug-React Native
Coding example for the question KeyboardAvoidingView padding bug-React Native. ... KeyboardAvoidingView extra padding blank area on the top of keyboard ...
Read more >KeyboardAvoidingView - React Native
This component will automatically adjust its height, position, or bottom padding based on the keyboard height to remain visible while the ...
Read more >React Native KeyboardAvoidingView: A How-To Guide - Waldo
Look into the issue on-screen keyboards cause with a long form ... Also, we're aligning the text to the center and adding vertical...
Read more >keyboard avoiding view not working ios - You.com
The main issue with KeyboardAvoidingView is that; the understanding of how ... First thing, use of flex:1 in KeyboardAvoidingView and behavior: 'padding'.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi there! This issue is being closed because it has been inactive for a while. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. Either way, we’re automatically closing issues after a period of inactivity. Please do not take it personally!
If you think this issue should definitely remain open, please let us know. The following information is helpful when it comes to determining if the issue should be re-opened:
If you would like to work on a patch to fix the issue, contributions are very welcome! Read through the contribution guide, and feel free to hop into #react-native if you need help planning your contribution.
Issue still exists version 49