-
Notifications
You must be signed in to change notification settings - Fork 24.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fbsdk IOS - framework not found CoreServices for architecture i386 #25063
Comments
I have : package.json Which SDK should I install ? |
You should use lower version of fbsdk. So or You can upgrade xcode version to 10.x |
It is ok using react-native-fbsdk ^0.6.0 + FacebookSDKs-iOS-4.32.0 + Build Active architecture Only : Yes but when I set Build Active architecture Only : NO, I get this error : |
It means that fbsdk doesn't include i386 binary. Closing this issue because it's not related to React Native. |
I am using FBSDK with RNN2, I get this issue when I compile IOS xcode project
ld: framework not found CoreServices for architecture i386
clang: error: linker command failed with exit code 1 (use -v to see invocation)
React Native Environment Info:
System:
OS: macOS Sierra 10.12.6
Binaries:
Node: 11.13.0 - /usr/local/bin/node
Yarn: 1.15.2 - /usr/local/bin/yarn
npm: 6.9.0 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 11.2, macOS 10.13, tvOS 11.2, watchOS 4.2
Android SDK:
API Levels: 26, 28
Build Tools: 27.0.2, 27.0.3, 28.0.3
System Images: android-27 | Google APIs Intel x86 Atom, android-28 | Google Play Intel x86 Atom
IDEs:
Android Studio: 3.3 AI-182.5107.16.33.5314842
Xcode: 9.2/9C40b - /usr/bin/xcodebuild
npmPackages:
react: 16.8.3 => 16.8.3
react-native: 0.59.8 => 0.59.8
npmGlobalPackages:
create-react-native-web-app: 0.1.14
react-native-cli: 2.0.1
react-native-git-upgrade: 0.2.7
I set with Xcode :
Architecture : $(ARCHS_STANDARD)
Base SDK : 11.2
Build Active architecture Only : NO
Valid Architecture : arm64 armv7 armv7s i386
Can you give me help ?
The text was updated successfully, but these errors were encountered: