Open
Description
I tried to update a dependency which already depends on 0.7.0
and got an error from another dependency (Coil) which still depends on 0.6.2
that kotlinx.datetime.Clock
wasn't found. Then I tried to force the compatibility version in my root build.gradle.kts
with
allprojects {
configurations.all {
resolutionStrategy {
force("org.jetbrains.kotlinx:kotlinx-datetime:0.7.0-0.6.x-compat")
}
}
}
but now get a different error
Caused by: java.lang.NoSuchMethodError: No static method year$default(Lkotlinx/datetime/format/DateTimeFormatBuilder$WithDate;Lkotlinx/datetime/format/Padding;ILjava/lang/Object;)V in class Lkotlinx/datetime/format/DateTimeFormatBuilder$WithDate$DefaultImpls; or its super classes (declaration of 'kotlinx.datetime.format.DateTimeFormatBuilder$WithDate$DefaultImpls' appears in /data/app/~~7Z3_IikACjkCB-_civW-EQ==/de.penny.app.debug-kzv8FZtDrjNSMuRnZiqteg==/base.apk!classes24.dex)
at coil3.network.cachecontrol.internal.UtilsKt.BROWSER_DATE_TIME_FORMAT$lambda$17$lambda$11(utils.kt:120)
at coil3.network.cachecontrol.internal.UtilsKt.$r8$lambda$XswvxyzVtkM_bmImCCcvwvcumyI(Unknown Source:0)
at coil3.network.cachecontrol.internal.UtilsKt$$ExternalSyntheticLambda7.invoke(D8$$SyntheticClass:0)
at kotlinx.datetime.format.AbstractDateTimeFormatBuilder$DefaultImpls.appendAlternativeParsingImpl(DateTimeFormatBuilder.kt:458)
at kotlinx.datetime.format.DateTimeComponentsFormat$Builder.appendAlternativeParsingImpl(DateTimeComponents.kt:643)
at kotlinx.datetime.format.DateTimeFormatBuilderKt.alternativeParsing(DateTimeFormatBuilder.kt:394)
at coil3.network.cachecontrol.internal.UtilsKt.BROWSER_DATE_TIME_FORMAT$lambda$17(utils.kt:119)
at coil3.network.cachecontrol.internal.UtilsKt.$r8$lambda$P2kSIgKbgxvklJRj6h-PvKCZauc(Unknown Source:0)
at coil3.network.cachecontrol.internal.UtilsKt$$ExternalSyntheticLambda10.invoke(D8$$SyntheticClass:0)
at kotlinx.datetime.format.DateTimeComponents$Companion.Format(DateTimeComponents.kt:58)
at coil3.network.cachecontrol.internal.UtilsKt.<clinit>(utils.kt:95)
Could there be an issue with the compatibility layer?
Metadata
Metadata
Assignees
Labels
No labels