Cloud Firestore in iOS Swift - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ ui_behavior

intermediate

Firestore Data Fetching Behavior

You have this Swift code snippet to fetch a document from Firestore and update a label. What will be the label's text if the document does not exist?

iOS Swift

let db = Firestore.firestore()
db.collection("users").document("user123").getDocument { document, error in
  if let document = document, document.exists {
    label.text = document.get("name") as? String ?? "No Name"
  } else {
    label.text = "Document not found"
  }
}

A "Document not found"

B "No Name"

C App crashes with nil error

D "" (empty string)

💡 Hint

Check the condition that tests if the document exists.

If the document does not exist, the else block runs and sets the label text to "Document not found".

🧠 Conceptual

intermediate

Firestore Offline Persistence

What happens when Firestore offline persistence is enabled and the device loses internet connection?

A Firestore caches data locally and serves reads from cache until connection is restored

B Firestore stops all reads and writes until internet is back

C Firestore deletes all cached data immediately

D Firestore automatically switches to a backup server

💡 Hint

Think about how offline apps should behave to keep working.

Enabling offline persistence allows Firestore to cache data locally and serve reads from cache when offline, syncing changes when back online.

📝 Syntax

advanced

Correct Firestore Document Update Syntax

Which option correctly updates the "age" field to 30 in the Firestore document "users/user123"?

iOS Swift

let db = Firestore.firestore()
db.collection("users").document("user123").updateData(["age": 30]) { error in
  if let error = error {
    print("Error updating document: \(error)")
  } else {
    print("Document successfully updated")
  }
}

A db.collection("users").document("user123").update(["age": 30])

B db.collection("users").document("user123").setData(["age": 30])

C db.collection("users").document("user123").updateData(["age": 30]) { error in ... }

D db.collection("users").document("user123").updateData("age", 30)

💡 Hint

Look for the method that updates fields without overwriting the whole document.

updateData is the correct method to update specific fields. setData overwrites the whole document. update and updateData with wrong parameters cause errors.

❓ lifecycle

advanced

Firestore Listener Behavior on App Backgrounding

If you add a Firestore snapshot listener in your iOS app, what happens to the listener when the app goes to the background?

A Listener automatically stops and resumes when app returns to foreground

B Listener continues to receive updates until explicitly removed

C Listener causes app crash in background

D Listener pauses and never resumes

💡 Hint

Think about how Firestore listeners behave unless you remove them.

Firestore listeners remain active in background unless you remove them, which can affect battery and data usage.

🔧 Debug

expert

Diagnosing Firestore Permission Denied Error

You get a "Permission denied" error when trying to read a Firestore collection in your iOS app. Which is the most likely cause?

A The app is missing internet permission in Info.plist

B The Firestore database is offline

C The document ID is invalid

D Firestore security rules do not allow read access to the collection

💡 Hint

Check your Firestore security rules first when you see permission errors.

Permission denied errors usually mean Firestore security rules block access. Network or ID issues cause different errors.

Practice

1. What is the main purpose of Cloud Firestore in an iOS app?

easy

A. To compile Swift code into an app

B. To design the app's user interface

C. To handle user authentication only

D. To store and sync app data in the cloud with live updates

Solution

1. Step 1: Understand Cloud Firestore's role

   Cloud Firestore is a cloud database that stores app data and syncs it live across devices.

2. Step 2: Compare options with Firestore's function

   Only To store and sync app data in the cloud with live updates describes storing and syncing data live, which matches Firestore's purpose.

3. Final Answer:

   To store and sync app data in the cloud with live updates -> Option D

4. Quick Check:

   Firestore = cloud data storage and sync [OK]

Hint: Firestore is for cloud data storage and live sync [OK]

Common Mistakes:

• Confusing Firestore with UI design tools
• Thinking Firestore only handles authentication
• Believing Firestore compiles code

2. Which Swift code snippet correctly gets a reference to a Firestore collection named "users"?

easy

A. let usersRef = Firestore.firestore().collection("users")

B. let usersRef = Firestore.collection("users")

C. let usersRef = Firestore.getCollection("users")

D. let usersRef = Firestore.firestore().get("users")

Solution

1. Step 1: Recall Firestore syntax for collection reference

   The correct way is to call Firestore.firestore() then .collection("name") to get a collection reference.

2. Step 2: Check each option's method calls

   Only let usersRef = Firestore.firestore().collection("users") uses Firestore.firestore().collection("users"), which is correct syntax.

3. Final Answer:

   let usersRef = Firestore.firestore().collection("users") -> Option A

4. Quick Check:

   Firestore.firestore().collection("name") = correct [OK]

Hint: Use Firestore.firestore().collection("name") to get collection [OK]

Common Mistakes:

• Omitting .firestore() before .collection()
• Using non-existent methods like getCollection()
• Calling get("users") instead of collection("users")

3. Given this Swift code, what will be printed if the document exists with field "name" = "Alice"?

let docRef = Firestore.firestore().collection("users").document("user123")
docRef.getDocument { document, error in
  if let document = document, document.exists {
    let name = document.data()?["name"] as? String ?? "Unknown"
    print(name)
  } else {
    print("No document")
  }
}

medium

A. Unknown

B. No document

C. Alice

D. Error

Solution

1. Step 1: Understand the getDocument completion handler

   If the document exists, it extracts the "name" field and prints it; otherwise prints "No document".

2. Step 2: Given document exists with "name" = "Alice"

   The code will print the value "Alice" from the document field.

3. Final Answer:

   Alice -> Option C

4. Quick Check:

   Document exists with name = Alice, so print Alice [OK]

Hint: If document exists, print its field value [OK]

Common Mistakes:

• Assuming print shows "No document" even if document exists
• Confusing default "Unknown" with actual field value
• Ignoring optional cast and default fallback

4. What is wrong with this Swift Firestore code snippet?

let docRef = Firestore.firestore().collection("users").document("user123")
docRef.getDocument { document, error in
  if error != nil {
    print("Error fetching document")
  }
  if let document = document, document.exists {
    print(document.data())
  }
}

medium

A. It does not handle the case when document does not exist

B. It uses wrong method getDocument instead of get()

C. It should unwrap error with if let error = error

D. It tries to print document.data() without casting

Solution

1. Step 1: Analyze error and document handling

   The code prints error if error exists, then prints data if document exists, but does nothing if document does not exist and no error.

2. Step 2: Identify missing handling for non-existing document

   There is no else clause for when document does not exist, so no message is shown in that case.

3. Final Answer:

   It does not handle the case when document does not exist -> Option A

4. Quick Check:

   Missing else for document.exists = problem [OK]

Hint: Always handle document not existing case [OK]

Common Mistakes:

• Confusing getDocument with get() method
• Not unwrapping error properly but still works
• Printing data() without casting is allowed

5. You want to listen for live updates to a Firestore collection "messages" and update your UI in SwiftUI. Which code snippet correctly sets up a listener?

hard

A. Firestore.firestore().collection("messages").getDocuments { snapshot, error in
let messages = snapshot?.documents.map { $0.data() } ?? []
self.messages = messages
}

B. Firestore.firestore().collection("messages").addSnapshotListener { snapshot, error in
guard let snapshot = snapshot else { return }
let messages = snapshot.documents.map { $0.data() }
DispatchQueue.main.async {
self.messages = messages
}
}

C. Firestore.firestore().collection("messages").document("messages").addSnapshotListener { snapshot, error in
if let snapshot = snapshot {
self.messages = snapshot.data()
}
}

D. Firestore.firestore().collection("messages").listen { snapshot, error in
self.messages = snapshot?.documents ?? []
}

Solution

1. Step 1: Identify method for live updates

   addSnapshotListener listens for real-time updates; getDocuments fetches once.

2. Step 2: Check correct usage of addSnapshotListener and UI update

   Firestore.firestore().collection("messages").addSnapshotListener { snapshot, error in guard let snapshot = snapshot else { return } let messages = snapshot.documents.map { $0.data() } DispatchQueue.main.async { self.messages = messages } } uses addSnapshotListener on collection, maps documents to data, and updates UI on main thread.

3. Step 3: Verify other options

   Firestore.firestore().collection("messages").getDocuments { snapshot, error in let messages = snapshot?.documents.map { $0.data() } ?? [] self.messages = messages } fetches once, not live. Firestore.firestore().collection("messages").document("messages").addSnapshotListener { snapshot, error in if let snapshot = snapshot { self.messages = snapshot.data() } } listens on a document named "messages" (wrong). Firestore.firestore().collection("messages").listen { snapshot, error in self.messages = snapshot?.documents ?? [] } uses non-existent listen method.

4. Final Answer:

   Firestore.firestore().collection("messages").addSnapshotListener { snapshot, error in guard let snapshot = snapshot else { return } let messages = snapshot.documents.map { $0.data() } DispatchQueue.main.async { self.messages = messages } } -> Option B

5. Quick Check:

   Use addSnapshotListener for live updates [OK]

Hint: Use addSnapshotListener for live Firestore updates [OK]

Common Mistakes:

• Using getDocuments for live updates
• Listening on wrong document instead of collection
• Using non-existent listen method