CocoaPods集成异常：#if canImport无法识别可选subspec框架

我刚好之前处理过类似的CocoaPods subspec可选依赖问题，帮你梳理下原因和解决办法：

问题背景回顾 #

你当前的场景：

• 拆分了mainSDK（默认自动引入）和additionalSDK（可选引入，多占用8MB空间）两个subspec
• 在mainSDK代码中通过#if canImport(additionalSDK)实现条件分支逻辑
• 仅集成mainSDK时出现「missing module: additionalSDK.framework」错误，但集成完整subspec或非CocoaPods环境下逻辑正常

你的关键代码片段：
核心Podspec配置

s.default_subspec = 'mainSDK'
s.subspec 'mainSDK' do |mainSDK|
  mainSDK.vendored_frameworks = 'mainSDK.framework'
  mainSDK.source_files = "mainSDK.framework/Headers/*.h"
end
s.subspec 'additionalSDK' do |additionalSDK|
  additionalSDK.source_files = "additionalSDK.framework/Headers/*.h"
  additionalSDK.vendored_frameworks =['additionalSDK.framework', 'mainSDK.framework']
end

条件编译代码

#if canImport(additionalSDK)
// 添加可选代理
class ViewController: UIViewController, OptionalDelagate
#else
// 无需代理
class ViewController: UIViewController
#endif

问题原因分析 #

1. Podspec结构冗余导致依赖解析冲突

   • 你在根spec中重复定义了s.source_files = "mainSDK.framework/Headers/*.h"，和mainSDK subspec的定义冲突，让CocoaPods错误认为根spec需要访问additionalSDK模块
   • additionalSDK subspec重复打包了mainSDK.framework，不仅浪费空间，还打乱了CocoaPods的依赖解析逻辑，误以为mainSDK必须依赖additionalSDK

2. CocoaPods对canImport的特殊处理
   哪怕是条件编译中的canImport(additionalSDK)，CocoaPods会默认尝试解析该模块的依赖关系。如果没有明确标记为可选弱依赖，编译器会强制查找该框架，导致报错

3. 弱依赖配置未生效
   你尝试的-weak_framework additionalSDK没有加到正确的target上——根spec的配置不会自动继承到subspec，必须在mainSDK subspec中单独配置

具体解决方法 #

• 步骤1：修正Podspec结构与依赖关系
  重新整理Podspec，移除冗余配置，让additionalSDK依赖mainSDK而非重复打包：

  s.platform = :ios
  s.ios.deployment_target = '9.0'
  s.name = "mainSDK"
  s.summary = "mainSDK IOS SDK"
  s.requires_arc = true
  s.version = "1.0.8.6.5"
  s.source = { :http => "https://s3-eu-west-1.amazonaws.com/zipOfSDK.zip"}
  s.framework = "UIKit"
  s.swift_version = "4.2"
  
  # 移除根spec的source_files，避免和subspec冲突
  s.default_subspec = 'mainSDK'
  
  s.subspec 'mainSDK' do |mainSDK|
    mainSDK.vendored_frameworks = 'mainSDK.framework'
    mainSDK.source_files = "mainSDK.framework/Headers/*.h"
    # 关键：在mainSDK的subspec中添加弱依赖配置，告知编译器additionalSDK是可选的
    mainSDK.pod_target_xcconfig = {
      'OTHER_LDFLAGS' => '-weak_framework additionalSDK',
      'CLANG_ALLOW_NON_MODULAR_INCLUDES_IN_FRAMEWORK_MODULES' => 'YES'
    }
  end
  
  s.subspec 'additionalSDK' do |additionalSDK|
    additionalSDK.vendored_frameworks = 'additionalSDK.framework'
    additionalSDK.source_files = "additionalSDK.framework/Headers/*.h"
    # 让additionalSDK依赖mainSDK，避免重复打包框架
    additionalSDK.dependency 'mainSDK/mainSDK'
  end
  

• 步骤2：优化条件编译代码（可选，但更稳妥）
  将canImport判断与模块导入放在一起，避免编译器提前解析模块：

  #if canImport(additionalSDK)
  @import additionalSDK;
  class ViewController: UIViewController, OptionalDelagate
  #else
  class ViewController: UIViewController
  #endif
  

• 步骤3：验证集成流程

  • 仅使用核心功能：在Podfile中写入 pod 'mainSDK'
  • 需要额外功能：写入 pod 'mainSDK/additionalSDK'

为什么非CocoaPods环境正常？ #

非CocoaPods环境下，你手动将框架设置为「可选（Optional）」，编译器会忽略未找到的框架；但CocoaPods会自动生成xcconfig文件覆盖手动配置，因此必须在Podspec中明确声明弱依赖。

内容的提问来源于stack exchange，提问作者Viktor Vostrikov