-
I'm trying to leverage a Storage bucket with pre-signed URLs to play back audio on iOS. When trying to trigger the sound, I get
When I use the following remote test file (NOT in the bucket) it works fine. After digging on Google for a bit, I am pretty sure this error is due to the storage server not supporting byte range requests. The only relevant difference between the remote URL and the bucket response headers is the To my knowledge, S3 signed urls support byte range requests, and I think you all are using S3 under the hood? So, are byte range requests for pre-signed URLs possible? For now, I'll probably just not stream it and just download-and-play, since I'm still prototyping. Eventually, though, having a byte range request would be great. Maybe I could contribute something to the code here if it's feasible! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Hey @quicksnap, I haven't checked this but yeah we should support this if we aren't already. Creating an issue here Here is where we stream the response from s3. So I think we will need to pass through the headers from s3 to the client there. Let me know if want to contribute to the code and I can help you get up and running if you are stuck somewhere :) |
Beta Was this translation helpful? Give feedback.
Hey @quicksnap, I haven't checked this but yeah we should support this if we aren't already. Creating an issue here
Here is where we stream the response from s3. So I think we will need to pass through the headers from s3 to the client there. Let me know if want to contribute to the code and I can help you get up and running if you are stuck somewhere :)