realm-js: React Native build breaking - 64 bit support

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

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Reactions: 1
  • Comments: 15 (3 by maintainers)

Most upvoted comments

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.

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

$ pod --version
1.9.2