Description
Upgrading an app from 0.27.2 to 0.28.0 I get this message in simulator with no stack trace:
When I look at packager I get the message:
NotFoundError: Cannot find entry file global code@http://localhost:8081/index.ios.js in any of the roots: ["/Users/gantman/Documents/Projects/rn/MyApp"]
at DependencyGraph._getAbsolutePath (/Users/gantman/Documents/Projects/rn/MyApp/node_modules/node-haste/lib/index.js:288:13)
at /Users/gantman/Documents/Projects/rn/MyApp/node_modules/node-haste/lib/index.js:226:30
at process._tickCallback (node.js:379:9)
It looks like I'm not the only one: http://stackoverflow.com/questions/37999468/entry-file-error-in-react-native-from-packager/38044411
The stackoverflow issue claims this is due to dependencies that cannot handle 0.28.0 - which leads me to wonder what kind of error message would do that?
This is keeping our ignite project from progressing from 0.27.2 to 0.28 -> infinitered/ignite#199
I've been trying to crack this nut for a few days, any feedback/help would be appreciated. I'm currently going to init a new project and add dependencies one at a time to see if I can find the culprit. Not a very fun process, but there doesn't seem to be a clear opportunity otherwise.
Thanks ahead of time for whomever helps.
Activity
ashleydw commentedon Jun 27, 2016
The dependency is probably using
require
instead of the newimport
. As in: https://github.com/facebook/react-native/releases/tag/v0.25.1But strange if it worked in 0.27.2
satya164 commentedon Jun 27, 2016
Closing since this issue is with a third party module (from the issue you linked to) and it should be filed with that module's repo..
GantMan commentedon Jun 27, 2016
@satya164 - don't you think the error message should be better? Would that be a different issue to file?
satya164 commentedon Jun 27, 2016
@GantMan Feel free to open a new issue if you manage to get a reduced test case of this.
JohnyDays commentedon Jul 1, 2016
Also having this problem, but only on iOS 😢
Converted HTMLView.js to ES6 syntax - Fixes issue introduced recently
kfiroo commentedon Jul 3, 2016
I have a similar issue, you guys might have some insight.
My problem is with react-native run-android only, ios runs just fine.
My packager server is running, I can get http://localhost:8081/index.android.bundle in the browser.
When running react-native run-android, the build completes successfully but I get this error in my packager console:
the problem is that it seems to look for the index file in 10.0.2.2:8081 instead of localhost:8081.
Any idea where is this defined?
Thanks
GantMan commentedon Jul 3, 2016
Just to make sure the IP is the problem, neuter your initial screen from all
imports
outside of RN. If it runs, then it's the same issue we've seen. If it truly is the IP, look into the port/ip forwarding solutions many Android devs have worked with.JohnyDays commentedon Jul 4, 2016
For the record, in my case this error was occuring because I had not correctly setup push notifications on my xCode project. As soon as I linked the library, the error disappeared.
TheoGit commentedon Aug 30, 2016
@JohnyDays I'm having same issue; could you please expound a little more on "not correctly setup push notifications on my xCode project" - how would I fix this???
8 remaining items