Bird
Raised Fist0
iOS Swiftmobile~5 mins

URLSession basics in iOS Swift - Cheat Sheet & Quick Revision

Choose your learning style10 modes available
Recall & Review
beginner
What is URLSession used for in iOS development?
URLSession is used to make network requests, like downloading data from the internet or sending data to a server.
Click to reveal answer
beginner
What method of URLSession is commonly used to start a simple data task?
The dataTask(with:completionHandler:) method is used to start a task that fetches data from a URL.
Click to reveal answer
beginner
Why do we call resume() on a URLSessionDataTask?
Calling resume() starts the network request. Without it, the task stays suspended and does nothing.
Click to reveal answer
intermediate
What parameters does the completion handler of a URLSession data task provide?
It provides Data? (the response data), URLResponse? (info about the response), and Error? (any error that happened).
Click to reveal answer
intermediate
How can you handle errors when using URLSession?
Check if the Error? parameter in the completion handler is not nil, and handle it by showing a message or retrying.
Click to reveal answer
Which method starts a URLSession data task?
Alaunch()
Bstart()
Cresume()
Dbegin()
What type of object does URLSession's dataTask(with:) method return?
AURLSessionDataTask
BURLRequest
CURLResponse
DData
Which parameter in the completion handler contains the downloaded data?
AURLResponse
BData
CError
DURLRequest
What happens if you forget to call resume() on a URLSessionDataTask?
AThe task completes instantly
BThe task runs automatically
CThe app crashes
DThe task never starts
Which class is responsible for managing network requests in iOS?
AURLSession
BUIViewController
CUIApplication
DURLRequest
Explain how to create and start a simple URLSession data task to fetch data from a URL.
Think about the steps from making the request to getting the response.
You got /4 concepts.
    Describe the role of the completion handler in a URLSession data task.
    What do you do after the network call finishes?
    You got /4 concepts.

      Practice

      (1/5)
      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
      Recommended

      Ready to prove it?

      Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

      10 questions~5 mineasy hard