React-Native packages not finding React headers

-

I'm currently trying to integrate React-Native into my existing Swift iOS project. I'm using Cocoapods already so I followed the documentation on the topic by adding the following to my Podfile:

# React Native
react_native_path = "../node_modules/react-native"
pod "Yoga", :path => "#{react_native_path}/ReactCommon/yoga"
pod "DoubleConversion", :podspec => "#{react_native_path}/third-party-podspecs/DoubleConversion.podspec"
pod "GLog", :podspec => "#{react_native_path}/third-party-podspecs/GLog.podspec"
pod "Folly", :podspec => "#{react_native_path}/third-party-podspecs/Folly.podspec"
pod ‘React’, :path => react_native_path, :subspecs => [
  ‘Core’,
  'CxxBridge',
  'DevSupport',
  ‘RCTImage’,
  ‘RCTNetwork’,
  ‘RCTText’,
  ‘RCTWebSocket’
]

This all works well enough and I'm able to build my app both in the simulator as well as on the device and play around with it.

In a second step I wanted to add react-native-navigation. I added the module to package.json, ran npm install and afterwards react-native-link. All these commands finished successfully. Unfortunately when now trying to build the project it can't find any of the React header files while compiling the react-native-navigation dependency. I already tried various combinations of downgrading react-native again, adapting HEADER_SEARCH_PATHs and so on but with no success ...

react-native version: 0.46.1 react version: 16.0.0-alpha.12 react-native-navigation version: 1.1.134

Any idea what could cause this?

I keep getting this error as well. Tried clearing all caches, build folder, etc. I believe the error is with Pos files, if I reinstall Pods and then try I can often run my app a few times before the error appears again.

Not sure if this helps, but maybe it will get the conversion started.

Comments

Post a Comment

Popular posts from this blog

flutter websocket connection issue

-
I am trying to develop a flutter app which connects to the server and exchanges data using websocket. The server is in .Net Core and using Asp.Net Core Websockets to implement this functionality. The problem I am facing is, my flutter app is not able to connect to the server and throws following error. E/flutter (31498): [ERROR:topaz/lib/tonic/logging/dart_error.cc(16)] Unhandled exception: E/flutter (31498): WebSocketChannelException: WebSocketChannelException: WebSocketException: Connection to 'http://127.0.0.1/client#' was not upgraded to websocket E/flutter (31498): #0 new IOWebSocketChannel._withoutSocket.<anonymous closure> (package:web_socket_channel/io.dart:83:24) E/flutter (31498): #1 _invokeErrorHandler (dart:async/async_error.dart:13:29) E/flutter (31498): #2 _HandleErrorStream._handleError (dart:async/stream_pipe.dart:286:9) E/flutter (31498): #3 _ForwardingStreamSubscription._handleError (dart:async/stream_pipe.dart:168:13) E/flutter (3149...
Read more

Webpack 5 and Storybook 6 integration throws an error in DefinePlugin.js

-
6 1 Working on Webpack 5 and Storybook integration in our React apps' repository. Mainly upgrading from Webpack v4 to v5 because its support has been announced here in this blog post officially. Following the suggested full instructions. With the below mentioned setup I get the following error message on the console: <i> [webpack-dev-middleware] wait until bundle finished 10% building 0/1 entries 0/0 dependencies 0/0 modulesℹ ｢wdm｣: wait until bundle finished: /opt/app/node_modules/webpack/lib/DefinePlugin.js:549 const oldVersion = compilation.valueCacheVersions.get(name); ^ TypeError: Canno...
Read more

Meaning of `{}` for return expression

-
15 1 I found by accident that the following compiles: #include <string> #include <iostream> class A{ int i{}; std::string s{}; public: A(int _i, const std::string& _s) : i(_i), s(_s) { puts("Called A(int, const std::string)"); } }; A foo(int k, const char* cstr){ return {k, cstr}; // (*) } int main(){ auto a = foo(10, "Hi!"); return 0; } The line of interest is (*). I guess the function foo is equivalent to: A foo(int k, const char* str){ return A(k, cstr); } However, is there a special name for this mechanism in (*)? Or is it just the simple fact that the compiler knows which constructor to call due to the return type? ...
Read more