react-native: Unable to run AwesomeProject sample app successfully with error Failed to build iOS project. We ran "xcodebuild" command but it exited with error code 65.

🐛 Bug Report

To Reproduce

  1. Open Getting Started for macOS iOS.
  2. Follow all dependencies installation steps
  3. Create a new application via command: react-native init AwesomeProject
  4. Run AwesomeProject via command:
cd AwesomeProject
react-native run-ios
  1. Error occured when running project:
error Failed to build iOS project. We ran "xcodebuild" command but it exited with error code 65. To debug build logs further, consider building your a
pp with Xcode.app, by opening AwesomeProject.xcodeproj
  1. Run sample app failed.

Expected Behavior

Run sample app successfully.

Code Example

Run new project named AwesomeProject as mentioned in Getting Started for macOS iOS.

Environment

  React Native Environment Info:
    System:
      OS: macOS 10.14.4
      CPU: (8) x64 Intel(R) Core(TM) i7-4980HQ CPU @ 2.80GHz
      Memory: 190.08 MB / 16.00 GB
      Shell: 3.2.57 - /bin/bash
    Binaries:
      Node: 11.14.0 - /usr/local/bin/node
      npm: 6.7.0 - /usr/local/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
    SDKs:
      iOS SDK:
        Platforms: iOS 12.2, macOS 10.14, tvOS 12.2, watchOS 5.2
      Android SDK:
        API Levels: 27, 28
        Build Tools: 27.0.3, 28.0.3
        System Images: android-23 | Google APIs Intel x86 Atom, android-25 | Google APIs Intel x86 Atom, android-27 | Google APIs Intel x86 Atom, andr
oid-27 | Google Play Intel x86 Atom, android-28 | Google APIs Intel x86 Atom
    IDEs:
      Android Studio: 3.3 AI-182.5107.16.33.5314842
      Xcode: 10.2/10E125 - /usr/bin/xcodebuild
    npmPackages:
      react: 16.8.3 => 16.8.3 
      react-native: 0.59.4 => 0.59.4 
    npmGlobalPackages:
      react-native-cli: 2.0.1

Debug Log

macusers-MacBook:AwesomeProject HighSierra$ react-native run-ios
info Found Xcode project AwesomeProject.xcodeproj
info Launching iPhone X (iOS 12.2)...
info Building using "xcodebuild -project AwesomeProject.xcodeproj -configuration Debug -scheme AwesomeProject -destination id=274D552C-C67B-4EFA-A90C-
AF559D0954F0 -derivedDataPath build/AwesomeProject"
info User defaults from command line:

info     IDEDerivedDataPathOverride = /Users/HighSierra/Documents/GitHub/AwesomeProject/ios/build/AwesomeProject


info Build Preparation

info Couldn't create workspace arena folder '/Users/HighSierra/Documents/GitHub/AwesomeProject/ios/build/AwesomeProject': Unable to write to info file
 '<DVTFilePath:0x7f9358f7b8d0:'/Users/HighSierra/Documents/GitHub/AwesomeProject/ios/build/AwesomeProject/info.plist'>'.

info 

error Failed to build iOS project. We ran "xcodebuild" command but it exited with error code 65. To debug build logs further, consider building your a
pp with Xcode.app, by opening AwesomeProject.xcodeproj

2019-04-15 11:50:32.423 xcodebuild[30913:229065] Error saving log: Error Domain=NSPOSIXErrorDomain Code=13 "Permission denied" UserInfo={NSFilePath=/U
sers/HighSierra/Documents/GitHub/AwesomeProject/ios/build/AwesomeProject/Logs/Build/09631BCB-251C-4C0A-8A81-7451C031D0B5.xcactivitylog, NSLocalizedDes
cription=Permission denied} | User info: {
    NSFilePath = "/Users/HighSierra/Documents/GitHub/AwesomeProject/ios/build/AwesomeProject/Logs/Build/09631BCB-251C-4C0A-8A81-7451C031D0B5.xcactivit
ylog";
    NSLocalizedDescription = "Permission denied";
}
** BUILD FAILED **

. Run CLI with --verbose flag for more details.

Could anyone assist on this issue?

Thanks.

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Reactions: 33
  • Comments: 74 (3 by maintainers)

Commits related to this issue

Most upvoted comments

@Piero87 I had exactly the same problem, I just delete the build folder inside /ios then just run again react-native run-ios and the error disappear.

If you don’t have cocoa pods installed you need to sudo gem install cocoapods

  1. cd /ios
  2. run pod install
  3. cd 

  4. delete build folder
  5. run react-native run-ios

if error persists,

  1. delete build folder again
  2. open the /ios folder in x-code
  3. navigate File -> Project Settings -> Build System -> change (Shared workspace settings and Per-User workspace settings): Build System -> Legacy Build System

@jerrychong25 Hey! I can provide a temporary workaround for your problem. Follow these steps:

File -> Workspace Settings -> Build System -> Legacy Build System

File -> Shared Project Settings -> Build System -> Legacy Build System

I just try sudo react-native run-ios the error disappear.

None of these is working for me either. Why is this even closed?

@Piero87 I had exactly the same problem, I just delete the build folder inside /ios then just run again react-native run-ios and the error disappear.

This should be the answer

@Piero87 I had exactly the same problem, I just delete the build folder inside /ios then just run again react-native run-ios and the error disappear.

I tried this and it worked
 Thanks!

This worked for me!

     react-native start --reset-cache
     rm -rf node_modules/
     rm -rf package-lock.json 
     cd ios
     pod deintegrate
     cd ..
     rm -rf ios/Podfile.lock 
     npm install
     npm audit fix
     react-native link
     cd ios
     pod install
     cd ..
     react-native run-ios

so far
 with those configs above, the only thing that worked for me was creating a new projet with react-native version 0.59.5 (and reset cache react-native start --reset-cache)

react-native init MyApp --version 0.59.5

I deleted the build folder inside the ios and run the react-native run-ios, It Worked

If you don’t have cocoa pods installed you need to sudo gem install cocoapods

  1. cd /ios
  2. run pod install
  3. cd 

  4. delete build folder
  5. run react-native run-ios

if error persists,

  1. delete build folder again
  2. open the /ios folder in x-code
  3. navigate File -> Project Settings -> Build System -> change (Shared workspace settings and Per-User workspace settings): Build System -> Legacy Build System

I have no words to describe how useful it was.

Same issue error Failed to build iOS project. We ran "xcodebuild" command but it exited with error code 65. To debug build logs further, consider building your app with Xcode.app, by opening TestProject.xcworkspace. Run CLI with --verbose flag for more details. User defaults from command line: IDEDerivedDataPathOverride

None of mentioned above has worked for me. I just created new project and can not run it


if error persists,

  1. delete build folder again
  2. open the /ios folder in x-code
  3. navigate File -> Project Settings -> Build System -> change (Shared workspace settings and Per-User workspace settings): Build System -> Legacy Build System

image

not work at all

image

  1. sudo gem install cocoapods
  2. cd ios (Folder in your react-native project)
  3. pod install
  4. Restart XCode
  5. react-native run-ios
  1. cd /ios
  2. run pod install
  3. cd 

  4. delete build folder
  5. run react-native run-ios

if error persists,

  1. delete build folder again
  2. open the /ios folder in x-code
  3. navigate File -> Project Settings -> Build System -> change (Shared workspace settings and Per-User workspace settings): Build System -> Legacy Build System

I hope it will work, install pods ongoing

yes!! it works. Your cocoapods not installed, maybe its the problem. I follow this instruction and run well. thanks!!

If you don’t have cocoa pods installed you need to sudo gem install cocoapods

  1. cd /ios
  2. run pod install
  3. cd 

  4. delete build folder
  5. run react-native run-ios

if error persists,

  1. delete build folder again
  2. open the /ios folder in x-code
  3. navigate File -> Project Settings -> Build System -> change (Shared workspace settings and Per-User workspace settings): Build System -> Legacy Build System

Thanks. it works goooooooood.

If you don’t have cocoa pods installed you need to sudo gem install cocoapods

  1. cd /ios
  2. run pod install
  3. cd 

  4. delete build folder
  5. run react-native run-ios

if error persists,

  1. delete build folder again
  2. open the /ios folder in x-code
  3. navigate File -> Project Settings -> Build System -> change (Shared workspace settings and Per-User workspace settings): Build System -> Legacy Build System

Thank you SO MUCH @qodehub-nanadjei. It’s the only solution works to me!

@alvin-toffler After update XCode i’ve got that problem with build project. I’ve discovered that in XCode project in Libraries directory i have 2 bad linked libs (gray icon against blue and without posibility to extend arrow). I deleted it from the project and once again do a react-native link. And now it’s work properly.

Zrzut ekranu 2019-04-17 o 11 02 06

iOS bug

pod install failed

image

image

None of these is working for me either. Why is this even closed?

downgrade to react-native@0.59.5, only thing that worked for me.

This error occurred when I opened my project for the first time in XCode cuz i needed to add a library. Deleting the build folder in the ios folder alone didn’t work for me.

What worked for me:

  • In XCode set “Build System” to “Legacy Build System” (File -> Project Settings -> Build System -> Legacy Build System)
  • Delete the “build” folder in the “ios” folder
  • npm install (I also deleted my node_modules, cuz was installing a new library)
  • react-native run-ios

Eu tentei todas as opçÔes acima e ainda assim, nada funciona. Tudo estava bem até que eu atualizei meu sistema operacional hoje (atualização de 30 min).

Atualização: excluí o arquivo AwesomeProject e inicializei um novo e a compilação foi bem-sucedida. No entanto, agora recebo uma mensagem no simulador dizendo “não foi possível conectar ao servidor de desenvolvimento” Captura de tela 2019-07-31 em 1 48 36 PM

Atualização 2 : excluir a pasta de compilação funcionada, voltando a ver a tela “Bem-vindo ao reagir no simulador do iPhone”

Comigo foi assim também, mas e so dar um ( command + R ) pra resetar a conexão

Not gonna lie. RN should post this on its tutorial section to make sure older version user has to spend hours to find what’s been wrong with the settings
Not everyone knows how to use xcode properly. Isn’t it the whole purpose of using RN?

@Piero87 I had exactly the same problem, I just delete the build folder inside /ios then just run again react-native run-ios and the error disappear.

This should be the answer

This was the answer for me too!

The same after update xcode 
 Solution for me was to delete 2 “gray” elements problem from Libraries and rebuild project.

@kamilzamerski Can you elaborate?

This happens when you terminate the metro bundler terminal window. So make sure you start the metro bundler again by running

npx react-native start

then open your iOS project in Xcode Goto -> Product -> Clean build folder. Then goto your terminal project path start again

npm react-native run-ios

Hope it helps

Ok, I got it. Had issues setting-up a new project after not using React-Native for a lot of time.

My system:

macOS High Sierra 10.13.6 XCode 9.4 Had to reinstall the project in order to use the installation guide from version 0.59.0, because the installation guide from 0.61 uses approach with npx react-native 
, which disallows the usage of react-native below 0.60 (quite totalitarian). 0.59.0 was still using the global version of react-native installed through npm.

In other words: Reinstall the project by removing the old one and use the steps mentioned in the “Getting Started” guide of React-Native 0.59.0 (or any other version compatible with your version of OS and XCode) to install your project again. No need to delete any build or node_modules or installing pods again and so forth, just pick the version of React-Native compatible with your macOS and Xcode (by downgrading and reinstalling the project until you get it) and no need to upgrade to the latest versions, they are developed for the latest systems, if you don’t want to buy the latest devices to support the latest software (OS) or you can’t afford them, just stay with the old ones - it’s totally fine 😃

@nihp in my case, the project that I work has two schemes in Xcode (Dev and Prod).

So, I used the command below and it worked for me

react-native run-ios --scheme "Dev" or react-native run-ios --scheme "Prod"

Nothing above worked for me. Only worked when I include --scheme param in react-native run-ios

react-native run-ios --scheme “xxxx”

@phuongthuan @garshen Your solution not worked for me

If you don’t have cocoa pods installed you need to sudo gem install cocoapods

  1. cd /ios
  2. run pod install
  3. cd 

  4. delete build folder
  5. run react-native run-ios

if error persists,

  1. delete build folder again
  2. open the /ios folder in x-code
  3. navigate File -> Project Settings -> Build System -> change (Shared workspace settings and Per-User workspace settings): Build System -> Legacy Build System

Yes! This worked a charm, Cocoapods wasn’t installed correctly react-native-cli: 2.0.1 react-native: 0.60.5 Xcode: 10.1

if you have this error :

-> remove your folder build in forlder ios -> rm -rf node_modules -> yarn install -> react-native run-ios

enjoys !

My problem was that I forgot to add startup parameters. I used “react-native run-ios --help” to see some options, and finally I use “react-native run-ios – secheme XXXX” to start my project.

Same issue error Failed to build iOS project. We ran “xcodebuild” command but it exited with error code 65. To debug build logs further, consider building your app with Xcode.app, by opening TestProject.xcworkspace. Run CLI with --verbose flag for more details. User defaults from command line: IDEDerivedDataPathOverride

The original author hasn’t commented recently, and the template is already tested as part of our CI system, so this shouldn’t be a problem on master right now. If anyone runs into a similar problem, please submit a new issue.

I was getting this same error with regards to the Info.plist. None of the above worked for me - what did was removing <key>NSAllowsArbitraryLoads</key> in Info.plist which was git diffed and added in RN 0.59.8 when I did the manual upgrade. Once I removed that line, everything complied and I was good to go.