Closed david-shiko closed 6 months ago
Hey @david-shiko, we have this sample app where we use bottom tabs, and it works well. Your issue doesn't give me any clarity on what you might be facing. Please follow the sample app, and this should work fine for you. I don't think it's a fault of our components like OverlayProvider
.
https://github.com/GetStream/stream-chat-react-native/tree/develop/examples/SampleApp
Hey @david-shiko, we have this sample app where we use bottom tabs, and it works well. Your issue doesn't give me any clarity on what you might be facing. Please follow the sample app, and this should work fine for you. I don't think it's a fault of our components like
OverlayProvider
.https://github.com/GetStream/stream-chat-react-native/tree/develop/examples/SampleApp
I have already reviewed the sample app before posing my question, but found it not very informative due to its extensive use of styles. Maybe the sample app have encountered the same issue and resorted to using "position: absolute" as a workaround. BTW I believe that the styles in the demo are excessive and not necessary for addressing the fundamental problem.
Hello Stream Team, I have an issue related to the React Native (RN) SDK, specifically with the GetStream chat screens (Chat, Channel List, Channel) which overlap my bottom menu from the React Native Navigation library. I'm not very experienced with layout design, but I think it's related to the OverlayProvider. According to the documentation, it should be positioned outside of the navigation components (stack screen). However, instead of wrapping the screens as usual, my bottom menu is now inside the GetStream Chat wrapper and is being overlapped by it. I could manually add padding to make my bottom menu visible, but the real problem, in my opinion, is that wrapping the navigation is breaking the design architecture.
P.S. it's the only screen with a such issue, other screens works fine with my bottom navigation menu.
Enviroment:
Device:
Running:
npx expo start -c
->a