ExpoKit iOS build error: duplicated symbols for architecture x86_64
🐛 Bug Report
https://github.com/pedro-lb/expokit-duplicated-symbols
Environment
pedrobini@Pedros-MacBook-Pro ios % expo diagnostics
Expo CLI 3.11.7 environment info:
System:
OS: macOS 10.15.2
Shell: 5.7.1 - /bin/zsh
Binaries:
Node: 12.12.0 - /usr/local/bin/node
Yarn: 1.19.1 - /usr/local/bin/yarn
npm: 6.11.3 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
IDEs:
Android Studio: 3.5 AI-191.8026.42.35.5900203
Xcode: 11.3.1/11C504 - /usr/bin/xcodebuild
npmGlobalPackages:
expo-cli: 3.11.7
Target: iOS
Steps to Reproduce
Clone our repo that reproduces the problem:
git clone https://github.com/pedro-lb/expokit-duplicated-symbols
Follow setup guide:
- Run
yarn install.
- Go into
ios directory and run pod install: cd ios && pod install.
- Start the expo server with
yarn start --clear.
- Open the project in XCode, click
Build (or hit ⌘ + B).
You should hit the error: duplicate symbols for architecture x86_64.
Expected Behavior
The app builds successfully and works.
Actual Behavior
Build error when trying to build for iOS:
ld: 90 duplicate symbols for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
You can find the full build error here.
Reproducible Demo
https://github.com/pedro-lb/expokit-duplicated-symbols
Solutions already attempted:
We've tried a few fixes as listed below.
❌ Upgrading to XCode 10's new build system:
Yeah, we're late to the party and still using the old build system. Although when trying to use the new one, the same error still happens and it doesn't build.
ld: 90 duplicate symbols for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
❌ Manually removing conflics in Podfile:
We've tried to manually remove conflicting links on a post-install hook in our Podfile. The script looks as below.
The links were removed but that solution does not work. Same error happens (duplicate symbols for architecture x86_64).
post_install do |installer|
installer.pods_project.targets.each do |target|
if %w(RNScreens RNCMaskedView react-native-safe-area-context).include?(target.name)
target.remove_from_project
end
end
end
❌ Disabling autolink for conflicting dependencies on react-native.config.js:
By disabling React Native's autolink for the conflicting dependencies in react-native.config.js file, the project still does not build, and a new error appears.
module.exports = {
dependencies: {
...,
'@react-native-community/masked-view': {
platforms: {
ios: null,
},
},
'react-native-safe-area-context': {
platforms: {
ios: null,
},
},
'react-native-screens': {
platforms: {
ios: null,
},
},
},
};
A new error happens when trying to build:
ld: library not found for -lRNCMaskedView
clang: error: linker command failed with exit code 1 (use -v to see invocation)
❌ Removing conflicting dependencies from package.json:
By removing the conflicting dependencies below from package.json and re-installing our modules and pods (by running the commands below).
yarn remove @react-native-community/masked-view react-native-screens react-native-safe-area-context
rm -rf node_modules yarn.lock
yarn install
cd ios
rm -rf Podfile.lock Pods
pod install
> build on XCode
On this repository, the project builds and works correctly! But I guess this happens since we don't really use these dependencies here (they were just installed via yarn add). On our project another error happens during build, since we actually import and use these dependencies:
ld: library not found for -lRNCMaskedView
clang: error: linker command failed with exit code 1 (use -v to see invocation)
❌ Tinkering with XCode build settings:
We've tried to change a few XCode build settings as mentioned in a few Stack Overflow posts, but none of them worked.
- ❗ Removing
-ObjC flag Other Linker Flags in XCode Build Settings: It builds! But doesn't work as stated in its topic below.
- 😵 Setting
No Common Blocks to NO under Build Settings.
- 😵 Setting
Enable Testability to NO under Build Settings.
- 😵 Running in production and debug modes.
- 😵 Removing
Link Binary with Libraries under Build Phases.
- 😵 Removing duplicated (there were none) items in
Compile Sources under Build Phases.
- 😵 Removing duplicated (there were none) libraries in
Libraries folder in XCode.
❓ Removing -ObjC flag in Other Linker Flags under XCode's Build Settings:
By removing -ObjC flag from Other Linker Flags (located in Build Settings) on XCode, the project builds!
...but it immediately force-closes after opening 😞. The error below pops up.
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[RCTRootView setReactTag:]: unrecognized selector sent to instance 0x7f84f6e10f40'
terminating with uncaught exception of type NSException
abort() called
CoreSimulator 681.17.2 - Device: iPhone 11 (0974E59B-9AA8-4E0B-915D-A083AB917955) - Runtime: iOS 13.3 (17C45) - DeviceType: iPhone 11
When looking at the exception that caused the app to crash with Mac OS console:
2020-01-17 14:35:13.414 [info][tid:main][RCTBridge.m:145] Class EXDisabledRedBox was not exported. Did you forget to use RCT_EXPORT_MODULE()?
Apparently, -ObjC is necessary to correctly build all the dependencies.
❌ Add React dependencies to Podfile:
When seeing the error above, while still without -ObjC flag in Other Linker Flags under XCode's Build Settings, we've tried adding the missing pods as described above (Did you forget to use RCT_EXPORT_MODULE()?) in our Podfile:
pod 'React', :path => '../node_modules/react-native/'
pod 'React-Core', :path => '../node_modules/react-native/React'
pod 'React-DevSupport', :path => '../node_modules/react-native/React'
pod 'React-fishhook', :path => '../node_modules/react-native/Libraries/fishhook'
pod 'React-RCTActionSheet', :path => '../node_modules/react-native/Libraries/ActionSheetIOS'
pod 'React-RCTAnimation', :path => '../node_modules/react-native/Libraries/NativeAnimation'
pod 'React-RCTBlob', :path => '../node_modules/react-native/Libraries/Blob'
pod 'React-RCTImage', :path => '../node_modules/react-native/Libraries/Image'
pod 'React-RCTLinking', :path => '../node_modules/react-native/Libraries/LinkingIOS'
pod 'React-RCTNetwork', :path => '../node_modules/react-native/Libraries/Network'
pod 'React-RCTSettings', :path => '../node_modules/react-native/Libraries/Settings'
pod 'React-RCTText', :path => '../node_modules/react-native/Libraries/Text'
pod 'React-RCTVibration', :path => '../node_modules/react-native/Libraries/Vibration'
pod 'React-RCTWebSocket', :path => '../node_modules/react-native/Libraries/WebSocket'
and we've also tried with:
pod 'React',
:path => "../node_modules/react-native",
:inhibit_warnings => true,
:subspecs => [
"Core",
"ART",
"RCTActionSheet",
"RCTAnimation",
"RCTCameraRoll",
"RCTGeolocation",
"RCTImage",
"RCTNetwork",
"RCTText",
"RCTVibration",
"RCTWebSocket",
"DevSupport",
"CxxBridge"
]
After running rm -rf Podfile.lock Pods && pod install, we've tried to build, but the same error happens.
2020-01-17 14:35:13.414 [info][tid:main][RCTBridge.m:145] Class EXDisabledRedBox was not exported. Did you forget to use RCT_EXPORT_MODULE()?
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot]")
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent
