🚀 CodeAssist 3.19.0

BUILD OUTPUT

The build log is readable now. It shows the steps as they run (> Task :app:compileKotlin), your errors and warnings, and a closing BUILD SUCCESSFUL in 12.4s. Everything the build used to say about its own bookkeeping (cache hits, dex accounting, resource merging) moved behind a Show build details toggle in the Log tab.
When something goes wrong inside CodeAssist itself, you get one line saying what happened instead of twenty lines of Java stack trace. The full details are still there for a bug report: Copy takes the whole log, details and all.
Compiler errors appear once. A failed Kotlin or Java build used to print every error twice, once as a clickable problem and again as a wall of raw text.
Errors come from the compilers directly rather than being read back out of their printed output, so a problem now carries its exact column and the offending line of source, and things that merely mention the word "error" are no longer coloured red.
Better messages from the resource compiler, the dexer, the manifest merger and the signer, and each one points at the file it came from.

BUILD SYSTEM

A module's src/test folder is no longer compiled into the module itself. Test code that used its test-only dependencies (a test assertion library, a shared fixtures module) failed with what looked like unresolved references in your own code.
A testImplementation dependency on another module no longer counts as a build order dependency. That kind of dependency is normally circular on purpose, and the build refused to configure with a cyclic-dependency error naming modules that do not depend on each other.
A module whose Kotlin is entirely generated (a Compose Res class, output from an annotation processor) is compiled and packaged. It used to be skipped, and the generated classes went missing from the APK.

FIXES

Parts of the on-device build system were calling Java methods that do not exist below Android 14. They would have failed on most devices, silently in one case.

Navigation Menu