You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Builds from Android Studio sometimes break because of the motif generated file.
The stacktrace was similar to #188.
While debugging why this happens, I found the repro steps.
Repro Steps
Execute the following commands in motif repo's current master branch. (f95ecde)
Second assemble command will fail with the following error
> Task :samples:sample-kotlin:compileDebugKotlin FAILED
e: ..../motif/samples/sample-kotlin/src/main/java/motif/sample/MainActivity.kt: (24, 40): Unresolved reference: MainScopeImpl
FAILURE: Build failed with an exception.
Reason why build fails
When the first build finishes, MainScopeImpl.kt is generated.
When the second build is triggered, kapt generates stub for kotlin files including the generated kotlin files.
(You can find the stub file after the second build fails)
This makes motif compiler think that MainScopeImpl is already generated and skip the code generation for MainScopeImpl when there will be no MainScopeImpl since kapt will erase the previous generated files.
This issue doesn't happen when motif.mode is changed to java.
The text was updated successfully, but these errors were encountered:
Library version: 0.3.4
Builds from Android Studio sometimes break because of the motif generated file.
The stacktrace was similar to #188.
While debugging why this happens, I found the repro steps.
Repro Steps
Execute the following commands in motif repo's current master branch. (f95ecde)
Second assemble command will fail with the following error
Reason why build fails
When the first build finishes, MainScopeImpl.kt is generated.
When the second build is triggered, kapt generates stub for kotlin files including the generated kotlin files.
(You can find the stub file after the second build fails)
This makes motif compiler think that MainScopeImpl is already generated and skip the code generation for MainScopeImpl when there will be no MainScopeImpl since kapt will erase the previous generated files.
This issue doesn't happen when motif.mode is changed to java.
The text was updated successfully, but these errors were encountered: