question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Xcode 11 release build Yoga.cpp compiling error

See original GitHub issue

Impossible to assemble release iOS build with latest Xcode 11.0 or 11.1. During assembling release build we can see Yoga.cpp compiling error:

error: non-portable path to file ‘“/Users/distiller/mobile-web-app/ios/Pods/Target Support Files/yoga/yoga-prefix.pch”’; specified path differs in case from file name on disk [-Werror,-Wnonportable-include-path]

Full logs:

Building library libReact-jsiexecutor.a
[15:22:29]: ▸ Building library libReact-jsiexecutor.a
[15:22:30]: ▸ Compiling log.cpp
[15:22:30]: ▸ ❌  error: non-portable path to file ‘“/Users/distiller/mobile-web-app/ios/Pods/Target Support Files/yoga/yoga-prefix.pch”’; specified path differs in case from file name on disk [-Werror,-Wnonportable-include-path]
[15:22:30]: ▸ Compiling experiments.cpp
[15:22:30]: ▸ Compiling event.cpp
[15:22:30]: ▸ Compiling Yoga.cpp
[15:22:30]: ▸     The iOS deployment target ‘IPHONEOS_DEPLOYMENT_TARGET’ is set to 7.0, but the range of supported deployment target versions is 8.0 to 13.1.99. (in target ‘react-native-version-number’ from project ‘Pods’)
[15:22:30]: ▸     The iOS deployment target ‘IPHONEOS_DEPLOYMENT_TARGET’ is set to 6.0, but the range of supported deployment target versions is 8.0 to 13.1.99. (in target ‘RSKImageCropper’ from project ‘Pods’)
[15:22:30]: ▸ ** ARCHIVE FAILED **
[15:22:30]: ▸ The following build commands failed:
[15:22:30]: ▸     CompileC /Users/distiller/Library/Developer/Xcode/DerivedData/Brandgility-ccncokfacuuibwcjplhtkspodqby/Build/Intermediates.noindex/ArchiveIntermediates/Brandgility/IntermediateBuildFilesPath/Pods.build/Release-iphoneos/Yoga.build/Objects-normal/armv7/event.o /Users/distiller/mobile-web-app/node_modules/react-native/ReactCommon/yoga/yoga/event/event.cpp normal armv7 c++ com.apple.compilers.llvm.clang.1_0.compiler
[15:22:30]: ▸ (1 failure)

With Xcode 10.2.1 everything works fine.

React Native version:

System:
    OS: macOS 10.14.6
    CPU: (4) x64 Intel(R) Core(TM) i5-6360U CPU @ 2.00GHz
    Memory: 105.80 MB / 8.00 GB
    Shell: 3.2.57 - /bin/bash
  Binaries:
    Node: 12.4.0 - ~/.nvm/versions/node/v12.4.0/bin/node
    Yarn: 1.19.0 - /usr/local/bin/yarn
    npm: 6.9.0 - ~/.nvm/versions/node/v12.4.0/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  SDKs:
    iOS SDK:
      Platforms: iOS 13.0, DriverKit 19.0, macOS 10.15, tvOS 13.0, watchOS 6.0
    Android SDK:
      API Levels: 23, 24, 25, 26, 27, 28
      Build Tools: 23.0.1, 25.0.1, 26.0.1, 26.0.2, 26.0.3, 27.0.3, 28.0.0, 28.0.3
      System Images: android-23 | Intel x86 Atom_64, android-23 | Google APIs Intel x86 Atom, android-23 | Google APIs Intel x86 Atom_64, android-25 | Google APIs Intel x86 Atom, android-27 | Google Play Intel x86 Atom, android-28 | Google APIs Intel x86 Atom
  IDEs:
    Android Studio: 3.5 AI-191.8026.42.35.5791312
    Xcode: 11.0/11A420a - /usr/bin/xcodebuild
  npmPackages:
    @react-native-community/cli: 2.9.0 => 2.9.0 
    react: 16.9.0 => 16.9.0 
    react-native: 0.61.2 => 0.61.2 

Steps To Reproduce

  1. Run assembling release build
  2. Use Xcode 11.0 or 11.1
  3. Check Build error during compiling Yoga.cpp

Expected result: Build assembled correctly without Yoga.cpp compiling error.

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Reactions:13
  • Comments:15 (1 by maintainers)

github_iconTop GitHub Comments

10reactions
Bernabe-Felixcommented, Jan 26, 2020

Just in case anyone happens on this thread looking for solutions to this issue…

This likely happened because the yoga directory and files had their names changed to Yoga. MacOS, by default, is a case insensitive file system, so if you had your Pod folder committed in Git, the rename was probably not detected.

There’s probably a more elegant way to do this, but you can fix the issue with two commits. First, rename all instances of “yoga” under ios/Pods/Target Support Files/yoga (including the directory itself) to “yogurt” or something. Commit your changes. Now change the “yogurt” files and directory to Yoga (note the uppercase Y). Commit your changes. Any new clones of your git repo should now have the proper casing.

Or you could git rm --cached Pods/ -r && git add .

10reactions
dougkeencommented, Jan 17, 2020

Just in case anyone happens on this thread looking for solutions to this issue…

This likely happened because the yoga directory and files had their names changed to Yoga. MacOS, by default, is a case insensitive file system, so if you had your Pod folder committed in Git, the rename was probably not detected.

There’s probably a more elegant way to do this, but you can fix the issue with two commits. First, rename all instances of “yoga” under ios/Pods/Target Support Files/yoga (including the directory itself) to “yogurt” or something. Commit your changes. Now change the “yogurt” files and directory to Yoga (note the uppercase Y). Commit your changes. Any new clones of your git repo should now have the proper casing.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Xcode 12 beta 4 - error compiling … | Apple Developer Forums
Try upgrading the Project Xcode compatibility to Xcode 11 and change the VALIDARCHS to $(ARCHSSTANDARD). It worked for me. Posted 2 years ago...
Read more >
Xcode 12 Problems: "Build input file cannot be found "
Symptoms: "build input file could not be found..." when running on device in debug AND release. Simulator worked fine.
Read more >
How to fix "Build input file cannot be found" error in Xcode
Solution · Open "Project Navigator" (Menu View > Navigators > Project ⌘ - command + 1 ). · You will see a group...
Read more >
RN IOS xproj build failed : main.jsbundle does not exist
Bitrise Build Issue Report template Foosby.app/main.jsbundle does not exist. This must be a bug with Last lines of the Xcode's build log: ...
Read more >
[Solved]-Connecting code to UI in storyboard with multiple ...
... question Connecting code to UI in storyboard with multiple ViewControllers, Xcode. ... C++ Build Failed on Xcode OSX with multiple errors File...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found