File object transferred using Socket.IO becomes 'ArrayBuffer'?

Question

When I transfer a file object (File interface) using Socket.IO with Typescript, the file becomes an ArrayBuffer on the receiving end.

Is there any way to transform the ArrayBuffer back into a File, or should I not send the entire file object using socket io (send name, data, mime type separately)?

File is just a special Blob, ArrayBuffer to Blob is easy.

Jonas Wilms
– Jonas Wilms

2017-08-13 17:34:18 +00:00
Commented Aug 13, 2017 at 17:34 — Jonas Wilms
– Jonas Wilms, Commented Aug 13, 2017 at 17:34

guest271314 · Accepted Answer · 2017-08-13 17:34:24Z

2

Pass the ArrayBuffer to Blob or File constructor

const file = new Blob([ab])

const file = new File([ab], "filename.ext", {type:/* valid MIME type */})

answered Aug 13, 2017 at 17:34

guest271314

1

Sign up to request clarification or add additional context in comments.

3 Comments

Kevin Van Ryckegem Over a year ago

I tried that, var file : File = new Blob(arraybuffer); however, I get the error that the Blob class is missing the lastModifiedDate that the File requires, and so cannot be converted. If I force it using typecasting, I get the error: core.es5.js:1084 ERROR TypeError: Failed to construct 'Blob': Iterator getter is not callable.

Kevin Van Ryckegem Over a year ago

Missed the update, will try the second line, thanks!

guest271314 Over a year ago

If lastModifiedDate is required by your application you can set that property at the object at the third parameter of File() constructor

Collectives™ on Stack Overflow

File object transferred using Socket.IO becomes 'ArrayBuffer'?

1 Answer 1

3 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

3 Comments

Your Answer

Sign up or log in

Post as a guest

Related