Corey Walo
Corey Walo
I think it's pretty straightforward if you already have the image data. I think controlling playback will be pretty essential, even if it's just internal as a means to manage...
@Jeyhey Sounds like SwiftGif has some memory leak issues with their implementation and that's definitely something we wouldn't want to inherit. https://github.com/bahlo/SwiftGif/issues/6
@drougojrom Are you trying to run this in the simulator? I believe this needs to be run on an ARM device, since the sim is i386.
This appears fixed in iOS 26-Beta 4 (likely fixed in beta 3).
Thanks for taking a look @grdsdev! >Instead, Supabase should expose a protocol that the `TUSKit` library implements in a separate library. Then, when someone wants resumable upload support, they would...
> Additionally, we could introduce a new option for a `ResumableUploadProtocol`, which a third-party library would import TUSKit and provide an implementation of that protocol. I was just poking at...
I think this might do the trick Define a protocol with associated types: ```swift public protocol ResumableUploadProtocol: Sendable { associatedtype UploadType associatedtype UploadStatus init(bucketId: String, url: URL, headers: [String: String])...
With the addition of the protocol, I'll probably still want to package my implementation separately just because it provides a nice concurrency api over TUSKit :)
@grdsdev Nice! I'll check it out.
You'll likely need to stand up your own token swap server if you aren't already. This allows you to authenticate without needing to call `authorizeAndPlay`.