Fix Build and Deploy workflow

[M4dhav]

🐛 Describe the bug

Because of previous changes to the App to make it compatible for automatic deployment to the Google Play Store, and other changes related to versioning updates, the Build and Deploy workflow is currently broken. We should fix it by adding the necessary configuration steps and changing the versions where appropriate, etc.

[github-actions]

👋 Hello @M4dhav!
Thank you for opening this issue. Our team will review it soon. 🚀

• If you can, please provide more details like steps to reproduce, expected vs. actual behavior, and screenshots (if applicable). 📌

We appreciate your contribution! 💡

[uju09]

@M4dhav I want to work on this. I request you to assign it to me.

[M4dhav]

Hey @uju09 , I forgot to add, please modify the triggers so that the workflow is only triggered after pushes to the Master branch instead of PRs

[uju09]

@M4dhav I want some time as my mid-sems are going on. I will surely look into the issue. Thank you

[4555jan]

I would really like it if u assign this issue to me I will give results as fast as possible

[M4dhav]

Hey @4555jan , sorry, this issue is already assigned to @uju09

[uju09]

@M4dhav I've fixed the build workflow to correctly sign and release the app, but it now requires repository secrets to function. Could you please add the four keystore secrets? I have the final workflow code ready to go once they are in place.
KEYSTORE_BASE64 , KEYSTORE_PASSWORD, KEY_ALIAS, KEY_PASSWORD need to be added.

[M4dhav]

Hey @uju09 , please use the same secret variable names as used in the CI_STORE_DEPLOY_ANDROID workflow, as the secrets for those are already added. For local testing of the workflow, you can add your own secrets to your fork

[Stonebanks-js]

Hey @M4dhav , I was working on this issue and have solved it as per the requirements given by you.

Here is the solution -

What changes I made

• Updated CI to build a signed Android App Bundle (AAB) instead of APK.
• Added Java 21 setup and pinned Flutter to a compatible version.
• Added secure signing using repository secrets (key.properties + keystore.jks).
• Exported APPWRITE_PROJECT_ID env needed by the Android build.
• Uploaded AAB as a workflow artifact and to GitHub Release.
• Added optional Google Play deploy step (internal track) triggered via manual input.
• Removed the duplicate workflow at the repo root to avoid conflicts.

Steps I took

• Reviewed current Android Gradle config to match toolchain (Java 21, compileSdk 36).
• Reworked workflow to:
• Install Java and Flutter.
• Restore/create signing materials from secrets.
• Run flutter pub get.
• Build appbundle --release.
• Upload AAB as artifact and attach to a GitHub Release.
• Optionally deploy to Play Console using a service account when deploy=true.
• Ensured triggers and paths are aligned with your repo’s structure.

File edited and what it fixed

• Resonate/.github/workflows/build_and_deploy.yml
• Fixed broken build by aligning toolchain (Java 21, Flutter 3.24.3) and producing a release AAB.
• Fixed lack of signing by generating android/key.properties and decoding keystore from secrets.
• Fixed deployment gap by adding an optional Play Console upload step via r0adkll/upload-google-play.
• Fixed artifact mismatch by uploading AAB instead of APK to Releases and artifacts.

@M4dhav If you want I can make a exact pull request so that you can review the changes, if anything needs to be checked further kindly comment out.

Thanks and Hoping for a positive reply