i have a podspec that is pushed to the trunk. Now, i need to make few changes to my podspec and push it again. However, i do not wish to change the version number. can i update my podspec and push it to the trunk keeping the version number same?
for.e.g.,
Pod::Spec.new do |s|
s.name = "MySDKName"
s.version = "1.1.0"
s.summary = "Pod Summary"
s.author = { "Deepak Badiger" => "email#domain.com" }
s.homepage = "www.myhomepage.com"
s.license = {My License Agreement}
s.source = { My Source }
s.platform = :ios, '7.0'
end
in the example above, i wish to add -
s.subspec 'Categories' do |c|
c.source_files = 'cats/Classes/*.{h,m}'
end
however, i wish to keep the version as 1.1.0 and i don't want to bump the version to 1.1.1 or 1.1.0.1
The simplest way would be to bump the version. And this is how you should do it.
An alternative A bad idea would be to submit a pull request on Cocoapods/Specs but this will take time and annoy people.
Related
For a iOS project we are using a lot of private SDK's. Maybe 10 .framework files and growing. We would like to create a private git repo and dump all the .framework files in the repo. Is it possible cocoapods uses this git repo as a source so we can specify the frameworks we need? Maybe use the vendored_frameworks prop?
Can not find a solution online. Tried it myself without success.
Thanks!
UPDATE
I have a git repo with a branch TEST including 1 .framework file and 1 podspec file
Pod::Spec.new do |s|
s.name = 'xSDK'
s.version = '0.0.1'
s.summary = 'x SDK'
s.homepage = 'https://www.google.com'
s.author = { 'Sample' => 'sample#sample.com' }
s.license = { :type => "MIT", :text => "MIT License" }
s.platform = :ios
s.ios.deployment_target = '13.0'
s.ios.vendored_frameworks = 'x.framework'
end
I have a react native module including swift code that is using the .framework with a podspec file
require "json"
package = JSON.parse(File.read(File.join(__dir__, "package.json")))
Pod::Spec.new do |s|
s.name = "react-native-x-module"
s.version = package["version"]
s.summary = package["description"]
s.homepage = "https://github.com/x"
s.license = "MIT"
s.authors = { "x" => "x#x" }
s.platforms = { :ios => "13.0" }
s.source = { :git => "", :tag => "#{s.version}" }
s.source_files = "ios/**/*.{h,m,mm,swift}"
s.dependency 'xSDK', :git => 'https://git.x.org/x/cocoapods/-/tree/TEST'
end
I want to do something like this, but s.dependency is indeed not correct
We have more react-native-x-module's so it would be nice if we could collect all the .frameworks in a git repo
You host a private pod repository. See the Private Pods guide for a start. The details vary very much based on your local infrastructure. For example, our in-house repo and pods all make use of our GitLab installation.
Basically, you need to set up a Git repo for the specs, and you need to add source <url_to_repo> to your Podfile so CocoaPods can find the private pods. The pods can reference internal Git repositories or other sources. In the end, you'd use an in-house pod repo, and the pods would refer to in-house sources.
For some example, search for something like "cocoapods private repo" to find articles like this describing this in more detail. Most articles I've found set up a private pod repo on GitHub, but you can use your own in-house Git server (which is what my company is doing).
I have created sample CocoaPod file and it worked successfully, now on final stage when I am doing Pod Repo Push it showing me error. Below are the command and error which I am getting.
Pod::Spec.new do |s|
s.name = "IDFVSample"
s.version = "1.0.0"
s.summary = "A short description of VFIDOneFramework. Please check this awesome work from me you will like it"
s.description = "This is the best tutorial. Recently given presentation in the world great forum for the member."
s.homepage = "https://github.com/kashiftriffort/IDFVSample"
s.license = "MIT"
s.author = { "KJilani" => "Kashif.triffort#gmail.com" }
s.platform = :ios, "9.0"
s.source = { :git => "https://github.com/kashiftriffort/IDFVSample.git", :tag => "1.0.0" }
s.source_files = "IDFVSample/IDFVSample/IDFVSample.swift"
s.dependency 'Firebase/Core'
end
pod repo push IDFVPodSpecs IDFVSample.podspec --allow-warnings
Validating spec
Cloning spec repo `-1` from ``
[!] Unable to add a source with url `` named `-1`.
You can try adding it manually in `~/.cocoapods/repos` or via `pod repo add`.
Looks like you have not added the repo containing your specs yet.
Do something like:
pod repo add IDFVSample <git source>
Move your IDFVSample.podspec to the root of your repository(where is already located LICENSE and README files)
I'm getting an error when I'm trying to add GeoFire to my iOS Flutter project which has the FlutterFire Database plugin included. This is what the error looks like:
Resolving dependencies of `Podfile`
[!] Unable to satisfy the following requirements:
- `Firebase (~> 2.1)` required by `GeoFire (1.1.0)`
Specs satisfying the `Firebase (~> 2.1)` dependency were found, but they required a higher minimum deployment target.
My podspec file looks like this atm:
#
# To learn more about a Podspec see http://guides.cocoapods.org/syntax/podspec.html
#
Pod::Spec.new do |s|
s.name = 'geofire'
s.version = '0.0.1'
s.summary = 'A new flutter plugin project.'
s.description = <<-DESC
A new flutter plugin project.
DESC
s.homepage = 'http://example.com'
s.license = { :file => '../LICENSE' }
s.author = { 'Your Company' => 'email#example.com' }
s.source = { :path => '.' }
s.source_files = 'Classes/**/*'
s.public_header_files = 'Classes/**/*.h'
s.dependency 'Flutter'
s.dependency 'GeoFire', '>= 1.1' # Adding GeoFire
s.ios.deployment_target = '8.0'
end
I also tried using the git page in to add Geofire in my podspec file as suggested here: GeoFire giving problems with CocoaPods
s.dependency 'GeoFire', :git => 'https://github.com/firebase/geofire-objc.git'
Is there a (simple) solution for this?
I faced the same kind of issue few days ago.
I think I fixed it by doing the following steps:
Run the command 'pod repo update' (it will update your repo information)
Then run the command 'pod update' (it will update your pods using the latest repo information)
Let me know if this is solving your issue :)
Please try the approach suggested by Bjørn Børresen here:
Since Flutter kind of abstracts away this Cocoapods process. Here's what I did to be able to run "pod repo / update":
Run pod repo update
Set the environment variable FLUTTER_FRAMEWORK_DIR to something that looks like /Users/youruser/bin/flutter/bin/cache/artifacts/engine/ios/. You can do a locate Flutter.podspec to find this directory
From YourFlutterProject/ios run pod update
After this you should be able to run your app again
I just installed React Native following the instructions here:
http://facebook.github.io/react-native/docs/embedded-app-ios.html#content
However, I don't know how to install third-party extensions like react-native-icons. What I have tried so far is to npm install react-native-icons in ReactComponent directory. But when I run the app, it shows the error saying that react-native-icons cannot require react-native, which is understandable since react-native is NOT in node_modules. So what is the correct way to install extensions when React Native is installed with Cocoapods? Any hint is appreciated!
If the extension you want to use does not have one, you will need to create a Podspec for it. You can copy over most of the info from the extension's package.json file.
An example podspec, taken from https://github.com/fraserxu/react-native-couchbase-lite/blob/master/ReactNativeCouchbaseLite.podspec
# To learn more about a Podspec see http://guides.cocoapods.org/syntax/podspec.html
#
Pod::Spec.new do |s|
s.name = "ReactNativeCouchbaseLite"
s.version = "0.2.2"
s.summary = "couchbase lite binding for react-native"
s.license = 'MIT'
s.platform = :ios, '7.0'
s.requires_arc = true
s.authors = "Fraser Xu <xvfeng123#gmail.com>"
s.homepage = "https://github.com/fraserxu/react-native-couchbase-lite.git"
s.source = { :git => 'https://github.com/fraserxu/react-native-couchbase-lite.git' }
s.source_files = 'ios/**/*.{h,m}'
s.dependency 'couchbase-lite-ios'
s.dependency 'couchbase-lite-ios/Listener'
end
Once you've confirmed its working, go ahead and send the author a pull request with the Podspec file like I did :)
I'm in the process of writing my very first pod spec, and while I have managed to write a spec that passes validation and pod install seems to install the pod OK the actual source-files are nowhere to be found in my workspace. This is my podfile:
platform :ios, '7.0'
xcodeproj 'NORLabelNodeiOStest'
pod 'NORLabelNode', :path => '~/Programmering/Development/NORLabelNodePodSpec'
pod 'AFNetworking'
As you can see the NORLabelNode pod is installed through a local version of the podspec which looks like this:
Pod::Spec.new do |s|
s.name = "NORLabelNode"
s.version = "0.9.2"
s.summary = "Extension of Apple's SKLabelNode. Allowing multiple lines through the use of \n in the text-string. "
s.description = <<-DESC
Behaves like an ordinary SKLabelNode with the one difference that adding newline characters to the text- property actually adds line-breaks. This is achieved by creating SKLabelNodes as child-nodes, but keeping these as part of the internal (private) logic.
DESC
s.homepage = "https://github.com/nickfalk/NORLabelNode.git"
s.license = 'MIT'
s.author = { "T. Benjamin Larsen" => "benjamin.larsen#noreagle.no" }
s.source = {
:git => "https://github.com/nickfalk/NORLabelNode.git",
:tag => 'v0.9.2'
}
s.social_media_url = 'https://twitter.com/noreagle'
s.platform = :ios, '7.0'
s.ios.deployment_target = '7.0'
s.osx.deployment_target = '10.9'
s.requires_arc = true
s.frameworks = 'SpriteKit'
s.source_files = 'NORLabelNode.{h,m}'
end
Running pod install gives no indication that anything has gone amiss:
Analyzing dependencies
Fetching podspec for `NORLabelNode` from `~/Programmering/Development/NORLabelNodePodSpec`
Downloading dependencies
Installing AFNetworking (2.2.3)
Installing NORLabelNode (0.9.2)
Generating Pods project
Integrating client project
[!] From now on use `NORLabelNodeiOStest.xcworkspace`.
The AFNetworking pod installs the files as expected, but my own NORLabelNode does not. Anyone?
As you can see the NORLabelNode pod is installed through a local version of the podspec which looks like this
That's not how the path option works. It expects a path to the project itself, not the spec.
From the docs:
Using this option CocoaPods will assume the given folder to be the root of the Pod and will link the files directly from there in the Pods project.
If you would like to just use your spec without adding it to the master repo you can create your own repo of specs (docs). Or just place your spec in the correct folder structure in ~/.cocoapods/repos/master