Sharing Wi-Fi network credentials

At a glance

Project structure

Source bundle/
├── WiFiNetworkSharing/
│   ├── ASKSampleWiFiAccessory/
│   │   ├── ASKSampleWiFiAccessoryApp.swift
│   │   ├── SampleAccessoryView.swift
│   │   └── DiceAccessory.swift
│   ├── WiFiNetworkSharingSample/
│   │   ├── WiFiNetworkSharingSampleApp.swift
│   │   ├── ContentView.swift
│   │   └── DiceSessionManager.swift
│   ├── TransportExtension/
│   │   ├── TransportExtension.swift
│   │   └── WiFiNetworkSharingProvider.swift
│   └── Shared/
│       ├── DiceColor.swift
│       ├── DiceConstants.swift
│       └── DiceValue.swift
└── Configuration/
    └── SampleCode.xcconfig

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 10 project/configuration file(s) and 12 source declaration(s).

Overall architecture

flowchart LR
    N1["ASKSampleWiFiAccessoryApp"]
    N2["SampleAccessoryView"]
    N3["DiceSessionManager"]
    N4["WiFiNetworkSharingProvider"]
    N5["WiFiInfrastructure APIs"]
    N1 --> N2
    N2 --> N3
    N3 --> N4
    N4 --> N5

Reference code

WiFiNetworkSharing/ASKSampleWiFiAccessory/ASKSampleWiFiAccessoryApp.swift:10 — architecture anchor

@main
struct ASKSampleWiFiAccessoryApp: App {
    var body: some Scene {
        WindowGroup {
            SampleAccessoryView()
        }
    }
}

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 Wi-Fi Infrastructure.

Ownership and state

classDiagram
    TransportExtension *-- Logger : logger
    EventHandler *-- ASAccessorySession : askSession
    EventHandler o-- WiFiNetworkSharingProvider : sharingProvider
    EventHandler o-- AccessoryTransportSession : transportSession

Ownership evidence

WiFiNetworkSharing/TransportExtension/TransportExtension.swift:15 — stored dependency or nearest verified ownership anchor

private let logger = Logger(subsystem: subsystem, category: "Extension")

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

WiFiNetworkSharing/TransportExtension/TransportExtension.swift:66 — representative execution boundary

    class EventHandler: AccessoryTransportSession.EventHandler {
        // ...
            askSession.activate(on: DispatchQueue.main, eventHandler: handleASAccessoryEvent(event:))
        // ...
    }

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

WiFiNetworkSharing/ASKSampleWiFiAccessory/ASKSampleWiFiAccessoryApp.swift:11 — representative type boundary

@main
struct ASKSampleWiFiAccessoryApp: App {
    // ...
            SampleAccessoryView()
    // ...
}

No local protocol conformance is claimed as protocol-oriented design; external framework conformances are listed only as dependencies.

Access control

Reference code

WiFiNetworkSharing/ASKSampleWiFiAccessory/DiceAccessory.swift:103 — representative boundary

    private func sendRollValue(value: String) {
        guard
        // ...
    }

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

Naming conventions

• Types: App: ASKSampleWiFiAccessoryApp, WiFiNetworkSharingSampleApp; Handler: EventHandler; Manager: DiceSessionManager; Provider: WiFiNetworkSharingProvider; View: ContentView, SampleAccessoryView.
• Protocols: no local protocol declaration in the scanned source.
• Methods: accept, invalidationHandler, handleASAccessoryEvent, activate, invalidate, listenForNetworkEvents, handleNetworkEvent, listenForAccessPointConnectionEvents.
• Files: WiFiNetworkSharing/ASKSampleWiFiAccessory/ASKSampleWiFiAccessoryApp.swift, WiFiNetworkSharing/WiFiNetworkSharingSample/WiFiNetworkSharingSampleApp.swift, WiFiNetworkSharing/TransportExtension/TransportExtension.swift, WiFiNetworkSharing/TransportExtension/WiFiNetworkSharingProvider.swift, WiFiNetworkSharing/ASKSampleWiFiAccessory/SampleAccessoryView.swift, WiFiNetworkSharing/WiFiNetworkSharingSample/ContentView.swift.

Architecture takeaways

• ASKSampleWiFiAccessoryApp is the main source-visible entry or composition anchor for this sample.
• Framework work reaches SwiftUI, AccessorySetupKit, CoreBluetooth, WiFiInfrastructure 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.
• The source does not justify labeling the design protocol-oriented.

Source map

• Official Apple documentation