Open nizam-betterapp opened 6 days ago
I did the following and tried to figure out which library is not working with ksp incremental
Added these flags to track the dirty files
ksp.incremental=true
ksp.incremental.log=true
I commented compose destinations ksp line in build.gradle and ran the gradlew command
// ksp "io.github.raamcosta.compose-destinations:ksp:$raamcostaVersion"
./gradlew :app:kspDebugKotlin --scan
Dirty flag was perfect as below:
Dirty / All: 0.05%
Disappeared Outputs
Affected By CP
Affected By new syms
src/main/java/ai/blox100/feature_zen_mode/presentation/bottom_sheet_end_session/ZenEndSessionViewModel.kt
build/generated/ksp/debug/java/byRounds/1/ai/blox100/feature_zen_mode/presentation/bottom_sheet_end_session/ZenEndSessionViewModel_HiltModules.java
Affected By sealed
CP changes
Dirty:
src/main/java/ai/blox100/feature_zen_mode/presentation/bottom_sheet_end_session/ZenEndSessionViewModel.kt
Dirty / All: 0.05%
When i uncommented the ksp of compose destinations it shows 100% dirty
Dirty / All: 100.00%
This makes every line change in the code taking 13 seconds extra for building. I have been stuck with this issue for 2 days. Any help would be deeply appreciated.
Simple steps to reproduce
ksp.incremental=true
ksp.incremental.log=true
My main question, is this what it is expected due to the library (or) Am I misisng something?
It looks like you have fixed this issue in v2. Is my understanding correct?
Everytime we make a code change (eg: add a log line), kspDebugKotlin step takes 13 seconds and causes issues. Is this expected due to annotation library (or) is it supposed to be compiling incrementally? below is our gradle.properties Can you please help here how to enable ksp incremental build
org.gradle.jvmargs=-Xmx8g -XX:+HeapDumpOnOutOfMemoryError -Dfile.encoding=UTF-8 -XX:+UseParallelGC -Dkotlin.daemon.jvm.options=-Xmx8g -XX:+HeapDumpOnOutOfMemoryError