Create .xcframework with dependencies

I am trying to create a custom Swift xcframework "FrameworkA" for a client based on my own code, which has a dependency to another 3rd party framework "FrameworkB" (which I integrate through SPM). I'm having trouble figuring out the best way to do this.

In my case, I already have multiple targets in my project, and I have added another one for "FrameworkA", and added the relevant files to the framework target.

I can get my new framework to build if I add "FrameworkB" to "Framework and Libraries" section for my framework target, and adding it in code.

import FrameworkB 

let frameworkKit = FrameworkKit()

Now, referencing Apple's documentation, I used xcodebuild archive to create archive files for both "iOS" and "iOS Simulator".

However, when I read about 'umbrella frameworks', the answer listed here and Apple's documentation suggests that I shouldn't include a framework inside another framework.

So what are the concrete ways to accomplish this? I can't exclude the dependency because without it, my framework won't build at all.

When creating a custom Swift xcframework that has a dependency on a third-party framework, there are a few approaches you can take to ensure the proper integration without violating best practices. Here are some concrete ways to accomplish this:

1. Embed FrameworkB as a binary: Instead of including FrameworkB inside FrameworkA as a framework, you can embed FrameworkB as a binary in your FrameworkA xcframework. This way, FrameworkB is not treated as a framework within FrameworkA but rather as a binary dependency. To achieve this, follow these steps:

   • Build FrameworkB separately and obtain the binary file (e.g., FrameworkB.framework).
   • Add the binary to your FrameworkA project by dragging it into the project navigator.
   • In the project settings for FrameworkA, navigate to the target's settings, go to the "Build Phases" tab, and under "Embed Frameworks," add the FrameworkB binary.
   • In your code, you can continue to import and use FrameworkB.

   This approach avoids the potential issues associated with including one framework inside another.

2. Specify FrameworkB as a transitive dependency: If you're using Swift Package Manager (SPM) to manage dependencies, you can specify FrameworkB as a dependency of FrameworkA in your Package.swift file. This way, when you build or use FrameworkA, SPM will automatically handle the dependency resolution and include FrameworkB for you. Here's an example of how you can specify the dependency in your Package.swift:

   let package = Package(
       name: "FrameworkA",
       products: [
           .library(
               name: "FrameworkA",
               targets: ["FrameworkA"]
           ),
       ],
       dependencies: [
           .package(url: "https://github.com/vendor/FrameworkB", .upToNextMajor(from: "1.0.0")),
       ],
       targets: [
           .target(
               name: "FrameworkA",
               dependencies: [
                   .product(name: "FrameworkB", package: "FrameworkB"),
               ]
           ),
       ]
   )
   

   With this setup, when you build FrameworkA, SPM will automatically fetch and include FrameworkB as a dependency.

3. Document FrameworkB as a prerequisite: If FrameworkB is a separate framework that needs to be present alongside FrameworkA, you can document it as a prerequisite. In your documentation, provide clear instructions on how to obtain and include FrameworkB before integrating FrameworkA. This way, consumers of FrameworkA will be aware of the dependency and can handle its integration separately.

Choose the approach that best fits your requirements and project structure. Embedding the binary or using SPM for transitive dependency management are generally preferred to avoid issues related to including frameworks inside other frameworks.