-
Notifications
You must be signed in to change notification settings - Fork 322
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unrecognized UTF8 Byte #76
Comments
This bug is currently being fixed and I have added you to the list of people to be notified when it's done. Thanks! |
We're experiencing the same error. Could you add me to the list of notified people? In case this helps: in attempt to narrow down the root cause, we've found that we can't reproduce the error when only using Best I can tell, both forms are valid: # Just plain Ruby
["<foo>"].to_json
# => "[\"<foo>\"]"
JSON.parse(["<foo>"].to_json)
# => ["<foo>"]
# After `require 'active_support/json'`
["<foo>"].to_json
# => "[\"\\u003cfoo\\u003e\"]"
JSON.parse(["<foo>"].to_json)
# => ["<foo>"] |
You have been added @pbyrne and thanks for the additional feedback! |
@thinkingserious is there a version that don't have this issue for |
@ming-relax, Unfortunately not. This is a server side issue. That said, as of right now, it looks like this fix is scheduled to be released today. |
The fix for this has been deployed :) Thank you for your patience! |
Add Gemfile
Hey,
Some of our requests seem to be having UTF8 encoding issues when using the new API. Running a request with the same html body (I'm assuming that's where this fall) against the old API results in a successful send.
From what I can tell, it is rather similar to this issue brought up in the Go client: sendgrid/sendgrid-go#66
Error below.
{"errors":[{"message":"Unrecognized UTF8 Byte at position 31051","field":null,"help":"http://sendgrid.com/docs/API_Reference/Web_API_v3/Mail/errors.html#-Encoding-Errors"}]}
Can provide more details upon request, but just wanted to bring it to your attention since it seems to be impacting multiple clients.
Technical details:
The text was updated successfully, but these errors were encountered: