utf8 encoding on responses corrupts data

Currently I don’t see any ways to disable this behaviour, but binary data that is sent gets corrupted, i.e., downloading a public spreadsheet file is impossible, because it’s corrupted as soon as you get it.

drive.files.export({
    auth: API_KEY,
    fileId: "<mySpreadSheet>",
    mimeType: "application/vnd.openxmlformats-officedocument.spreadsheetml.sheet"
}, (err: any, result: any) => {

at this point result is utf8.

Workaround: make a https request and don’t set the encoding to utf8. Bonus points for being lazy and finding the url via debugging this library.

[rsxdalv]

Ok, so I wrote this to satisfy my use case:

import * as google from "googleapis";

const drive = google.drive("v3");

import { writeFileSync } from "fs";

const buffers = new Array<Buffer>();

drive.files.export({
    auth: key,
    fileId: "<file id>",
    mimeType: 'application/vnd.openxmlformats-officedocument.spreadsheetml.sheet'
})
    .on('data', (buffer: Buffer) => {
        buffers.push(buffer);
    })
    .on('end', function () {
        const result = Buffer.concat(buffers);
        writeFileSync("./test.xlsx", result);
        console.log('Done');
    })
    .on('error', (err: any) => {
        console.log('Error during download', err);
    });

Hopefully my woes will act as a documentation for poor souls who didn’t guess that the output has an encoding set to utf8 that corrupts binary data, and that they need to use the (at least back then, my guess is still now) implicit pipe API with omitting the callback.

So yes, this can be closed

[bantini]

Didn’t the pipe solve the issue for file downloads? If not, can you be more specific on what didn’t work on the file download? Accordingly, I can reopen this issue, or create a new one.