Closed ifier closed 3 years ago
Couldn't find version numbers for the following packages in the issue:
expo
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-native-reanimated
(found: 2.0.0-alpha.9
, latest: 1.13.2
)Can you verify that the issue still exists after upgrading to the latest versions of these packages?
Can you open a bug report in Reanimated repo? This sounds like a bug in their code.
Can you open a bug report in Reanimated repo? This sounds like a bug in their code.
Okay. Will create there as well.
I have added repo where you can reproduce this issue - https://github.com/ifier/reanimated-tab-view-bug
Still, if I will return null, not <TabView>
- everything is fine.
Having the exact same bug in my code as well, and I am using the createMaterialTopTabNavigator from react-navigation 5.
Current behaviour
I have used
react-native-tab-view
with reanimated v1 previously and today I've updated reanimated to v2. After that (update) I got this error. When I downgraded reanimated from v2 to v1 - error gone. Then I've updated reanimated again and tried to disconnect some screens/components and etc. Just trying to figure out where the error is and which module causing it. After disconnecting components where Tabs lives - everything become fine. At my code sample, if I willreturn null;
, error will gone.Expected behaviour
Without errors.
Code sample
Screenshots (if applicable)
What have you tried
Tried to search through issues and etc but got nothing. Tried to read documentation how to install
reanimated v2
(I didn't install it like v1 and used it previously, just like dependency for your library) andreact-native-tab-view
Tried to uninstallnode_modules
completely and install them again andpod install
. Thennpm start -- --reset-cache
.Your Environment
babel.config.js
package.json