The array that is returned when sourcing an individual message is being mangled with superfluous CRLF characters (ie: \r\n), making it impossible to pull values like UUID’s from emails.
I addressed this by just stripping out all CRLF chars that come back in the body when sourcing an individual message. A bit inconsistent behavior between the two email retrieval methods.
Here’s an example :
When getting all emails and pulling the ‘mail_text_only’, this UUID is formatted properly : dabfc1a3-7435-11ea-9b95-b62166aae693
When sourcing a specific email, the UUID appears like so : dabfc1a3-7=\r\n435-11ea-9b95-b62166aae693
Junte-se à discussão - adicione o comentário abaixo:
Efetue login / inscreva-se para postar novos comentários
I addressed this by just stripping out all CRLF chars that come back in the body when sourcing an individual message. A bit inconsistent behavior between the two email retrieval methods.
Here’s an example :
When getting all emails and pulling the ‘mail_text_only’, this UUID is formatted properly : dabfc1a3-7435-11ea-9b95-b62166aae693
When sourcing a specific email, the UUID appears like so : dabfc1a3-7=\r\n435-11ea-9b95-b62166aae693