With Kotlinx datetime 0.7.0, there is a crash due to missing `kotlinx/datetime/Clock$System`

[opatry]

I can't update to Kotlinx Datetime 0.7.0 because of a runtime crash when running KtorMonitor which relies on kotlinx.datetime.Clock which doesn't exist anymore.

See changelog for 0.7.0: https://github.com/Kotlin/kotlinx-datetime/releases/tag/v0.7.0

Remove kotlinx.datetime.Instant and kotlinx.datetime.Clock in favor of kotlin.time.Instant (Kotlin/kotlinx-datetime#506). See https://github.com/Kotlin/kotlinx-datetime?tab=readme-ov-file#deprecation-of-instant for a description of what to do if this causes problems.

Also, Ktor 3.2.1 was updated to take this into account as well: https://github.com/ktorio/ktor/releases/tag/3.2.1

Replace kotlinx.datetime APIs with kotlin.time (KTOR-8635)

---

Edit Oh, my bad, it appears it's already done in 7f36aa3

Do you plan to release this quickly or are some other changes on the road? Maybe you were waiting for Ktor 3.2.1?

[opatry]

In 0.7.1 (https://github.com/Kotlin/kotlinx-datetime/releases/tag/v0.7.1), they introduced typealias to ease migration, especially useful in this case.

[opatry]

In fact, even with 0.7.1, I still have java.lang.ClassNotFoundException: kotlinx.datetime.Clock$System…

[opatry]

I missed the instructions provided in the Kotlinx Datetime README.md

Here is the recommended procedure for migrating from kotlinx-datetime version 0.6.x or earlier to 0.7.x:

• First, simply try upgrading to 0.7.1. If your project has a dependency on kotlinx-datetime, but doesn't have dependencies on other libraries that are themselves reliant on an older kotlinx-datetime, you are good to go: the code should compile and run. This applies both to applications and to libraries!
• If your project depends on other libraries that themselves use an older version of kotlinx-datetime, then your code may fail at runtime with a ClassNotFoundException for kotlinx.datetime.Instant or kotlinx.datetime.Clock, or maybe even fail to compile. In that case, please check if the affected libraries you have as dependencies have already published a new release adapted to use Instant and Clock from kotlin.time.
• If you use kotlinx-serialization to serialize the Instant type, update that dependency to use 1.9.0 or a newer version.
• If all else fails, use the compatibility release of kotlinx-datetime. Instead of the version 0.7.1, use 0.7.1-0.6.x-compat. This artifact still contains kotlinx.datetime.Instant and kotlinx.datetime.Clock, ensuring that third-party libraries reliant on them can still be used. This artifact is less straightforward to use than 0.7.1, so only resort to it when libraries you don't control require that the removed classes still exist.

TL;DR: use Kotlinx Datetime 0.7.1-0.6.x-compat version until dependencies are updated.