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.