-
Notifications
You must be signed in to change notification settings - Fork 184
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
Can't do pod install in example project when choose Turbo Native Modules with backward compatible: Invalid Podfile
file: Could not find Node
#639
Comments
### Summary This makes the vanilla example app the first option when the CLI asks for the type of the example app. ![Screenshot 2024-10-18 at 18 12 00](https://github.com/user-attachments/assets/63943479-cab2-4a54-b8e7-6d5a6355799d) We were seeing some RNTA specific bugs such as #639 With that being said, this is in no way an attempt to fix the bugs that are caused by create-react-native-library when we integrate with the React Native Testing App. Such bugs should still be fixed by the team. ### Test plan 1. Run creact-react-native-library 2. Pick a native library template 3. Make sure when the example type is asked, vanilla example is the first option.
Hey, @LeXuanKhanh this was an issue with the way RNTA searches for node and the way asdf treats the "binaries" as shellscript files. Please create a new library from scratch or update your RNTA version. This should be fixed. Closing the issue, please open it again if it isn't fixed. |
hi @atlj, I have created a new library from scratch with test app option and the newest RNTA but this issue still exists, you can check out here: I have checked the yarn.lock file and saw the version of RNTA installed is since this is mainly an issue about RNTA, should I bring this conversation to current main issue of RNTA that you mention above ? |
Hey @LeXuanKhanh I think filing an issue for React Native Test App and creating a reproducable enviroment for them would be the best move. Also if you want to be able to move forward faster, I would recommend either using nvm or just straight installing node from brew/nix for the moment being. Once the issue is fixed, you can go back to asdf. |
Thanks for the suggestion, I think I should stick with the vanilla app option when create a new library since It still work fine for me without this issue |
Hi @atlj, after some poking around, I figure out that this is not an issue with the Node finder rather than the cocoapod itself, my global pod seems to get the error when installing dependencies, I then try to set up a local cocoapod for the project using bundler then everything is working as normal |
Description
Step:
Error:
Example/ios/Podfile:
Packages
Selected options
Link to repro
https://github.com/LeXuanKhanh/react-native-awesome-module
Environment
The text was updated successfully, but these errors were encountered: