Verify --warning-mode all flag on all Gradle commands in Android CI

[Copilot]

The Android CI build was failing with generic Gradle errors. Adding --warning-mode all to Gradle commands provides detailed deprecation warnings for debugging.

Status

All 5 ./gradlew invocations in .github/workflows/android-ci.yml already include the flag:

• assembleDebug (line 54)
• assembleRelease with signing (lines 109-114)
• assembleRelease unsigned fallback (line 117)
• testDebugUnitTest (line 163)
• connectedDebugAndroidTest (line 234)

This was previously implemented in PR #36. No changes required.

# Example: multi-line command with signing parameters
./gradlew assembleRelease \
  -Pandroid.injected.signing.store.file=$(pwd)/app/release.keystore \
  -Pandroid.injected.signing.store.password="$KEYSTORE_PASSWORD" \
  -Pandroid.injected.signing.key.alias="$KEY_ALIAS" \
  -Pandroid.injected.signing.key.password="$KEY_PASSWORD" \
  --no-daemon --stacktrace --warning-mode all

Original prompt

The Android CI build is failing with a generic Gradle error. This pull request adds the --warning-mode all flag to all ./gradlew commands in the .github/workflows/android-ci.yml file. This will provide more detailed logs to identify the specific deprecations causing the failure.

This pull request was created as a result of the following prompt from Copilot chat.

The Android CI build is failing with a generic Gradle error. This pull request adds the --warning-mode all flag to all ./gradlew commands in the .github/workflows/android-ci.yml file. This will provide more detailed logs to identify the specific deprecations causing the failure.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.