First off, I don\'t know react, but I figured deploying to an iOS device instead of the simulator wouldn\'t be too difficult to do with the docs. They were a bit sparse but
This is a lot later, but I was still experiencing this same issue. I tried to follow the restart everything path but it didn't fix it. What ended up fixing this for me was making sure my app.json 'name' field (used the same value in the 'displayName' field) matched the 'moduleName' field in my RCTRootView. matched those up and everything was groovy. Hope this helps someone out there.
I am not fan of closing down everything so I dig this further.
All I had to do is in my terminal window, I ran this command:
../lala/node_modules/react-native/packager/launchPackager.command ; exit;
My project name was "lala" , so find that there is node_modules in your project too.
replace lala with your project name it should work.
If there is an error says port is already in use:
ERROR Packager can't listen on port 8081
Then you have two choices:
../lala/node_modules/react-native/packager/packager.js
then find your port number, example 8081, and replace with the port number that is not in use. var options = parseCommandLine([{ command: 'port', default: 8082, }, {
Save this file and then run the above command again.
This way I can run multiple react(ors).
I'm pretty sure @krazyeom's fix has nothing to do with this error. In my case, I fixed this by quitting the terminal that was running from a previous test app I had run. It seems the terminal was confused and was still hooked to a process whose project was no longer loaded in XCode. Try the following:
Reference a nameless person.
it works for me.
I had almost the same problem you currently have a few days ago. For me it was a real device.
From all my research, the solution that worked for me is the following:
C:\Users\username\AppData\Local\Android\Sdk\platform-tools\
)Did you change the name of the app that you're registering? I started the app with the name 'tricky', then later changed the name in this line:
AppRegistry.registerComponent('MyNewApp', () => MyNewApp);
and I started getting the invariant error.
Usually, this Error
nowadays has to do with the different versions of react-navigation
being used.
If you are using react-navigation 4.0
"react-navigation": "^4.1.0",
you have to make sure you are importing the right elements from the right places
in your app.js
import { createAppContainer, createSwitchNavigator } from 'react-navigation'
import { createStackNavigator } from 'react-navigation-stack'
import { createBottomTabNavigator } from 'react-navigation-tabs'
This has helped me resolved the issue.