[Feature]: Upload progress callbacks for Storage uploads (Swift parity with Android SDK)

[arbyruns]

Searched existing issues?

• I have searched the existing issues

Problem Description

The Android SDK supports upload progress tracking via uploadAsFlow, which emits UploadStatus.Progress events during an upload:

val bucket = supabase.storage.from("avatars")
bucket.uploadAsFlow("test.png", byteArrayOf()).collect {
    when(it) {
        is UploadStatus.Progress -> println("Progress: ${it.totalBytesSend.toFloat() / it.contentLength * 100}%")
        is UploadStatus.Success -> println("Success")
    }
}

The Swift SDK has no equivalent. The current API is fire-and-forget with no way to observe bytes sent:

try await supabase.storage
    .from("avatars")
    .upload(
        path: "public/avatar.png",
        file: fileData,
        options: FileOptions(contentType: "image/png")
    )

Proposed Solution

Proposed Swift API — an AsyncSequence-based equivalent that fits naturally into Swift concurrency.

for try await status in supabase.storage
    .from("avatars")
    .uploadStream(path: "public/avatar.png", file: fileData) {
    switch status {
    case .progress(let byteSent, let totalBytes):
        let percent = Double(byteSent) / Double(totalBytes) * 100
        print("Progress: \(percent)%")
    case .success(let response):
        print("Upload complete: \(response.fullPath)")
    }
}

Alternative Solutions

URLSession supports upload progress via URLSessionTaskDelegate.urlSession(_:task:didSendBodyData:totalBytesSent:totalBytesExpectedToSend:). The upload must be initiated from a file URL (not in-memory Data) for the byte count to be known upfront. An AsyncStream wrapping a URLSession with a delegate would be a minimal, clean implementation.

Priority

Medium - Would significantly improve my workflow

Additional Context

No response

[grdsdev]

Hey @arbyruns thanks for requesting this feature, I do plan to add it in the next major release, you can follow implementation along in the #917

[Swathiga-proj]

Hi @grdsdev, I'm interested in helping out with this parity feature! I saw you've linked this to #917 for the next major release—are you looking for outside contributors to help with the core implementation, or would you prefer to handle that yourself? Happy to help