fix: pass keystore properties in release workflow - #141
Conversation
The CI workflow was failing because the release `signingConfig` in `app/build.gradle.kts` expects the `storePassword`, `keyAlias`, and `keyPassword` values to be provided via Gradle properties. This commit passes the environment variables mapped from GitHub Secrets to the `./gradlew` command using the `-P` flags. Co-authored-by: tazztone <62671577+tazztone@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
1 participant
Fixes a CI failure in the "🚀 Production Release (AAB/APK)" workflow where the
Build App Bundle & APKstep fails due to missing keystore properties in the releasesigningConfig.The problem was that the
app/build.gradle.ktsconfiguration was looking for Gradle properties (e.g.project.findProperty("storePassword")) but the GitHub Action was only supplying-PstoreFile=../keystore.jksalongside environment variables.This PR passes the three required credentials as
-Pparameters to the./gradlew bundleRelease assembleReleasecommand, properly resolving the properties.PR created automatically by Jules for task 7459182430651629229 started by @tazztone