Skip to content

ci(play): fix gradlew exec bit and align store password secret#42

Merged
AKPWebDesign merged 1 commit into
developfrom
fix/play-workflow-gradlew-and-secret
May 4, 2026
Merged

ci(play): fix gradlew exec bit and align store password secret#42
AKPWebDesign merged 1 commit into
developfrom
fix/play-workflow-gradlew-and-secret

Conversation

@AKPWebDesign

Copy link
Copy Markdown
Member

Two fixes for the first failing run of the Publish to Google Play workflow:

  1. gradlew was 100644 in the repo, so the Ubuntu runner failed with ./gradlew: Permission denied (exit 126). Set the execute bit in the index with git update-index --chmod=+x gradlew. This is the right long-term fix — it lives in git's tree and works for every checkout, no chmod step required in the workflow.

  2. Secret name mismatch. The workflow referenced secrets.ANDROID_KEYSTORE_PASSWORD but the Gradle property in app/build.gradle is ANDROID_STORE_PASSWORD, and that's the name the secret was actually created under. Renamed both the workflow reference and the README table to ANDROID_STORE_PASSWORD so all five secrets line up 1:1 with the Gradle properties they feed.

Caught from the failed run logs at https://github.com/WhenApp/WhenApp-Android/actions/runs/25323562875.

Two fixes for the failing 'Publish to Google Play' run (#41 follow-up):

1. gradlew was committed with mode 100644, so the runner refused to
   execute it ('./gradlew: Permission denied', exit 126). Set the
   execute bit in the index via 'git update-index --chmod=+x gradlew'
   so checkouts on Linux runners can invoke it directly.

2. The workflow read the store password from a secret named
   ANDROID_KEYSTORE_PASSWORD, but the matching Gradle property in
   app/build.gradle is ANDROID_STORE_PASSWORD. Renamed the workflow
   reference + README documentation to ANDROID_STORE_PASSWORD so all
   five secrets line up 1:1 with the Gradle property names.
@AKPWebDesign AKPWebDesign merged commit 4afaa18 into develop May 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant