dokka: Can't find node by signature spam

I have a Java annotation that is imported in my class and I refer to it in the KDoc with [AnnotationName]. IntelliJ correctly links to the annotation but Dokka just spams Can't find node by signature foo.bar.AnnotationName. Additionally, the generated Javadoc does not link correctly to the annotation class.

About this issue

Original URL
State: closed
Created 7 years ago
Reactions: 8
Comments: 28 (5 by maintainers)

Commits related to this issue

Work around Dokka spamming on the shell as per Kotlin/dokka#184 — committed to AlchemistSimulator/Alchemist by DanySK 5 years ago
Try to work around Kotlin/dokka#184 also during publish — committed to AlchemistSimulator/Alchemist by DanySK 5 years ago

Most upvoted comments

This is still happening in 0.10.1

mrclrchtr on Mar 13, 2020

This is still happening on 0.9.17.

kirill-grouchnikov on Oct 9, 2018

I confirm this is still happening in 0.9.18.

atoulme on May 5, 2019

Can this ticket be reopened? I am observing the same behavior in version 0.10.1: … [WARNING] Can’t find node by signature android.view.SurfaceHolder, referenced at … This is probably caused by invalid configuration of cross-module dependencies [WARNING] Can’t find node by signature android.view.Surface, referenced at … This is probably caused by invalid configuration of cross-module dependencies [WARNING] Can’t find node by signature android.media.AudioManager$setStreamVolume(kotlin.Int, kotlin.Int, kotlin.Int), referenced at … This is probably caused by invalid configuration of cross-module dependencies [WARNING] Can’t find node by signature android.view.SurfaceHolder, referenced at … This is probably caused by invalid configuration of cross-module dependencies [WARNING] Can’t find node by signature android.view.Surface, referenced at … This is probably caused by invalid configuration of cross-module dependencies [WARNING] Can’t find node by signature android.graphics.SurfaceTexture, referenced at … This is probably caused by invalid configuration of cross-module dependencies [WARNING] Can’t find node by signature android.graphics.SurfaceTexture$getTimestamp(), referenced at … This is probably caused by invalid configuration of cross-module dependencies [WARNING] Can’t find node by signature android.view.Surface, referenced at … This is probably caused by invalid configuration of cross-module dependencies [WARNING] Can’t find node by signature android.media.AudioManager$setStreamVolume(kotlin.Int, kotlin.Int, kotlin.Int), referenced at … This is probably caused by invalid configuration of cross-module dependencies [WARNING] Can’t find node by signature android.media.audiofx.EnvironmentalReverb, referenced at … This is probably caused by invalid configuration of cross-module dependencies [WARNING] Can’t find node by signature android.media.audiofx.AudioEffect$getId(), referenced at … This is probably caused by invalid configuration of cross-module dependencies [WARNING] Can’t find node by signature android.media.MediaPlayer.OnErrorListener, referenced at … This is probably caused by invalid configuration of cross-module dependencies …

Thank you,

Moacir

msilva-verimatrix on Aug 17, 2020

I didn’t have this previously, but now I’m drowning in these messages…

xeruf on Jun 21, 2019

@hzsweers Yes

semoro on Feb 5, 2018

I confirm this is still happening in 0.10.0

Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
null:-1:-1: Tag @see cannot be used in inline documentation.  It can only be used in the following types of documentation: overview, package, class/interface, constructor, field, method.
null:-1:-1: Tag @see cannot be used in inline documentation.  It can only be used in the following types of documentation: overview, package, class/interface, constructor, field, method.
null:-1:-1: Tag @see cannot be used in inline documentation.  It can only be used in the following types of documentation: overview, package, class/interface, constructor, field, method.
null:-1:-1: Tag @see cannot be used in inline documentation.  It can only be used in the following types of documentation: overview, package, class/interface, constructor, field, method.
null:-1:-1: Tag @see cannot be used in inline documentation.  It can only be used in the following types of documentation: overview, package, class/interface, constructor, field, method.
null:-1:-1: Tag @see cannot be used in inline documentation.  It can only be used in the following types of documentation: overview, package, class/interface, constructor, field, method.
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
null:-1:-1: Tag @see cannot be used in inline documentation.  It can only be used in the following types of documentation: overview, package, class/interface, constructor, field, method.
null:-1:-1: Tag @see cannot be used in inline documentation.  It can only be used in the following types of documentation: overview, package, class/interface, constructor, field, method.
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
null:-1:-1: Tag @see cannot be used in inline documentation.  It can only be used in the following types of documentation: overview, package, class/interface, constructor, field, method.
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
null:-1:-1: Tag @see cannot be used in inline documentation.  It can only be used in the following types of documentation: overview, package, class/interface, constructor, field, method.
null:-1:-1: Tag @see cannot be used in inline documentation.  It can only be used in the following types of documentation: overview, package, class/interface, constructor, field, method.
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies

pavelaizen on Jan 20, 2020

@semoro An EAP would be appreciated for the rest of us experiencing this issue 😃

mattbdean on Dec 12, 2017