Sendgrid-nodejs: Send mail failed with v3 API and multi-byte contents

[akifo]

I have the same issue.

https://github.com/sendgrid/sendgrid-go/issues/66

It works.

var content = new helper.Content("text/plain", "あああ");

but, the following code does not work.

var content = new helper.Content("text/plain", "あああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああああ");

{"errors":[{"message":"Unrecognized UTF8 Byte at position 510","field":null,"help":"http://sendgrid.com/docs/API_Reference/Web_API_v3/Mail/errors.html#-Encoding-Errors"}]}

Is there any update?

[thinkingserious]

@akifo,

This is currently being fixed, I've added you to the list of people to notify when the fix goes live.

[fockus]

Hello, thinkingserious.

Show you have any news? We start the project and we can not send invites to our first users?

[thinkingserious]

@fockus,

It's moved into a higher priority, but I don't know exactly when it will be fixed. As soon as it is, I will let you know.

[Josebaseba]

Same problem here:

var content = new helper.Content("text/html", html);
        var mail = new helper.Mail(from_email, subject, to_email, content);
        var requestBody = mail.toJSON();
        var request = sg.emptyRequest();
        request.method = 'POST';
        request.path = '/v3/mail/send';
        request.body = requestBody;
        sg.API(request, function (response) {
          sails.log.debug(response.statusCode);
          sails.log.debug(response.body);
          sails.log.debug(response.headers);
        });

Randomly gets:

{"errors":[{"message":"Unrecognized UTF8 Byte at position 511","field":null,"help":"http://sendgrid.com/docs/API_Reference/Web_API_v3/Mail/errors.html#-Encoding-Errors"}

The emails are normal html, and it happens 1 per 10 emails more or less...

[thinkingserious]

@JacobBarba this is a known server side issue and it currently being resolved in this sprint by our engineering team. I will be updating this thread when the fix is deployed.

[thinkingserious]

The fix for this has been deployed :)

Thank you for your patience!