[Android] Screen size not adjusted properly when navigationBar is hidden

[larslr]

🐛 Bug Report

Screen size remains the same size when navigationBar is hidden, leaving a background colored box where the navigationBar used to be.

Have you read the Contributing Guidelines on issues?

Yes.

To Reproduce

1. Start with playground app
2. In app.ts, edit the setRoot() call so that that the Options stack is directly below root, removing bottomTabs and the other screens
3. Start the app, click the "Toggle Navigation bar visibility" button

Expected behavior

The usable screen should expand towards the bottom when the navigation bar disappears. This works when using the bottomBar.

Actual Behavior

The navigation bar disappears, but the area remains unusable. Scrolling the view moves the buttons under the navigation bar area instead of letting them hit the bottom of the screen.

Attached are screenshots showing the situation.

Your Environment

• React Native Navigation version: 7.16.0
• React Native version: 0.63.1
• Platform: Only tested on Android
• Device info: Android 8.1 simulated and device

Reproducible Demo

git clone https://github.com/hooplab/react-native-navigation.git rnn_navbar
cd rnn_navbar
git checkout navbar_bug

Follow Playground instructions to start app

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
If you believe the issue is still relevant, please test on the latest version and report back. Thank you for your contributions.

[MagnusEklof]

Any chance getting an estimate when this is going to be fixed? I can't seem to find a workaround besides creating a "fake" bottomTabs just to be able to remove it...

[swabbass]

Fixed in the mentioned PR:

Screen.Recording.2021-11-17.at.16.53.43.mov

[MagnusEklof]

Hmm yes, but will it work without a bottomtabs @swabbass? I mentioned in #7199 that I could not make it work without first creating a dummy bottomtabs and then hiding both bottomtabs and navbar... but that was not a very good workaround.

[swabbass]

@MagnusEklof yes it will work without, you can check out the PR :#7343, the one mentioned in this issue.