#import "RCTBridgeModule.h" file not found #22
Comments
|
@adrianotadao did you upgrade to React-native 0.40? if so you need to follow up with this issue |
|
@alinz I'm using the version I tried to update the react-native version but I'm using other libs that conflict with the version Now, everything here is okay and I don't know how I fixed. Thank you a lot! |
|
@adrianotadao what I usually do is slowly added each module and try to see if I can compile and run, and then I move to the next one. It is painful but this is how you should do it. |
|
@alinz yes, you're right but, React Native is a bit strange. This error has disappeared, now, it returns after I deleted the |
|
@adrianotadao same here - how did you resolve? |
|
@njt1982 I have been using this module with react-native 0.45 without any issues. Please read the doc and follow the instruction. Pretty sure you missed something in there. Also, start with a plain simple project and try to get it to work. |
|
I had the same issue as @adrianotadao - turns out you seem to need to compile the main target first?! (I have followed the instructions). |
|
@njt1982 I need to confess that I don't like so much React Native. Every single update that Xcode had, we had problems with the app. That's incredible! About the error, I saw a lot of blog posts talking about the order on header search path. I changed everything and nothing had worked. The bad news is that I don't know how I did the error disappear. In many of many times, the problem was with the update of Xcode but I don't know if is your case. |
|
@njt1982 I know the pain, unfortunately when you are working with edge technologies which only backed by community you always find yourself in this situation. To me that's the fun of it, figure things out the solutions and understand the concepts. One thing I usually do, is commit small things and once I solve it, I do every new SDK will break your code, it's not just react-native, swift has gone into many iterations and every iteration breaks the previous one. |
|
IIRC what fixed it for me was to compile and run the main application first, then the extension compiled and ran fine. For me it was caused by project build space being cleaned and the extension being unable to compile as the main project wasn't compiled. I think ;) @adrianotadao I know what you mean. Sometimes a task which should seem simple snowballs for the most frustrating and obscure reason... However, equally, React Native has let me build my app much more quickly than it would have taken to do it directly in xcode and I have got the added benefit of (in theory) being able to run it with very few changes on Android too. |
|
I entirely agree with both of you guys. hehehe I don't hate react-native. I like it, is better than write native code ( a thing that I already did) but, if for instance, the product owner, knows what is react-native, he will think that all things that we will create will be very easy and quick. So, when you have some of these problems, the company starts to think that you are unable to do the job and if you gather it with the unknown problem, you start to live a stressful day. That's my point. React and react native are nice! I don't like Xcode. hahahaha I need to say: I H-A-T-E Xcode... |
|
If it helps at all guys I fixed this issue by including in my header search paths for the files that were missing these files: $(SRCROOT)/../../../node_module/React |
|
Same problem in |
how do you fix it |
|
same problem in react-native0.61.5 |
I'm receiving this error. What went wrong?
Take a look how is my
Header Search Paths. It's a strange error because on my friend's computer it's working well.Thank you.
The text was updated successfully, but these errors were encountered: