Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

React Native 0.43 completely broken #13311

Closed
Swizec opened this issue Apr 5, 2017 · 5 comments
Closed

React Native 0.43 completely broken #13311

Swizec opened this issue Apr 5, 2017 · 5 comments
Labels
Resolution: Locked This issue was locked by the bot.

Comments

@Swizec
Copy link

Swizec commented Apr 5, 2017

Description

I ran react-native init MyAwesomeApp. It finishes with npm warnings about peer dependencies and the default app doesn't even run.

screen shot 2017-04-05 at 00 20 13
screen shot 2017-04-05 at 00 21 41

Reproduction Steps and Sample Code

react-native init MyAwesomeApp
cd MyAwesomeApp
react-native run-ios

Observe that it doesn't work.

Solution

I assume the issue stems from this:

screen shot 2017-04-05 at 00 18 48

And potentially other things related to that. I don't understand enough about how react-native works to know what's wrong.

Additional Information

  • React Native version: 0.43.0
  • Platform: iOS
  • Development Operating System: MacOS Sierra
  • Dev tools: CLI
@janicduplessis
Copy link
Contributor

Thanks for reporting this, the peer dep isn't actually the issue. Might be related to some yoga commits that were cherry picked recently. cc @grabbou

@grabbou
Copy link
Contributor

grabbou commented Apr 5, 2017

Have you tried restarting packager after upgrading React Native? Before pushing, I've checked run-ios on UIExplorer (bundled example of React Native) and everything worked.

@janicduplessis I was planning to cherry-pick Yoga commit but eventually didn't, as the commit was to Yoga separate repo.

@Swizec
Copy link
Author

Swizec commented Apr 5, 2017

I wasn't updating React Native, I was starting a new project.

But it does look like I had a packager from a different project running in a hidden terminal window. After killing that and restarting, everything seems to work.

Thanks for the help ... but why can different projects impact each other like this?

@grabbou
Copy link
Contributor

grabbou commented Apr 5, 2017

@Swizec packager was serving you a bundle for a different React Native version which resulted in a mismatch when JS -> Native calls happen (as per error message).

@grabbou grabbou closed this as completed Apr 5, 2017
@janicduplessis
Copy link
Contributor

janicduplessis commented Apr 5, 2017

Yea every RN packager always runs on the same port so it didn't start a new packager for your new project and just used the one that was running already.

@facebook facebook locked as resolved and limited conversation to collaborators May 24, 2018
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Jul 18, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Resolution: Locked This issue was locked by the bot.
Projects
None yet
Development

No branches or pull requests

4 participants