Repository navigation
✖ Installing Bundler error Error: Looks like your iOS environment is not properly set. #1832
Description
Environment
info Fetching system and libraries information...
System:
OS: macOS 13.0.1
CPU: (8) arm64 Apple M1
Memory: 161.55 MB / 8.00 GB
Shell: 3.2.57 - /bin/sh
Binaries:
Node: 18.12.1 - /usr/local/bin/node
Yarn: 1.22.11 - /usr/local/bin/yarn
npm: 9.4.2 - /usr/local/bin/npm
Watchman: 2023.01.23.00 - /usr/local/bin/watchman
Managers:
CocoaPods: Not Found
SDKs:
iOS SDK:
Platforms: DriverKit 22.2, iOS 16.2, macOS 13.1, tvOS 16.1, watchOS 9.1
Android SDK: Not Found
IDEs:
Android Studio: Not Found
Xcode: 14.2/14C18 - /usr/bin/xcodebuild
Languages:
Java: 1.8.0_292 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: Not Found
react-native: Not Found
react-native-macos: Not Found
npmGlobalPackages:
*react-native*: Not Found
Description
Issue Occurring on MAC OS M1 chip - I am not the only one with this:
I opened this issue here on the react-native GitHub and was told this is a bug and post it here by @cortinico
- except I have Xcode installed and I have other projects using expo which run perfectly with simulators etc etc
✔ Downloading template
✔ Copying template
✔ Processing template
✖ Installing Bundler
error Ignoring ffi-1.15.4 because its extensions are not built. Try: gem pristine ffi --version 1.15.4
Ignoring ffi-1.15.3 because its extensions are not built. Try: gem pristine ffi --version 1.15.3
Ignoring ffi-1.14.2 because its extensions are not built. Try: gem pristine ffi --version 1.14.2
✖ Installing Bundler
error Error: Looks like your iOS environment is not properly set. Please go to https://reactnative.dev/docs/next/environment-setup and follow the React Native CLI QuickStart guide for macOS and iOS.
Error: Error: Looks like your iOS environment is not properly set. Please go to https://reactnative.dev/docs/next/environment-setup and follow the React Native CLI QuickStart guide for macOS and iOS.
at createFromTemplate (/private/var/root/.npm/_npx/7930a8670f922cdb/node_modules/@react-native-community/cli/build/commands/init/init.js:129:11)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async Object.initialize [as func] (/private/var/root/.npm/_npx/7930a8670f922cdb/node_modules/@react-native-community/cli/build/commands/init/init.js:181:3)
at async Command.handleAction (/private/var/root/.npm/_npx/7930a8670f922cdb/node_modules/@react-native-community/cli/build/index.js:106:9)
info Run CLI with --verbose flag for more details.
Version
10.1.3
Reproducible Demo
npx react-native init newProject
Snack, code example, screenshot, or link to a repository
Activity
adamTrz commentedon Feb 17, 2023
Looks like bundler installation failed for you. Could you try solution proposed here?
laurencebedford commentedon Feb 22, 2023
None work same issues occurring - been playing around with this for a while.
nazmeln commentedon Mar 4, 2023
Hey @laurencebedford,
I fixed a similar issue by changing my Ruby version to the proper one.
Please ensure you have this version of Ruby.
What I did:
eval "$(rbenv init - zsh)"at the end of the.zschrfile after installation.Optional: you might need to install Xcode dev tools, run
xcode-select --installin terminalOptional: the command above might not work if you have
.ruby-versionfile, delete file and try againrbenv versionsdocsnpx react-native@latest init AwesomeProjectklwdallas commentedon Mar 7, 2023
I am having this issue on an Intel Mac. First timer following: https://reactnative.dev/docs/environment-setup
whoCanStopMe commentedon Mar 16, 2023
I had this issue too in an Intel Mac. Anyone know how to fix this?
huangtian615 commentedon Mar 16, 2023
laurencebedford commentedon Mar 17, 2023
Sorry it has been two week, this does not work.
laurencebedford commentedon Mar 17, 2023
Translation:
I also had this problem on an Intel Mac. Does anyone know how to fix this thing?
Me too, really speechless, the official cli has a problem, and the imac m1 has the same problem
This is completely correct this issue is leaving M1 chip users screwed over currently.
Visharada commentedon Apr 17, 2023
It's 17th April. This issue is not fixed yet. I am still facing the issue.
thymikee commentedon Apr 17, 2023
hey @Visharada we'd appreciate some help from you on this one :)
saadh393 commentedon Apr 24, 2023
I am also facing the same issue. I am tried lot's of solutions from both Github and StackOverFlow but nothing worked.
jkotchoff commentedon Apr 28, 2023
Am seeing a very similar issue on an M1 Macbook. I tried using ruby version 2.7.6 per @nazmeln's suggestion however when trying to run:
npx react-native init DetoxExample --template react-native-template-typescriptI get the error:
Not sure if it's relevant, however in that stacktrace, the cocoapods gem seems to be vendored with ruby 2.7.0, not sure if that's introducing an incompatibility issue.
nazmeln commentedon Apr 28, 2023
@jkotchoff Have you tried reinstalling the Ruby version using another version manager, like RVM?
Hope it helps, also, don't forget to relaunch the terminal every time after changing Ruby version.
jkotchoff commentedon Apr 29, 2023
I use ASDF and am very familiar with Ruby, that's not the problem.
6 remaining items
khoanguyen-yang commentedon Jul 28, 2023
Here is my solution.
I encounter this error as well although have probably set appropriate ruby version using
rbenv.Turn out the error comes from dependency installations with
pod install. The error did not displayed at all with the init project command.You guys can try
cdto theproject/iosand performpod installto see if there is any error here and follow the instructions in the error messages. For me it just to dopod install --repo-updatemanually 🎉github-actions commentedon Oct 27, 2023
There hasn't been any activity on this issue in the past 3 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 7 days.
southLand1101 commentedon Nov 1, 2023
The error still exists
lijun0222 commentedon Nov 15, 2023
@laurencebedford I have the same error with you.How can I resolve it ?
PanArnaud commentedon Nov 15, 2023
Same error on my side, with M1.
israx commentedon Dec 15, 2023
I have the exact same issue using M1
github-actions commentedon Mar 15, 2024
There hasn't been any activity on this issue in the past 3 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 7 days.
romanmiftakhur commentedon Mar 22, 2024
I have the exact same issue using Mac Intel
github-actions commentedon Jun 21, 2024
There hasn't been any activity on this issue in the past 3 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 7 days.