NativeScript / NativeScript/nativescript-cli

Customize the command used to install CocoaPods

Open
#1,628 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

CocoaPods feature os: ios
Dominant language
JavaScript
Stars
1.1k
Forks
204
Avg merge
1d 9h
Merged PRs (30d)
8

Description

From @NathanWalker on March 19, 2016 23:55

Because some CocoaPods can be finicky at best to get working with {N} plugins, it would probably help to be able to customize or specify a command to run a pod install.
For example, please see this issue:
https://github.com/segment-integrations/analytics-ios-integration-google-analytics/issues/3#issuecomment-164874798

The issue arises from the Segment-GoogleAnalytics pod and the solution posted above involves a custom install of CocoaPods and the usage of bundle exec pod install along with a Gemfile to circumvent the issues.

It would be nice that when running tns emulate ios with CocoaPods involved, a command line argument could be passed to provide a custom pod install command to be able to use this solution.

Working on this {N} plugin for Segment:
https://github.com/NathanWalker/nativescript-segment
Blocked by this at moment.

Copied from original issue: NativeScript/ios-runtime#535

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the tns emulate ios flow and trace where CocoaPods runs pod install. Review the requested bundle exec pod install and Gemfile workaround, then define how a custom command would be supplied. Done means the iOS emulation flow can use that command for projects needing a customized CocoaPods installation.

Written by the indexing model from the issue text.

Assessment

Tech stack
ios, javascript
Domain
cli, mobile-dev
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.