How do you package an iOS framework for external consumption

Question

How do you package an iOS framework for external consumption Any recommended approach

Sam · Answer

At a minimum you can just zip up the framework bundle and distribute it Most people choose a package manager like Cocoapods Swift Package Manager may now work since it supports binaries now as well

dazza5000 · Answer

is swift package manager supported by apple

dazza5000 · Answer

Nikolay Kasyanov · Answer

IIRC SwiftPM s binary framework support is coming with Xcode 12

Nikolay Kasyanov · Answer

but binaries have to be packed as XCFramework the Kotlin s FatFramework task doesn t support it as of yet

Romain Dubreucq · Answer

I managed to make it work with CocoaPods let me know if you are interested

kpgalligan · Answer

I m very interested in this Have been wrestling with it for a few days < Romain Dubreucq> Do you mean CocoaPods and XCFramework I can get an XCFramework to work directly but when I try to push that into a cocoapods repo it fails I ve also tried using the fat framework task but that fails on archive

Romain Dubreucq · Answer

Here is a working podspec that uses FatFrameworkTask

kpgalligan · Answer

Interesting thanks

Romain Dubreucq · Answer

Feel free to ping me if you have issues

kpgalligan · Answer

Any chance you ve ever seen this We keep getting it when attempting to validate and push the archive to app store connect

kpgalligan · Answer

I m going to do a full clean and try again See if I can figure that out

Romain Dubreucq · Answer

You said that you were using XCFramework Because I don t think that I m using them on my side

Romain Dubreucq · Answer

The two last lines of the podspec are a workaround to fix an issue with Xcode 12 to prevent using arm64 in simulator Xcode 12 is prepared to build for Apple Silicon

kpgalligan · Answer

Not using XCFramework with that test I have multiple different attempts going on In this case I get that error after running the fat framework task It all seems to work fine until validating and or trying to distribute to the app store Digging some more though

kpgalligan · Answer

Waiting on confirmation but I m pretty sure it was something else in the podspec and had nothing to do with fat framework at all Kind of a big self own and another instance of be careful with copy paste

Romain Dubreucq · Answer

Hello you can share your podspec and your fat framework task if you want me to check

kpgalligan · Answer

No we figured it out We had reused another podspec which had `spec resources = ` in it I believe that copied the binary file directly into the framework resources and the Mach O header error was caused by the verifying seeing that file Pulling out the resources line fixed the issue