I work on an SDK, and one of the ways we distribute it is as a pre-compiled static XCFramework. As far as I know, it’s the nature of a static framework to not contain symbols since the framework will be embedded in the final app binary, and the symbols should then be generated. However, when testing the "Validate" function of the Xcode 16 deployment process, our users are receiving a warning that says the framework does not contain symbols. Is my assumption about static frameworks and symbols incorrect? Could this be a bug in Xcode 16? Should we modify something in our framework to inform Xcode that symbols are not needed?

I have a lib that I also distribute with cocoapod, and the project has both Swift and Objc code. Im using modules to expose objc private classes to Swift, but some of this private classes also have a reference to the public objc classes. Then the compiler complains about "Duplicate interface definition" This does not happen if the project is created as a framework, but I have not control how the project will be used as. Any suggestion?

I have a swift Package, and I have some extra .h header to be shipped with the package, but this files are not copied to the build destination. It would be nice to have this files included as header in the modulemap file