I recently updated datetime time from 0.6 to 0.7
B...
# kotlinx-datetimet
Tomáš Procházka
10/31/2025, 1:31 AMI recently updated datetime time from 0.6 to 0.7
But then it crashing at runtime in 3rd party libs that was build using older version on: "Failed resolution of: Lkotlinx/datetime/Instant"
It means that there is no way how to migrate to that new version until all libraries will migrate?
But nobody will migrate because nobody want to break somebody else project.
I was expected that Kotlin is able to follow that alias even in runtime and use right class instead of kotlinx/datetime/Instant.
j
jw
10/31/2025, 1:42 AMUse the compat version
gratitude thank you 1
jw
10/31/2025, 1:42 AMt
Tomáš Procházka
10/31/2025, 1:55 AMThanks!
j
jw
10/31/2025, 1:55 AMDon't forget to file a bug on the library, too!
t
Tomáš Procházka
10/31/2025, 1:59 AMIt is our internal company library. It is even worse then with public one 😭.
Tomáš Procházka
10/31/2025, 2:11 AMI hope that maven/gradle will consider
0.7.1-0.6.x-compat0.7.1j
jw
10/31/2025, 2:12 AMIt does, intentionally so
t
Tomáš Procházka
10/31/2025, 2:13 AMBut If some library will update in the future to 0.7.2 and other library will still use 0.6.X.
I will need to always update to the latest compat version in the application.
j
jw
10/31/2025, 2:42 AMFor the 0.7.x series, you will always have to use -compat if you have dependencies built against 0.6.x and using the offending types.
jw
10/31/2025, 2:42 AMI believe the plan is for 0.8.x to not have a compat artifact, so work on fixing your dependencies.
e
ephemient
10/31/2025, 10:47 PMI was expected that Kotlin is able to follow that alias even in runtimetypealiases are resolved at build time and the result is baked into the compiled code (which is pretty much the only way to be JVM compatible)
t
Tomáš Procházka
10/31/2025, 11:33 PMIt could create something like proxy class that will just call the original 😉
j
jw
10/31/2025, 11:44 PMThe type could be final
e
ephemient
11/05/2025, 11:29 PMcome to think of it, it should be possible to write a jetifier-style bytecode transform to fix libraries still using
kotlinx.datetime.{Duration,Instant}5 Views