A problem occurred configuring project ':kmp'. > Sentry Cocoa Framework not found at /user/path/.../

[franmontiel]

Platform

Apple

Installed

None

Version

0.1.0

Steps to Reproduce

1. Create a new KMP app project and use "Regular Framework" for distribution to Xcode.
2. Add the Sentry KMP plugin.
3. Sync gradle and the error will appear. The same one mentioned in this issue -> [Gradle Plugin] improve error message #303

Expected Result

Sentry is added to my KMP project and let me build it.

Actual Result

Cannot sync gradle, the following error appears:
A problem occurred configuring project ':shared'.

Sentry Cocoa Framework not found at /path/to/iosApp/build/SourcePackages/artifacts/sentry-cocoa/Sentry-Dynamic/Sentry-Dynamic.xcframework/ios-arm64 or /path/to/iosApp/build/SourcePackages/artifacts/sentry-cocoa/Sentry/Sentry.xcframework/ios-arm64

[buenaflor]

hey, this is definitely a docs issue and an error message issue, you have to add the Sentry-Cocoa dependency via SPM first if you use a regular framework. we should mention it in the error message as well

[franmontiel]

I added Sentry SPM dependency to the iosApp and the problem persists. I also tried with Sentry-Dynamic and the result is the same.

[franmontiel]

Seems to only start working if I add the cocoapods plugin but according to this comment it shouldn't be needed

[buenaflor]

@franmontiel if you add the cocoapods plugin it will work because our gradle plugin detects this and installs the sentry-cocoa dependency via the cocoapods plugin.

can you show your kmp gradle config? in case you changed something

/path/to/iosApp/ doesnt seem right unless you purposefully changed the log

[franmontiel]

The /path/to/iosApp/ was just me modifying the path as it was irrelevant.

Here the gradle file as it is failing right now

import org.jetbrains.kotlin.gradle.dsl.JvmTarget

plugins {
    alias(libs.plugins.kotlinMultiplatform)
    alias(libs.plugins.androidLibrary)
    id("io.sentry.kotlin.multiplatform.gradle") version "0.10.0"
}

kotlin {
    androidTarget {
        compilations.all {
            compileTaskProvider.configure {
                compilerOptions {
                    jvmTarget.set(JvmTarget.JVM_1_8)
                }
            }
        }
    }
    
    listOf(
        iosX64(),
        iosArm64(),
        iosSimulatorArm64()
    ).forEach {
        it.binaries.framework {
            baseName = "shared"
            isStatic = false
        }
    }

    sourceSets {
        commonMain.dependencies {
            //put your multiplatform dependencies here
        }
        commonTest.dependencies {
            implementation(libs.kotlin.test)
        }
    }
}

android {
    namespace = "io.bridify.sentrytest"
    compileSdk = 35
    defaultConfig {
        minSdk = 24
    }
    compileOptions {
        sourceCompatibility = JavaVersion.VERSION_1_8
        targetCompatibility = JavaVersion.VERSION_1_8
    }
}

[buenaflor]

Thanks! I was able to reproduce it.

The issue is that in newer versions the sentry-cocoa artifacts changed the folder names

• ios-arm64
• ios-arm64_x86_64-maccatalyst
• ios-arm64_x86_64-simulator

turned into

• ios-arm64_arm64e
• ios-arm64_arm64e_x86_64-maccatalyst
• ios-arm64_x86_64-simulator

I will add a fix for this

[buenaflor]

If you want to try it out for now you can for example use the sentry-cocoa version8.37.0 which will still be compatible

[franmontiel]

With version 8.37.0 the same thing is happening.

For what I am understanding we required the Sentry library to be build in a specific folder location (that I believe it does not coincide with the XCode default build folder). Could that be the cause?

I tried moving my DerivedData folder to a different place and using frameworkPath option to direct to the exact folder were the .xcframework was, is this the expected setup?

[buenaflor]

I tested it locally on a new project with 8.37.0 which works and 8.38.0 which doesnt work.

by default the gradle plugin will use the xcodeproj to determine where the build folder is located via xcodebuild -project yourproject.xcodeproj -showBuildSettings which spits out a bunch of info including BUILD_DIR which points to the derived data path of your build and thats where we are looking for the framework that you installed with SPM

if for some reason that deviates you'll need to update the frameworkPath configuration to point to that - that's the main purpose of this option so in your case it is expected although I am not sure in your case why the framework is not in the build folder that we receive from the xcodebuild command

can you paste here the location where the framework is by default? (before you moved it)