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

Errors after upgrading to 0.6.0 #1754

Closed
VonD opened this issue Jun 26, 2015 · 8 comments
Closed

Errors after upgrading to 0.6.0 #1754

VonD opened this issue Jun 26, 2015 · 8 comments
Labels
Resolution: Locked This issue was locked by the bot.

Comments

@VonD
Copy link
Contributor

VonD commented Jun 26, 2015

After upgrading to 0.6.0 I cannot get the react app to boot. Here are the various warnings from the console :

Error: undefined is not an object (evaluating 'RCTScrollViewConsts.KeyboardDismissMode.None')
the line in question is :

'none': RCTScrollViewConsts.KeyboardDismissMode.None, // default

Error: Invariant Violation: Application MyApp has not been registered

RCTDataManager.queryData was called with 4 arguments, but expects 3
Also reported here: #1578

Any hints on how to solve these issues ?

@janmonschke
Copy link
Contributor

@VonD Did you try to clean project? XCode > Product > Clean. If that doesn't help, I also try to clean the build folder hold alt > Product > Clean.

@jevakallio
Copy link
Contributor

The issue seems to be that transitive npm dependencies include their own, older copies or react-native, and the packager loads them, causing incompatibilities:

Issue documented here:
#1606 (comment)

@VonD If you want to figure out which dependency is causing this issue, load your app in the debugger, Cmd+O to find ScrollView.js, right click on the file and choose Reveal in navigator. That's your culprit.

@alinz
Copy link

alinz commented Jun 26, 2015

Could it be if one of the module is using peerDependencies? Since in npm 2.x if you are using peerDependencies with range version, npm will show you this warning:

peerDependencies in npm 3+. Your application will need to depend on it explicitly.

@VonD
Copy link
Contributor Author

VonD commented Jun 28, 2015

Many thanks everyone, the problem was some packages depending on older versions of react-native. @jevakallio the Reveal in navigatortip was particularly useful.

@VonD VonD closed this as completed Jun 28, 2015
@albertwchang
Copy link

@VonD, wondering how you resolved the issue specifically? Not sure where the "Reveal in Navigator" link can be found. I couldn't find the Reveal in Finder link when finding the ScrollView.js file.

@VonD
Copy link
Contributor Author

VonD commented Jun 30, 2015

@Achang28 i resolved the issue by upgrading the packages that had dependencies on older versions of react native. once you load the app in the debugger (Cmd+D) you can type Cmd+O in the console, type in the name of the RN file causing your issue, and select it in the autocomplete menu. Then you can right click on the file and you should have the Reveal in Navigator link. This will show you what package the file comes from, and so which one you should upgrade/patch. Hope it helps.

@olivierlesnicki
Copy link

@VonD this helped me, thanks!

@chai2
Copy link

chai2 commented Sep 5, 2015

@janmonschke Thanks man. Product clean fixed my issue.

@facebook facebook locked as resolved and limited conversation to collaborators Jun 28, 2018
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Jul 22, 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

8 participants