react-native-root-toast | react native toast like component , pure javascript solution | Frontend Framework library

Yes, there is nothing wrong with using it to install all of your dependencies. All expo install does is check for compatibilities with your current expo version.

From expo docs:

The expo install command will pick a version that is compatible with your project and then use your JavaScript package manager (such as npm) to install it.

So if you use yarn instead of npm for example, expo will use yarn instead.

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.

If somebody stumbles onto this issue, I solved it by:

1. creating a new project
2. moving all the files to this project (except for package.json)
3. installing all the needed dependencies 1 by 1

PS. I haven't tested it, but you might be able to do it by removing all dependencies in package.json and installing them one by one without creating a whole new project.

In your case actually this is not an error. This is a warning from react native.

componentWillReceiveProps is a synchronous hook. Calling asynchronous function like data fetching inside this hook will need to render in between when the new props are set and when data has finished loading.

Thus, componentWillReceiveProps is being deprecated in favor of the following reason:

1. Use componentDidUpdate

So, I suggest you to use componentDidUpdate hook as far as possible and update your code.

• The similar things happen when comparing componentWillMount and componentDidMount. Use componentDidMount whenever you need operate async operation and forget componentWillMount at all condition.

Can you try with changing function to fat arrow like my code below and putting that function in top , coz during debug mode it uses a different engine to process JS data, so try this out: