React Native FBSDK IOS build is failing - ios

Undefined symbols for architecture x86_64:
"___darwin_check_fd_set_overflow", referenced from:
_RAND_poll in libcrypto.a(rand_unix.o)
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
React Native version: 0.63
Xcode version: 11.3.1
react-native-fbsdk: 2.0.0

1° Solution (Recommended):
I also have this problem, it seems to occur in the Xcode 11.3.1 version. One way to fix is updating the version to 11.6.
2° Solution:
Comment all flipper function in podfile
Remove the function InitializeFlipper and Imports from appDelegate:
Run pod install:
Clean project;
Try again: react-native run-ios

Related

Flutter 2.5 on Mac M1 - symbol(s) not found for architecture arm64

I have a flutter project which uses a plugin written by a colleague (which is not there anymore). I develop on Mac M1.
Since I upgraded to Flutter 2.5, I cannot start my app on iOS in Debug-Mode.
It says
ld: symbol(s) not found for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
When I remove the dependency to this plugin, everything works.
I tried the following:
Change architecture-settings in xcode
Delete derived data
Delete podfile
Upgrade all dependencies
run pod repo-update
Does anyone have an idea?
Thanks!

Undefined symbols for architecture armv7: "query_call_back(callback_func_type)"

I've a problem to build iOS project after recently upgraded my project from Unity 5.6.4 to 2018.4.19f1. Everything is ok to export, build and run on my device, but if I archive the exported project, then the error occurs:
Undefined symbols for architecture armv7:
"query_call_back(callback_func_type)", referenced from:
il2cpp::vm::MetadataCache::Initialize() in
libil2cpp.a(External_il2cpp_il2cpp_libil2cpp_vm_6.o)
il2cpp::vm::MetadataCache::Initialize() in
libil2cpp.a(External_il2cpp_il2cpp_libil2cpp_vm_6.o) ld: symbol(s) not
found for architecture armv7 clang: error: linker command failed with
exit code 1 (use -v to see invocation)
Environments:
Unity 2018.4.19f1
Xcode 10.1 (10B61)
Appreciate if anyone can help!
Solution:
After hours of upgrade unity again to 2019.3.4f1 and fix mirror error.
Finally, Xcode archive the project successful!
This looks like a bug, try to upgrade Unity to the latest stable version.

iOS Unity Firebase Messenger Xcode Compile Error: FIRDynamicLinks

Building with Unity 2018.4.2 - Xcode 10.2 - Latest iOS Targets
Firebase Latest (6.1.1) for Unity with .Net 4
For Firebase We are using the following unity packages:
- FirebaseMessaging.unitypackage
- FirebaseAnalytics.unitypackage
Get the following Build Error in Xcode:
Undefined symbols for architecture arm64:
"_OBJC_CLASS_$_FIRDynamicLinks", referenced from:
objc-class-ref in libFirebaseCppApp.a(invites_receiver_internal_ios_aa7b75b2efc3269e88f1077e55250e5a.o)
ld: symbol(s) not found for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
On another Machine same error however armv7 target:
Undefined symbols for architecture armv7:
"_OBJC_CLASS_$_FIRDynamicLinks", referenced from:
objc-class-ref in libFirebaseCppApp.a(invites_receiver_internal_ios_aa7b75b2efc3269e88f1077e55250e5a.o)
ld: symbol(s) not found for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
Tested Solutions (no solution yet):
Obj-C to frameworks (was already there)
Updated Cocoa Pods to Latest
Deleted Developer/Xcode/DerivedData
Updated Cocoa Pods and deleted caches
The strangest thing is this only started happening on Monday, previously was working, nothing else was changed, so this leads to believe this is Google changed something in their Cocoa pods library which is linking agains't another package which is not included now.
Problem does not occur in the same Android Variant of the Project.
Solution:
It now requires you to also include and install Firebase: DynamicLinks in order to compile for iOS.
FirebaseDynamicLinks.unitypackage
So install the following package into your unity project from the download of Firebase Unity.

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

I'm using realm in my react-native project: https://github.com/kdnakt/pixelarn
After running ncu -u on my Mac to update react-native-elements to 1.0.0 and realm to 2.23.0, react-native run-ios would not start my app and I'm getting the following error:
realm::jsc::ObjectWrap<realm::js::CollectionClass<realm::jsc::Types> >::create_class() in libRealmReact.a(jsc_init.o)
...
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
** BUILD FAILED **
I saw some Github issues and tried rm -rf ~/Library/Developer/Xcode/DerivedData/ and rm -rf ios/build/ in my project directory, but still failing ... how can I start my react native app with react-native run-ios?
There was some modifications after upgrade to react native 0.58.5 and above versions.
Xcode Archive build failed with react native project
Try to manually link the JavaScriptCore.framework in "Link Binary With Libraries". I had the same problem and it work for me.
Image

MSCollectionViewCalendarLayout example: undefined symbols for architecture

I want that the example of MSCollectionViewCalendarLayout compiles and run.
Steps I've done:
installed CocoaPods
downloaded project
run pod install in the Example project directory
run the project from the .xcworkspace
Now I'm getting
Undefined symbols for architecture i386:
"_RKLogCoreDataError", referenced from:
___33-[RKEntityByAttributeCache load:]_block_invoke in libRestKit.a(RKEntityByAttributeCache.o)
___43-[RKManagedObjectImporter finishImporting:]_block_invoke in libRestKit.a(RKManagedObjectImporter.o)
ld: symbol(s) not found for architecture i386
clang: error: linker command failed with exit code 1 (use -v to see invocation)
I tried the tips from here, but the version seem to be wrong.
How can I run this project?
Problem is, that RestKit version (0.22.0) specified in the Podfile is not compatible with Cocoapods 0.38.x. Switching to latest version 0.24.1 should fix this:
In Podfile:
pod 'RestKit', '0.24.1'

Resources