title: How to build an iOS xcframework from Swift framework importing an Obj-C project
body: <p><strong>### SOLVED ###</strong></p>
  <p>What we changed was to remove any umbralla headers etc in our Objective-C project (static library). Instead we added a private module map (named PROJECT_Private) and a regular module map. Also added the private module map in the build settings. In the private one we import headers we need from the static library. That way those could be used in our Swift code without being exposed to any app.</p>
  <p><strong>### SOLVED ###</strong></p>
  <p>Our target is to be able to deliver a Swift framework to other app developers to enable them to easily implement our functionality.</p>
  <p>Our goal is:</p>
  <ul>
  <li>We have an Objectice-c project which contains Java-converted classes + some native Objective-C classes. We want to add a Swift interface on top of it which utilizes the Objective-C code to allow Swift app developers to import it and simply call functions on the Swift interface to use our functionality.</li>
  </ul>
  <p>Our current situation:</p>
  <ul>
  <li>We use Xcode 12.4</li>
  <li>We have the Objective-C code project which is used as a project with target static library. It has an added module with an umbrella header which exports most of the Objective-C code.</li>
  <li>We have created a Swift framework which imports the Objective-C project (as a static library, .a). It references the Objective-C project by importing the module with the umbrella header in classes where we reference Objective-C code.</li>
  <li>We have set Distribution as a library to YES in both projects</li>
  <li>We want to use it in Swift apps.</li>
  </ul>
  <p>When building the framework into an xcframework everything seems fine. However, when we try to add it to an application and build it complains about the Swift framework import of our Objective-C umbrella header module, simply saying the module is not found.</p>
  <p>What would be the solution to building this framework so that an app can use it? We can't completely move away from Objective-C b/c it would require us to rewrite A LOT of code.</p>