I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

Thanks for the request. We're exploring an async/await API with Progress support in #10161. We're somewhat hesitant to go forward with this since Apple's roadmap for Progress is unclear. See https://forums.swift.org/t/what-s-next-for-foundation/61939#removed-types-8

In the meantime, the original non-async/await Storage APIs continue to support Progress.

Hello @paulb777

Thank you!

After more thought, I believe the original APIs that return Task handles should be sufficient if you want to check task status. The async/await API's should only be used for fire and forget mode.

I'll close here, but feel free to continue the conversation.

@paulb777 Hi, yeah, I'm using original Api to check statuses now, but I want to improve my code to fit async await, and functions like delete are working well, so I thought if you can improve other methods as well, so I won't loose any functionality

@paulb777 Hi

Why do you think that async await API should be different from the original one?
From my perspective it should be the same. Also Apple's doing the same thing. For example you can access 'fractionCompleted' in async/await in Progress, it is easy to access via KVO. What do you think about KVO?

I defined an extension which takes a closure, which is called when progress happens, while the result is still returned from an async function.

extension StorageReference {
    func write(toFile url: URL, onProgress: @escaping (Double?) -> Void) async throws {
        let downloadTask = self.write(toFile: url)
        try await withCheckedThrowingContinuation { continuation in
            downloadTask.observe(.progress) {
                onProgress($0.progress?.fractionCompleted)
            }
            
            downloadTask.observe(.success) { _ in
                continuation.resume(with: .success(()))
            }
            
            downloadTask.observe(.failure) { snapshot in
                continuation.resume(with: .failure(snapshot.error ?? NSError()))
            }
        }
    }
}

// on the call site
try await reference .write(toFile: file) { progress in
    print(progress ?? 0.0)
}

That is working fine so far, but an integration of something like this into the package would be nice.

@JarnoRFB Thanks for the suggestion! PR in progress at #11289