-
Notifications
You must be signed in to change notification settings - Fork 24.4k
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
Missing .xcodeproj for iOS projects #30196
Comments
To elaborate a bit, by removing the By disabling manual linking, the only way for any project to use react-native seems to be by using CocoaPods. There are many existing projects that rely heavily on Carthage for example, or SPM. By forcing CocoaPods, one can only decide to either use both CocoaPods and the other dependency manager (welcome trouble, this is definitely not advisable nor maintainable) in the same project, or migrate the complete project to CocoaPods. But the latter is not even always possible, as for example some specific dependencies might not be available using CocoaPods. I am very curious if there is another way of using the latest |
I also hope to be able to provide a solution, without the help of any third-party management, to directly deal with project dependencies. I encountered a situation where cocoapods cannot be used in the project, and I need to deal with it urgently. The react-native version I currently use is 0.62.0, if I can't find a solution, I can only fall back to version 0.59.10 |
Thanks for describing your pains points with the upgrade to latest. Still, this is not strictly a new functionality regression. Please recreate this issue in the upgrade-support repo, as indicated by the issue templates: |
@rectified95 Can you please elaborate more why do you think it is upgrade issue? Because it is not: the same issue you will get in a new/existing project which does not support pods.
Did you also read this comment? This is official documentation and it clearly says: Moreover it is an issue for native project without cocoapods which could benefit from integrating RN into it, but you just killed that possibility by closing the issue and ignoring support. |
My impression was that you were trying to leverage patterns that used to work in a previous release and use them in a newer version of RN - that's what made me classify the issue as an upgrade problem. Do note that there are around 800 open issues, and in order to keep it manageable, proper redirection to eg. the Proposals/Upgrade repo helps achieve that. Also, note that I suggested opening the issue in another repo, rather than saying it was going to be ignored - thanks for creating it there. I'm reopening this issue, and tagging it for further investigation, and will let my colleagues decide which of the 2 issues to track this with. |
That's only part of the problem, but do not try to looks at it only from the upgrade side (which is a pain for a lot of projects of course). Looking at React v17.0 release, there is a good statement:
So in web they take care about other technologies and make it possible to embed the app. Why it is different in React native? You can also look at it from another point of view: it is not a secret that there are at least 2 dependency management on iOS: Carthage and Pods. By forcing new project to use
which can easily fix that problem. Or find a better solution together and make React Native compatible with other technologies, just like React does. |
https://reactnative.dev/docs/integration-with-existing-apps#3-install-cocoapods Hope to improve the document, convenient for developers to use. |
Can you give a solution or a feasibility plan? Or estimate the time for the solution, so that the next step can be planned |
@suwu150 did you discover a solution? having the same problem... |
@JacksonGL I lowered the react-native version. . |
I have also the problem of missing.xcodeproj file and to use xcode and cocoapods which is impossible as I cannot run pod init |
I am also very interested in a solution to use RN with a different dependency manager than Cocoapods. In my case I‘d like to cache RN instead of recompiling it all the time and something like Carthage support would definetly help in this scenario. |
Are there no further developments here. It seems crazy to omit these files from the libraries given the impact this is causing. This also invalidates the underlying documentation. |
This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
This issue was closed because it has been stalled for 7 days with no activity. |
Description
During upgrade the project from react-native 0.60.* to react-native c it was observer that react native does not have *.xcodeproj files anymore. That make it impossible to use the latest and greatest react native in project that uses Carthage. There is also nothing about it in docs. For example, https://reactnative.dev/docs/integration-with-existing-apps says that CocoaPods are needed, but that is not an option for existing projects that uses Carthage. Same for https://reactnative.dev/docs/upgrading.html, it does not cover this case.
As a result migration to the latest react native is blocked:
React Native version:
Steps To Reproduce
Provide a detailed list of steps that reproduce the issue.
Or
Expected Results
.xcodeproj
files are part of the react nativeSnack, code example, screenshot, or link to a repository:
Not needed
Additional information
According to official RN documentation linking-libraries-ios
it is also clearly stated that there must be an
.xcodeproj
and this is how iOS development happens.The text was updated successfully, but these errors were encountered: