Tolriq
10/06/2022, 6:38 AMTrevor Stone
10/06/2022, 2:08 PMTolriq
10/06/2022, 2:12 PMAlex Acosta
10/06/2022, 3:30 PMVitor Hugo Schwaab
10/06/2022, 9:54 PM1.6.21
), where the IDE failed to autocomplete types and suggest auto-import when using library types from the Android project. But it got worse after that.
The elephant in the room is that the Kotlin Plugin for the IDE (be it IntelliJ or Android Studio) doesn't officially support Multiplatform projects + Composite builds, see this issue.
As you can see in the comments, @mbonnin did come up with a work-around there to solve it, although I'm not sure he had the same exact issue with composite builds (IDE not resolving symbols between modules of the included build).
I tried my luck with it and couldn't make it work with all the IDEs I mentioned before. The project I'm working on has a different structure so maybe I missed something when trying to apply the same idea and ended up leaving it to the side.
We ended up staying in 1.6.10
because we're really close to releasing to prod, and we want stable grounds and as-fast-as-possible development until then.
Considering that the IDE can resolve all symbols from the library when making changes to the Android project.
And that the IDE can resolve all library symbols from other modules when opening the IDE in the library directly.
Our team agreed that after we release we're bumping Kotlin, updating libraries and start:
• Opening the IDE on the Android project if you want to make changes there
• Opening the IDE directly in the KMP library if you want to change the library
Personally I already do this most of the time anyway. But for some that got used to just opening the Android project and managing everything in there, this can be a bit annoying to get used to.Vitor Hugo Schwaab
10/06/2022, 10:14 PMmbonnin
10/07/2022, 6:41 AMchrmelchior
10/07/2022, 1:03 PM