Auth state observer in Firebase - Step-by-Step Execution

Process Flow - Auth state observer

Start App

↓

Attach Auth State Observer

↓

User Signs In or Out

↓

Observer Detects Change

↓

Run Callback with User Info or Null

↓

Update UI or State Accordingly

↓

Wait for Next Auth Change

The app starts and attaches an observer to watch authentication changes. When a user signs in or out, the observer runs a callback with the current user info or null, allowing the app to update the UI.

Execution Sample

Firebase

firebase.auth().onAuthStateChanged(user => {
  if (user) {
    console.log('User signed in:', user.uid);
  } else {
    console.log('No user signed in');
  }
});

This code listens for authentication state changes and logs whether a user is signed in or not.

Process Table

Step	Event	User State	Callback Action	Output
1	App starts	No user signed in	Callback runs with null	Logs 'No user signed in'
2	User signs in	User object present	Callback runs with user	Logs 'User signed in: <uid>'
3	User signs out	User is null	Callback runs with null	Logs 'No user signed in'
4	No further auth changes	User state unchanged	No callback	Idle, waiting

💡 Execution waits indefinitely for auth state changes; no exit unless app closes.

Status Tracker

Variable	Start	After Step 2	After Step 3	Final
user	null	{uid: 'abc123'}	null	null
callback output	none	Logs user signed in	Logs no user signed in	waiting

Key Moments - 3 Insights

Why does the callback run immediately after attaching the observer even if no user signs in?

The observer triggers once on attachment to provide the current auth state, as shown in step 1 and 2 of the execution_table.

What does the 'user' variable contain when no one is signed in?

It is null, indicating no authenticated user, as shown in steps 1 and 3 in the execution_table.

Does the observer stop running after one auth change?

No, it stays active waiting for any future auth changes, as explained in the exit_note and step 4.

Visual Quiz - 3 Questions

Look at the execution_table, what is the 'user' value at Step 2?

A null

B undefined

C {uid: 'abc123'}

D empty string

💡 Hint

Check the 'User State' column at Step 2 in the execution_table.

At which step does the callback log 'No user signed in'?

A Step 2

B Step 3

C Step 1

D Step 4

💡 Hint

Look for the 'Callback Action' and 'Output' columns in the execution_table.

If the user never signs out, what happens at Step 4?

A No callback runs, waiting for changes

B Callback runs with null

C Callback runs with user object

D Observer detaches automatically

💡 Hint

Refer to the 'Exit Note' and Step 4 in the execution_table.

Concept Snapshot

Auth state observer listens for sign-in/out events.
Attach with onAuthStateChanged(callback).
Callback runs immediately with current user or null.
Updates app UI based on user presence.
Observer stays active until app closes.

Full Transcript

When your app starts, it attaches an observer to watch for authentication changes. This observer runs a callback right away with the current user state, which can be a user object if signed in or null if not. When the user signs in or out later, the observer detects this change and runs the callback again with the updated user info. This lets your app update the interface or state to match whether a user is signed in or not. The observer keeps running, waiting for any future sign-in or sign-out events until the app closes.

Practice

1. What is the main purpose of an auth state observer in Firebase?

easy

A. To store user data permanently in the database

B. To watch for user sign-in or sign-out events and respond accordingly

C. To send emails to users automatically

D. To create new user accounts without user input

Solution

1. Step 1: Understand the role of auth state observer

   An auth state observer listens for changes in user authentication status, such as sign-in or sign-out.

2. Step 2: Identify the correct purpose

   It helps the app respond instantly to these changes by updating the UI or user info.

3. Final Answer:

   To watch for user sign-in or sign-out events and respond accordingly -> Option B

4. Quick Check:

   Auth state observer = watch sign-in/out [OK]

Hint: Auth observer tracks sign-in/out changes instantly [OK]

Common Mistakes:

• Thinking it stores user data permanently
• Confusing it with email sending service
• Assuming it creates accounts automatically

2. Which of the following is the correct syntax to add an auth state observer in Firebase JavaScript SDK?

easy

A. firebase.auth().onAuthStateChanged(user => { /* code */ });

B. firebase.auth().addUserObserver(user => { /* code */ });

C. firebase.auth().watchUserState(user => { /* code */ });

D. firebase.auth().observeAuth(user => { /* code */ });

Solution

1. Step 1: Recall Firebase auth observer method

   The correct method to listen for auth state changes is onAuthStateChanged.

2. Step 2: Match the syntax

   firebase.auth().onAuthStateChanged(user => { /* code */ }); uses the exact method name and callback syntax as per Firebase docs.

3. Final Answer:

   firebase.auth().onAuthStateChanged(user => { /* code */ }); -> Option A

4. Quick Check:

   Correct method = onAuthStateChanged [OK]

Hint: Look for onAuthStateChanged method name [OK]

Common Mistakes:

• Using non-existent methods like addUserObserver
• Mixing method names with watchUserState
• Using observeAuth which is invalid

3. Given this code snippet, what will be logged if a user is signed in?

firebase.auth().onAuthStateChanged(user => {
  if (user) {
    console.log('User ID:', user.uid);
  } else {
    console.log('No user signed in');
  }
});

medium

A. Nothing will be logged

B. No user signed in

C. An error message about missing user

D. User ID: followed by the user's unique ID

Solution

1. Step 1: Understand the callback behavior

   The callback runs whenever auth state changes. If a user is signed in, the user object is not null.

2. Step 2: Check the if condition

   Since user exists, it logs 'User ID:' plus the user's unique ID (user.uid).

3. Final Answer:

   User ID: followed by the user's unique ID -> Option D

4. Quick Check:

   Signed-in user logs ID [OK]

Hint: If user exists, logs user.uid [OK]

Common Mistakes:

• Assuming it logs 'No user signed in' when user is present
• Expecting an error message incorrectly
• Thinking nothing logs without explicit call

4. Identify the error in this Firebase auth state observer code:

firebase.auth().onAuthStateChanged(user => {
  if (user) {
    console.log('Welcome ' + user.email);
  } else {
    console.log('User signed out');
  }
});
firebase.auth().onAuthStateChanged();

medium

A. Missing semicolon after console.log statements

B. Using user.email is invalid; should use user.id

C. Calling onAuthStateChanged without a callback causes an error

D. No error; code works fine

Solution

1. Step 1: Review the first observer usage

   The first call to onAuthStateChanged correctly passes a callback function.

2. Step 2: Check the second call

   The second call to onAuthStateChanged has no callback, which is required and causes an error.

3. Final Answer:

   Calling onAuthStateChanged without a callback causes an error -> Option C

4. Quick Check:

   Callback required for onAuthStateChanged [OK]

Hint: Always provide a callback to onAuthStateChanged [OK]

Common Mistakes:

• Thinking user.email is invalid (it is valid)
• Ignoring missing callback error
• Assuming missing semicolons cause runtime errors

5. You want your app to update the UI immediately when the user signs in or out, and also fetch user profile data only when signed in. Which approach using Firebase auth state observer is best?

hard

A. Use onAuthStateChanged to detect user, then fetch profile data inside the callback only if user exists

B. Fetch profile data once at app start, ignoring auth state changes

C. Use onAuthStateChanged but fetch profile data outside the callback unconditionally

D. Do not use onAuthStateChanged; instead poll user status every 5 seconds

Solution

1. Step 1: Understand the need for immediate UI update

   Using onAuthStateChanged lets the app react instantly to sign-in or sign-out events.

2. Step 2: Fetch profile data conditionally

   Fetching profile data inside the callback only when user exists avoids unnecessary calls and ensures data is current.

3. Final Answer:

   Use onAuthStateChanged to detect user, then fetch profile data inside the callback only if user exists -> Option A

4. Quick Check:

   Fetch profile inside auth callback if user present [OK]

Hint: Fetch profile only inside auth callback when user exists [OK]

Common Mistakes:

• Fetching profile data regardless of auth state
• Polling user status wastes resources
• Ignoring auth state changes for UI updates