-
Notifications
You must be signed in to change notification settings - Fork 121
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support RN 0.60+ autolinking #118
Comments
@WoodyWoodsta have you found any work around yet for this problem, i am getting error |
That sounds unrelated. |
It is kind of related, it is what happens if you manually link then try to build. |
@sam17896 any luck figuring this out? |
FWIW I figured this out. I have a fork working with autolinking. In case you want to do it on your own, the TLDR is:
Checkout the podspec in the fork above for an example if you're unsure. Good learning experience! |
@sam17896 Where you able to find a solution to that issue? |
@wkoutre Your fork isn't currently compiling for me. I'm receiving deprecation errors for some of the methods. |
@alexkendall If you're able to share some logs, I can check it out. Currently using my fork in production without issues. |
@wkoutre Thanks for taking a look. Currently I'm receiving the following errors:
XCode Version 12.4 |
Hm, it seems like (for some reason) |
@wkoutre My compiler flags have "Treat Warnings as Errors" set to "No". Unsure how to work around this. What version of react-native and Xcode are you currently using? |
Hey, sorry @alexkendall -- missed this response yesterday. I'm on react-native@0.63.4 and Xcode 12.4 using new build system (not legacy). Is it possible for you to point me to a repo replicating the issue you're having? |
Installing this module and using it results in the error indicating that the module does not support the new autolinking.
https://facebook.github.io/react-native/blog/2019/07/03/version-60#native-modules-are-now-autolinked
The text was updated successfully, but these errors were encountered: