Building an xcframework, how to get dependency framework headers to be included in final framework

I am building an xcframework that depends on a few other frameworks.

I have a header file which includes the header for one of the underlying frameworks. This is needed to make the framework build successfully: #import <MTBeaconPlus/MTBeaconPlus.h>

I archived 2 different framework builds for device and simulator architectures/platforms. I built the xcframework successfully. However, when I try to use the built framework in a project, I get an error stating: 'MTBeaconPlus/MTBeaconPlus.h' file not found

When I inspect the folder structure of my xcframework, I see the frameworks included for each architecture/platform build, but the headers folder for each isn't there. How do I make sure those are included when building the archives and then when using those archives to build the final xcframework?

Can you reduce your projects down to a basic skeleton that shows how the project is configured with a framework implementation that is akin to "Hello World"? The source code itself too interesting, but questions like yours are best answered when we have a buildable project skeleton that reflects your actual project configuration. Once you have such a test project, you can share a link to it here.

—Ed Ford,  DTS Engineer

Building an xcframework, how to get dependency framework headers to be included in final framework
 
 
Q