Android Gradle builds
Use Gradle when export needs Android plugins, AAB, Java/Kotlin dependencies or Android-project changes. It does not replace matching templates and the Android S
Use Gradle when export needs Android plugins, AAB, Java/Kotlin dependencies or Android-project changes. It does not replace matching templates and the Android SDK.
Configure
- Complete Android preparation.
- Install the Android build template through the editor. Enable
gradle_build/use_gradle_buildin the preset.gradle_build/gradle_build_directoryselects its directory; do not reuse a random build directory from another version. - Build once without custom changes. Add dependencies/plugins one at a time to localize failures.
- Select APK or AAB through
gradle_build/export_format, then configure signing and architectures. - Export and retain the first complete Gradle error including
Caused by, not justBUILD FAILED.
Common causes
| Message | Check |
|---|---|
| Java/Gradle incompatibility | JDK 17 and this template’s wrapper; do not upgrade Gradle/AGP independently |
| Dependency not found | Coordinates, repository, network and private-repository access |
| Duplicate class | A dependency included as both a local AAR and a transitive dependency |
| Manifest merger failed | Conflicting attributes, minimum SDK and plugin manifest |
| Native library loading failure | ABI and transitive SO libraries inside the final APK |
The current template specifies Android Gradle Plugin 8.13.2. Do not substitute a number from an older guide. Generated directories can be reinstalled: keep custom changes reproducible and back up before replacing templates. No Gradle build was executed here.
Reckfell Engine documentationBack to top ↑