π§βπ» Flutter flavors for multiple installed app instances #57
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request introduces support for multiple build flavors (
developmentandproduction) in the Flutter app. The changes include updates to the build configuration, Gradle setup, and main application entry point to handle the new flavors. The most important changes are summarized below.Build workflow updates:
.github/workflows/build.ymlto include the--flavoroption when building APKs and app bundles, and adjusted file paths to reflect the newproductionflavor. [1] [2] [3]Gradle configuration changes:
flavorDimensionsand defineddevelopmentandproductionproduct flavors inandroid/app/build.gradle. Each flavor has a uniqueapplicationIdSuffixand app name.Application-level updates:
AndroidManifest.xmlto use a dynamic app name (@string/app_name) based on the selected flavor.lib/main.dartto inject the current flavor (developmentorproduction) into the app using theProviderpackage.Flutter configuration:
default-flavorconfiguration (development) inpubspec.yamlto set the default flavor for the app.