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.

Support catalyst/UIKit for Mac

See original GitHub issue

Goals

Compile and use Realm for iOS in a Project Catalyst (iPad app for macOS) project.

➡️https://github.com/realm/realm-cocoa/issues/6163

Expected Results

A successful build.

Actual Results

ld: in /Users/xxx/Documents/xxx/node_modules/realm/vendor/realm-ios/librealm-ios.a(placeholder.o), building for Mac Catalyst, but linking in object file built for iOS Simulator, file '/Users/xxx/Documents/xxx/node_modules/realm/vendor/realm-ios/librealm-ios.a' for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

Steps to Reproduce

Create a RN project with realm and select the Mac target :

67369890-16de6680-f57a-11e9-9c6e-a0ac2deac569

Version of Realm and Tooling

Realm JS SDK Version: 4.0.0-alpha.2
Node or React Native: 0.61.5
Client OS & Version: Xcode 11.2.1
Which debugger for React Native: ?/None

Issue Analytics

State:
Created 4 years ago
Comments:5 (2 by maintainers)

Top GitHub Comments

1reaction

marcosrdzcommented, Aug 27, 2020

For Catalyst, I changed the Podspec:

s.ios.vendored_libraries = ‘vendor/realm-ios/librealm-maccatalyst.a’, ‘vendor/realm-ios/librealm-parser-maccatalyst.a’

1reaction

tgoynecommented, Dec 3, 2019

CocoaPods does not support prebuilt libraries with catalyst yet. https://github.com/CocoaPods/CocoaPods/pull/9334 is a PR which will add the required functionality.