-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
BottomNavigation SafeArea inconsistent #2419
Comments
Couldn't find version numbers for the following packages in the issue:
Can you update the issue to include version numbers for those packages? The version numbers must match the format 1.2.3. |
Couldn't find version numbers for the following packages in the issue:
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:
Can you verify that the issue still exists after upgrading to the latest versions of these packages? |
Found a workaround: react-navigation/react-navigation#8972 (comment) That feels dirty though - as said, IMO, devs should be able and responsible to take care of safe areas themselves. That issues wouldn't even exist then. Just my 0.02$ of course 👍 |
@hardcodet This is a regression that came with 4.5.0 If you downgrade to 4.4.1 it works consistently out of the box (no need for additional SafeAreaView) |
Hi @vtoupet I'm afraid I actually am on 4.4.1. Here's my yarn.lock:
|
@hardcodet Could you try version v4.5.0? We migrated away from safe-are-view which seems to be buggy on the latest Iphone. |
yup, 4.5.0 seems to fix the issue, thanks! Good timing! ;) |
add this one to your BottomNavigation, you will love it.safeAreaInsets={{ bottom: 0 }} |
"react-native-paper": "^4.12.0" <BottomNavigation
safeAreaInsets={{ bottom: 35 }}
...
/> |
Current behaviour
My bottom navigation has inconsistent padding at the bottom depending on whether it runs on an iPhone 11 or iPhone 12 Max simulator:
SaveAreaView
, it looks good on the 12 Max, but has a huge bottom-padding on the 11SaveAreaView
, it looks good on the 11, but is placed outside the safe area on the 12It appears that the component tries to do some safe area calculations by itself, but fails at the more recent and bigger 12 Max.
Expected behaviour
This should be consistent. I would prefer it to not try and be smart about safe areas. After all, I have to take care of those on every screen, whether it contains a bottom navigation or not.
Code sample
Really just a simple bottom navigation. Every other control aligns properly on the bottom (if I use a SaveAreaView).
Screenshots (if applicable)
Without a SafeArewView around. 11 left, 12 Pro Max on the right:
Your Environment
react-native: 0.63.4
react-native-paper: 4.4.1
react-native-vector-icons: 0.0.0
expo: 40.0.0
The text was updated successfully, but these errors were encountered: