auto linking is not working for react native 0.60 version if we use 2.23.1 #407
Comments
Can I check how you're running this? The correct way would be to either run If opening in Xcode, please double check that you're opening e.g. Thanks! |
I am sure I am running correctly by using react-native run-ios and if I choose from Xcode also I am running the MyProject.xcworkspace only.. because I am finding pods in my project.. |
@naveenthukkani Also can I double check you've run |
can you please find the Podfile
podfile.lock
I am doing same what you are asking me react-native unlink bugsnag-react-native |
my react native version is now 0.60.6 |
I can see this in your
Why are these being removed from the project? That's the likely cause of the errors you're seeing. |
@mattdyoung no I am causing errors before doing that, so that I am removing from my project |
@naveenthukkani That relates to conflicts / duplicate symbols where React is included twice. But it appears with your current config the dependencies required for bugsnag-react-native aren't included at all. Have you recently upgrade to RN 0.60.6. Are you sure the previous workaround is still required? I'd suggest starting by removing these lines:
to confirm if you're still seeing the previous error. If the approach still is required, this blog post may help: But I think this is a generic issue with handling iOS dependencies in RN rather than an issue with Bugsnag. |
ok thank you I will look into it... |
@naveenthukkani did you find a solution? |
I am getting an error with react-native-bugsnag. I am using the
|
@mattdyoung In which version of bugsnag-react-native working with the latest react-native. I am downgraded to 0.60.0 but still the above error arise for me. Any solution. It is existing for me more than 5 days. |
@nihp @sanjayradadiya |
@mattdyoung I have a general question about a huge file generated after upgrade. After react-native upgrade I found huge files like ios/Index/Datasource/some thing.... What is the use of this files. Shall I need to commit this or need to move in .gitignore. Can you explain why it get generated? |
Hi @nihp I don't believe that folder is anything to do with Bugsnag or React Native. This post suggests it's used by XCode to speed up subsequent builds and can be excluded from source control: |
@mattdyoung Thanks. So only I have mentioned it is a general question |
How can i exclude that. If I remove this does it make any error in Xcode |
I just update the new version of Bugsnag to 2.23.1and install the pods and I am running app then I am getting below error. can any one help on this.. my react native version is 0.60
Undefined symbols for architecture x86_64:
"_RCTGetReactNativeVersion", referenced from:
___44-[BugsnagReactNative findReactNativeVersion]_block_invoke in BugsnagReactNative.o
"OBJC_CLASS$_RCTConvert", referenced from:
objc-class-ref in BugsnagReactNative.o
"_RCTRegisterModule", referenced from:
+[BugsnagReactNative load] in BugsnagReactNative.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
** BUILD FAILED **
I am getting below error also even:
error React Native CLI uses autolinking for native dependencies, but the following modules are linked manually:
This is likely happening when upgrading React Native from below 0.60 to 0.60 or above.
The text was updated successfully, but these errors were encountered: