Can't build on Mac M1 with 11.5.0

[vesparny]

How frequently does the bug occur?

Always

Description

Since version 11.5.x I am unable to run the project on Apple silicon.
Using RN 0.71.3

Stacktrace & log output

info Found Xcode workspace "MyApp.xcworkspace"
info Found booted iPhone 13
info Launching iPhone 13
info Building (using "xcodebuild -workspace MyApp.xcworkspace -configuration Debug -scheme MyApp -destination id=F9D05ED7-9D66-4017-B18C-FE9E6B107B6F")
▸ Running script 'Create Symlinks to Header Folders'
▸ Running script 'Create Symlinks to Header Folders'
▸ Running script 'Create Symlinks to Header Folders'
▸ Running script 'Start Packager'
▸ Linking MyApp

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



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


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 MyApp.xcworkspace.

Can you reproduce the bug?

Always

Reproduction Steps

react-native run-ios

Version

11.5.0

What services are you using?

Local Database only

Are you using encryption?

Yes

Platform OS and version(s)

any

Build environment

Which debugger for React Native: ..
sas

Cocoapods version

11.5.0

[stevenmathers]

well, I dont know about M1, but I am getting a similar error building on App Center, although it builds fine locally on my intel mac mini

xcode version 13.4.1 node version 16, react native 71.3, realm-js 11.5.0

where should I look?

thanks

======

Undefined symbols for architecture arm64:
"_objc_msgSend$allBundles", referenced from:
realm::copy_bundled_realm_files() in librealm-js-ios.a(platform.o)

and a bunch more like this...

ld: symbol(s) not found for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
ARCHIVE FAILED

[superdorvil]

I'm having this issues as well. I'm using react-native and android works just fine. But I have no idea how to fix this issue on IOS.

[nirinchev]

Is everyone affected by this using Xcode 13? If that's the case, then it is likely related to https://developer.apple.com/forums/thread/716965 as we switched to building the native binaries with Xcode 14 on CI. Based on the comment on the issue, we may need to add -fno-objc-msgsend-selector-stubs when building the native binary.

As a temporary workaround, you can upgrade Xcode to the latest version. @kneth assigning this back to you it's more involved than I hoped. Looks like it's a simple fix, but I don't have anything RN setup to test that it works.

[vesparny]

@nirinchev I confirm the issue happens using Xcode 13. Didn't have a chance to try other versions

[stevenmathers]

Is everyone affected by this using Xcode 13? If that's the case, then it is likely related to https://developer.apple.com/forums/thread/716965 as we switched to building the native binaries with Xcode 14 on CI. Based on the comment on the issue, we may need to add -fno-objc-msgsend-selector-stubs when building the native binary.

As a temporary workaround, you can upgrade Xcode to the latest version. @kneth assigning this back to you it's more involved than I hoped. Looks like it's a simple fix, but I don't have anything RN setup to test that it works.

yes, can confirm that simply using xcode 14 on App Center fixed my issue, altho as I said before, I was able to build the identical app on my local machine which has xcode 13 installed, so its not consistent for whatever reason. Thats all I can say.

[kneth]

can confirm that simply using Xcode 14

Thank you for the confirmation. We will work on a fix and get a release out as soon as possible but if you can, please upgrade to Xcode 14.

[kneth]

I have a PR for it in #5531 but I haven't verified that the artefacts can be used with Xcode 13.

[kneth]

Released in v11.5.2

[vesparny]

@kneth same issue happening again with xcode 14 and [email protected]

[kneth]

@vesparny Please create a new issue