URLSession basics in iOS Swift - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a default URLSession instance.

iOS Swift

let session = URLSession.[1]

Drag options to blanks, or click blank then click option'

Adefault

Bshared

Cconfiguration

Dinit

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'default()' which does not exist

Trying to call 'init()' directly

The shared property gives you a shared singleton URLSession instance for simple tasks.

2fill in blank

medium

Complete the code to create a URL from a string.

iOS Swift

guard let url = URL(string: [1]) else { return }

Drag options to blanks, or click blank then click option'

A"https://apple.com"

BURL(string: "https://apple.com")

CurlString

Dhttps://apple.com

Attempts:

3 left

💡 Hint

Common Mistakes

Passing a URL object instead of a string

Forgetting quotes around the URL string

The URL(string:) initializer expects a string literal or variable containing the URL string.

3fill in blank

hard

Fix the error in the code to start a data task.

iOS Swift

let task = session.dataTask(with: url) [1]

Drag options to blanks, or click blank then click option'

A.begin()

B.start()

C.resume()

D.run()

Attempts:

3 left

💡 Hint

Common Mistakes

Using .start() or .begin() which are not valid methods

Forgetting to call any method to start the task

You must call resume() on the task to start it. Other methods do not exist.

4fill in blank

hard

Fill both blanks to handle the data and error in the completion handler.

iOS Swift

let task = session.dataTask(with: url) { data, response, [1] in
    if let error = [2] {
        print(error.localizedDescription)
    }
}

Drag options to blanks, or click blank then click option'

Aerror

Berr

Cfailure

Dexception

Attempts:

3 left

💡 Hint

Common Mistakes

Using different names for the parameter and the unwrapped variable

Using undefined variable names

The completion handler parameter for errors is usually named error. You check it with if let error = error.

5fill in blank

hard

Fill all three blanks to safely unwrap data and convert it to a string.

iOS Swift

let task = session.dataTask(with: url) { data, response, error in
    guard let [1] = data, error == nil else { return }
    let result = String(data: [2], encoding: [3])
    print(result ?? "No data")
}

Drag options to blanks, or click blank then click option'

Adata

Bresponse

CString.Encoding.utf8

DString.Encoding.ascii

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'response' instead of 'data'

Using ASCII encoding which may not work for all data

You unwrap data safely, then use it to create a string with UTF-8 encoding.

Practice

1. What is the main purpose of URLSession in Swift?

easy

A. To create user interface elements

B. To handle network requests and communicate with the internet

C. To manage local file storage

D. To perform mathematical calculations

Solution

1. Step 1: Understand URLSession role

   URLSession is designed to manage network tasks like downloading or uploading data.

2. Step 2: Compare with other options

   Creating UI, managing files, or math are unrelated to URLSession.

3. Final Answer:

   To handle network requests and communicate with the internet -> Option B

4. Quick Check:

   URLSession = network communication [OK]

Hint: Remember URLSession is for internet tasks only [OK]

Common Mistakes:

• Confusing URLSession with UI components
• Thinking URLSession manages local files
• Assuming URLSession does math operations

2. Which of the following is the correct way to create a data task with URLSession?

easy

A. let task = URLSession.dataTask(url) { data, error in }

B. let task = URLSession.shared.dataTask(url)

C. let task = URLSession.shared.downloadTask(url)

D. let task = URLSession.shared.dataTask(with: url) { data, response, error in }

Solution

1. Step 1: Check correct method signature

   The correct method is dataTask(with:completionHandler:) on URLSession.shared.

2. Step 2: Validate options

   let task = URLSession.shared.dataTask(with: url) { data, response, error in } matches the correct syntax with closure parameters data, response, error. Others have wrong method names or missing parameters.

3. Final Answer:

   let task = URLSession.shared.dataTask(with: url) { data, response, error in } -> Option D

4. Quick Check:

   Correct dataTask syntax = let task = URLSession.shared.dataTask(with: url) { data, response, error in } [OK]

Hint: Look for shared session and closure with three parameters [OK]

Common Mistakes:

• Using dataTask without shared session
• Missing response parameter in closure
• Using downloadTask instead of dataTask

3. What will the following code print if the network request succeeds and returns data?

let url = URL(string: "https://example.com")!
let task = URLSession.shared.dataTask(with: url) { data, response, error in
  if let data = data {
    print("Data received: \(data.count) bytes")
  } else {
    print("No data")
  }
}
task.resume()

medium

A. Data received: [number] bytes

B. Syntax error

C. No data

D. Data received: 0 bytes

Solution

1. Step 1: Analyze dataTask completion handler

   If the request succeeds, data contains the downloaded bytes, so data.count is a positive number.

2. Step 2: Check print statements

   The code prints "Data received: \(data.count) bytes" if data exists, otherwise "No data".

3. Final Answer:

   Data received: [number] bytes -> Option A

4. Quick Check:

   Successful dataTask prints data size [OK]

Hint: If data exists, print shows byte count, not zero [OK]

Common Mistakes:

• Assuming data is always nil
• Confusing data.count with zero
• Thinking code has syntax errors

4. Identify the error in this code snippet:

let url = URL(string: "https://example.com")!
let task = URLSession.shared.dataTask(with: url) { data, response, error in
  if let data = data {
    DispatchQueue.main.async {
      print("Data length: \(data.count)")
    }
  }
}
// Missing task.resume()

medium

A. Missing call to task.resume() to start the request

B. Incorrect URL string format

C. DispatchQueue.main.async should not be used here

D. Closure parameters are incorrect

Solution

1. Step 1: Check for starting the task

   URLSession tasks are created suspended. You must call task.resume() to start the network request.

2. Step 2: Validate other parts

   URL string is valid, closure parameters are correct, and updating UI on main thread is good practice.

3. Final Answer:

   Missing call to task.resume() to start the request -> Option A

4. Quick Check:

   Always call resume() to run URLSession tasks [OK]

Hint: Remember to call resume() after creating a data task [OK]

Common Mistakes:

• Forgetting to call task.resume()
• Misusing DispatchQueue for UI updates
• Incorrect closure parameters

5. You want to fetch JSON data from a URL and update a label with the result. Which approach correctly ensures the UI updates happen on the main thread?

let url = URL(string: "https://api.example.com/data")!
let task = URLSession.shared.dataTask(with: url) { data, response, error in
  guard let data = data else { return }
  let text = String(data: data, encoding: .utf8) ?? "No data"
  // Update label here
}
task.resume()

Options:

hard

A. Call label.text = text before task.resume()

B. Update label.text directly inside the closure without DispatchQueue

C. Use DispatchQueue.main.async { label.text = text } inside the closure

D. Use a background thread to update label.text

Solution

1. Step 1: Understand threading in URLSession

   The completion handler runs on a background thread, so UI updates must be dispatched to the main thread.

2. Step 2: Check each option

   Use DispatchQueue.main.async { label.text = text } inside the closure correctly uses DispatchQueue.main.async to update the label safely. Update label.text directly inside the closure without DispatchQueue risks UI bugs. Call label.text = text before task.resume() updates UI before data is fetched. Use a background thread to update label.text wrongly uses background thread for UI.

3. Final Answer:

   Use DispatchQueue.main.async { label.text = text } inside the closure -> Option C

4. Quick Check:

   UI updates on main thread = Use DispatchQueue.main.async { label.text = text } inside the closure [OK]

Hint: Always update UI on main thread with DispatchQueue.main.async [OK]

Common Mistakes:

• Updating UI on background thread
• Updating UI before data arrives
• Ignoring thread safety for UI changes