GeezerVison

Kotlin-metadata warnings from D8

Every CI build logs ~1000 lines of

WARNING: D8: An error occurred when parsing kotlin metadata. This normally happens when using a newer version of kotlin than the kotlin version released when this version of R8 was created.
WARNING: D8: Unexpected error during rewriting of Kotlin metadata for class 'kotlin.text.StringsKt__StringBuilderJVMKt':

during mergeExtDexDebug. f36b01c moved Kotlin to 2.4.10 while AGP stayed on 8.12.1, whose bundled R8 (8.12.14) predates Kotlin 2.4 metadata. Per Google's AGP/D8/R8 requirements for Kotlin, Kotlin 2.4 needs R8 9.1.29+, and no 8.x AGP bundles that (8.13.2 ships 8.13.19, which only knows 2.3). AGP 9.x would, but it requires Gradle 9.6, built-in Kotlin and the removal of the legacy variant API, which the shipped app/build.gradle and NativeScript plugins rely on; that is a separate migration.

So this PR:

• bumps AGP to 8.13.2 (last 8.x), and
• pins com.android.tools:r8:9.1.43 on the buildscript classpath, the override mechanism the same doc describes.

Both are NS_DEFAULT_* properties in gradle.properties and overridable per project (-Pr8Version=..., like -PandroidBuildToolsVersion). Since gradle.properties and build.gradle ship in the npm package, every app build picks this up.

Measured locally on :app:mergeExtDexDebug --rerun-tasks:

Gradle deprecation notices

CI on Gradle 8.14.3 reports three kinds of deprecation; all are fixed so --warning-mode all is clean:

1. Groovy space-assignment (namespace "x" → namespace = "x", removed in Gradle 10): the reported sites in runtime/build.gradle, app/build.gradle, BuildToolTask.gradle, plus the same pattern at ignoreExitValue, the root build.gradle task description, and main → mainClass on the SBG JavaExec.
2. Gradle.useLogger (removed in 9.0): CustomExecutionLogger.gradle is now a BuildService implementing OperationCompletionListener. It records TaskFailureResults and prints the same styled failure summary from close(), still skipping BuildToolTask failures (those log their own errors). StyledTextOutputFactory cannot be injected into a build service, so the script hands the output over in taskGraph.whenReady; that makes it not configuration-cache compatible, which it wasn't before either.
3. -b <file> custom build file (removed in 9.0): the jsparser spec now runs gradlew -p static-binding-generator, whose settings.gradle sets rootProject.buildFileName = 'runtests.gradle'. That settings file is only read for standalone runs; as a test-app subproject nothing changes.

Verified: ./gradlew :app:help :runtime:help --warning-mode all goes from 10 deprecation lines to 0 (the one remaining warning is KGP saying Gradle 8.14.3 itself is deprecated), runSbgTests passes 8/8, and a forced task failure prints the styled summary exactly once.

Not in this PR

Deprecations that only fire on code paths CI's help-style runs don't exercise, left for a follow-up since they need ExecOperations/design choices:

• Task.project at execution time in cleanupAllJars (app/build.gradle:641, error in Gradle 10).
• project.exec {} inside doFirst/doLast (runtime/build.gradle:322,328, root build.gradle:75; removed in Gradle 9).
• The root build.gradle's runTests still invokes -b runtests.gradle in test-app/, which has its own settings, so the buildFileName trick doesn't apply there.

Summary by CodeRabbit

• Chores

  • Updated build configuration syntax across multiple scripts for consistency.
  • Adjusted project setup so standalone builds use the intended build file and launch settings.
  • Updated default Android build tool and related version settings.

• Bug Fixes

  • Improved build failure reporting so task errors are collected and shown more reliably.
  • Updated build execution setup to work with the latest Gradle and Android toolchain changes.