NativeScript / NativeScript/nativescript-cli
NS DOCTOR Should Be More Helpful in Identifying CocoaPods Issues
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.1k
- Forks
- 204
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 8
Description
My brand new Mac arrived 2 1/2 weeks ago, I still can't create and run a template new app.
WARNING: There was a problem with CocoaPods is the hurdle; yet it gives no useful information.
At the very least, it might suggest printing out env results and asking for help.
If ns doctor could out the specific fail points and errors encountered with the pod tests, might also be helpful.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the ns doctor command and its CocoaPods checks, then inspect how pod-test failures are currently surfaced. Done means the command reports specific failure points and errors and suggests collecting env results or asking for help.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli, mobile
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100