react-native-tab-view | A cross-platform Tab View component for React Native | iOS library

Try to put your connect() inside an useEffect with an empty array as second argument of useEffect, then your connect function will be called only at the first render of Main.js.

I think the prop indicatorStyle in TabBar that can resolves you problem.

You need to do item.item.codoc in the renderItem.

More information in this post

Edit

I use this code.

Update: Actually the issue is that if your clustered map is animation enabled using the animationEnabled prop here, any following UI change is animated on iOS, see here.

I now reverted my original change (see below) and simply set the animationEnabled prop to false.

Initial answer:

Alright, found it (my fault :)) As you can see from the attached package.json file I'm using react-native-maps and react-navigation. As the screen rendering the map was not dismissed by react-navigationwhen navigating to the settings shown in the screenshots and changing the settings affects which map is rendered, changing the settings and the following update to the redux store trigger the hooks of my map component, thus re-rendering the screen and slowing down the app.

I addressed this issue now by using react-navigation event listeners and unmounting the map screen whenever it loses focus.

Finally, I was able to fix the issue. The issue was in the router file(Navigation setup).

I was using the createNativeStackNavigator from react-native-screens/native-stack instead of createStackNavigator from @react-navigation/stack for better performance.

However, there was an option for screenOrientation in the screenOptions which I didn't know. By default it will allow all options which was causing the issue. In ios, the default falls to UIInterfaceOrientationMaskAllButUpsideDown.

Here goes the documentation.

Search for screenOrientation

I have also updated Expo for SDK40, same problem, so that's why i just again installed 38 that is much more better and optimized, try to write to their expo - community: Expo-Community, and expo - devs and admins are there

hope i could help you! https://forums.expo.io/

If i'm not mistaken Modal has to be inside of return()

Ok, I figured it out by comparing a fresh react native app with only react-native-reanimated installed and my original project.

As expected the issue was with the babel configuration, especially the wildcard plugin. I couldn't exactly figure out the reason, but applying the plugin to the whole project caused some side effects, i.e. import * as abc from './somelocation in my node_modules not being treated correctly.

As I need the wildcard plugin only to be applied to a specific folder ./src/i18n/* I changed my babel.config.js as follows:

Ciao, this problem is connected to graceful-fs package. Plase, reinstall graceful-fs: