How can I convert this to proper Kotlin Multiplatform code? `val ldt = LocalDateTime.ofInstant(Inst...

# multiplatform

[jQrgen]

How can I convert this to proper Kotlin Multiplatform code?

val ldt = LocalDateTime.ofInstant(Instant.ofEpochMilli(d.firstRecv), ZoneId.systemDefault())

Currently, it's not working on iOS:

Uncaught Kotlin exception: kotlinx.datetime.DateTimeArithmeticException: Instant [phone]T23:59:59.999999999Z is not representable as LocalDateTime.

[Joel Denke]

Something like this:

Clock.System.now().toLocalDateTime(TimeZone.UTC)

Use kotlinx datetime library.
toLocalDateTime is an extension in that library 🙂

[jQrgen]

Thanks, and where do I put the instant:Long ?

[jQrgen]

I have epoch milliseconds as the input

[Joel Denke]

Ah sorry you want from existing unix timestamp in the other direction kind a 😛
Hmm let me double check how I solved that 😄

[Joel Denke]

Instant.fromEpochMilliseconds, see https://kotlinlang.org/api/kotlinx-datetime/kotlinx-datetime/kotlinx.datetime/-instant/-companion/from-epoch-milliseconds.html

[Joel Denke]

In general, always use the kotlinx datetime extensions/classes, and will be safe. That including stuff like timezones.

[Joel Denke]

Like these kind of combos:

Clock.System.todayIn(TimeZone.currentSystemDefault())

[Joel Denke]

https://github.com/Kotlin/kotlinx-datetime
This provides a lot of nice examples. Its not all ofc.

[Joel Denke]

Instant.fromEpochMilliseconds(d.firstRecv).toLocalDateTime(TimeZone.currentSystemDefault())
I think in your case will be something like this 🙂

[jQrgen]

Thanks!!

[jQrgen]

Maybe I have been using the wrong "Instant"?

[jQrgen]

From java

[jQrgen]

For example with TimeZone

[Joel Denke]

Depends what mean wrong Instant. I think they partly overlapping some things, and some not. Its similar way had to deal with desugaring in Android or Threeten library wrapping things. As never been able in Android doing this in a nice way.
Its nice Jetbrains solve this multiplatform. I wished they had this back in time 😄

[Joel Denke]

But yeah I think if you using kotlinx.datatime.Instant and all those classes it will be fine.
And equivalent to the System.currentMilli weird thing, you using Clock.now etc instead.