software-mansion / software-mansion/react-native-screens
sheetInitialDetentIndex: 0 makes the bottom sheet appear under the system navigation on android
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 3.7k
- Forks
- 714
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 71
Description
Description
setting the sheetInitialDetendIndex to zero makes the screen hide behind the system navigation on android, and it doesn't snap out, even setting the first index of allowed detent to something big like 0.5 which is half of the screen doesn't allow the bottom sheet to snap out.
Steps to reproduce
presentation: 'formSheet',
headerShown: false,
headerBackVisible: false,
sheetGrabberVisible: false,
sheetCornerRadius: 20,
gestureEnabled: true,
sheetInitialDetentIndex: 0,
sheetAllowedDetents: [0.18,0.5, 0.9],
sheetLargestUndimmedDetentIndex: 1,
statusBarTranslucent: false,
statusBarHidden: false,
Snack or a link to a repository
https://github.com/Okiharaherbst/nextpro.git
Screens version
4.10.0
React Native version
0.76.9
Platforms
Android
JavaScript runtime
None
Workflow
Expo managed workflow
Architecture
None
Build type
Debug mode
Device
Real device
Device model
Samsung Galaxy A16 (Android 14)
Acknowledgements
Yes
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue from the provided Expo repository using the sheetInitialDetentIndex and sheetAllowedDetents configuration on Android. Trace the handling of the initial detent and system navigation in the bottom-sheet entry point; done means the sheet no longer appears behind navigation and can snap to a permitted detent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, react-native
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100