Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Fix: KeyboardAvoidingView Android behavior fix. #51132

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

HyopeR
Copy link

@HyopeR HyopeR commented May 6, 2025

Try to resolve Android compatibility for KeyboardAvoidingView component.

Summary:

On Android devices, KeyboardAvoidingView causes various space errors after opening / closing.

The main reason for this is that when I examine the values ​​in the KeyboardAvoidingView component, in some cases the area covered by the keyboard does not equal 0.

This change resolves the following issues.

#29614 #47140 #50444 #50728

Changelog:

[ANDROID] [FIXED] - Fixed issues with KeyboardAvoidingView after keyboard on/off.

Test Plan:

1- Implement the change.
2- Try the steps of the referenced issues again.
3- Verify that everything works correctly.

Examination:

Case 1: View cannot set correct height after keyboard open/close. #29614 #47140

Before After
State1-Before.mp4
State1-After.mp4

Case 2: Orientation problem is observed after Android API >= 30. This problem is not observed when Android API < 30. #50444 #50728

Before After
State2-Before.mp4
State2-After.mp4

@facebook-github-bot
Copy link
Contributor

Hi @HyopeR!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at [email protected]. Thanks!

@facebook-github-bot facebook-github-bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label May 6, 2025
@facebook-github-bot
Copy link
Contributor

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

@facebook-github-bot facebook-github-bot added the Shared with Meta Applied via automation to indicate that an Issue or Pull Request has been shared with the team. label May 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. Shared with Meta Applied via automation to indicate that an Issue or Pull Request has been shared with the team.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants