react-native-scrollable-tab-view | Tabbed navigation that you swipe between , each tab | iOS library

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/

1- I change line in package file

"@react-native-firebase/analytics": "^6.0.0-alpha.25"

with

"@react-native-firebase/analytics": "^6.13.0-alpha.25"

2- cd iOS

3- pod update

every things work fine

thanks

You'll need to do a few things

1. If you don't already have a .babelrc, create one and add the following

As I can see in error log, it's having error related to Native modules.

So I hope your crashlytics module is not properly connected with your iOS Native Module, that's why it's stucked on splash screen as per your explanation.

Please cross-check below added URL code with your Podfile code, whether your crashlytic and dependant plugin pods are their or not.

https://rnfirebase.io/crashlytics/usage/installation/ios

And crashlytics plugin depending on the core firebase app as per stated in crashlytics plugin installation guide, so confirm using below URL as well,

https://rnfirebase.io/install-ios

I hope this will resolve your issues.

when i face this issue add debuggable true in release

After struggling for days Finally i solved it.

1. First Delete index.android.bundle (Located in Assets folder under android project)
2. Run command react-native bundle --platform android --dev false --entry-file index.js --bundle-output android/app/src/main/assets/index.android.bundle --assets-dest android/app/src/main/res/ (I replaced index.js to App.js)

Thank you all for the support, after multiple efforts of solving this, I found the solution was related to my network making IPV6 requests instead of IPV4, I don't filly understand this but this is how I solved:

System Preferences > Network > Advanced > TCP/IP > Configure IPv6: Link-local only

Source

if you are trying to navigate from a component that is a direct descendant of a router that you have the navigation prop available and you can use this.props.navigation.navigate() to navigate. If the component is not a direct descendant of a router you can wrap it inside the withNavigation hoc provided by react-navigation and it will drill the navigation prop to you component and then again you can use it in the same way mentioned above

Your question not clear. But i think this is your problem:

View.propTypes deprecated.

-> Change to use ViewPropTypes instead.