[!] Unable to install vendored xcframework `Diffusion` for Pod `diffusion_flutter`, because it contains both static and dynamic frameworks.

[emreakcan]

We are having a linking problem while using the xcframework in our package.
Any idea why xcframework including both static and dynamic libraries?
Is it possible to have just static libraries in the build?

[!] Unable to install vendored xcframework Diffusionfor Poddiffusion_flutter, because it contains both static and dynamic frameworks.

#
# To learn more about a Podspec see http://guides.cocoapods.org/syntax/podspec.html.
# Run `pod lib lint diffusion_flutter.podspec` to validate before publishing.
#
Pod::Spec.new do |s|
  s.name             = 'diffusion_flutter'
  s.version          = '0.0.1'
  s.summary          = 'Flutter plugin for Diffusion SDK'
  s.description      = 'A Flutter plugin that provides integration with the Diffusion SDK for iOS and Android platforms.'
  s.homepage         = 'http://example.com'
  s.license          = { :type => 'MIT', :file => '../LICENSE' }
  s.author           = { 'Your Company' => 'email@example.com' }
  s.source           = { :git => "https://github.com/yourusername/diffusion_flutter.git", :tag => s.version.to_s }
  s.source_files = 'Classes/**/*'
  s.dependency 'Flutter'
  s.platform = :ios, '12.0'

    s.vendored_frameworks = 'Diffusion.xcframework'
    s.preserve_paths = 'Diffusion.xcframework'
    s.pod_target_xcconfig = {
      'DEFINES_MODULE' => 'YES',
      'EXCLUDED_ARCHS[sdk=iphonesimulator*]' => 'i386 arm64',
      'EXCLUDED_ARCHS[sdk=iphoneos*]' => 'i386 x86_64 arm64',
      'OTHER_LDFLAGS' => '-framework Diffusion'
    }

  s.swift_version = '5.0'
end

[dimejiogunyoye]

Hello @emreakcan - thanks for the heads up. We will look into this and get back to you

[seanmc86]

If this won't be changing anytime soon, does anyone have a recommendation for how to approach the problem when needing to build for both the simulator locally and an iOS device separately?

[dimejiogunyoye]

Hi @seanmc86 - we're investigating this and should be able to give a more definitive timeline on resolution (or workaround) as soon as possible

Thanks

[emreakcan]

Thanks @dimejiogunyoye
Our workaround is just to keep the real device framework in the CI pipeline, keep simulator in our local branches