kotlin-tooling-cocoapods-spm-migration

Migrate Kotlin Multiplatform projects from CocoaPods to SwiftPM by adding swiftPMDependencies in Gradle, converting cocoapods imports to swiftPMImport, and reconfiguring iOS project wiring in Xcode to update framework embedding and linkage packaging.

Converting cocoapods imports to swiftPMImport involves transforming Kotlin namespace declarations from cocoapods.* to swiftPMImport.* and updating iOS integration wiring to reflect SwiftPM usage without breaking existing module builds.

Yes, SwiftPM can be introduced alongside existing CocoaPods configuration by adding swiftPMDependencies to enable SwiftPM-based linking, allowing a gradual migration path for your iOS modules before removing CocoaPods artifacts.

The best way to reconfigure Xcode project settings for SwiftPM in KMP is to update embedAndSign configurations, adjust linkage packaging, and apply Phase 5 integration steps to complete the migration in a single module.

CocoaPods artifacts should be removed in Phase 6 of the migration process, after swiftPMDependencies have been added, imports transformed, and iOS project wiring successfully reconfigured across Gradle and Xcode integrations.

Migrating KMP modules from CocoaPods to SwiftPM does not break iOS builds when properly executing namespace transformations and updating Pod and Xcode settings, ensuring continuous framework integration throughout the migration workflow.