How do you actually use the

frameworkName.set("name...")

setting? 'cause with this setup

listOf(
        iosX64(),
        iosArm64(),
        iosSimulatorArm64()
    ).forEach {
        it.binaries.framework {
            isStatic = true
        }
    }

// Rest of the file...

kmmbridge {
    frameworkName.set("ZenBreakCoreKit")
    spm()
    mavenPublishArtifacts()
}

I get

Only one framework name currently allowed. Found ZenBreakCoreKit and shared-core

and the docs don't mention anything about this Additionally, previously I was setting the baseName inside the framework block, and I was getting a wrong name in the github packages, like shared-core-kmmbridge with unspecified version

Are you using the template project or setting up your own? If setting up your own, you need to configure version.

I've setup the project a while ago with the compose multiplatform template. I checked your template before asking here and I think I copied all relevant instructions. Which

version

are you referring to?

Gradle config for pretty much anything has a

version

property. KMMBridge uses that. I was looking through the docs to find where that's clearly explained, and it's not, so we need to update that. The docs are mostly around using the tutorial, then just "docs". Anyway,

version

needs to be set on Gradle https://github.com/touchlab/KMMBridgeSKIETemplate/blob/main/build.gradle.kts#L28, then the docs that talk about it are here https://kmmbridge.touchlab.co/docs/general/CONFIGURATION_OVERVIEW#versionmanager, but they're not clear about version, so we'll need to update that.

Alright, I'll try that then. But what's the point of autoversion if I need it in gradle?

Are you using autoversion? If so, you need to pull that into Gradle. Autoversion is just a CI thing.

I'm using the autoversion workflow yeah

Yeah, same issue on our end. We talk about autoversion for CI, but don't really explain that bit

I'll decide between the two, there should be no issues with autoversion if I also have another version for my full app releases on github correct?

You mean if you have

1.2

as your prefix and

1.2.12

(for example) as the dev/published version for KMMBridge builds? If your app version is

1.2

I haven't tested that scenario, but SPM should prefer

1.2.12

over

1.2

, so I would assume that should be fine. If you can explain a bit better how your version releases would work, it might be easier to comment and test it out.

basically I'm making a desktop app (for the multiplatform contest ^^ irrelevant) and I publish releases of that on github, versioned releases obv. so example release 1.0.0 has all the installers for the 1.0.0 version, release 1.0.1 is the next one etc... The swift package compiled from the shared kotlin module of the app would go out with the 0.1.x version prefix to not interfere with the "actual app" versions

OK, if you're pushing tags with 0.1.x for SPM, assuming Xcode is grabbing them < 1.0.0, you should be fine.

perfect appreciate the help a ton

Appreciate the feedback. Let me know how that goes and if you run into more issues.

One last thing, would about the naming. What's the proper way of setting it?