I’m seeing the following problem: If I cancel a coroutine with a specific exception as the cause on the JVM, I can access that cause with exception.cause. But if I run the same code on K/N, the cause is null. Any ideas how to solve this? Ironically, the exception.message still states, that it was caused by the correct exception, I just don’t have access to it.
11/19/2019, 2:59 PM
That’s a #kotlin-native question. Currently K/N does not “natively” (pun intended) support cause.