I’m having a bit of trouble with Dokka on a Kotlin...

# dokka

[Ben Lancaster]

I’m having a bit of trouble with Dokka on a Kotlin Multiplatform, multi-module project. Unfortunately the error message/stacktrace are pretty vague and I haven’t really got much of a clue where to start, can anyone give me some pointers? More in the thread…

[Ben Lancaster]

The stack overflow is on org.jetbrains.kotlin.descriptors.impl.AbstractTypeAliasDescriptor$typeConstructor$1.getSupertypes(AbstractTypeAliasDescriptor.kt:108)

Untitled.txt

[Ben Lancaster]

seems to happen on any of the dokka*MultiModule commands (I’ve tried HTML and GFM)

[Ben Lancaster]

and using 1.6.21

[Ben Lancaster]

I have 5 modules, and only one of them throws like this, the other modules’ dokka*Partial commands work fine

[Ben Lancaster]

I figured out what was wrong. we had the following expect class:

public expect class WeakReference<T : Any>(referred: T) {
    public fun get(): T?
}

With actual implementations that looked like this:

iOS:

import kotlin.native.ref.WeakReference

public actual typealias WeakReference<T> = WeakReference<T>

Android:

import java.lang.ref.WeakReference

public actual typealias WeakReference<T> = WeakReference<T>

[Ben Lancaster]

The solution was to use an import alias, like so:

// android
import java.lang.ref.WeakReference as JvmWeakReference

public actual typealias WeakReference<T> = JvmWeakReference<T>

// ios
import kotlin.native.ref.WeakReference as NativeWeakReference

public actual typealias WeakReference<T> = NativeWeakReference<T>

[Joffrey]

Did this only make Dokka fail? Or did the compiler fail before that? I'm surprised it even compiled!

[Vadim Mishenev]

This is https://github.com/Kotlin/dokka/issues/2281
I suppose you did not configure your project correctly.
You can take a look at my sample project with typealias WeakReference .

[Karel Petránek]

I am actually the author of the Github issue. This only happens in Dokka and compiles fine when Dokka is disabled.

[Karel Petránek]

I agree it’s not the best code but it would be great if Dokka didn’t crash with a hard-to-find stackoverflow error. Still need to provide a reproducer for the issue as it doesn’t seem to be happening in isolation.