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

React native bottom tab bar pushing itself up when opening keyboard #11868

Closed
4 of 11 tasks
sandeep-kumar-eptura opened this issue Mar 5, 2024 · 4 comments
Closed
4 of 11 tasks

Comments

@sandeep-kumar-eptura
Copy link

sandeep-kumar-eptura commented Mar 5, 2024

Current behavior

We are using createBottomTabNavigator. In one of the tab contains search bar at the top. While clicking on that search bar, we are opening the keyboard. But the keyboard pushing up the bottom tab bar also. We need the bottom tab bar remains at the bottom when opening keyboard
we are using "@react-navigation/bottom-tabs": "6.5.3",

Also I used {tabbarhideonkeyboard =true } inside tab.input . It's not working.

I tried other option, like changing "adjustresize " to "adjustPan " in side androidMainfest.xml file, and set the Custom keyboard hook for hiding tabbar . But none of those are working.

Expected behavior

We need the bottom tab bar remains at the bottom when opening keyboard

Reproduction

Screenshot 2024-03-05 at 5 32 09 PM

Platform

  • Android
  • iOS
  • Web
  • Windows
  • MacOS

Packages

  • @react-navigation/bottom-tabs
  • @react-navigation/drawer
  • @react-navigation/material-top-tabs
  • @react-navigation/stack
  • @react-navigation/native-stack
  • react-native-tab-view

Environment

  • [] I've removed the packages that I don't use
package version
@react-navigation/native ^6.0.8
@react-navigation/bottom-tabs 6.5.3
@react-navigation/drawer
@react-navigation/material-top-tabs
@react-navigation/stack ^6.2.0
@react-navigation/native-stack 6.9.7
react-native-safe-area-context 4.4.1
react-native-screens
react-native-gesture-handler
react-native-reanimated 3.6.1
react-native-tab-view
react-native-pager-view
react-native
expo
node
npm or yarn yarn
Copy link

github-actions bot commented Mar 5, 2024

Hey @sandeep-kumar-eptura! Thanks for opening the issue. It seems that the issue doesn't contain a link to a repro.

The best way to get attention to your issue is to provide an easy way for a developer to reproduce the issue.

You can provide a repro using any of the following:

A snack link is preferred since it's the easiest way to both create and share a repro. If it's not possible to create a repro using a snack, link to a GitHub repo under your username is a good alternative. Don't link to a branch or specific file etc. as it won't be detected.

Try to keep the repro as small as possible by narrowing down the minimal amount of code needed to reproduce the issue. Don't link to your entire project or a project containing code unrelated to the issue. See "How to create a Minimal, Reproducible Example" for more information.

You can edit your original issue to include a link to the repro, or leave it as a comment. The issue will be closed automatically after a while if you don't provide a repro.

Copy link

github-actions bot commented Mar 5, 2024

Couldn't find version numbers for the following packages in the issue:

  • @react-navigation/drawer
  • @react-navigation/material-top-tabs
  • react-native-tab-view

Can you update the issue to include version numbers for those packages? The version numbers must match the format 1.2.3.

The versions mentioned in the issue for the following packages differ from the latest versions on npm:

  • @react-navigation/bottom-tabs (found: 6.5.3, latest: 6.5.16)
  • @react-navigation/native (found: 6.0.8, latest: 6.1.14)
  • @react-navigation/stack (found: 6.2.0, latest: 6.3.25)

Can you verify that the issue still exists after upgrading to the latest versions of these packages?

@sandeep-kumar-eptura
Copy link
Author

yes, issue is with latest version

Copy link

github-actions bot commented Apr 5, 2024

Hello 👋, this issue has been open for more than a month without a repro or any activity. If the issue is still present in the latest version, please provide a repro or leave a comment within 7 days to keep it open, otherwise it will be closed automatically. If you found a solution or workaround for the issue, please comment here for others to find. If this issue is critical for you, please consider sending a pull request to fix it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant