CocoaPods/CocoaPods

Possible to connect single Pod to multiple targets with different min deployment target?

Open

#9,932 opened on Jul 22, 2020

View on GitHub
 (9 comments) (0 reactions) (0 assignees)Ruby (2,685 forks)batch import
help wanted

Repository metrics

Stars
 (14,815 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

I couldn't find anything related to this question. That's why I am posting it here.

Recently, we did increase our app's min deployment target iOS 9.0 > 11.0. However, our app uses additional internal frameworks that are still pointing to iOS 9. Is it possible to share the same Pod with two targets that they do have different minimum deployment target?

So far I tried.

workspace 'ABC.xcworkspace'
platform :ios, '11.0'
use_frameworks! :linkage => :static

# ============= SCOPES ============= #
def firebase
    pod 'Firebase/Core'
    pod 'Firebase/Messaging'
    pod 'Firebase/DynamicLinks'
    pod 'Firebase/InAppMessaging'
end

# ============= TARGETS ============ #
target 'ABC' do
    firebase
end

target :Core do
    platform :ios, '9.0'
    firebase
end

Note: This is not the exact Podfile but rather a sample of it.

But this generates duplicate Targets under Pods.xcodeproj appending -iOS9.0 and -iOS11.0.

What is the right way achieving what I am looking for? If currently possible.

Contributor guide

Research direction
Investigate how CocoaPods handles multiple targets with different minimum deployment targets in the Podfile. Look at the source code for platform resolution and dependency installation to see if shared pods across targets with different deployment targets is supported or if there is a workaround.
Tech stack
ruby
Domain
toolingdeveloper experience
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
CocoaPodsRuby
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70