Can't compile React Native iOS app to run on physical device, issue with React Native Firebase

Question

For some reason since recently, I cannot run my React Native app on a physical device from Xcode or even from the command line. I'm getting the following error:

duplicate symbol '_md5_block_data_order' in:
    /XXX/Library/Developer/Xcode/DerivedData/XXXX-bdrylwsxpcqgzvgkcljteyttcdmr/Build/Products/Debug-iphoneos/BoringSSL-GRPC/libBoringSSL-GRPC.a(md5.o)
    /XXX/project/ios/Pods/OpenSSL-Universal/ios/lib/libcrypto.a(md5_dgst.o)
ld: 1 duplicate symbol for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

However it works fine from a simulator. And I can upload the app to AppStoreConnect without any issue.

From what I understand it looks like the same symbol exists in 2 libraries. Not sure why, most likely one of the mobile app dependencies.

In the list of Pods installed I have both BoringSSL-GRPC (0.0.3) and OpenSSL-Universal (1.0.2.19)

BoringSSL is used by Firebase and OpenSSL is used by Flipper.

This is the list of third party dependencies I use:

  pod 'Firebase/Core', '~> 6.3.0'

  pod 'Firebase/Messaging', '~> 6.3.0'

  pod 'Firebase/Firestore', '~> 6.3.0'

  pod 'Firebase/Auth', '~> 6.3.0'

  pod 'TrustKit'

  pod 'Stripe', '16.0.0'

  pod 'Amplitude-iOS', '~> 4.5'

  pod 'Intercom', '~> 5.5.1'

  flipper_pods()

When I remove Firebase all together, it works fine and I can run my app on the device. But I need Firebase...

Any idea how to resolve this?

Thanks!

In which mode you are running the application? You might have to change it to debug mode. — Kishan Bharda, Jan 31 '20 at 18:15
I tried to remove Firebase from the project, I was able to run it on a device. But Firebase is needed on this app. — alexmngn, Feb 03 '20 at 09:59
Which RN version are you on? Flipper is fully implemented in RN 0.62 which is curently in RC and RN Firebase 6.x init template is curently on RN 0.61. — Christos Lytras, Feb 03 '20 at 19:25
Try to delete all Link Binary With Libraries and run pod install again, or try to link it manually — tuledev, Feb 06 '20 at 03:40
Do you have the same library in "Link Binary With Libraries" and "Pods"? If you do, remove the one from Libraries. — Ashwin Mothilal, Feb 09 '20 at 08:29
I'm having the same issue with `/node_modules/react-native-live-stream/ios/libs/NodeMediaClient.framework/NodeMediaClient(md5_dgst.o)` and ` /ios/build/MedicHub/Build/Products/Debug-iphoneos/BoringSSL-GRPC/libBoringSSL-GRPC.a(md5.o)` on rn 0.59.9 — Cristi Milea, Mar 05 '20 at 03:14

score 10 · Answer 1 · answered Apr 02 '20 at 13:14

This is a problem others are noticing as well https://github.com/invertase/react-native-firebase/issues/3384

The symptoms most are seeing look like:

Pods/OpenSSL-Universal/ios/lib/libcrypto.a(bio_lib.o)' does not contain bitcode. You must rebuild it with bitcode enabled (Xcode setting ENABLE_BITCODE), obtain an updated library from the vendor, or disable bitcode for this target. for architecture arm64

There is an upstream issue logged here https://github.com/facebook/flipper/issues/485 that was closed before it became clear it would be a bigger problem than expected.

I tested a workaround which is sub-optimal but functional for now until an OpenSSL library with bitcode is available in the transitive dependencies - the workaround is

disable bitcode for development (that is where flipper exists)
make sure you have dead code stripping turned on everywhere
enable bitcode for release mode

In my experience this worked for debug builds on local devices (where it failed before) and a TestFlight build in release mode worked

Hope this helps!

Disabling bitcode for Debug mode triggers all kinds of Swift problems. I have 15 additional issues when I put it to No. But having it on Yes, I only have only the one issue described above. — Benjamin Heinke, May 09 '20 at 18:05
Hi there. There are workarounds on other issues plus an install guide that instruct you to make a dummy Swift bridging header *and leave it in place*. This is also recommended https://fbflipper.com/docs/troubleshooting#build-errors-in-react-native - please note that I discussed this in the react-native-firebase issue tracker and the problem was ultimately resolved to these errors, and fixed - so it's a little hacky but it does work. https://github.com/invertase/react-native-firebase/issues/3384#issuecomment-626345098 — Mike Hardy, May 10 '20 at 19:14
@MikeHardy thank you. This workaround still works for **RN 0.63.4** and **XCode 12.4** — Christos Lytras, Feb 01 '21 at 18:34

score 2 · Answer 2 · answered Oct 08 '20 at 20:44

I had the same issue for latest RN and firebase modules. There is PR https://github.com/facebook/flipper/pull/1171 in the flipper, that will fix this issue, but it is still not merged to master, and it seems that 1.0.2.19 version is used for OpenSSL.

So to run your app in real devices I just disabled Flipper. To do it you need to:

comment all Flipper's lines in your pod file and in AppDelegate.m file.
remove yarn.lock file and pods folder
run pod install again.

After these steps all will work.

score -1 · Answer 3 · answered Jan 31 '20 at 15:55

-1

clean the project and then run, the libraries were compiled for the simulator and duplicates were created for the device

answered Jan 31 '20 at 15:55

Lena Bru

12,299
9
53
109

I've tried, doesn't work. The issue is reproducible also on my colleague's computer. – alexmngn Jan 31 '20 at 17:25

score -1 · Answer 4 · answered Feb 07 '20 at 06:27

Like you mentioned it is due to multiple generated files, one thing you can do is clean the entire folder and before running it restart the computer and xcode .Also Clear the derived data folder for Xcode. and Rebuild it, delete any older versions of the RN APP in your "Mobile Device" the caches could also provide this . Also hoping you did not change the target name recently?

Can't compile React Native iOS app to run on physical device, issue with React Native Firebase

4 Answers4