Closed
Description
I'm following the quick start guide to create a RN app, but got the error message:
Command `run-android` unrecognized. Did you mean to run this inside a react-native project?
and the command react-native android
is also unrecognized.
Environment:
- node v4.0.0 (npm v2.14.2)
- RN v0.11.0
Metadata
Metadata
Assignees
Type
Projects
Milestone
Relationships
Development
No branches or pull requests
Activity
shinriyo commentedon Sep 20, 2015
thank you
react-native android
command was finecodingwithus commentedon Sep 21, 2015
same issues happens to me also
pcqpcq commentedon Sep 22, 2015
copy directory "node_modules" to my project fixed.
you can find "node_modules" in demo project.
so i guess we should run "react-native init" or "react-native android" first.
mkonicek commentedon Sep 24, 2015
Did you change to your app's folder? Just updated the Getting Started guide to make this clearer:
https://github.com/facebook/react-native/blob/master/docs/GettingStarted.md
pcqpcq commentedon Sep 25, 2015
i don't think what you have updated is useful to this issue
a0ccebc#diff-c427a522f4ea08a4c045a518ac721ce9
xinthink commentedon Sep 26, 2015
Thanks @pcqpcq, changing directory did fix my problem.
mbylstra commentedon Oct 2, 2015
If you are using a version of react-native-cli less than 0.12, any error will get swallowed and you'll see the error "Command
run-android
unrecognized", regardless of what the actual error is. In my case, I was running the command from the correct directory, but lodash had somehow gotten into a corrupt state. Doingnpm uninstall lodash
andnpm install lodash
fixed the problem for me.The react-native-cli in v0.12.0-rc will not swallow errors: 373c877.
What I did was hack my installed version of react-native-cli (found using
which react-native
) so that the error is logged to the console.deeppatidar commentedon Nov 20, 2015
Command
run-android
unrecognized. Did you mean to run this inside a react-native project?Getting same issue i have tried all possible stuff but still doesn't working even android command also not working
9mm commentedon Nov 22, 2015
Im getting same thing... it's on an existing project that I just did a fresh npm install on. It worked before, so maybe an updated package broke it?
bmichal commentedon Feb 7, 2016
Had the same issue, it turned out I did not have /node_modules directory inside.
Running
npm install
solved the problem.windmxf commentedon Feb 18, 2016
miss node_modules directory
27 remaining items