URLSession and Swift Concurrency: Does cancelling a Task abort the underlying dataTask?

Yes, cancelling a Swift Task that awaits URLSession.shared.data(for:) automatically cancels the underlying network request.

In modern Swift concurrency, the data(for:delegate:) methods in URLSession are designed to be cancellation-aware. When the Task awaiting these methods is cancelled, the cancellation signal propagates to the underlying URLSessionDataTask, triggering an immediate abort of the network activity to save system resources.

Swift Concurrency vs. Legacy Methods

The behavior depends entirely on which API you are using. Here is the breakdown:

• Async/Await (data(for:)): Cancellation is automatically forwarded. If you cancel the Task, the request is cancelled, and the method will throw a URLError.cancelled (code -999).
• Legacy Completion Handlers (dataTask(with:)): If you are manually wrapping the old dataTask in a CheckedContinuation, cancelling the Task will not stop the request. You must explicitly use withTaskCancellationHandler to manually call task.cancel().
• Combine (.timeout): The timeout operator emits an error to the subscriber but does not automatically cancel the upstream dataTaskPublisher unless the subscription itself is cancelled via AnyCancellable.

How to Ensure Immediate Cancellation

To ensure your network requests are aborted properly when a user navigates away or cancels an operation:

let task = Task {
    do {
        let (data, response) = try await URLSession.shared.data(for: request)
        // Process data
    } catch is CancellationError {
        // Handle cancellation specifically
        print("Request was aborted")
    } catch {
        // Handle other errors
    }
}

// Later, to abort the request:
task.cancel()

Summary Table

Method	Auto-Abort?	Error Type
data(for:)	Yes	URLError.cancelled
dataTask(with:)	No	Manual task.cancel() required
Combine .timeout	No	Upstream remains active

Diagnostic Question: Are you currently using the native data(for:) async method, or are you wrapping a legacy completion-handler task in a continuation? This determines if manual cleanup is required.