Firebase setup for Flutter - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Firebase Initialization in Flutter

What is the correct way to initialize Firebase in a Flutter app before using any Firebase services?

A Call WidgetsFlutterBinding.ensureInitialized() then await Firebase.initializeApp() inside main() before runApp().

B No need to initialize Firebase explicitly; it initializes automatically when first used.

C Call Firebase.initializeApp() after runApp() in main().

D Directly call Firebase.initializeApp() inside the build() method of the main widget.

💡 Hint

Think about what must happen before the app UI builds and before Firebase services are used.

Firebase must be initialized before the app UI starts. Calling WidgetsFlutterBinding.ensureInitialized() ensures Flutter is ready, then await Firebase.initializeApp() sets up Firebase. This must happen before runApp().

❓ ui_behavior

intermediate

Firebase Authentication UI Behavior

After setting up Firebase Authentication in Flutter, what happens if you try to sign in a user with an incorrect password using FirebaseAuth.signInWithEmailAndPassword()?

A The app crashes with an unhandled exception.

B The method returns null silently without error.

C The method throws a FirebaseAuthException with code 'wrong-password'.

D The method signs in the user anyway ignoring the password.

💡 Hint

Think about how FirebaseAuth reports errors for failed sign-in attempts.

FirebaseAuth throws a FirebaseAuthException with a specific error code like wrong-password when sign-in fails due to incorrect password. This allows the app to handle errors gracefully.

❓ lifecycle

advanced

Firebase App Lifecycle and Hot Reload

When using Flutter with Firebase, what happens to the Firebase initialization state when you perform a hot reload during development?

A Firebase remains initialized; hot reload preserves the Firebase app instance.

B Firebase reinitializes automatically on every hot reload.

C Firebase initialization is lost and causes runtime errors after hot reload.

D Hot reload is disabled when Firebase is used.

💡 Hint

Consider how Flutter hot reload preserves state and variables.

Flutter hot reload preserves the app state including initialized Firebase instances. This means Firebase does not reinitialize on hot reload, allowing faster development without losing Firebase connection.

❓ navigation

advanced

Navigating After Firebase Authentication

In a Flutter app using Firebase Authentication, which approach correctly navigates to the home screen only after a successful sign-in?

A Call Navigator.pushReplacement before calling signInWithEmailAndPassword().

B Use Navigator.pushReplacement inside the sign-in success callback after await signInWithEmailAndPassword().

C Navigate to home screen in the build() method regardless of authentication state.

D Use Navigator.pop() to go to home screen after sign-in.

💡 Hint

Think about when you know the user is signed in successfully.

You should navigate only after the sign-in completes successfully. Calling Navigator.pushReplacement inside the success callback ensures the user sees the home screen only when authenticated.

📝 Syntax

expert

Correct Firebase Initialization Code Snippet

Which code snippet correctly initializes Firebase in Flutter with null safety and async main()?

A

void main() async {
  Firebase.initializeApp();
  runApp(MyApp());
}

B

void main() {
  await Firebase.initializeApp();
  runApp(MyApp());
}

C

Future<void> main() {
  WidgetsFlutterBinding.ensureInitialized();
  Firebase.initializeApp();
  runApp(MyApp());
}

D

void main() async {
  WidgetsFlutterBinding.ensureInitialized();
  await Firebase.initializeApp();
  runApp(const MyApp());
}

💡 Hint

Remember that main() must be async to await Firebase initialization and Flutter binding must be ensured.

The correct way is to make main() async, call WidgetsFlutterBinding.ensureInitialized() before awaiting Firebase.initializeApp(), then call runApp(). This ensures Flutter and Firebase are ready.