Error generating new project with Expo
See original GitHub issueWhat’s going on?
When creating a new project with expo support, I’ll get the following error:
➜ ~ npx ignite-cli new myProject --expo
· · · · · · · · · · · · · · · · · · 🔥 Ignite 🔥 · · · · · · · · · · · · · · · · · ·
█ Creating myProject using Ignite 7.0.6
█ Powered by Infinite Red - https://infinite.red
█ Using expo-cli
────────────────────────────────────────────────
🔥 Igniting app
🪔 Summoning Expo CLI
🎫 Cleaning up Expo install
🧶 Unboxing NPM dependencies
⠋ Writing your app name in the sand
/Users/ph/.npm/_npx/e31027f3785124a8/node_modules/gluegun/build/index.js:13
throw up;
^
mv: no such file or directory: /Users/ph/myProject/ios/myProject
mv: no such file or directory: /Users/ph/myProject/ios/myProject-tvOS
mv: no such file or directory: /Users/ph/myProject/ios/myProject-tvOSTests
mv: no such file or directory: /Users/ph/myProject/ios/myProject.xcodeproj
mv: no such file or directory: /Users/ph/myProject/ios/myProject.xcodeproj/xcshareddata/xcschemes/myProject-tvOS.xcscheme
mv: no such file or directory: /Users/ph/myProject/ios/myProject.xcodeproj/xcshareddata/xcschemes/myProject.xcscheme
mv: no such file or directory: /Users/ph/myProject/ios/myProjectTests
mv: no such file or directory: /Users/ph/myProject/ios/myProjectTests/myProjectTests.m
mv: no such file or directory: /Users/ph/myProject/ios/myProject.xcworkspace
mv: no such file or directory: /Users/ph/myProject/ios/myProject/myProject.entitlements
mv: no such file or directory: /Users/ph/myProject/ios/myProject-Bridging-Header.h
node:internal/process/promises:246
triggerUncaughtException(err, true /* fromPromise */);
^
[Error: ENOENT: no such file or directory, open '/Users/ph/myProject/android/app/src/main/AndroidManifest.xml'] {
errno: -2,
code: 'ENOENT',
syscall: 'open',
path: '/Users/ph/myProject/android/app/src/main/AndroidManifest.xml'
}
Creating the project without expo (vanilla react native) is working.
Steps to reproduce
- Issue
npx ignite-cli new myProject --expo
ignite doctor
results:
➜ ~ npx ignite-cli doctor
System
platform darwin
arch x64
cpu 12 cores Intel(R) Core(TM) i7-8700B CPU @ 3.20GHz
directory ph /Users/ph
JavaScript (and globally-installed packages)
node 16.4.2 /usr/local/bin/node
npm 7.18.1 /usr/local/bin/npm
dblsqd-cli 0.6.0
npm 7.18.1
yarn 1.22.10 /usr/local/bin/yarn
expo-cli 4.7.3
Ignite
ignite-cli 7.0.6 /Users/ph/.npm/_npx/e31027f3785124a8/node_modules/.bin/ignite
ignite src build /Users/ph/.npm/_npx/e31027f3785124a8/node_modules/ignite-cli/build
Android
java 1.8.0_231 /Users/ph/.jenv/shims/java
android home - undefined
iOS
xcode 12.5.1
cocoapods 1.10.1 /usr/local/bin/pod
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (2 by maintainers)
Top Results From Across the Web
Common development errors - Expo Documentation
This page outlines a list of errors that are commonly encountered by developers using Expo. For each error, the first bullet provides an...
Read more >Expo project created with create-expo-app errors · Issue #18545
An Expo project created with create-expo-app causes a bundle error when ran with expo start command. I'm using Expo Go on iOS (both ......
Read more >Error while create new react-native project by using expo ...
When I wrote npm pack expo-template-blank-typescript --dry-run in my vscode terminal.
Read more >5 common errors found in a React Native app (using Expo)
In this article, I will list 5 errors that we as developers faced, while creating a mobile app in React Native (using Expo)...
Read more >'expo' is not recognized as an internal or external command
if you got permissions error sudo npm install --global expo-cli # 👇️ Create a new project expo init my-project. If the "'expo' is...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The update fixes the problem - at least for me. Thanks for the quick help
Hi
I am using Ignite 7.0.8 and still facing the same issue. (Using Node 16).