CI/CD for Flutter - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Flutter build command output

What is the output of the following Flutter build command when run successfully for an Android app?

flutter build apk --release

Flutter

flutter build apk --release

A Error: No connected devices found.

B Built build/app/outputs/flutter-apk/app-release.apk (12.3MB).

C Warning: Deprecated flag used.

D Build failed due to missing dependencies.

💡 Hint

Think about what a successful build message looks like.

When Flutter builds an APK successfully, it outputs the path and size of the generated APK file.

🔀 Workflow

intermediate

Correct order of CI steps for Flutter app

Arrange the following steps in the correct order for a typical CI pipeline for a Flutter app:

A 1,2,3,4

B 2,1,3,4

C 1,3,2,4

D 3,1,2,4

💡 Hint

Think about quality checks before building and deploying.

First analyze code, then run tests, then build, then deploy.

❓ Troubleshoot

advanced

Diagnosing Flutter build failure in CI

A CI pipeline running 'flutter build ios' fails with the error:

error: CocoaPods not installed or not configured correctly

Which option correctly fixes this issue in the CI environment?

A Run 'flutter clean' before the build step

B Remove the Podfile from the iOS project

C Increase the CI machine's memory

D Add a step to install CocoaPods using 'sudo gem install cocoapods' before building

💡 Hint

CocoaPods is a dependency manager for iOS projects.

Installing CocoaPods ensures dependencies for iOS builds are managed correctly.

✅ Best Practice

advanced

Best practice for caching in Flutter CI pipelines

Which caching strategy is best to speed up Flutter CI builds without causing stale dependencies?

A Cache the entire Flutter SDK and the .pub-cache directory

B Cache only the build output directory

C Do not use caching to avoid any stale files

D Cache only the source code directory

💡 Hint

Think about what takes time to download and install repeatedly.

Caching Flutter SDK and pub packages avoids repeated downloads and speeds up builds.

🧠 Conceptual

expert

Understanding Flutter CI/CD pipeline triggers

In a Flutter CI/CD pipeline, which trigger setup ensures that the pipeline runs only when code affecting the app's UI or logic changes?

A Trigger pipeline only on changes to 'docs/' directory

B Trigger pipeline on any commit to the repository

C Trigger pipeline on changes to 'lib/' and 'test/' directories only

D Trigger pipeline on changes to 'android/' and 'ios/' directories only

💡 Hint

UI and logic code is usually inside 'lib/' and tests in 'test/'.

Limiting triggers to 'lib/' and 'test/' avoids unnecessary builds for unrelated changes.

Practice

1. What is the main purpose of using CI/CD in Flutter app development?

easy

A. To automate building, testing, and deploying the app

B. To write Flutter code faster manually

C. To design app UI without coding

D. To run the app only on physical devices

Solution

1. Step 1: Understand CI/CD basics

   CI/CD stands for Continuous Integration and Continuous Delivery, which automates building and testing.

2. Step 2: Apply to Flutter context

   In Flutter, CI/CD runs commands like flutter pub get, flutter test, and flutter build automatically.

3. Final Answer:

   To automate building, testing, and deploying the app -> Option A

4. Quick Check:

   CI/CD automates app build and test = A [OK]

Hint: CI/CD means automate build and test steps [OK]

Common Mistakes:

• Thinking CI/CD is manual coding
• Confusing UI design with CI/CD
• Believing CI/CD only runs on devices

2. Which of the following is the correct command to run Flutter tests in a CI workflow?

easy

A. flutter test

B. flutter pub get

C. flutter build apk

D. flutter run

Solution

1. Step 1: Identify test command in Flutter

   The command to run tests in Flutter is flutter test.

2. Step 2: Differentiate from other commands

   flutter build apk builds the app, flutter pub get fetches packages, and flutter run runs the app on a device.

3. Final Answer:

   flutter test -> Option A

4. Quick Check:

   Run tests = flutter test = A [OK]

Hint: Tests run with 'flutter test' command [OK]

Common Mistakes:

• Using 'flutter build apk' to run tests
• Confusing 'flutter pub get' with testing
• Trying to run tests with 'flutter run'

3. Given this GitHub Actions snippet for Flutter CI:

steps:
  - uses: actions/checkout@v3
  - name: Install Flutter
    uses: subosito/flutter-action@v2
  - name: Get dependencies
    run: flutter pub get
  - name: Run tests
    run: flutter test
  - name: Build APK
    run: flutter build apk --release

What will happen if tests fail?

medium

A. The workflow retries tests automatically

B. APK is built regardless of test results

C. The workflow stops and APK is not built

D. Tests are skipped and APK is built

Solution

1. Step 1: Understand GitHub Actions default behavior

   If a command like flutter test fails, the workflow stops by default.

2. Step 2: Apply to given steps

   Since tests run before build, failure stops the workflow and APK build does not run.

3. Final Answer:

   The workflow stops and APK is not built -> Option C

4. Quick Check:

   Test failure stops workflow = D [OK]

Hint: Failed test stops workflow before build [OK]

Common Mistakes:

• Assuming APK builds even if tests fail
• Thinking tests are skipped automatically
• Believing workflow retries tests

4. You wrote this GitHub Actions step to build your Flutter app:

- name: Build APK
  run: flutter build apk --release
  shell: bash

But the build fails with "flutter: command not found". What is the likely cause?

medium

A. The shell should be powershell, not bash

B. The build command syntax is incorrect

C. The APK build requires emulator running

D. Flutter SDK is not installed or not added to PATH

Solution

1. Step 1: Analyze error message

   "flutter: command not found" means the system cannot find the Flutter tool.

2. Step 2: Identify missing setup

   This usually happens if Flutter SDK is not installed or its path is not set in the environment before running the build.

3. Final Answer:

   Flutter SDK is not installed or not added to PATH -> Option D

4. Quick Check:

   Command not found = missing Flutter setup = C [OK]

Hint: Ensure Flutter SDK is installed and in PATH before build [OK]

Common Mistakes:

• Blaming command syntax for 'command not found'
• Thinking shell type causes missing command
• Assuming emulator is needed for build

5. You want to speed up your Flutter CI workflow by caching dependencies. Which step should you add before flutter pub get to cache packages in GitHub Actions?

hard

A. Run flutter clean before flutter pub get

B. Use actions/cache@v3 with path ~/.pub-cache and key based on pubspec.yaml

C. Add flutter build apk before flutter pub get

D. Use actions/upload-artifact@v3 to upload pubspec.yaml

Solution

1. Step 1: Understand caching in GitHub Actions

   actions/cache@v3 caches files between workflow runs to speed up repeated steps.

2. Step 2: Apply caching to Flutter dependencies

   Flutter packages are stored in ~/.pub-cache; caching this folder keyed by pubspec.yaml hash speeds up flutter pub get.

3. Final Answer:

   Use actions/cache@v3 with path ~/.pub-cache and key based on pubspec.yaml -> Option B

4. Quick Check:

   Cache ~/.pub-cache with actions/cache = B [OK]

Hint: Cache ~/.pub-cache keyed by pubspec.yaml for faster builds [OK]

Common Mistakes:

• Running flutter clean which clears cache
• Building APK before fetching dependencies
• Uploading pubspec.yaml as artifact instead of caching