Skip to content

Latest commit

 

History

History
55 lines (51 loc) · 2.13 KB

File metadata and controls

55 lines (51 loc) · 2.13 KB
  1. Assets Created App Icon: Generated a majestic crown icon and saved it to assets/icons/app_icon.png . Splash Screen: Generated a cinematic battlefield image and saved it to assets/splash/splash.png . Native Assets: Successfully ran flutter_launcher_icons and flutter_native_splash to apply these to the Android and iOS projects.
  2. Flavor Environment System I have implemented a robust environment system using .env files and Dart entry points:

Environment Files: Created three environment files: .env.dev : For development (API_URL, APP_NAME, etc.) .env.stg : For staging/testing. .env.prod : For production. Dart Entry Points: Created separate entry points for each flavor: lib/main_dev.dart lib/main_stg.dart lib/main_prod.dart Common Logic: All flavors share lib/main_common.dart , which handles initialization of environment variables and global services. Flavor Config: Created lib/flavor_config.dart to easily access environment variables (e.g., FlavorConfig.apiUrl). 3. Build Configuration The pubspec.yaml has been updated with:

flutter_flavorizr: Configured for dev , stg , and prod flavors with unique Application IDs. flutter_dotenv: To load the variables. flutter_launcher_icons & flutter_native_splash: For automated asset management. How to Run: You can now run the app for a specific environment using the -t (target) flag:

Development: flutter run -t lib/main_dev.dart Staging: flutter run -t lib/main_stg.dart Production: flutter run -t lib/main_prod.dart Note on Icon Badges: The system is ready to support different icons per flavor. To add a "badge" to the dev icon, you can simply replace assets/icons/app_icon_dev.png and update the flavorizr config if you wish to automate it further. Currently, all flavors use the base majestic icon.

4. Resolving Xcode Flavor Error

If you encountered Error: The Xcode project does not define custom schemes. You cannot use the --flavor option, it has been resolved by running flutter_flavorizr.

  • iOS Schemes Created: dev, stg, prod.
  • Android Flavors Configured: dev, stg, prod.
  • VS Code Launch Config: Updated to support running with flavor via the Debug sidebar.