Security, Release & Monitoring Interview Questions (Flutter)
3 Security, Release & Monitoring questions from the Flutter track. Read each short answer here, then open a question for the full explanation, examples, common mistakes, and sources.
- Senior
How do you protect sensitive data in a Flutter app (secure storage, certificate pinning, and obfuscation)?
Store tokens and secrets in the Keychain/Keystore through flutter_secure_storage and not in SharedPreferences, pin the server's certificate or its public key to prevent man-in-the-middle attacks, enable obfuscate with split-debug-info, and do not place real secrets inside the app because it can be reverse engineered.
Read the full explanation - Senior
How do you build a CI/CD pipeline for a Flutter app that covers tests, signing, flavors, and publishing to the stores?
The pipeline runs analysis and tests on every change, then builds the signed release file (AAB/IPA) with the required flavor using secrets stored in the CI system, and uploads it to an internal testing track in the store with automated version numbering.
Read the full explanation - Mid-level
How do you capture unhandled Flutter errors and send them to Crashlytics in production?
Flutter covers three error paths: framework errors through FlutterError.onError, async and platform-layer errors through PlatformDispatcher.onError, and errors of other isolates through Isolate.current.addErrorListener; you connect them all to a monitoring tool such as Crashlytics.
Read the full explanation