uli
03/15/2024, 11:50 AMcompileCommonMainKotlinMetadata
due to an error in one of my actual app source files. (just a typo in the imports).
I don’t think I have ever seen that on pure android projects so it was quite surprising to me to see that the actual app sources are relevant for the sync process. And it is a real pain to make the app sources compile again without your IDE working.
Am I doing something wrong here?
Is this just a plain (known?) bug that needs to be fixed in the gradle plugin?
Or does it work as designed due to some multi platform requirements?
I’d be thankful if anyone could shed some light on that issue.uli
03/15/2024, 11:57 AMGleb
03/15/2024, 5:48 PMuli
03/15/2024, 8:40 PMGleb
03/16/2024, 10:27 PMuli
03/18/2024, 7:44 AMTing-Yuan Huang
03/18/2024, 6:07 PMTing-Yuan Huang
03/18/2024, 6:10 PMkspCommonMainMetadata
to see if the problems remains?uli
03/20/2024, 4:17 PMuli
03/20/2024, 4:49 PMuli
03/20/2024, 6:37 PMkotlin.mpp.enableCInteropCommonization=true
on the main project will cause the task compileCommonMainKotlinMetadata
to run on the includeBuild during IDE gradle project sync and thereby causes the sync to fail on all errors in the kotlin codeuli
03/20/2024, 7:01 PMuli
03/22/2024, 8:39 AMI found the cause:
Having a main kotlin multi platform project with an includeBuild kotlin multi platform library. Then settingon the main project will cause the taskkotlin.mpp.enableCInteropCommonization=true
to run on the includeBuild during IDE gradle project sync and thereby causes the sync to fail on all errors in the kotlin code (edited)compileCommonMainKotlinMetadata
Here is a reproducer:
https://github.com/uluckas/SyncIssueDemo