Anybody have any insight as to why `embedAndSignAppleFrameworkForXcode` would be SKIPPED? I've gener...

# ios

[kpgalligan]

Anybody have any insight as to why embedAndSignAppleFrameworkForXcode would be SKIPPED? I've generally used local CocoaPods for building and avoided the embed task. Tried it recently and was pretty surprised at how easy that was to set up. Until now 🙂 It wasn't seeing my Kotlin changes. Did a Gradle clean, still not seeing them. Then did an Xcode clean, and now it doesn't see the module at all. Looking at the script in Xcode's build log I see

Showing All Messages
> Task :analytics:compileKotlinIosSimulatorArm64 UP-TO-DATE
> Task :breeds:generateCommonMainKMMBridgeKickStartDbInterface UP-TO-DATE
> Task :breeds:compileKotlinIosSimulatorArm64 UP-TO-DATE
> Task :allshared:compileKotlinIosSimulatorArm64
> Task :allshared:linkDebugFrameworkIosSimulatorArm64
> Task :allshared:assembleDebugAppleFrameworkForXcodeIosSimulatorArm64
> Task :allshared:embedAndSignAppleFrameworkForXcode SKIPPED

[russhwolf]

Was debugging an issue like this earlier today and it was a X64 vs Arm64 issue. Project was only configured for M1 simulators so the embed task wouldn't run when building for simulator on an Intel Mac, But that looks like the KMMBridge sample that I know has all simulator targets declared, so maybe something else.

[kpgalligan]

I figured it out. It was me not reading the docs fully.

[brandonmcansh]

@kpgalligan What was the issue that missed from the docs? Started seeing this as well while trying to integrate cocoapods for Google Maps

[kpgalligan]

That would probably be a different issue. In my case, you only embed if it's dynamic, and I was building static. That's not in the docs. What's in the docs is adding -framework "[your module]" to "Other Liner Args" and adding the "Framework Search Paths" to the framework in your build folder.

[brandonmcansh]

yp was able to get it to work 🙂

[mbonnin]

Just bumped into this and filed https://youtrack.jetbrains.com/issue/KT-66054 as a nice-to-have

[kpgalligan]

Yeah, actually addressing the issue is a good idea 🙂 I've been making "Android" code work on iOS for almost 10 years and debugging that took some effort. Not really "newbie friendly".