Could not determine the dependencies of task ':app:compileDebugJavaWithJavac'. #554

tifroz · 2025-12-13T00:42:30Z

tifroz
Dec 13, 2025

I am trying to set up dual-platform logging using the directions provided for swift-android-native/AndroidLogging. The module SWConsoleLogger (native) that depends on it gets compiled ok via swift build or skip android build but I keep hitting this error when building the Project from Xcode:

FAILURE: Build failed with an exception.

* What went wrong:
Could not determine the dependencies of task ':app:compileDebugJavaWithJavac'.
error: Could not determine the dependencies of task ':app:compileDebugJavaWithJavac'.
> Could not resolve all dependencies for configuration ':app:debugCompileClasspath'.
   > Could not resolve project :skipstone:SWConsoleLogger.
     Required by:
         project ':app' > project :skipstone:HelloSkip
         project ':app' > project :skipstone:HelloSkip > project :skipstone:HelloModel
         project ':app' > project :skipstone:HelloSkip > project :skipstone:SWFuseLogger
         project ':app' > project :skipstone:HelloSkip > project :skipstone:SWXLogger
      > No matching variant of project :skipstone:SWConsoleLogger was found. The consumer was configured to find a library for use during compile-time, preferably optimized for Android, as well as attribute 'com.android.build.api.attributes.AgpVersionAttr' with value '8.13.0', attribute 'com.android.build.api.attributes.BuildTypeAttr' with value 'debug', attribute 'org.jetbrains.kotlin.platform.type' with value 'androidJvm' but:
          - No variants exist.

* Try:
> Creating consumable variants is explained in more detail at https://docs.gradle.org/9.1.0/userguide/declaring_dependencies.html#sec:resolvable-consumable-configs.
> Review the variant matching algorithm at https://docs.gradle.org/9.1.0/userguide/variant_attributes.html#sec:abm_algorithm.
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to generate a Build Scan (Powered by Develocity).
> Get more help at https://help.gradle.org.

Here are the relevant parts from Package.swift:

// swift-tools-version: 6.0
// This is a Skip (https://skip.tools) package.
import PackageDescription

let package = Package(
    name: "swishly-x-logger",
    defaultLocalization: "en",
    platforms: [.iOS(.v17), .macOS(.v14), .visionOS(.v1), .tvOS(.v17)],
    products: [
[...]
        .library(name: "SWConsoleLogger", type: .static, targets: ["SWConsoleLogger"]),
    ],
    dependencies: [
        .package(url: "https://source.skip.tools/skip.git", from: "1.6.28"),
        .package(url: "https://source.skip.tools/skip-foundation.git", from: "1.0.0"),
        .package(url: "https://source.skip.tools/skip-bridge.git", from: "0.16.0"),
        .package(url: "https://source.skip.tools/skip-fuse.git", from: "1.0.0"),
        .package(url: "https://github.com/skiptools/swift-android-native", from: "1.0.0"),
        .package(url: "https://github.com/pointfreeco/swift-dependencies", from: "1.0.0"),
        // Local override for combine-schedulers (transitive dep from swift-dependencies)
        .package(path: "../combine-schedulers")
    ],
    targets: [
      [...]
        .target(name: "SWConsoleLogger", dependencies: [
          .product(name: "AndroidLogging", package: "swift-android-native", condition: .when(platforms: [.android]))
        ], plugins: [.plugin(name: "skipstone", package: "skip")]),
    ]
)

and from the code:

import Foundation
#if canImport(Darwin)
import OSLog
#elseif os(Android)
import AndroidLogging
#endif

let logger = Logger(subsystem: "Subsystem", category: "Category")

public protocol SWLogger: Sendable {
    func v(_ message: @autoclosure () -> String, tag: String, file: String, line: Int32, function: String, error: Error?)
    ...
  
}


public extension SWLogger {
    func v(_ message: @autoclosure () -> String, tag: String = "general", file: String = #file, line: Int32 = #line, function: String = #function, error: Error? = nil) {
        v(message(), tag: tag, file: file, line: line, function: function, error: error)
    }
    ...
}


public class SWConsoleLogger: SWLogger, @unchecked Sendable {
    
    ...
    private func makeMessage(_ message: String?, _ error: Error?) -> String {
    ...
    }  

    private func logOutput(level: String, tag: String, file: String, line: Int32, function: String, message: String) {
        let formattedMessage = "[\(tag)] \(filename(from: file)):\(line) \(function) - \(message)"
        logger.info("\(formattedMessage)")
    }

    public func v(_ message: @autoclosure () -> String, tag: String, file: String, line: Int32, function: String, error: Error?) {
        let composed = makeMessage(message(), error)
        logOutput(level: "V", tag: tag, file: file, line: line, function: function, message: composed)
    }
    ...
}

skip.yml for the SWConsoleLogger module:

# Configuration file for https://skip.tools project
# Uses OSLog.Logger on Apple, AndroidLogging on Android for cross-platform logcat
skip:
  mode: 'native'

tifroz · 2025-12-13T01:09:53Z

tifroz
Dec 13, 2025
Author

Adding the entire log file from Xcode
Build HelloSkip App_2025-12-12T16-29-39.txt

0 replies

marcprux · 2025-12-13T01:22:10Z

marcprux
Dec 13, 2025
Maintainer

Can you describe SWConsoleLogger a bit more? Is this a pure native module, or does it utilize Skip for bridging? If it is a stand-alone pure-Swift Android module without any Kotlin dependencies, then you can exclude the skipstone plugin and all the Skip dependencies (like skip-foundation). If it is indeed a pure Swift project that only needs other pure Swift dependencies (and note, AndroidLogging in swift-android-native is also pure-Swift), then the usage of the skipstone plugin might be confusing the Gradle build process into thinking that there should be a Kotlin component, which could be that is triggering the failure.

Showing the output of swift package show-dependencies might help more light on the dependency expectations.

1 reply

tifroz Dec 13, 2025
Author

Thanks! The module itself has no kotlin dependencies (pure swift), but the package it belongs to does have transpiled modules (hence the .package(url: "https://source.skip.tools/skip-foundation.git", from: "1.0.0") and other dependencies).

I removed the skipstone plugin (below), but the outcome did not change

...
.target(name: "SWConsoleLogger", dependencies: [
          .product(name: "AndroidLogging", package: "swift-android-native", condition: .when(platforms: [.android]))
        ]),
....

Here is the output for swift package show-dependencies for the SWConsoleLogger module:

swift package show-dependencies
Found unhandled resource at /Users/hugo/Swishly/Projects/webvideocast/sandbox/skip-sandbox/swishly-x-logger/Sources/SWRawLogger/Resources
Found unhandled resource at /Users/hugo/Swishly/Projects/webvideocast/sandbox/skip-sandbox/swishly-x-logger/Sources/SWFuseLogger/Resources
warning: 'swift-dependencies': Conflicting identity for combine-schedulers: dependency 'github.com/pointfreeco/combine-schedulers' and dependency '/users/hugo/swishly/projects/webvideocast/sandbox/skip-sandbox/combine-schedulers' both point to the same package identity 'combine-schedulers'. The dependencies are introduced through the following chains: (A) /users/hugo/swishly/projects/webvideocast/sandbox/skip-sandbox/swishly-x-logger->github.com/pointfreeco/swift-dependencies->github.com/pointfreeco/combine-schedulers (B) /users/hugo/swishly/projects/webvideocast/sandbox/skip-sandbox/swishly-x-logger->/users/hugo/swishly/projects/webvideocast/sandbox/skip-sandbox/combine-schedulers. If there are multiple chains that lead to the same dependency, only the first chain is shown here. To see all chains use debug output option. To resolve the conflict, coordinate with the maintainer of the package that introduces the conflicting dependency. This will be escalated to an error in future versions of SwiftPM.
warning: 'skip-android-bridge': Conflicting identity for swift-android-native: dependency 'source.skip.tools/swift-android-native' and dependency 'github.com/skiptools/swift-android-native' both point to the same package identity 'swift-android-native'. The dependencies are introduced through the following chains: (A) /users/hugo/swishly/projects/webvideocast/sandbox/skip-sandbox/swishly-x-logger->source.skip.tools/skip-fuse->source.skip.tools/skip-android-bridge->source.skip.tools/swift-android-native (B) /users/hugo/swishly/projects/webvideocast/sandbox/skip-sandbox/swishly-x-logger->github.com/skiptools/swift-android-native. If there are multiple chains that lead to the same dependency, only the first chain is shown here. To see all chains use debug output option. To resolve the conflict, coordinate with the maintainer of the package that introduces the conflicting dependency. This will be escalated to an error in future versions of SwiftPM.
warning: 'swishly-x-logger': dependency 'skip-fuse' is not used by any target
.
├── skip<https://source.skip.tools/[email protected]>
├── skip-foundation<https://source.skip.tools/[email protected]>
│   ├── skip<https://source.skip.tools/[email protected]>
│   └── skip-lib<https://source.skip.tools/[email protected]>
│       ├── skip<https://source.skip.tools/[email protected]>
│       └── skip-unit<https://source.skip.tools/[email protected]>
│           └── skip<https://source.skip.tools/[email protected]>
├── skip-bridge<https://source.skip.tools/[email protected]>
│   ├── skip<https://source.skip.tools/[email protected]>
│   ├── skip-lib<https://source.skip.tools/[email protected]>
│   │   ├── skip<https://source.skip.tools/[email protected]>
│   │   └── skip-unit<https://source.skip.tools/[email protected]>
│   │       └── skip<https://source.skip.tools/[email protected]>
│   ├── skip-foundation<https://source.skip.tools/[email protected]>
│   │   ├── skip<https://source.skip.tools/[email protected]>
│   │   └── skip-lib<https://source.skip.tools/[email protected]>
│   │       ├── skip<https://source.skip.tools/[email protected]>
│   │       └── skip-unit<https://source.skip.tools/[email protected]>
│   │           └── skip<https://source.skip.tools/[email protected]>
│   └── swift-jni<https://source.skip.tools/[email protected]>
├── skip-fuse<https://source.skip.tools/[email protected]>
│   ├── skip-android-bridge<https://source.skip.tools/[email protected]>
│   │   ├── skip<https://source.skip.tools/[email protected]>
│   │   ├── skip-foundation<https://source.skip.tools/[email protected]>
│   │   │   ├── skip<https://source.skip.tools/[email protected]>
│   │   │   └── skip-lib<https://source.skip.tools/[email protected]>
│   │   │       ├── skip<https://source.skip.tools/[email protected]>
│   │   │       └── skip-unit<https://source.skip.tools/[email protected]>
│   │   │           └── skip<https://source.skip.tools/[email protected]>
│   │   ├── swift-jni<https://source.skip.tools/[email protected]>
│   │   ├── skip-bridge<https://source.skip.tools/[email protected]>
│   │   │   ├── skip<https://source.skip.tools/[email protected]>
│   │   │   ├── skip-lib<https://source.skip.tools/[email protected]>
│   │   │   │   ├── skip<https://source.skip.tools/[email protected]>
│   │   │   │   └── skip-unit<https://source.skip.tools/[email protected]>
│   │   │   │       └── skip<https://source.skip.tools/[email protected]>
│   │   │   ├── skip-foundation<https://source.skip.tools/[email protected]>
│   │   │   │   ├── skip<https://source.skip.tools/[email protected]>
│   │   │   │   └── skip-lib<https://source.skip.tools/[email protected]>
│   │   │   │       ├── skip<https://source.skip.tools/[email protected]>
│   │   │   │       └── skip-unit<https://source.skip.tools/[email protected]>
│   │   │   │           └── skip<https://source.skip.tools/[email protected]>
│   │   │   └── swift-jni<https://source.skip.tools/[email protected]>
│   │   └── swift-android-native<https://github.com/skiptools/[email protected]>
│   │       └── swift-jni<https://source.skip.tools/[email protected]>
│   └── swift-jni<https://source.skip.tools/[email protected]>
├── swift-android-native<https://github.com/skiptools/[email protected]>
│   └── swift-jni<https://source.skip.tools/[email protected]>
├── swift-dependencies<https://github.com/pointfreeco/[email protected]>
│   ├── combine-schedulers</Users/hugo/Swishly/Projects/webvideocast/sandbox/skip-sandbox/combine-schedulers@unspecified>
│   │   ├── swift-concurrency-extras<https://github.com/pointfreeco/[email protected]>
│   │   ├── xctest-dynamic-overlay<https://github.com/pointfreeco/[email protected]>
│   │   └── opencombine<https://github.com/OpenCombine/[email protected]>
│   ├── swift-clocks<https://github.com/pointfreeco/[email protected]>
│   │   ├── swift-concurrency-extras<https://github.com/pointfreeco/[email protected]>
│   │   └── xctest-dynamic-overlay<https://github.com/pointfreeco/[email protected]>
│   ├── swift-concurrency-extras<https://github.com/pointfreeco/[email protected]>
│   ├── xctest-dynamic-overlay<https://github.com/pointfreeco/[email protected]>
│   └── swift-syntax<https://github.com/swiftlang/[email protected]>
└── combine-schedulers</Users/hugo/Swishly/Projects/webvideocast/sandbox/skip-sandbox/combine-schedulers@unspecified>
    ├── swift-concurrency-extras<https://github.com/pointfreeco/[email protected]>
    ├── xctest-dynamic-overlay<https://github.com/pointfreeco/[email protected]>
    └── opencombine<https://github.com/OpenCombine/[email protected]>

marcprux · 2025-12-13T02:51:49Z

marcprux
Dec 13, 2025
Maintainer

I'm still not entirely understanding the structure. Your original error message lists modules HelloSkip, HelloModel, SWFuseLogger, SWXLogger, and SWConsoleLogger . Which of those is intended to be pure Swift, and which of them need to use Skip for bridging and/or transpilation?

If you run swift package show-dependencies from the topmost project (HelloSkip, I think), what does it show? And can you show the Skip/skip.yml for each of the listed modules?

0 replies

tifroz · 2025-12-13T04:16:32Z

tifroz
Dec 13, 2025
Author

`HelloSkip` Package Modules

Both modules HelloSkip and HelloModel are native. The only changes made to the sample app are

Some additional log calls
Added some dependencies to Package.swift (below)

        .package(url: "https://github.com/pointfreeco/swift-dependencies", from: "1.0.0"),
        .package(path: "../combine-schedulers"),
        .package(path: "../swishly-x-logger")

`swishly-x-logger` Package Modules

All modules are native, unbridged except for SWRawLogger (which is transpiled + bridged)
<< means 'depends on'

SWFuseLogger <<SWXLogger + SWConsoleLogger + Dependencies from the swift-dependencies package
SWConsoleLogger << AndroidLogging
SWXLogger <<SWConsoleLogger + SWRawLogger
SWRawLogger (transpiled + bridged) << NSLoggerObjC ObjC NSLogger client + has the Java source code for the Android NSLogger client

...apologies for the inconsistent/confusing naming, we are experimenting with this project sandbox to learn/validate a few things, including how to best structure our app in terms of packages/modules (needless to say so we are not exactly navigating in a straight line)

For context, the responsibilities for SWConsoleLogger simply to provide a logging functionality to the app's native modules, logging to the Xcode console (ios) + logcat (Android)

Attaching package.swift from swishly-x-logger + HelloSkip for completeness

Packages.zip

1 reply

marcprux Dec 14, 2025
Maintainer

Where, there is a problem that I see:

        .package(path: "../combine-schedulers"),
        .package(path: "../swishly-x-logger")

We unfortunately don't support this in native packages. The reason is that we need to relocate and modify the Package.swift files when we perform the native build. Which generally works fine, but it breaks relative package references. If you can change this to be the absolute path to the packages, that will resolve that issue.

All that being said, I don't see how this issue is causing your particular build errors, but it might be a good first step to fix it.

Another thing you might try while debugging this is to run skip export --verbose --debug, which might provide some additional insights into the cause of the issue.

tifroz · 2025-12-17T22:47:15Z

tifroz
Dec 17, 2025
Author

Apologies for the delay, I had to deal with some distractions :(

Update #1: I had to restore the skipstone plugin config to the SWConsoleLogger module in order to get past the issue below (the issue was not raised initially - likely something to do with build caching?)

error: Build input file cannot be found: '/[...]/xcodelocations/DerivedData/[...]/BuildToolPluginIntermediates/swishly-x-logger.output/SWConsoleLogger/skipstone/.SWConsoleLogger.sourcehash'. Did you forget to declare this file as an output of a script phase or custom build rule which produces it? (in target 'swishly-x-logger_SWXLogger' from project 'swishly-x-logger')

Update #2: The original issue (Could not determine the dependencies of task ':app:compileDebugJavaWithJavac'.) cleared after updating the SWConsoleLogger config in Package.swift to add a SkipFoundation dependency (see below)

...
   .target(name: "SWConsoleLogger", dependencies: [
          .product(name: "SkipFoundation", package: "skip-foundation"),
        ], plugins: [.plugin(name: "skipstone", package: "skip")]),
...

Here's a clearer summary of the package's dependency tree (excluding external dependencies, test targets)

-SWFuseLogger (native)
      -SWConsoleLogger
      -SWXLogger (native)
            -SWRawLogger (transpiled, bridged)
                   -NSLoggerObjC (NSLogger ObjC client)
                   -NSLogger.java (NSLogger android client)
            -SWConsoleLogger (native)

I think I now understand that, because the SWConsoleLogger imports Foundation (its only import in fact), it must make the dependency to SkipFoundation explicit in Package.swift.

Is this the right interpretation? Or was SWConsoleLogger was singled out because it was the only native module in the package that did not depend directly or indirectly on a skip module?

4 replies

marcprux Dec 17, 2025
Maintainer

That might be the issue. Any target that uses the skipstone plugin should have a dependency on at least one other Skip package (typically SkipFoundation, but it could be a lower-level one like SkipLib). So if you need SWConsoleLogger to use the skipstone plugin (e.g., to create Kotlin bridging or transpile embedded Kotlin), then add a target dependency on a Skip library.

You might also not need the skipstone plugin for that target, in which case you should be able to simply remove it from the plugins attribute.

tifroz Dec 18, 2025
Author

SWConsoleLogger should not have a need for the skipstone plugin, at least not as I understand it (native, unbridged, does not interface with kotlin at all).

I tried removing both the skipstone plugin and the SkipFoundation dependency from the previous (working) state, but landed right back on the error couldn't build /[...]/skipstone/.SWXLogger.sourcehash because of missing inputs: /[...]/skipstone/.SWConsoleLogger.sourcehash

The target was defined as simply .target(name: "SWConsoleLogger")

It would be great to have some clarity on the subject of these native modules with no apparent run-time need for skip modules - but we have a way forward by adding the SkipFoundation dependency, & that is good enough for us at the moment

marcprux Dec 18, 2025
Maintainer

This might just be an issue where you need to clean the Xcode project (and maybe restart) and then rebuild.

Does SWConsoleLogger build from the Terminal with skip android build? If so, then you probably don't need any Skip dependency, and you should be able to exclude any Skip dependencies from the target. You only need the skipstone plugin and a Skip dependency (like SkipFoundation) if you are using any Skip-specific features, like bridging to Kotlin or resource handling.

tifroz Dec 18, 2025
Author

skip android build --target SWConsoleLogger completes successfully no matter the config in Package.swift

However, when building the entire package with skip android build:

with .target(name: "SWConsoleLogger"), in Package.swift:

settings.gradle.kts: note: settings.gradle.kts (3 KB) gradle settings written
/root/sandbox/skip-sandbox/swishly-x-logger/.build/plugins/outputs/swishly-x-logger/SWRawLogger/destination/skipstone/.SWRawLogger.sourcehash: note: .SWRawLogger.sourcehash (233 bytes) sourcehash written
[35/197] Skip SWRawLogger
error: couldn't build /root/sandbox/skip-sandbox/swishly-x-logger/.build/plugins/outputs/swishly-x-logger/SWXLogger/destination/skipstone/.SWXLogger.sourcehash because of missing inputs: /root/sandbox/skip-sandbox/swishly-x-logger/.build/plugins/outputs/swishly-x-logger/SWConsoleLogger/destination/skipstone/.SWConsoleLogger.sourcehash
[36/197] Copying .SWRawLogger.sourcehash
[37/197] Emitting module SwiftJNI
[37/197] Write sources
[38/197] Emitting module SWConsoleLogger
[39/197] Emitting module ConcurrencyExtras
[40/197] Emitting module IssueReportingPackageSupport
Error: Error terminated(code: 1) running command: /Users/hugo/Library/Developer/Toolchains/swift-6.2-RELEASE.xctoolchain/usr/bin/swift build --swift-sdk aarch64-unknown-linux-android28 -Xswiftc -DSKIP_BRIDGE -Xswiftc -DTARGET_OS_ANDROID

with .target(name: "SWConsoleLogger", dependencies: [ .product(name: "SkipFoundation", package: "skip-foundation"), ], plugins: [.plugin(name: "skipstone", package: "skip")])

[...]
[551/556] Emitting module SWFuseLogger
[552/556] Compiling SWFuseLogger AnyDynamicObject_Support.swift
[553/556] Compiling SWFuseLogger resource_bundle_accessor.swift
[554/557] Wrapping AST for SWFuseLogger for debugging
[555/557] Write Objects.LinkFileList
[556/557] Archiving libSWFuseLogger.a
Build complete! (20.91s)

Are there any artifacts from the build logs to help detect if the SWConsoleLogger module is unwittingly using any skip-specific feature? I will share the content
SWConsoleLogger.zip
from the SWConsoleLogger module here for reference.

Skip

Could not determine the dependencies of task ':app:compileDebugJavaWithJavac'. #554

Uh oh!

Uh oh!

tifroz Dec 13, 2025

Replies: 5 comments · 6 replies

Uh oh!

tifroz Dec 13, 2025 Author

Uh oh!

marcprux Dec 13, 2025 Maintainer

Uh oh!

tifroz Dec 13, 2025 Author

Uh oh!

Uh oh!

marcprux Dec 13, 2025 Maintainer

Uh oh!

tifroz Dec 13, 2025 Author

HelloSkip Package Modules

swishly-x-logger Package Modules

Uh oh!

marcprux Dec 14, 2025 Maintainer

Uh oh!

tifroz Dec 17, 2025 Author

Uh oh!

marcprux Dec 17, 2025 Maintainer

Uh oh!

tifroz Dec 18, 2025 Author

Uh oh!

marcprux Dec 18, 2025 Maintainer

Uh oh!

tifroz Dec 18, 2025 Author

tifroz
Dec 13, 2025

Replies: 5 comments 6 replies

tifroz
Dec 13, 2025
Author

marcprux
Dec 13, 2025
Maintainer

tifroz Dec 13, 2025
Author

marcprux
Dec 13, 2025
Maintainer

tifroz
Dec 13, 2025
Author

`HelloSkip` Package Modules

`swishly-x-logger` Package Modules

marcprux Dec 14, 2025
Maintainer

tifroz
Dec 17, 2025
Author

marcprux Dec 17, 2025
Maintainer

tifroz Dec 18, 2025
Author

marcprux Dec 18, 2025
Maintainer

tifroz Dec 18, 2025
Author