-
-
Notifications
You must be signed in to change notification settings - Fork 197
TNS Doctor should check CocoaPods/Ruby version #1294
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
Comments
Why can't I add a label to this issue? GitHubbing is hard. |
We generally avoid to deal with dependencies of dependencies, because once you start this way, there's no end. CocoaPods site clearly states that Otherwise, we check for CocoaPods existence: https://github.com/NativeScript/nativescript-cli/blob/master/lib/services/doctor-service.ts#L49 |
Understood. However, let me provide the feedback that as a developer, I would have bailed on this endeavor and would have mentally blamed {N} out of ignorance. I'm convinced that our ability to smooth our the developer experience is paramount. Throwing cryptic errors about Maybe we could provide better error handling in the build where pods are added? |
|
I agree that we must check whether CocoaPods works robustly. I disagree that checking for particular version of Ruby brings value, because there can be millions of others issues which prevents CocoaPods from working. Imho, a better approach is to add a dummy pod into a dummy project and see if everything works. But this may not be easily doable. |
@hshristov, this was fixed in 4834e80 and is included in the upcoming CLI 1.5.2 release. |
@teobugslayer, Great. Thanks |
Now doctor get iOS runtime and build a project to check cocoapods. |
I noticed that Ruby can wreak absolute havoc on a project when using CocoaPods. The wrong version (< 2.0.0) will throw cryptic errors that make people feel sad.
It would be nice if TNS doctor could...
The text was updated successfully, but these errors were encountered: