I upgraded my project to React Native 0.59 and since then building the project fails.
Successfully built project.
When I run react-native run-ios I receive the following error.
error Failed to build iOS project. We ran "xcodebuild" command but it exited with error code 65. To debug build logs further, consider building yourapp with Xcode.app, by opening project.xcodeproj
** BUILD FAILED **
The following build commands failed:
CompileC /Users/me/project/ios/build/dmReactNative57/Build/Intermediates.noindex/RealmJS.build/Debug-iphonesimulator/RealmJS.build/Objects-normal/x86_64/jsc_value.o /Users/me/project/node_modules/realm/src/jsc/jsc_value.cpp normal x86_64 c++ com.apple.compilers.llvm.clang.1_0.compiler
(1 failure)
When I build the project in xcode I get the following errors:

Add realm 2.26.0 to a react native 0.59.4 project on a mac with xcode 10.2.
Simply adding a case kJSTypeSymbol: break; at the end of the switch fixes the problem in Libraries/RealmReact.xcodeproj/Libraries/RealmJS.xcodeproj/RealmJS/JSC/jsc_value.hpp. Though I'm sure this isn't the best way fix.
I'd imagine the correct fix is to add case kJSTypeSymbol: return "symbol"; to the end of the switch case. Like below:
template<>
inline const char *jsc::Value::typeof(JSContextRef ctx, const JSValueRef &value) {
switch (JSValueGetType(ctx, value)) {
case kJSTypeNull: return "null";
case kJSTypeNumber: return "number";
case kJSTypeObject: return "object";
case kJSTypeString: return "string";
case kJSTypeBoolean: return "boolean";
case kJSTypeUndefined: return "undefined";
case kJSTypeSymbol: return "symbol";
}
}
But this is just my guess based on the case name, and the other cases.
exact same problem. Just started happening when upgrading my Xcode
Duplicated issue
Original Issue: https://github.com/realm/realm-js/issues/2246
Solved PR comment: https://github.com/realm/realm-js/pull/2303#issuecomment-482517874
I have just released v2.26.1 with the fix.
By @kneth
@jgreen01su @sajsanghvi Upgrading to v2.26.1 should solve it.
Hey - looks like you forgot to add a T:* label - could you please add one?
Most helpful comment
@jgreen01su @sajsanghvi Upgrading to v2.26.1 should solve it.