Tag: gradle

The manifest's .MainActivity resolves against the Gradle namespace, and no class with that name is in the APK. Make namespace, the Kotlin package line, and the manifest agree.

Another Gradle process holds ~/.gradle/caches/journal-1 and cannot hand it over. Find the Owner PID, kill that daemon, and stop deleting .lock files: that only moves the error.

On Windows, Kotlin incremental compilation fails when the Flutter project and the pub cache sit on different drives. Move PUB_CACHE to the project's drive or turn off IC for pub-cache plugins.

The full path from an AGP 8 Flutter app that applies kotlin-android to AGP 9.1 with android.builtInKotlin=true on Flutter 3.47. Every step was built and measured, including the two edits that look optional and are not: kotlinOptions is a compile error under KGP 2.2+, and the KGP line in settings.gradle.kts has to stay.

The release APK shipped without libapp.so. Flutter 3.44.0 to 3.44.4 could drop it: upgrade to 3.44.5 or later and split the combined subprojects block.

The JEP 472 warning on JDK 24+ is harmless and prints once. Fix it by matching your JDK to a Gradle version that supports it, not by pasting flags into gradle.properties.

Gradle is compiling with a JRE. It is not searching your machine, it is using the exact JVM it was launched on. Point flutter config --jdk-dir at a real JDK, or clear org.gradle.java.home.

The SDK Manager is re-unpacking a corrupt archive it cached in .downloadIntermediates. Delete that folder and the half-extracted ndk/<version> directory, then re-run the build.

Play rejects the bundle because a 64-bit .so still has 4 KB ELF segments. Find the offending library, rebuild it with NDK r28+, and verify with zipalign -P 16.

That line is a wrapper, not the error. Re-run with flutter run --verbose or ./gradlew assembleDebug --stacktrace, read the real Gradle failure, then fix that.