Refreshing and Maintaining Your App Using Background Tasks

At a glance

Project structure

Source bundle/
├── ColorFeed/
│   ├── Operations.swift
│   ├── AppDelegate.swift
│   ├── ColorView.swift
│   ├── FeedTableViewController.swift
│   ├── Server.swift
│   ├── Mocks.swift
│   ├── PersistentContainer.swift
│   ├── FeedEntryTableViewCell.swift
│   └── Base.lproj/
│       ├── LaunchScreen.storyboard
│       └── Main.storyboard
└── ColorFeed.xcodeproj/
    ├── .xcodesamplecode.plist
    └── project.pbxproj

Structure observations

• Architecturally prominent files are ranked from entry points and role-named declarations; resource-only paths are omitted.
• Primary languages: Swift.
• The verified tree contains 7 project/configuration file(s) and 21 source declaration(s).

Overall architecture

flowchart LR
    N1["AppDelegate"]
    N2["FeedTableViewController"]
    N3["ColorTransformer"]
    N4["BackgroundTasks APIs"]
    N1 --> N2
    N2 --> N3
    N3 --> N4

Reference code

ColorFeed/AppDelegate.swift:11 — architecture anchor

@UIApplicationMain
class AppDelegate: UIResponder, UIApplicationDelegate {
    // ...
    var window: UIWindow?
    // ...
}

Interpretation

The arrows summarize the source-visible entry, role-named types or folders, and framework direction; when nodes come from structural folders, the sequence is a high-level interpretation rather than proof that every adjacent node calls the next. Ownership is claimed only where the next section cites a stored property or assignment. The diagram is intentionally limited to the dominant path into Background Tasks.

Ownership and state

classDiagram
    FetchMostRecentEntryOperation o-- NSManagedObjectContext : context
    FetchMostRecentEntryOperation o-- FeedEntry : result
    DownloadEntriesFromServerOperation o-- NSManagedObjectContext : context
    DownloadEntriesFromServerOperation o-- Server : server

Ownership evidence

ColorFeed/Operations.swift:48 — stored dependency or nearest verified ownership anchor

class FetchMostRecentEntryOperation: Operation {
    private let context: NSManagedObjectContext
    // ...
}

Composition arrows indicate a source-visible construction expression or locally owned value state; aggregation means the owner stores or receives a dependency without proving exclusive lifetime ownership.

Concurrency, scheduling, and thread safety

Evidence limit: actor isolation, async/await, or Task creation does not by itself prove background-thread execution; Sendable conformance alone does not prove thread-safe mutation.

@MainActor/MainActor.run, DispatchQueue.main, and RunLoop.main are reported as distinct isolation, queue, and event-loop mechanisms. A plain Task is kept separate from Task.detached; neither is labeled as a background thread.

Reference code

ColorFeed/ColorView.swift:44 — representative execution boundary

            DispatchQueue.main.async() {
                guard !operation.isCancelled else { return }

                self.setImage(image: image, animated: true)
            }

State propagation, frameworks, and dependencies

Evidence limit: an import proves a source-level compilation dependency at the cited line; it does not prove runtime use, architectural adoption, or whether a Swift package is a direct application dependency.

receive(on:) describes downstream delivery scheduling, while subscribe(on:) describes upstream subscription/request/cancel scheduling. An import Combine alone establishes neither behavior nor a Store, reducer, Redux, or other application architecture.

Class and protocol design

ColorFeed/Server.swift:10 — representative type boundary

protocol Server {
    // Fetch any entries on the server that are more recent than the start date.
    @discardableResult
    func fetchEntries(since startDate: Date, completion: @escaping (Result<[ServerEntry], Error>) -> Void) -> DownloadTask
}

The source explicitly defines local protocol relationships: MockServer → Server, MockDownloadTask → DownloadTask.

Access control

Reference code

ColorFeed/AppDelegate.swift:16 — representative boundary

@UIApplicationMain
class AppDelegate: UIResponder, UIApplicationDelegate {
    // ...
    private let server: Server = MockServer()
    // ...
}

Swift declarations without a modifier are internal; explicit private, fileprivate, private(set), public, or open entries above are interpreted by language semantics. Objective-C/C samples instead rely on header and implementation boundaries, which are not equivalent to Swift lexical privacy.

Logic ownership and placement

Design patterns

Main application flow

One app-refresh launch reschedules the next request, constructs an ordered operation chain, wires cancellation and completion callbacks, and returns success to the system task.

sequenceDiagram
    participant Scheduler as BGTaskScheduler
    participant App as AppDelegate
    participant Factory as Operations
    participant Queue as OperationQueue
    participant Last as Last operation
    participant Task as BGAppRefreshTask
    Scheduler-->>App: Registered launch handler
    App->>Scheduler: scheduleAppRefresh()
    App->>Factory: getOperationsToFetchLatestEntries(...)
    Factory-->>App: Ordered operations
    App->>Task: Set expirationHandler
    App->>Last: Set completionBlock
    App->>Queue: addOperations(waitUntilFinished: false)
    Queue-->>Last: Complete or cancel chain
    Last-->>Task: setTaskCompleted(success)

Reference code

ColorFeed/AppDelegate.swift:79 — handleAppRefresh

    func handleAppRefresh(task: BGAppRefreshTask) {
        scheduleAppRefresh()

        let queue = OperationQueue()
        queue.maxConcurrentOperationCount = 1

        let context = PersistentContainer.shared.newBackgroundContext()
        let operations = Operations.getOperationsToFetchLatestEntries(using: context, server: server)
        let lastOperation = operations.last!

        task.expirationHandler = {
            // After all operations are cancelled, the completion block below is called to set the task to complete.
            queue.cancelAllOperations()
        }

        lastOperation.completionBlock = {
            task.setTaskCompleted(success: !lastOperation.isCancelled)
        }

        queue.addOperations(operations, waitUntilFinished: false)
    }

Naming conventions

• Types: Controller: FeedTableViewController; Delegate: AppDelegate; Operation: AddEntriesToStoreOperation, DeleteFeedEntriesOperation, DownloadEntriesFromServerOperation, FetchMostRecentEntryOperation; Transformer: ColorTransformer; View: ColorView.
• Protocols: Server, DownloadTask.
• Methods: getOperationsToFetchLatestEntries, main, cancel, finish, start, application, applicationDidEnterBackground, scheduleAppRefresh.
• Files: ColorFeed/Operations.swift, ColorFeed/AppDelegate.swift, ColorFeed/ColorView.swift, ColorFeed/FeedTableViewController.swift, ColorFeed/Server.swift, ColorFeed/PersistentContainer.swift.

Architecture takeaways

• AppDelegate is the main source-visible entry or composition anchor for this sample.
• Framework work reaches CoreData, UIKit, BackgroundTasks through a deliberately small high-level chain; the detailed API graph remains inside the cited implementation files.
• Stored-property evidence identifies lifecycle collaboration; it does not by itself prove exclusive object ownership.
• Access-control conclusions separate verified language visibility from the likely design rationale.
• Local protocol relationships provide an explicit substitution boundary.

Source map

• Official Apple documentation