These are screenshots from two separate projects I...

# android-studio

[eygraber]

These are screenshots from two separate projects I have. They both use the same versions of Kotlin, Gradle, etc... What would cause the difference between how commonMain is being treated by the IDE here?

[efemoney]

They do not have the same build configuration. On the right src/commonMain/kotlin is added as a source root. Looks like custom configuration either directly in the build scripts or from a plugin.

[eygraber]

The projects are using the exact same configuration

[eygraber]

After I restarted the IDE they both look like the one on the left ¯\_(ツ)_/¯

[efemoney]

Very curious. I guess it was a fluke.

[mkrussel]

I had the same thing happen yesterday with Intellij. Created a new module but it wouldn't recognize commonMain (other directories worked) but a closing and reopening of the project fixed it.

[Zac Sweers]

@eygraber do you do any management of source sets in your build file? such as using compose-resources and making them visible to android variants via something like sourceSets["main"].resources.srcDirs("src/commonMain/resources")? That was the issue for me

[eygraber]

It's possible I do that in one of my convention plugins that the project uses. I'll check that out, thanks

[eygraber]

I do have some code that manages the source set in a convention plugin, but for this project none of those paths should get hit

[Zac Sweers]

¯\_(ツ)_/¯

[eygraber]

I'm just chalking it up to Android Studio getting some wires crossed. Everything has been fine since then (and was fine then as well); was just curious about what was going on 😅