Project installs but does not run
See original GitHub issueWhat’s going on? Error when trying to start a newly created project. I’ve tried it on both Linux Mint and Windows 10 following the suggested course
Steps to reproduce
- npx ignite-cli new PizzaApp
- cd PizzaApp/
- yarn android
npx ignite-cli doctor
results:
System
platform linux
arch x64
cpu 16 cores Intel® Core™ i7-10700K CPU @ 3.80GHz
directory PizzaApp /home/danilodorgam/Documentos/projetos/PizzaApp
JavaScript (and globally-installed packages)
node 16.15.0 /home/danilodorgam/.nvm/versions/node/v16.15.0/bin/node
npm 8.5.5 /home/danilodorgam/.nvm/versions/node/v16.15.0/bin/npm
corepack 0.10.0
npm 8.5.5
yarn 1.22.19 /usr/bin/yarn
pnpm - not installed
Ignite
ignite-cli 7.10.10 /home/danilodorgam/.npm/_npx/e31027f3785124a8/node_modules/.bin/ignite
ignite src build /home/danilodorgam/.npm/_npx/e31027f3785124a8/node_modules/ignite-cli/build
Android
java 11.0.15 /usr/bin/java
android home - /home/danilodorgam/Android/Sdk
BUILD FAILED in 6s
at makeError (/home/danilodorgam/Documentos/projetos/PizzaApp/node_modules/execa/index.js:174:9)
at /home/danilodorgam/Documentos/projetos/PizzaApp/node_modules/execa/index.js:278:16
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async runOnAllDevices (/home/danilodorgam/Documentos/projetos/PizzaApp/node_modules/@react-native-community/cli-platform-android/build/commands/runAndroid/runOnAllDevices.js:109:5)
at async Command.handleAction (/home/danilodorgam/Documentos/projetos/PizzaApp/node_modules/@react-native-community/cli/build/index.js:192:9)
info Run CLI with --verbose flag for more details. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:5 (2 by maintainers)
Top GitHub Comments
@jamonholmgren
please help us many projects are generated by ignite these days but they cannot be runned using ignite ???
@ahdidou-mohamed thanks for pointing that out. I’ll go ahead and close this issue since its resolved in the latest build. Please re-open a new issue if you notice anything going on.
Also, my preferred
node
version isv16.15.1