Publishing in App Store fails for dynamic libraries about cargo-swift

[tapi]

I have some details here that might make it worth while reopening this.

iOS does not support shipping dylibs on the appstore, only macos does. Docs are here, Swift forum discussion here
For iOS we need to convert it to a universal library using lipo and then bundle the library, the module map and the header as a framework.

It may be worthwhile to do this for static libraries to produce static frameworks as well. It means simpler code in cargo-swift but it also allows for the inclusion of xcprivacy manifests which Apple has started warning about and will be required in the future.

I was taking a crack at hand hacking the xcframework with frameworks but was getting issues in Xcode, the Swift wrapper could not see the uniffi header symbols, I was wondering if these docs might be related to the issue I was seeing. Some useful context, The framework and binary must have the same name, ie RustModule.framework must contain the RustModule binary, otherwise xcodebuild -create-xcframework will fail with an error code of 70. The path it attempts to copy matches that naming. Might be worth filing a rdar to just copy the contents, but I don't have high hopes that it would ever get addressed.

If we can get dynamic frameworks working it would be awesome to include a step to generate dsyms for them so stack traces can be decoded on platforms like Crashlytics, Bugsnage, etc