Realm fails to compile when gRPC-Core is also in the project
See original GitHub issueGoals
I’m seeing compilation errors in object-store
files. I’d like to be able to compile my project on iOS.
Expected Results
I expected my project to compile.
Actual Results
I added Firebase to my app via Cocoapods, then got the following errors in Realm:
In file included from /Users/kevboh/my-project/node_modules/realm/react-native/ios/RealmReact/RealmReact.mm:25:
In file included from ../../src/object-store/src/shared_realm.hpp:22:
In file included from ../../src/object-store/src/execution_context_id.hpp:30:
In file included from /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/thread:96:
In file included from /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/chrono:303:
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/ctime:60:9: error: no member named 'clock' in the global namespace; did you mean 'flock'?
using ::clock;
There are many members it cannot find, including clock as above, plus difftime, mktime, and many more.
Steps to Reproduce
react-native init MyProject
cd MyProject/
yarn add realm
react-native link realm
cd ios/
pod init
and addpod 'Firebase/Core'
andpod 'Firebase/Firestore'
to the Podfilereact-native run-ios
A sample project that is the result of these steps is here: https://github.com/kevboh/RealmFirebaseBugDemo
Version of Realm and Tooling
- Realm JS SDK Version: 2.1.0
- Node or React Native: 0.51.0
- Client OS & Version: macOS 10.13.2, Xcode 9.2
- Which debugger for React Native: None
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:13 (4 by maintainers)
Top Results From Across the Web
no viable overloaded '=' error on iOS 11 - realm - Stack Overflow
Try to change your podfile to the latest version of Realm : pod 'Realm'. This fix is up to version 2.8.1 , so...
Read more >Building the CocoaPods dependency project gRPC-Core Error
I was trying to building the cocoapods dependency project gRPC-Core. (for using Firebase) fatal error: 'absl/memory/memory.h' file not found.
Read more >Realm: Create reactive mobile apps in a fraction of the time
Go to your app target's build phases tab in Xcode and add the Realm file to the “Copy Bundle Resources” build phase. At...
Read more >gRPC-Core on CocoaPods.org
gRPC – An RPC library and framework. gRPC is a modern, open source, high-performance remote procedure call (RPC) framework that can run anywhere....
Read more >How can I run a Java app, created with the Java bindings ...
The Java bindings library lets you connect to a Daml Ledger via a secure connection. ... < plexus.core [DEBUG] Populating class realm maven.api...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Confirm that remove “$(SRCROOT)/…/…/…/…/ios/Pods/Headers/Public/React**” search path on RealmReact working for me
I wonder if the search path could be changed to only add the headers for the ReactNative pod to the search path, rather than headers for all pods. That seems like it’d avoid picking up headers from unrelated pods while also allowing Realm to find ReactNative’s headers when it is integrated via CocoaPods.