New React Native project won't build on Xcode 13. #31733

adrianbartyczak · 2021-06-16T18:32:39Z

Description

Running a new React Native project on Xcode 13 beta throws the following error:

ld: warning: Could not find or use auto-linked library 'swift_Concurrency'
ld: warning: Could not find or use auto-linked library 'swiftFileProvider'
Undefined symbols for architecture x86_64:
  "__swift_FORCE_LOAD_$_swiftFileProvider", referenced from:
      __swift_FORCE_LOAD_$_swiftFileProvider_$_YogaKit in libYogaKit.a(YGLayoutExtensions.o)
     (maybe you meant: __swift_FORCE_LOAD_$_swiftFileProvider_$_YogaKit)
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

/Users/admin/testpro/ios/Pods/Pods.xcodeproj: warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 15.0.99. (in target 'Flipper-Glog' from project 'Pods')
/Users/admin/testpro/ios/Pods/Pods.xcodeproj: warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.4, but the range of supported deployment target versions is 9.0 to 15.0.99. (in target 'Flipper-PeerTalk' from project 'Pods')
/Users/admin/testpro/ios/Pods/Pods.xcodeproj: warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 15.0.99. (in target 'YogaKit' from project 'Pods')
/Users/admin/testpro/ios/Pods/Pods.xcodeproj: warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 15.0.99. (in target 'boost-for-react-native' from project 'Pods')
/Users/admin/testpro/ios/Pods/Pods.xcodeproj: warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 15.0.99. (in target 'Flipper-DoubleConversion' from project 'Pods')

2021-06-16 14:18:52.665 xcodebuild[28989:583546] [MT] DVTPlugInManager: Required plug-in compatibility UUID 42E1F17B-27B3-4DE8-92A8-DC76BA4F5921 for DVTCoreGlyphs.framework (com.apple.dt.DVTCoreGlyphs) not present
** BUILD FAILED **

The following build commands failed:
        Ld /Users/admin/Library/Developer/Xcode/DerivedData/testpro-bhjbeszkrctxppesyqiyhzyvzilq/Build/Products/Debug-iphonesimulator/testpro.app/testpro normal (in target 'testpro' from project 'testpro')

React Native version:

System:
    OS: macOS 11.4
    CPU: (4) x64 Intel(R) Core(TM) i7-8700B CPU @ 3.20GHz
    Memory: 4.20 GB / 8.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 16.3.0 - /usr/local/bin/node
    Yarn: Not Found
    npm: 7.15.1 - /usr/local/bin/npm
    Watchman: 2021.06.07.00 - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.10.1 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: DriverKit 21.0, iOS 15.0, macOS 12.0, tvOS 15.0, watchOS 8.0
    Android SDK: Not Found
  IDEs:
    Android Studio: Not Found
    Xcode: 13.0/13A5154h - /usr/bin/xcodebuild
  Languages:
    Java: Not Found
  npmPackages:
    @react-native-community/cli: Not Found
    react: 17.0.1 => 17.0.1 
    react-native: 0.64.2 => 0.64.2 
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

Steps To Reproduce

Initialize a project with npx react-native init testproject.
Run the project with npx react-native run-ios.

Expected Results

I expected the application to build.

The text was updated successfully, but these errors were encountered:

kelset · 2021-06-18T11:25:10Z

👋 Adrian, couple of quick questions:

are you building against iOS 14 or 15?
can you try with 0.65-rc.2 and see if it breaks there too?

Some folks have reported that their project have been building fine with Xcode 13

Via CLI and manually - android/app/build.gradle - ios/Podfile And update - package.json https://react-native-community.github.io/upgrade-helper/?from=0.64.2&to=0.65.0-rc.2 Builds on XCode 12.5 Build fails on XCode 13.0 beta: Undefined symbol: __swift_FORCE_LOAD_$_swiftFileProvider facebook/react-native#31733

leotm · 2021-06-19T16:03:31Z

Same error logs here with XCode 13.0 beta and 0.65-rc.2 referenced above ^

XCode 12.5 builds fine on both 0.64.2 and 0.65.0-rc.2

I'm on macOS Monterey 12.0 Beta too

leotm · 2021-06-20T11:05:11Z

Seems related to flipper, disabling it builds successfully for now as a temporary workaround

Podfile

- use_flipper!()
+ # use_flipper!()

pod install

ios/MyApp/AppDelegate.m

+ // #ifdef FB_SONARKIT_ENABLED
+ // #import <FlipperKit/FlipperClient.h>
+ // #import <FlipperKitLayoutPlugin/FlipperKitLayoutPlugin.h>
+ // #import <FlipperKitUserDefaultsPlugin/FKUserDefaultsPlugin.h>
+ // #import <FlipperKitNetworkPlugin/FlipperKitNetworkPlugin.h>
+ // #import <SKIOSNetworkPlugin/SKIOSNetworkAdapter.h>
+ // #import <FlipperKitReactPlugin/FlipperKitReactPlugin.h>

+ // static void InitializeFlipper(UIApplication *application) {
+ //   FlipperClient *client = [FlipperClient sharedClient];
+ //   SKDescriptorMapper *layoutDescriptorMapper = [[SKDescriptorMapper alloc] initWithDefaults];
+ //   [client addPlugin:[[FlipperKitLayoutPlugin alloc] initWithRootNode:application withDescriptorMapper:layoutDescriptorMapper]];
+ //   [client addPlugin:[[FKUserDefaultsPlugin alloc] initWithSuiteName:nil]];
+ //   [client addPlugin:[FlipperKitReactPlugin new]];
+ //   [client addPlugin:[[FlipperKitNetworkPlugin alloc] initWithNetworkAdapter:[SKIOSNetworkAdapter new]]];
+ //   [client start];
+ // }
+ // #endif

...

+ // #ifdef FB_SONARKIT_ENABLED
+ //   InitializeFlipper(application);
+ // #endif

I've raised the issue here: facebook/flipper#2477

gazedash · 2021-06-24T20:28:05Z

Can flopper be opt in and not too invasive in project code? Too much problems for nothing.
Project was not building on 12.5, removed it and it worked

peterkuiper · 2021-07-15T12:59:46Z

@leotm You might want to checkout this comment: zalando/SwiftMonkey#80 (comment)

fkgozali · 2021-08-23T19:55:01Z

We believe this fixed it (in main): eb93886

cc @sammy-SC

alexisbronchart · 2021-08-26T12:28:07Z

We believe this fixed it (in main): eb93886

cc @sammy-SC

Just tested. It works™️

sammy-SC · 2021-09-13T10:32:07Z

@alexisbronchart confirmed that eb93886 fixes build issue in Xcode 13. I'm closing this.

nithinyell · 2021-09-21T13:07:34Z

@alexisbronchart confirmed that eb93886 fixes build issue in Xcode 13. I'm closing this.

This PR did not fixed my pipeline

@sammy-SC

Mac OS 11
Xcode 13 

⚠️  /Users/runner/work/1/s/myApp/ios/Pods/Headers/Private/Flipper-Folly/folly/synchronization/DistributedMutex-inl.h:1519:38: implicit conversion loses integer precision: 'unsigned long long' to 'std::uintptr_t' (aka 'unsigned long') [-Wshorten-64-to-32]

        tryWake(publishing, current, value, next, waker, sleepers, iter, task);
        ^


    no rule to process file '/Users/runner/work/1/s/myApp/ios/Pods/Flipper-RSocket/rsocket/benchmarks/CMakeLists.txt' of type 'text' for architecture 'arm64' (in target 'Flipper-RSocket' from project 'Pods')
    no rule to process file '/Users/runner/work/1/s/myApp/ios/Pods/Flipper-RSocket/rsocket/benchmarks/README.md' of type 'net.daringfireball.markdown' for architecture 'arm64' (in target 'Flipper-RSocket' from project 'Pods')
    no rule to process file '/Users/runner/work/1/s/myApp/ios/Pods/Flipper-RSocket/rsocket/README.md' of type 'net.daringfireball.markdown' for architecture 'arm64' (in target 'Flipper-RSocket' from project 'Pods')
    no rule to process file '/Users/runner/work/1/s/myApp/ios/Pods/Flipper-RSocket/rsocket/benchmarks/CMakeLists.txt' of type 'text' for architecture 'armv7' (in target 'Flipper-RSocket' from project 'Pods')
    no rule to process file '/Users/runner/work/1/s/myApp/ios/Pods/Flipper-RSocket/rsocket/benchmarks/README.md' of type 'net.daringfireball.markdown' for architecture 'armv7' (in target 'Flipper-RSocket' from project 'Pods')
    no rule to process file '/Users/runner/work/1/s/myApp/ios/Pods/Flipper-RSocket/rsocket/README.md' of type 'net.daringfireball.markdown' for architecture 'armv7' (in target 'Flipper-RSocket' from project 'Pods')
** BUILD FAILED **


The following build commands failed:
	CompileC /Users/runner/Library/Developer/Xcode/DerivedData/myApp-gnzuyhqjbxtcmgdefpewjfijhdya/Build/Intermediates.noindex/Pods.build/Release-iphoneos/Flipper-Folly.build/Objects-normal/armv7/DistributedMutex.o /Users/runner/work/1/s/myApp/ios/Pods/Flipper-Folly/folly/synchronization/DistributedMutex.cpp normal armv7 c++ com.apple.compilers.llvm.clang.1_0.compiler (in target 'Flipper-Folly' from project 'Pods')

gcrozariol · 2021-09-21T13:57:57Z

I just created a new Swift file + Bridging Header with literally nothing inside these files and the build completed successfully. Have no clue why this worked, but it did lol

heberuriegas · 2021-09-21T16:05:30Z

Same, swift file and bridge header works.

debianw · 2021-09-21T22:55:25Z

Same here, just created a new Swift file + Bridging Header and it worked!!. I don't know why Lol

nithinyell · 2021-09-22T13:59:53Z

I have updated to react-native 0.65.0 and able to build in Xcode 13(13A233)

ksarna · 2021-09-23T16:41:19Z

Bridging Header didn't help in rn 0.63. I had to turn off flipper

debianw · 2021-09-23T17:03:53Z

Bridging Header didn't help in rn 0.63. I had to turn off flipper

I'm also using 0.63, Try this for flipper:

use_flipper!({ 'Flipper-Folly' => '2.5.3', 'Flipper' => '0.87.0', 'Flipper-RSocket' => '1.3.1' })

EvanBacon · 2021-09-23T20:29:18Z

Someone building a project with expo run:ios, that was bootstrapped with React Native community CLI, will encounter the same error, but formatted as:

⚠️  ld: Could not find or use auto-linked library 'swift_Concurrency'
⚠️  ld: Could not find or use auto-linked library 'swiftFileProvider'
⚠️  ld: Could not find or use auto-linked library 'swiftDataDetection'
❌  Undefined symbols for architecture x86_64
┌─ Symbol: __swift_FORCE_LOAD_$_swiftDataDetection
└─ Referenced from: __swift_FORCE_LOAD_$_swiftDataDetection_$_YogaKit in libYogaKit.a(YGLayoutExtensions.o)

❌  ld: symbol(s) not found for architecture x86_64

❌  clang: error: linker command failed with exit code 1 (use -v to see invocation)

Solution

Create a bridging header, as described above.

xed ios to open the project
⌘+N - select swift file
Select "Create Bridging Header"
Rebuild expo run:ios should work as expected.

AbdelrahmanTealab · 2021-09-26T17:16:54Z

Can flopper be opt in and not too invasive in project code? Too much problems for nothing.
Project was not building on 12.5, removed it and it worked

I completely agree, everytime I make a project I have to go through this hassle with Flipper.
I dont understand why facebook does this, it's absurd.

nriccar · 2021-09-30T14:42:44Z

If you upgrade RN version and get to change the iOS target version to 11, don't forget to change it from Xcode under Build Settings => iOS Deployment Target.

nithinyell · 2021-09-30T14:45:12Z

#32301

danidaryaweesh · 2021-10-01T01:35:01Z

Doing the following fixed the issue for me in Xcode without disabling Flipper:

Go to Build Settings --> Search for "Search paths" and then add $(SDKROOT)/usr/lib/swift to "Library search paths"
Change "iOS deployment target" in Xcode to 11
Remove pods and build again , then it should work

I'm using RN 0.64.2

eliataylor · 2021-10-01T03:10:02Z

If you upgrade RN version and get to change the iOS target version to 11, don't forget to change it from Xcode under Build Settings => iOS Deployment Target.

@nriccar, what packages are you using and how many broke during the upgrade?

nriccar · 2021-10-01T08:57:25Z

If you upgrade RN version and get to change the iOS target version to 11, don't forget to change it from Xcode under Build Settings => iOS Deployment Target.

@nriccar, what packages are you using and how many broken during the upgrade?

Only one, react-native-view-pager. Why?

JeffPatricio · 2021-10-05T22:51:27Z

I'm using native react 0.64.0 and it worked for me after commenting out the use_flipper!() line In Podfile.

nikolavujkovic · 2021-11-13T14:49:04Z

Finally fixed this after so many headaches...

Using React Native 0.66 and in Podfile, if in the post_install section you have a line of code calling an "Xcode 12.5 M1 workaround" then you have to comment it out if you're using Xcode 13 or higher (I'm using 13.2 Beta).

Just to note, I'm using macOS Monterey, which doesn't allow Xcode 12.5.1 or other earlier versions. Also, I am using an M1 MacBook Air.

Applizone · 2021-12-01T03:50:52Z

I have follow leotm here and gcrozariol here and samridhgupta here and Saveen here but I'm still having the error while build.

I already publish the app last month and turn off mac. And when I open to do some change to code, the error shows up.
These are the less error after I comment flipper. If not, it will show more than this on the Xcode issue navigator

Showing Recent Messages
Could not find or use auto-linked library 'swiftSwiftOnoneSupport'
Could not find or use auto-linked library 'swiftObjectiveC'
Could not find or use auto-linked library 'swiftCoreGraphics'
Could not find or use auto-linked library 'swiftCore'
Could not find or use auto-linked library 'swiftDispatch'
Could not find or use auto-linked library 'swiftCoreFoundation'
Could not find or use auto-linked library 'swiftFoundation'
Could not find or use auto-linked library 'swiftDarwin'
Undefined symbol: __swift_FORCE_LOAD_$_swiftCoreFoundation
Undefined symbol: __swift_FORCE_LOAD_$_swiftDispatch
Undefined symbol: __swift_FORCE_LOAD_$_swiftDarwin
Undefined symbol: __swift_FORCE_LOAD_$_swiftObjectiveC
Undefined symbol: __swift_FORCE_LOAD_$_swiftCoreGraphics
Undefined symbol: __swift_FORCE_LOAD_$_swiftFoundation

Why is it suddenly happening?

mercpls · 2021-12-02T01:18:30Z

⌘+N - select swift file

Select "Create Bridging Header"

Hi Evan, I don't see the 'Create bridging header' option after creating a swift file. I just get a blank swift file in the root dir it looks like.

personjerry · 2021-12-13T21:45:09Z

Looks like this will be fixed in 0.67 https://github.com/facebook/react-native/pull/32284/files but for anyone looking for a workaround see my comment on the Flipper thread: facebook/flipper#3150 (comment)

EvanBacon · 2021-12-13T21:58:24Z

@mercpls Xcode can be buggy, create a bridging header manually or use Expo's new custom managed workflow to fix.

Rebsos · 2022-06-16T23:30:34Z

If you recently upgraded nodejs with nvm and got this error. Try this:
https://stackoverflow.com/a/72652877/3585272

adrianbartyczak added the Needs: Triage 🔍 label Jun 16, 2021

kelset added the Platform: iOS iOS applications. label Jun 18, 2021

sammy-SC closed this as completed Sep 13, 2021

ease-space mentioned this issue Sep 21, 2021

support xcode 13 Agontuk/react-native-geolocation-service#313

Closed

Valyria1995 mentioned this issue Sep 27, 2021

Unable to debug after updating ios15 emulator #32269

Closed

facebook locked as resolved and limited conversation to collaborators Sep 13, 2022

react-native-bot added the Resolution: Locked This issue was locked by the bot. label Sep 13, 2022

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

New React Native project won't build on Xcode 13. #31733

New React Native project won't build on Xcode 13. #31733

adrianbartyczak commented Jun 16, 2021 •

edited

Loading

kelset commented Jun 18, 2021 •

edited

Loading

leotm commented Jun 19, 2021

leotm commented Jun 20, 2021 •

edited

Loading

gazedash commented Jun 24, 2021 •

edited

Loading

peterkuiper commented Jul 15, 2021 •

edited

Loading

fkgozali commented Aug 23, 2021

alexisbronchart commented Aug 26, 2021

sammy-SC commented Sep 13, 2021

nithinyell commented Sep 21, 2021

gcrozariol commented Sep 21, 2021

heberuriegas commented Sep 21, 2021

debianw commented Sep 21, 2021

nithinyell commented Sep 22, 2021

ksarna commented Sep 23, 2021

debianw commented Sep 23, 2021 •

edited

Loading

EvanBacon commented Sep 23, 2021

AbdelrahmanTealab commented Sep 26, 2021

nriccar commented Sep 30, 2021

nithinyell commented Sep 30, 2021

danidaryaweesh commented Oct 1, 2021 •

edited

Loading

eliataylor commented Oct 1, 2021 •

edited

Loading

nriccar commented Oct 1, 2021

JeffPatricio commented Oct 5, 2021

nikolavujkovic commented Nov 13, 2021

Applizone commented Dec 1, 2021

mercpls commented Dec 2, 2021

personjerry commented Dec 13, 2021

EvanBacon commented Dec 13, 2021

Rebsos commented Jun 16, 2022

New React Native project won't build on Xcode 13. #31733

New React Native project won't build on Xcode 13. #31733

Comments

adrianbartyczak commented Jun 16, 2021 • edited Loading

Description

React Native version:

Steps To Reproduce

Expected Results

kelset commented Jun 18, 2021 • edited Loading

leotm commented Jun 19, 2021

leotm commented Jun 20, 2021 • edited Loading

gazedash commented Jun 24, 2021 • edited Loading

peterkuiper commented Jul 15, 2021 • edited Loading

fkgozali commented Aug 23, 2021

alexisbronchart commented Aug 26, 2021

sammy-SC commented Sep 13, 2021

nithinyell commented Sep 21, 2021

gcrozariol commented Sep 21, 2021

heberuriegas commented Sep 21, 2021

debianw commented Sep 21, 2021

nithinyell commented Sep 22, 2021

ksarna commented Sep 23, 2021

debianw commented Sep 23, 2021 • edited Loading

EvanBacon commented Sep 23, 2021

Solution

AbdelrahmanTealab commented Sep 26, 2021

nriccar commented Sep 30, 2021

nithinyell commented Sep 30, 2021

danidaryaweesh commented Oct 1, 2021 • edited Loading

eliataylor commented Oct 1, 2021 • edited Loading

nriccar commented Oct 1, 2021

JeffPatricio commented Oct 5, 2021

nikolavujkovic commented Nov 13, 2021

Applizone commented Dec 1, 2021

mercpls commented Dec 2, 2021

personjerry commented Dec 13, 2021

EvanBacon commented Dec 13, 2021

Rebsos commented Jun 16, 2022

adrianbartyczak commented Jun 16, 2021 •

edited

Loading

kelset commented Jun 18, 2021 •

edited

Loading

leotm commented Jun 20, 2021 •

edited

Loading

gazedash commented Jun 24, 2021 •

edited

Loading

peterkuiper commented Jul 15, 2021 •

edited

Loading

debianw commented Sep 23, 2021 •

edited

Loading

danidaryaweesh commented Oct 1, 2021 •

edited

Loading

eliataylor commented Oct 1, 2021 •

edited

Loading