-
Notifications
You must be signed in to change notification settings - Fork 209
feat(ci):fix build deploy workflow #559
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: dev
Are you sure you want to change the base?
Conversation
Signed-off-by: Ujwal Akotkar <24bcs012@iiitdwd.ac.in>
…y Store deployment Signed-off-by: Ujwal Akotkar <24bcs012@iiitdwd.ac.in>
🎉 Welcome @uju09!
We appreciate your contribution! 🚀 |
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the ✨ Finishing touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
@M4dhav I request you to review it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes are not related to the PR, please revert
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes are not related to the PR, please revert
run: | | ||
flutter build apk \ | ||
--release \ | ||
--split-per-abi \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is splitting the builds a good idea? This will form different apks for different architectures but most people do not know their architecture. What do you think we should do?
Splitting would mean smaller apks but arguably UX will be a little worse.
@M4dhav I will resolve it. |
Description
This PR fixes the broken Build and Deploy workflow that was caused by recent Play Store compatibility changes and versioning updates. The workflow now properly handles automatic deployment, signing configuration, and artifact management.
Key Changes:
workflow_dispatch
for manual triggering capabilitybuild/app/outputs/flutter-apk/
directoryandroid/app/build.gradle.kts
github.run_number
instead of static tagsFixes #539
Type of change
How Has This Been Tested?
Local Testing:
flutter test
- all tests passingWorkflow Testing:
Test Configuration:
Files Changed
.github/workflows/build_and_deploy.yml
- Complete workflow rewrite with proper configuration.github/workflows/store_deploy_android.yml
- Updated trigger configurationandroid/app/build.gradle.kts
- Fixed duplicate signing config issueBreaking Changes
None. This PR maintains backward compatibility while fixing broken functionality:
workflow_dispatch
is preservedDescription
This PR fixes the broken Build and Deploy workflows by updating trigger configuration and correcting Android build signing setup. The changes address workflow failures caused by Play Store compatibility requirements and ensure proper artifact management.
Fixes #(issue)
Changes Made
1.
.github/workflows/build_and_deploy.yml
What changed:
push + pull_request + workflow_dispatch
topush (master only) + workflow_dispatch
build/app/outputs/apk/release/
tobuild/app/outputs/flutter-apk/
flutter test
step before buildslatest_build
to dynamicv1.0.${{ github.run_number }}
Why:
2.
.github/workflows/store_deploy_android.yml
What changed:
push (main/master/deploy-actions) + pull_request + workflow_dispatch
topush (master only) + workflow_dispatch
Why:
3.
android/app/build.gradle.kts
What changed:
signingConfig = signingConfigs.getByName("debug")
linesigningConfigs
block outside ofbuildTypes
for proper Kotlin DSL structuresigningConfig = signingConfigs.getByName("release")
in release build typeWhy:
Type of Change
Testing
Local Verification:
Expected Behavior After Merge:
Files Changed
.github/workflows/build_and_deploy.yml
.github/workflows/store_deploy_android.yml
android/app/build.gradle.kts
Checklist
Additional Notes
Required for Deployment:
Ensure all GitHub Secrets are configured before merge:
ANDROID_KEYSTORE
ANDROID_KEY_PROPERTIES
ANDROID_RELEASE_SERVICE_ACCOUNT
GOOGLE_SERVICES_ANDROID
FIREBASE_OPTIONS
APPWRITE_BASE_DOMAIN
APPWRITE_PROJECT_ID
Post-Merge Validation:
After merging to master, monitor the Actions tab to ensure both workflows complete successfully.
Maintainer Checklist
bug
,ci
,workflows