Can't download compose artifacts' source code in the common code.

[Irineu333]

Describe the bug

When the android and desktop targets are defined in a project with only one module, it is not possible to download the source code of the Compose artifacts in the common code nor in the desktop code (both seem to use the same artifacts, *_desktop). This is terrible because to develop for Compose, it is strictly necessary to explore the source code of the composable functions.

Targets
By adding more targets, for example, iOS, the problem is solved, from the moment the common code starts to use the common artifacts. So I assume that the problem is precisely the artifacts for JVM.

Modules
For some reason that I still don't understand, the bug does not exist in projects with multiple modules. So, projects created with the Kotlin Multiplatform Wizard suffer from this bug.

My personal template, for example, started to show the bug after consolidating everything into one module.

Discussed in #4263

Affected platforms

• Desktop (Windows, Linux, macOS)
• Android

Versions

• Kotlin version*: 1.9.22
• Compose Multiplatform version*: 1.6.1
• OS version(s)* (required for Desktop and iOS issues): Fedora 39
• OS architecture (x86 or arm64): x86
• JDK (for desktop issues): 17

To Reproduce
Steps and/or the code snippet to reproduce the behavior:

1. Define the android and desktop targets.
2. Create a simple hello world in the common code.
3. Open the used composable and click on "download sources".
4. Nothing happens.

Expected behavior
It should download the source code so that we can explore it.

Screenshots
Gravação de tela de 2024-03-23 00-12-41.webm

[mazunin-v-jb]

Hello! Thank you for submitting the issue.
Looks like the problem with the Kotlin Wizard only. Please, create a ticket in Kotlin Issue Tracker
And feel free to reopen if you have any questions.

[Irineu333]

@mazunin-v-jb I think it might be a bug in the IDE

[osipxd]

Maybe caused by IDEA-349334

[okushnikov]

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.