Xcode: Undefined symbols for architecture x86_64: "_JSObjectGetPrototype"

Question

Xcode: Undefined symbols for architecture x86_64: "_JSObjectGetPrototype"

tapz opened this issue 5 years ago · comments

Environment

React Native Environment Info:
System:
OS: macOS 10.14.2
CPU: x64 Intel(R) Core(TM) i7-6567U CPU @ 3.30GHz
Memory: 476.27 MB / 16.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 8.12.0 - /usr/local/bin/node
Yarn: 1.12.3 - /usr/local/bin/yarn
npm: 6.4.1 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 12.1, macOS 10.14, tvOS 12.1, watchOS 5.1
Android SDK:
Build Tools: 21.1.1, 21.1.2, 22.0.0, 22.0.1, 23.0.1, 23.0.2, 23.0.3, 24.0.1, 25.0.0, 25.0.2, 25.0.3, 26.0.0, 26.0.2, 27.0.3, 28.0.0, 28.0.2, 28.0.3
API Levels: 22, 24, 26, 27, 28
IDEs:
Android Studio: 3.2 AI-181.5540.7.32.5014246
Xcode: 10.1/10B61 - /usr/bin/xcodebuild
npmPackages:
react: 16.7.0 => 16.7.0
react-native: 0.58.1 => 0.58.1
npmGlobalPackages:
react-native-cli: 2.0.1
react-native-git-upgrade: 0.2.7

MacOS 10.14.2 (18C54)
Xcode 10.1 (10B61)

Description

After upgrading from 0.57.8 to 0.58.1 started to get this error in Xcode when compiling to a simulator:

Undefined symbols for architecture x86_64:
"_JSObjectGetPrototype", referenced from:
facebook::jsc::JSCRuntime::createFunctionFromHostFunction(facebook::jsi::PropNameID const&, unsigned int, std::__1::function<facebook::jsi::Value (facebook::jsi::Runtime&, facebook::jsi::Value const&, facebook::jsi::Value const*, unsigned long)>)::HostFunctionMetadata::initialize(OpaqueJSContext const*, OpaqueJSValue*) in libjsi.a(JSCRuntime.o)
"_JSObjectSetPrototype", referenced from:
facebook::jsc::JSCRuntime::createFunctionFromHostFunction(facebook::jsi::PropNameID const&, unsigned int, std::__1::function<facebook::jsi::Value (facebook::jsi::Runtime&, facebook::jsi::Value const&, facebook::jsi::Value const*, unsigned long)>)::HostFunctionMetadata::initialize(OpaqueJSContext const*, OpaqueJSValue*) in libjsi.a(JSCRuntime.o)
"_JSPropertyNameAccumulatorAddName", referenced from:

Reproducible Demo

Just try to compile the project to a simulator.

React Native Bot · Answer 1 · Mon Jan 28 2019 17:05:12 GMT+0800 (China Standard Time)

Can you run react-native info and edit your issue to include these results under the Environment section?

If you believe this information is irrelevant to the reported issue, you may write [skip envinfo] under Environment to let us know.

Tapani Saarinen · Answer 2 · Mon Jan 28 2019 17:55:02 GMT+0800 (China Standard Time)

Adding JavaScriptCore.framework to the linked libraries solved the issue. This probably should be added to the release notes.

Ofer Morag · Answer 3 · Mon Jan 28 2019 18:12:08 GMT+0800 (China Standard Time)

Great, did it also for me. But now I’m getting the build error (on iOS):
error: {project_path}/node_modules/react-native/ReactCommon/privatedata/PrivateDataBase.h: No such file or directory

Any idea?

Sergey Shpadyrev · Answer 4 · Mon Jan 28 2019 18:16:45 GMT+0800 (China Standard Time)

Great, did it also for me. But now I’m getting the build error (on iOS):
error: {project_path}/node_modules/react-native/ReactCommon/privatedata/PrivateDataBase.h: No such file or directory

Any idea?

Try to clean build folder and rebuild

Ofer Morag · Answer 5 · Mon Jan 28 2019 18:49:47 GMT+0800 (China Standard Time)

Thank you, that did the trick for me!

Davyd NRB · Answer 6 · Mon Jan 28 2019 20:05:23 GMT+0800 (China Standard Time)

@tapz

Can you tell how add JavaScriptCore.framework to the linked libraries ?!

Update:

Lorenzo Sciandra · Answer 7 · Mon Jan 28 2019 20:48:38 GMT+0800 (China Standard Time)

👋 folks - thanks for reporting!

Yes it seems that we should add this to the changelog 👍 Maybe right below the highlights section? https://github.com/react-native-community/react-native-releases/blob/master/CHANGELOG.md#0580

Mike Hardy · Answer 8 · Tue Jan 29 2019 20:58:54 GMT+0800 (China Standard Time)

@retyui highly recommend visiting this project which exposes the exact changes between react-native versions in the form of easy-to-read diffs that you could even (likely) automatically apply if you wanted: https://github.com/pvinis/rn-diff-purge

Pratik Purohit · Answer 9 · Tue Jan 29 2019 21:00:57 GMT+0800 (China Standard Time)

Adding JavaScriptCore.framework to the linked libraries solved the issue. This probably should be added to the release notes.

I was getting same error after updating ReactNative version, adding JavaScriptCore.framework did the trick.

Gary Fung · Answer 10 · Tue Jan 29 2019 23:59:55 GMT+0800 (China Standard Time)

@kelset yes please, close to the highlights to not miss it

Héctor Ramos · Answer 11 · Wed Jan 30 2019 05:10:09 GMT+0800 (China Standard Time)

Thanks for looking into this. I'll close it given a solution has been found (projects need to add JavaScriptCore.framework during the upgrade).

S Anegondhi · Answer 12 · Thu Feb 07 2019 23:27:45 GMT+0800 (China Standard Time)

Guess what. This is not resolved. I added javascriptCore.framework and it still fails with the same error.
react-native: 0.58.3

Sean Conrad · Answer 13 · Thu Feb 14 2019 09:33:01 GMT+0800 (China Standard Time)

@IndeDude I also struggled with this problem for a while and had to clean the build folder using Xcode specifically. See my note here: #23166 (comment)

Good luck!

jialadykiller · Answer 14 · Fri Feb 22 2019 15:48:07 GMT+0800 (China Standard Time)

thank you very much, that also resolve my question;

Jonathan · Answer 15 · Mon Feb 25 2019 21:40:40 GMT+0800 (China Standard Time)

The answer form @tapz works, but if you wanna use the Release Scheme, don't forget to also add the JavaScriptCore.framework in you Tests Target too.

chengdh · Answer 16 · Sun Mar 03 2019 19:38:02 GMT+0800 (China Standard Time)

this answer from @tapz works, thanks a lot

S Anegondhi · Answer 17 · Wed Apr 17 2019 09:21:22 GMT+0800 (China Standard Time)

Thank you. I had to use a fresh build too and that was painful because I have too many native libraries to hand link for both IoS and Android. Cheers!

…

On Thu, Feb 14, 2019 at 7:04 AM Sean Conrad ***@***.***> wrote: @IndeDude <https://github.com/IndeDude> I also struggled with this problem for a while and had to clean the build folder using Xcode specifically. See my note here: #23166 (comment) <#23166 (comment)> Good luck! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#23183 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AKi9IYhoxX5o22pzGt_im-7dAP0UMqdmks5vNL09gaJpZM4aVcjV> .

James Wanga · Answer 18 · Mon May 06 2019 13:46:29 GMT+0800 (China Standard Time)

@tapz solution worked except I had to also repeat it for my test project.

Yadigar Berkay Zengin · Answer 19 · Wed Jun 19 2019 19:36:02 GMT+0800 (China Standard Time)

The answer form @tapz works, but if you wanna use the Release Scheme, don't forget to also add the JavaScriptCore.framework in you Tests Target too.

This is absoluetly actual solve (y)

Dr Washington Sanchez · Answer 20 · Fri Jun 21 2019 08:23:11 GMT+0800 (China Standard Time)

Adding this did the trick!

Nathan Novak · Answer 21 · Thu Sep 12 2019 02:39:54 GMT+0800 (China Standard Time)

The answer form @tapz works, but if you wanna use the Release Scheme, don't forget to also add the JavaScriptCore.framework in you Tests Target too.

Awesome this worked!

raman-sidhu · Answer 22 · Tue Jan 14 2020 15:46:51 GMT+0800 (China Standard Time)

thanks @tapz, adding JavaScriptCore.framework to the linked libraries solved the issue for me

Hamdi Gatri · Answer 23 · Thu Jan 16 2020 22:34:46 GMT+0800 (China Standard Time)

The JavaScriptCore.framework is added to my linked libraries but I'am still having the issue.
I'am using React Native 0.59.10

Zhehat Sadeeq · Answer 24 · Thu Jan 23 2020 04:35:51 GMT+0800 (China Standard Time)

Still having the issue after adding JavaScriptCore.framework to linked libraries.
I'm using React Native 0.60.3