Skip to content
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

BUG: android:windowSoftInputMode="adjustResize" will not work when StatusBar hidden="true" #12980

Closed
CodeXtinction opened this issue Mar 16, 2017 · 9 comments
Labels
Resolution: Locked This issue was locked by the bot.

Comments

@CodeXtinction
Copy link

AndroidManifest.xml
android:windowSoftInputMode="adjustResize"

I found this bug while playing with StatusBar
if you set StatusBar hidden="true" the keyboard push the header out of the screen instead of resizing.

hidden="false"

hidden="true"

"react": "15.4.2",
"react-native": "0.41.0",

@hramos
Copy link
Contributor

hramos commented Mar 16, 2017

Hey, thanks for reporting this issue!

It looks like your description is missing some necessary information. Can you please add all the details specified in the template? This is necessary for people to be able to understand and reproduce the issue being reported. Specifically, a code sample or Sketch would be ideal here.

I am going to close this, but feel free to open a new issue with the additional information provided. Thanks!

@rcorrie
Copy link

rcorrie commented Mar 13, 2018

This is pretty easy to reproduce.

Just try to use KeyboardAvoidingView on a scene that also has <StatusBar hidden="true" />.

Run it on android. KeyboardAvoidingView does not work as expected.

@hramos
Copy link
Contributor

hramos commented Mar 13, 2018

Can you open a new issue?

@Noitidart
Copy link

@hramos they did open a new issue but you closed that one as well - #13000

@hramos
Copy link
Contributor

hramos commented Mar 23, 2018

We are keeping new issues open a bit longer these days. Just make sure the new one has all the details. Opening an issue does not guarantee a fix, however. It’s up to the contributors that are active in the project to decide what they spend their time on. Having a detailed issue that demonstrates the root cause has been investigated usually helps.

@Noitidart
Copy link

Understood. I just found it funny that we are asking for them to create a new issue after already closing their new issue. :P haha

@hramos
Copy link
Contributor

hramos commented Mar 23, 2018

shrug I was talking to @rcorrie, who bumped this closed issue.

@Noitidart
Copy link

I understand. I didn't mean to point out or anything, i just wanted to share a laugh :P I know thats from your boss, he tells you to close things. You do amazing work in bring RN to us, thanks @hramos!

@facebook facebook locked as resolved and limited conversation to collaborators May 24, 2018
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Jul 18, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Resolution: Locked This issue was locked by the bot.
Projects
None yet
Development

No branches or pull requests

6 participants