fix: use Base64.strict_encode64 instead of Base64.encode64
#495
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes
When I used
Base64.encode64to encode attachments, I got the following error:{ "errors": [ { "message": "The attachment content must be base64 encoded.", "field": "attachments.0.content", "help": "http://sendgrid.com/docs/API_Reference/Web_API_v3/Mail/errors.html#message.attachments.content" } ] }It is resolved by changing to encode attachments using
Base64.strict_encode64where no line feeds are added.Checklist
If you have questions, please file a support ticket, or create a GitHub Issue in this repository.