Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

React Native build breaking - 64 bit support

See original GitHub issue

Hi folks,

Our react-native xcode build is failing to archive due to realm. I’ve searched exhaustively, but haven’t found a lead on what could fix this. It looks like it could be due to a 64 bit support requirement? Here’s the error:

Undefined symbols for architecture arm64:
  "realm::util::terminate_internal(std::__1::basic_stringstream<char, std::__1::char_traits<char>, std::__1::allocator<char> >&)", referenced from:
      void realm::util::terminate<unsigned long, unsigned long>(char const*, char const*, long, unsigned long, unsigned long) in libRealm.a(RLMArrayLinkView.o)
      void realm::util::terminate<unsigned long, int>(char const*, char const*, long, unsigned long, int) in libRealm.a(RLMArrayLinkView.o)
      void realm::util::terminate_with_info<int&&gt…

Goals

The build to run successfully

Expected Results

The build to run successfully.

Actual Results

The build broke at this error.

Steps to Reproduce

Code Sample

Undefined symbols for architecture arm64:
  "realm::util::terminate_internal(std::__1::basic_stringstream<char, std::__1::char_traits<char>, std::__1::allocator<char> >&)", referenced from:
      void realm::util::terminate<unsigned long, unsigned long>(char const*, char const*, long, unsigned long, unsigned long) in libRealm.a(RLMArrayLinkView.o)
      void realm::util::terminate<unsigned long, int>(char const*, char const*, long, unsigned long, int) in libRealm.a(RLMArrayLinkView.o)
      void realm::util::terminate_with_info<int&&gt…

Version of Realm and Tooling

Realm JS SDK Version: 3.6.0
Node or React Native: 61.5
Client OS & Version: Mac 10.14.5
Which debugger for React Native: None

Issue Analytics

State:
Created 4 years ago
Reactions:1
Comments:15 (3 by maintainers)

Top GitHub Comments

1reaction

bkboothcommented, May 30, 2020

Everytime I add/remove/update dependencies I have to

(cd ios && pod install)
yarn run ios
# ☝️ this one fails
(cd ios && pod install)
yarn run ios

It’s slightly annoying, but it seems to work consistently at least.

1reaction

sullyinccommented, May 29, 2020

@dbarner1 We also upgraded our cocoapods, that may have also contributed.

$ pod --version
1.9.2

Top Results From Across the Web

React Native: Give 64 bit support to your Android App. - Medium

From version 0.59, React Native added 64-bit support on Android. Let's explore the steps: How to make your app 64 bit supported ?...

How to build 64 and also 32 bit APK with React Native

For the x86 architecture, look for x86 for 32-bit and x86_64 for 64-bit. Which is covered in Universal APK. That is what you...

Handling 64-bit Android Builds for React Native - Red Shift

If you've upgraded properly, you shouldn't need to check that the 64-bit version of your app is included in your bundle, but rather...

React Native and Android: 64-bit - ReviewTrackers Engineering

56.0 . Usually having to upgrade one major version will cause something to break (especially in the React Native world) but having to...

React Native: Upgrade Dos and Don'ts | Shockoe

Unfortunately, React Native did not support builds targeting a 64-bit architecture on Android. We saw this supported added with version 0.59. If you...