Create git repo with private .framework sdks for cocoapods - ios

Question

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

Answer 1

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).