Skip to content

iOS targets fail to resolve in KMP project after adding v1.0.0 #51

Description

@mtpdog

Congratulations on this major milestone for the library!

We're running into an issue when trying to integrate it. After adding the dependency:

implementation("dev.nucleusframework:composewebview:1.0.0")

the Gradle build fails because it can't resolve the iOS targets in our Kotlin Multiplatform project:

> Could not resolve all files for configuration ':shared:iosArm64CInterop'.
   > Could not find composewebview:webview-compose-iosarm64:unspecified.

Activity

  1. self-assigned this
    on Aug 8, 2026
  2. added a commit that references this issue on Aug 10, 2026
    280bb24
  3. kdroidFilter commented on Aug 11, 2026

    @kdroidFilter
    Collaborator

    Fixed in 1.0.1, now on Maven Central.

    implementation("dev.nucleusframework:composewebview:1.0.1")

    Cause: the release job ran on ubuntu-latest, where iosArm64 / iosSimulatorArm64 are disabled. Kotlin still emitted their variants into the root Gradle module metadata, but with Gradle's default project coordinates — hence composewebview:webview-compose-iosarm64:unspecified — and the iOS klibs were never uploaded.

    Fix (#52): releases are published from a macOS runner, plus a verifyPublicationCoordinates check that fails the publish if any variant in the root module metadata points outside the group/version being released.

    Verified on a fresh KMP consumer resolving from Maven Central: iosArm64CInterop resolves to dev.nucleusframework:composewebview-iosarm64:1.0.1, and both compileKotlinIosArm64 and linkDebugFrameworkIosSimulatorArm64 succeed. Thanks for the report!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions