Repository navigation
AAPT2 36.0.0 Daemon Startup Failed on Samsung Galaxy S25 FE (ARM64) — Code on the Go 26.44 #2211
Replies: 2 comments
|
Thanks for the detailed report. The error means Code on the Go couldn’t start AAPT2, the tool that packages your app’s resources. Potential causes:
Potential solutions:
If none of this helps, we can look for other causes. Thank you. |
|
Hi @kwoohoo25-del — I'm not official support, just an experienced Code on the Go user, building on Ben's triage above. Your two direct AAPT2 tests are the most important clue in this report, and they are not the same failure, so they should not be treated as one problem. What the two errors actually mean
Why this points at the toolchain launch, not your project A brand-new Java Empty Activity with default settings failing the same way as your separate KEN Workflow project makes a project-specific resource, manifest or source-code defect very unlikely. Step 1 — Find the exact binary Gradle is launching, before changing anything Your manual tests may not be testing the same file Gradle uses. The SDK copy under Look for the exact AAPT2 path, the line where the daemon is started, and the first Step 2 — Confirm the device side with numbers, not assumptions In the same terminal / environment you tested AAPT2 in, run:
Step 3 — Inspect that exact executable Once you have the path from Step 1, substitute it here (use the Gradle path, not a different copy you happened to test): What matters: does Step 4 — Check where the binary lives and whether the OS will let anything execute there For the exact directory holding that AAPT2, check the mount, the directory permissions and the security context, plus free space: Look for Step 5 — Only then, the version pairing After the executable checks, confirm the toolchain pairing, because it is a real but secondary suspect here — an AGP/Gradle/JDK mismatch does not explain How the fix follows from the evidence
Could you post back one consolidated reply with: the full |
Uh oh!
There was an error while loading. Please reload this page.
Problem
I am using Code on the Go version 26.44 on my Samsung Galaxy S25 FE running Android 17 (ARM64).
I cannot successfully build Android APKs because AAPT2 fails to start.
Error Message
Execution failed for task ':app:processDebugResources'
AAPT2 36.0.0 Daemon #0: Daemon startup failed
BUILD FAILED
Steps to Reproduce
The same error occurs in my separate KEN Workflow Android project.
Troubleshooting Already Completed
Expected Behavior
Code on the Go should compile a basic Android project and produce a debug APK.
Actual Behavior
The build fails because the AAPT2 daemon cannot start.
Question
Is there a known ARM64 AAPT2 compatibility issue in version 26.44? Is there an officially supported fix or configuration that will allow APK builds directly on my phone?
Thank you for your assistance.
All reactions