My Expo-managed React Native project (0.65 +) suddenly stops during the “Run gradlew” phase when I trigger an Android build on EAS, returning only the generic “Gradle build failed with unknown error.” I haven’t consciously edited any Gradle files, so I need a fresh set of eyes to comb through the logs, isolate the real cause, and get the build green again. Scope • Analyse the full build log produced by EAS or a local `./gradlew assembleRelease` run. • Apply the necessary fixes—whether that means Gradle wrapper tweaks, SDK version alignment, dependency resolution, or script edits—so the project compiles into a working AAB / APK for Android. • Document every change in plain language so I can reproduce the fix on future builds and in CI. Acceptance criteria 1. `eas build -p android` (or equivalent local Gradle command) completes without errors. 2. The resulting AAB installs and launches successfully on an Android device or emulator. 3. A concise changelog explains what broke, what you changed, and why it works now. Tools in play: Expo CLI, EAS Build, Gradle, Android Studio (for local debugging). Remote troubleshooting via GitHub branch or screenshare is fine—whatever is quickest for you to deliver the fixed build.