Today we have an Android/Ios library that we deliver to our ios project via cocoapods. It's pretty easy to switch between using a published cocoapod and local development (using podspec build phases). Iteration times are slow though. Using something like

embedAndSignAppleFrameworkForXcode

speeds things up but that doesn't work with making ios archives (?). Has anyone here included

embedAndSignAppleFrameworkForXcode

in a development proces where it's easy to switch between compiling kotlin locally and using some precompiled artifact (XCFramework, cocoapod)?

Hi Siggi, Could you please elaborate on

embedAndSignAppleFrameworkForXcode

not working with iOS archives? Do you mean there are some problems with archiving iOS app for distribution?

It works fine for me when making archives. The code completion has stopped working for some reason but everything else is fine.

Encouraging to hear Sam. Code completion fails sometimes for us as well, might be unrelated. So that wouldn't be a deal breaker for us . Yes Viacheslav embedandsign is not working for us with archives, I just get a Swift compiler error "No such module ". After looking at the source code for the plugin I assumed it was expected to only work with debug builds and other solutions were required for release builds (assembleXCFramework + some build logic) Good to hear that it's supposed to work with archives/releases. I was mostly using: https://blog.jetbrains.com/kotlin/2021/07/multiplatform-gradle-plugin-improved-for-connecting-kmm-modules/ and the linked project. Is there any other documentation I should look at to narrow down our problem?

I can not say for sure why it does not work in your setup. But my guess is that you use custom Xcode configurations for archiving. If this is true, you should add KOTLIN_FRAMEWORK_BUILD_TYPE variable to your Xcode build settings and set it to release or debug for each of your custom xcode configurations. Here is an example If this does not resolve your issue please submit a ticket to Youtrack and provide a minimal reproducer if possible.

Thanks for that. No custom configuration, just Debug and Release. Not sure why, but it seems to be working now 👍 ...except for some new signing issue. The signing issue is not present on my minimal reproducer so hopefully something we can figure out.