Image loading from URL in iOS Swift - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ ui_behavior

intermediate

What will this SwiftUI code display?

Consider this SwiftUI view that loads an image from a URL asynchronously. What will the user see when the view appears?

iOS Swift

import SwiftUI

struct ContentView: View {
  let url = URL(string: "https://example.com/image.png")!
  var body: some View {
    AsyncImage(url: url) { image in
      image.resizable().scaledToFit()
    } placeholder: {
      ProgressView()
    }
  }
}

A A loading spinner appears first, then the image loads and fits the view.

B The image appears immediately without any loading indicator.

C The view shows a blank space with no image or indicator.

D The app crashes because AsyncImage requires a different initializer.

💡 Hint

Think about what AsyncImage does while waiting for the image to load.

AsyncImage shows the placeholder view (ProgressView) while loading the image from the URL. Once loaded, it displays the image resized to fit the view.

📝 Syntax

intermediate

Which code snippet correctly loads an image from a URL in UIKit?

You want to load an image from a URL asynchronously and display it in a UIImageView. Which code snippet is correct?

A

let url = URL(string: "https://example.com/image.png")!
let data = try? Data(contentsOf: url)
imageView.image = UIImage(data: data!)

B

let url = URL(string: "https://example.com/image.png")!
URLSession.shared.dataTask(with: url) { data, _, _ in
  if let data = data {
    DispatchQueue.main.async {
      imageView.image = UIImage(data: data)
    }
  }
}.resume()

C

let url = URL(string: "https://example.com/image.png")!
imageView.image = UIImage(contentsOfFile: url.path)

D

let url = URL(string: "https://example.com/image.png")!
imageView.image = UIImage(named: url.absoluteString)

💡 Hint

Remember that loading data from the network should be asynchronous and UI updates on the main thread.

Option B uses URLSession to fetch data asynchronously and updates the UIImageView on the main thread. Option B blocks the main thread and can crash. Options C and D misuse UIImage initializers.

❓ lifecycle

advanced

What happens if you load an image from a URL in viewDidLoad without caching?

In a UIViewController, you load an image from a URL in viewDidLoad every time the view appears. What is a likely consequence?

A The app crashes because images cannot be loaded in viewDidLoad.

B The image never loads because viewDidLoad is too early in the lifecycle.

C The image loads once and is cached automatically by the system, so no extra network calls happen.

D The image reloads every time the view appears, causing unnecessary network usage and slower UI.

💡 Hint

Think about how network requests behave if you do not store or cache the image data.

Without caching, loading the image in viewDidLoad causes a network request each time the view loads, which wastes data and slows the app.

🔧 Debug

advanced

Why does this SwiftUI AsyncImage code never show the image?

This SwiftUI code uses AsyncImage but the image never appears, only the placeholder spinner. What is the problem?

iOS Swift

AsyncImage(url: URL(string: "https://example.com/image.png")) { image in
  image.resizable()
} placeholder: {
  ProgressView()
}

A The image is not scaled or sized, so it has zero size and is invisible.

B The URL string is invalid and causes AsyncImage to fail silently.

C AsyncImage requires a .frame modifier to work properly.

D The placeholder view blocks the image from appearing.

💡 Hint

Think about how SwiftUI views need explicit size or scaling to be visible.

Without a size or scaling modifier like scaledToFit or a frame, the image has zero size and does not appear, even though it loads.

🧠 Conceptual

expert

What is the best practice for loading images from URLs in a production iOS app?

Which approach is best for loading images from URLs in a production iOS app to ensure good performance and user experience?

A Load images synchronously with Data(contentsOf:) to simplify code.

B Always use URLSession dataTask directly and reload images every time the view appears.

C Use a third-party library like SDWebImage or Kingfisher that handles async loading, caching, and placeholder images.

D Use UIImage(named:) with the URL string to load images efficiently.

💡 Hint

Think about caching, smooth loading, and reusability in real apps.

Third-party libraries provide optimized async loading, caching, and placeholder support, improving performance and user experience.

Practice

1. What is the main purpose of using URLSession when loading an image from a URL in Swift?

easy

A. To download data asynchronously from the internet

B. To display the image directly on the screen

C. To create a new UIImageView

D. To convert image data into a string

Solution

1. Step 1: Understand URLSession's role

   URLSession is used to perform network tasks like downloading data asynchronously, so the app doesn't freeze.

2. Step 2: Identify what happens when loading images

   When loading an image from a URL, URLSession downloads the image data in the background.

3. Final Answer:

   To download data asynchronously from the internet -> Option A

4. Quick Check:

   URLSession downloads data asynchronously [OK]

Hint: URLSession downloads data without blocking UI [OK]

Common Mistakes:

• Thinking URLSession displays images directly
• Confusing URLSession with UI components
• Assuming URLSession converts data to images

2. Which of the following Swift code snippets correctly creates a URL from a string to load an image?

easy

A. let url = URL.create("https://example.com/image.png")

B. let url = URL("https://example.com/image.png")

C. let url = URL(string: "https://example.com/image.png")

D. let url = URL.load("https://example.com/image.png")

Solution

1. Step 1: Recall URL initialization syntax

   The correct way to create a URL from a string is using the initializer URL(string:).

2. Step 2: Check each option

   Only let url = URL(string: "https://example.com/image.png") uses the correct initializer syntax. Others are invalid or do not exist.

3. Final Answer:

   let url = URL(string: "https://example.com/image.png") -> Option C

4. Quick Check:

   URL(string:) creates URL from string [OK]

Hint: Use URL(string:) to create URLs from strings [OK]

Common Mistakes:

• Using URL() without parameter label
• Using non-existent URL methods
• Forgetting to unwrap optional URL

3. Given the code below, what will be printed if the image data is successfully downloaded and converted?

let url = URL(string: "https://example.com/image.png")!
URLSession.shared.dataTask(with: url) { data, response, error in
  if let data = data, let image = UIImage(data: data) {
    print("Image loaded successfully")
  } else {
    print("Failed to load image")
  }
}.resume()

medium

A. Image loaded successfully

B. Failed to load image

C. Syntax error

D. No output

Solution

1. Step 1: Analyze the dataTask closure

   The closure checks if data exists and can be converted to UIImage. If yes, it prints success.

2. Step 2: Consider successful download scenario

   If the image data downloads correctly, the condition is true and prints "Image loaded successfully".

3. Final Answer:

   Image loaded successfully -> Option A

4. Quick Check:

   Successful data and UIImage means success message [OK]

Hint: Check if data and UIImage init succeed for success [OK]

Common Mistakes:

• Assuming print runs on main thread
• Confusing error with data presence
• Ignoring optional unwrapping

4. Identify the error in the following Swift code for loading an image from a URL:

let url = URL(string: "https://example.com/image.png")
URLSession.shared.dataTask(with: url!) { data, response, error in
  let image = UIImage(data: data!)
  imageView.image = image
}.resume()

medium

A. URL is not unwrapped safely

B. UIImage cannot be created from data

C. Missing call to resume()

D. Updating UI on background thread

Solution

1. Step 1: Check thread usage for UI update

   UI updates must happen on the main thread, but here imageView.image is set inside the background thread closure.

2. Step 2: Confirm other parts

   URL is force unwrapped (not safe but not the main error here), resume() is called, and UIImage creation is valid if data exists.

3. Final Answer:

   Updating UI on background thread -> Option D

4. Quick Check:

   UI updates must be on main thread [OK]

Hint: Always update UI on main thread after data task [OK]

Common Mistakes:

• Forgetting DispatchQueue.main.async for UI
• Force unwrapping optionals unsafely
• Not calling resume() on data task

5. You want to load an image from a URL and display it in a UIImageView safely, handling errors and updating UI correctly. Which code snippet correctly achieves this?

let url = URL(string: "https://example.com/image.png")
URLSession.shared.dataTask(with: url!) { data, response, error in
  if let data = data, let image = UIImage(data: data) {
    DispatchQueue.main.async {
      imageView.image = image
    }
  } else {
    print("Failed to load image")
  }
}.resume()

hard

A. This code misses calling resume() on data task

B. This code correctly loads image and updates UI on main thread

C. This code updates UI on background thread

D. This code does not handle optional URL safely

Solution

1. Step 1: Check for safe image loading and UI update

   The code unwraps data and image safely, then updates the UIImageView inside DispatchQueue.main.async, which is correct.

2. Step 2: Verify error handling and task start

   It prints an error message if loading fails and calls resume() to start the task.

3. Final Answer:

   This code correctly loads image and updates UI on main thread -> Option B

4. Quick Check:

   Safe unwrapping + main thread UI update = correct [OK]

Hint: Use DispatchQueue.main.async for UI updates after loading [OK]

Common Mistakes:

• Not calling resume() to start task
• Updating UI outside main thread
• Ignoring optional unwrapping safety