Collectives™ on Stack Overflow

Find centralized, trusted content and collaborate around the technologies you use most.

Learn more about Collectives

Teams

Q&A for work

Connect and share knowledge within a single location that is structured and easy to search.

Learn more about Teams

error Failed to build iOS project. We ran "xcodebuild" command but it exited with error code 65

Ask Question

I've build a react-native application and suddenly I get this error message on my terminal during run of the command react-native run-ios. The same code work fine 10 minutes ago and suddenly I get this error message. Please help...

Did you install any new dependencies since it last worked? Have cleaned the build folder and the derived data? Andrew Mar 19, 2019 at 8:03 Did you update react-native version? I had the same problem and I came back to the last RN version. Brian Fraiman Mar 22, 2019 at 4:12
  • delete build folder again
  • open the /ios folder in x-code
  • navigate File -> Project Settings -> Build System -> change (Shared workspace settings and Per-User workspace settings): Build System -> Legacy Build System`
  • You should be good to go.

    hey dude , this one really worked for me! but u need to change something 1. cd ios only not cd/ios Forhad Sep 19, 2019 at 3:56 This doesn't work no more. Actually, if you use the Legacy Build System, the build can't even prepare lol. Jack Murrow Oct 14, 2021 at 5:19
  • delete the build/ folder in ios/ and rerun if that doesn't do any change then
  • File -> Project Settings (or WorkSpace Settings) -> Build System -> Legacy Build System
  • Rerun and voilà!
  • In case this doesn't work, don't be sad, there is another solution to deeply clean project

  • Delete ios/ and android/ folders.

  • Run react-native eject [Edit: deprecated, so skip this step]

  • Run react-native link

  • react-native run-ios

    This will bring a whole new resurrection for your project

    I've try 2 times run the same command and now it works. 1) I removed the folder "/ios/build" and rerun. 2) After fail, I changed to Legacy Build System and rerun. 3) After fail, rerun again and voilà! :) romulobastos Aug 10, 2019 at 22:21 Thanks! The first solution worked for me. My case was that I moved a react-native project in another folder. That broke the npm run iOS for me. thinklinux Oct 14, 2019 at 10:19 This is the right answer, and I believe this is needed every single time we update XCode. Lucas Andrade Jan 16 at 14:22

    SOLVED: Always be sure to update your Xcode folks!

    Protip: And don't do it from the apple store (but always do it from an official apple website of course)

    tip from: http://ericasadun.com/2016/03/22/xcode-upgrades-lessons-learned/

    official apple download page: https://developer.apple.com/download/more/

    For those who are unable to resolve with above method

  • Go to project settings in Xcode. Menu File->Project Settings

  • Go to per-User Project Settings section.

  • Click on advanced.

  • Select Xcode Default option. previously this used to be Legacy for my project.

  • I have analysed on similar lines and concluded that clean is causing the archive to fail. So, the new build system is not clearing the custom/legacy build directory.

    delete the build/ folder in ios/ and rerun if that doesn't do any change then
    File -> Project Settings (or WorkSpace Settings) -> Build System -> Legacy Build System
    Rerun and voilà!
    

    If it still Fails you need to clean full project

    Do the following:

  • Delete ios dir manually
  • Clean cache Run npm cache clean --force
  • Run react-native eject
  • Re-install all packages npm install
  • Run the link command react-native link
  • Finally run react-native run-ios
  • You need to check your react-native version whether it stable to work with xcode version @Angel – Akshay Mulgavkar Apr 2, 2019 at 4:54 @ToroLoco OS X El Capitan 10.11.6 is the last supported release of macOS for your model of iMac. The latest release of Xcode that can be installed on your machine is Xcode 8.2.1 with macOS 10.12.2 SDK and iOS 10.2 SDK. So update ur imac – Akshay Mulgavkar Apr 2, 2019 at 4:57

    cd ios && rm Podfile.lock && pod install worked for me.

    And perhaps few updates if the first didn't help as much, as:

    sudo gem install cocoapods
    rm Podfile.lock && pod install --repo-update
                    Thanks! This worked for me because I deleted the ios directory and checked it back out from git.
    – Don Branson
                    Jun 20, 2020 at 12:10
                    You have to remove Podfile.lock to work the command pod install --repo-update  rm Podfile.lock && pod install --repo-update
    – Raphael Cangucu
                    Jul 20, 2022 at 13:03
    

    For me it caused by installing react-native-vector-icons and linking by running the react-native link react-native-vector-icons command.

    I just unlinked the react-native-vector-icons by following commands

  • react-native unlink react-native-vector-icons
  • cd ios
  • pod install
  • cd ..
  • react-native run-ios
  • As I already installed an other icon library.

    This was it for me. I had installed vector-icons for adhoc usage. Part of that installation process was to link react-native-vector-icons ... a while later, I wanted to use the react native elements. When I installed native elements and attempted to build the project, the stack trace included information about unlinking vector icons for react native elements to auto build and link it properly. – spencer741 Apr 24, 2021 at 2:33 I had the same issue and just had to uninstall react-native-vector-icons and it ran without an issue – Nero Oct 31, 2022 at 3:46

    After upgrading react-native, you may have stale dependencies. The steps below should fix it.

  • cd ios
  • delete Podfile.lock
  • pod deintegrate && pod install
  • Navigate back to package.json directory
  • run react-native run-ios
  • In Xcode you can build your project again too
  • I did this after upgrading to react-native 0.61

    I keep coming back to this answer. It's been probably my most consistently working fix to various issues I seem to have sometimes. THANK YOU – SeanMC Oct 21, 2022 at 18:51

    Should always start with the simplest first, after wasting hours and days on this error.

    And after an extensive amount of research,

    Simply

    RESTART YOUR MACHINE
    

    This resolved this error.

    I'm on

    react-native-cli: 2.0.1
    react-native: 0.63.3
                    I haven't restarted my computer since installing xcode about a week ago - this solution worked for me
    – MingMan
                    Apr 2, 2022 at 16:58
    

    This problem may occur after installing react-native-vector-icons

  • Open the project in Xcode.
  • Go to build phases.
  • go to Copy Build resources.
  • Remove all .ttf files from here.
  • Run the application.
  • delete build folder again
  • open the /ios folder in Xcode
  • navigate File -> Project Settings -> Build System -> change (Shared workspace settings and Per-User workspace settings): Build System -> Legacy Build System
  • I had the same error, but it was caused by the package manager process port being already used (port 8081).

    To fix, I just ran the react-native by specifying a different port, see below.

    react-native run-ios --port 8090

    A popular reason to builds failing and error code 65 is a missmatch between cached pod files and current packages used. Here is how to remove the cache and recreate the pods.

    1. Delete Derivate Data - Remove data that includes cached info of the project Example how to do it: https://www.youtube.com/watch?v=f8bTvx0Aoyo

    2. Delete .xcworkspace file from ios folder - This is the Xcode project file that gets created when you run pod install we want to recreate it in step 4. This project file uses pods and has a white coloured icon instead of the blue coloured base project without pods.

    3. Delete Podfile.lock - Remove old dependencies info so we can recreate them in the next step.

    Do a pod-install in ios folder or npx pod-install in root with (React native) - Here we download the pod dependencies again and the pod files only the ones that are used from the current packages are downloaded. A .xcworkspace is regenerated

    In my case, the issue was with my Xcode build scheme. When you run react-native run-ios you may see something like,

  • info Found Xcode workspace "myproject.xcworkspace"*

  • info Building (using "xcodebuild -workspace myproject.xcworkspace -configuration Debug -scheme myproject -destination id=xxxxxxxx-xxxxx-xxxxx-xxxx-xxxxxxxxx -derivedDataPath build/myproject")*

    In this case, there should be a scheme named myproject in your ios configurations. The way I fixed it is,

    Double clicked on myproject.xcworkspace in ios directory (to open workspace with Xcode)

    Navigate into Product > Scheme > Manage Schemes...

    Created a Scheme appropriately with name myproject (this name is case-sensitive)

    Ran react-native run-ios in project directory

    In case you are using a Mac M1 architecture it is not directly compatible with Cocoapods. If you encounter issues when installing pods, you can solve it by running:

  • sudo arch -x86_64 gem install ffi
  • arch -x86_64 pod install
  • These commands install the ffi package, to load dynamically-linked libraries and let you run the pod install properly, and runs pod install with the proper architecture.

    Source: https://reactnative.dev/docs/environment-setup see "Note for Mac M1 users"

    What worked for me was to rename the project by removing the special characters.

    Example: "project_marketplace" to "projectmarketplace"

    In this case, I redid the project with react-native init and copied the src and package.json folder.

    If you encountered issues with M1.

    Try installing the ffi package and running install again.

    sudo arch -x86_64 gem install ffi
    cd ios
    arch -x86_64 pod install
    

    Another solution that I found here works great, basically installing cacoapods with brew (and passing -arm64).

    sudo gem uninstall cocoapods
    arch -arm64 brew install cocoapods
    cd ios
    pod install
    

    In my case everything solved after re-cloning the repo and launching it again.

    Setup: Xcode 12.4 Mac M1

    In my case, none of the answers resolved it, since am not able to open .xcworkspace at all. But the legacy comment hinted to a RN to Xcode <> compatibility issue, so i tried all the previous RN Versions and all below RN@0.64 seem to work with xcode 11.3.1 npx react-native init projectName --version 0.62.0

    Thanks

    Below work for me though I encounter error code 65 due to I rename an existing project name to a new name which I did for all the files within the project. My solution was :-

  • At ios folder level open xworkspace with xcode.
  • Click on file tab then click on workspace settings.
  • I clicked on advance then I select xcode default then I clicked on close button.
  • I clicked on scheme tab which is beside the stop button at the right then I clicked on edit scheme.
  • When the edit scheme opened I clicked on build tab then I click on manage scheme button.
  • I selected scheme of my project name then I clicked the minus(-) button to delete it then I clicked on close
  • I clicked on clean build folder then when its complete I clicked on build tab to rebuild the project.
  • I clicked on play button which i selected the simulator I want then everything work perfectly again.
  • I too had an issue with react-native-vector-icons causing this. I still wanted to use the icons though, and I was using VSCode

    Workaround was to more or less the same as the manual instructions from the docs but a little different.

  • npm install --save react-native-vector-icons

  • copy the .tff files you want to use in node_modules -> react-native-vector-icons -> fonts

  • create a new folder "fonts" in src -> ios ...paste the .tff files in there

  • open 'info.plist' in src -> ios -> mobile

  • on the line above </dict> paste:

    <array>
        <string>AntDesign.ttf</string>
        <string>Entypo.ttf</string>
        <string>EvilIcons.ttf</string>
        <string>Feather.ttf</string>
        <string>FontAwesome.ttf</string>
        <string>FontAwesome5_Brands.ttf</string>
        <string>FontAwesome5_Regular.ttf</string>
        <string>FontAwesome5_Solid.ttf</string>
        <string>Foundation.ttf</string>
        <string>Ionicons.ttf</string>
        <string>MaterialIcons.ttf</string>
        <string>MaterialCommunityIcons.ttf</string>
        <string>SimpleLineIcons.ttf</string>
        <string>Octicons.ttf</string>
        <string>Zocial.ttf</string>
        <string>Fontisto.ttf</string>
      </array>
    

    ...or whatever fonts you selected.

    I ran react-native run-ios and it worked like a charm.

    For our project, we had to run the npx react-native link command in order to get the react native vector icons to show up on Android phones. But that added code to the ios/yourprojectname.xcodeproj/project.pbxproj file. And that caused the build to fail, throwing an error code 65 and listing out all the fonts that were duplicated.

    So, to fix the error, we just removed all of the new code that was added by the npx react-native link command.

    If you've built/run your app previous from Xcode and want to go back to using the terminal you need to clean your build folder. Go to product -> Clean Build Folder

    In my case it was an issue between different installations of npm installed via nvm and homebrew which somehow messed up my setup.

    Building via Xcode usually works without solving the initial problem. I have solved it as follows. Notice, that this guide is suitable if you want to use nvm.

    First, we remove a possible installation of npm and yarn using brew as follows.

    brew uninstall npm
    brew uninstall yarn
    

    We might want to remove nvm as well.

    rm -rf "$NVM_DIR"
    

    Next, we reinstall nvm by executing the following command.

    curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.1/install.sh | <ShellOfYourCoice>
    

    Replace <ShellOfYourCoice> with bash if you are using bash, with zsh if you are using zsh.

    Add the following content to ~/.bash_profile (.bashrc) for bash or to ~/.zshrc for zsh (you might need to create these files).

    export NVM_DIR="$HOME/.nvm"
    [ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"  # This loads nvm
    [ -s "$NVM_DIR/bash_completion" ] && \. "$NVM_DIR/bash_completion"  # This loads nvm bash_completion
    

    For zsh, we might need to fix some permissions. Execute the following command.

    compaudit | xargs chmod g-w
    

    Then, source the shell of your choice. Verify the installation by executing the following.

    nvm --version
    which npm
    

    The last command should print something similar to the following.

    /Users/<userName>/.nvm/versions/node/v16.10.0/bin/npm
    

    If yarn were installed using npm previously, we first remove it.

    npm uninstall yarn
    

    Next, we reinstall it.

    npm i -g yarn
    

    These steps fixed the issue for me.

    error Failed to build iOS project. We ran "xcodebuild" command but it exited with error code 65 That was my error and i resolve this error with the following commands:-

    1- Uninstall Ruby with: brew uninstall ruby --force

    2-Uninstall CocoaPods. At first, try to list all CocoaPods versions / components with gem list --local | grep cocoapods. Then uninstall them one by one, in my case:

    1- sudo gem uninstall cocoapods

    2- sudo gem uninstall cocoapods-core

    3- sudo gem uninstall cocoapods-downloader ,cocoapods-plugins ,cocoapods-search ,cocoapods-trunk ,cocoapods-try

    3- As a next step I was able to reinstall ffi and then CocoaPods with: i) sudo arch -x86_64 gem install ffi ii) sudo arch -x86_64 gem install cocoapods

    Once done, I could run pod install as expected. Note that I had the Terminal open all the time in standard mode - no Rosetta required.

    If you're like me and tried to change the name of the TestApp-folder. Notice the last line in the warning:

    xcodebuild: error: The workspace named "TestApp2" does not contain a scheme named "TestApp-tvOS". The "-list" option can be used to find the names of the schemes in the workspace.

    Not changing the TestApp name in the command nor after from this, helped me get rid of the message and the app was built:

    react-native init TestApp --version=react-native@npm:react-native-tvos@latest
    

    Some changes in Podfile haven't been updated. Maybe one of your native dependencies has changed.

  • expo prebuild --clean
  • cd ios
  • pod install
  • yarn iOS
  • Had the same problem again with the error No such module 'ExpoModulesCore', and the above solution didn't work. This time this code in Podfile saved me:

    installer.pods_project.build_configurations.each do |config|
          config.build_settings["EXCLUDED_ARCHS[sdk=iphonesimulator*]"] = "arm64"
    

    found it here https://github.com/expo/expo/issues/17511#issuecomment-1128657487

    In my case I did just nee to reinstall my dependencies run yarn && cd ios && pod install thanks. – TMin Mar 22, 2022 at 16:56 It's not strictly true that the AppDelegate.m relies on the Podfile. The podfile specifies the native ios libs to be to be imported for your project. This includes native code that is used by RN Libs that you may be using, and if you are using a hybrid app, native libs that could be used elsewhere in your app. The AppDelegate.m may or may not import these libraries. – TMin Mar 22, 2022 at 17:00

    there was some issue while creating the app so in my case i just deleted the package-lock.json and did npm i

    after that

    cd ios/ and pod install

    deleting package-lock or yarn.lock is not recommended. Mere rm-rf node_modules then npm i or yarn might be enough – MCH Oct 10, 2021 at 14:06 I created new React-Native project, but its not running on my iOS simulator and getting this error See more linked questions
  •