-
Notifications
You must be signed in to change notification settings - Fork 175
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
Bug when using lazy mode with react-native-collapsible-tab-view version 5.0.0-rc.13 #308
Comments
@PedroBern is this a known issue? |
bump, anyone? |
@alexpchin @andreialecu is this a known issue? |
using 6.1.4 version of app. We are seeing that if we use lazy, sometimes it does not load the component of a particular tab infinitely, and navigating through routes also could cure sometimes only. |
I get something like this occasionally on the second tab only of many tabs. Swiping to it from the first shows nothing, but going to the third tab (which renders) then coming back to the second seems to resolve it. Any developments on this issue? |
#394 might fix this, I released it as 7.0.1-beta.0 on npm. Please help test it for unwanted side effects and report back. Thanks! |
I am trying to use the lazy property when declaring <Tabs.Container lazy ...></Tabs.Container>. Only the first tab is rendering, and all other tabs are completely blank. The issue goes away when I remove "lazy". I am using a Tabs.FlatList in each of the tabs. The lazy property worked when I was on version 4.5.2 of the react-native-collapsible-tab-view. Would appreciate any help in resolving this matter.
The text was updated successfully, but these errors were encountered: