Mattermost-server: API attachments with text doesn't display emojis

Created on 16 Feb 2018  路  7Comments  路  Source: mattermost/mattermost-server

Summary

Submitting a attachment with text data per api will not show any emojis, in Version 4.5.0 this worked fine. In Version 4.7.0 it doesn't work any longer...

Steps to reproduce

Post a message with payload attachment to the Webhook and add a emojis like : white_check_mark : (without the spaces) to the text

Expected behavior

Showing a Green icon with a white check mark

Observed behavior (that appears unintentional)

Showing the emoji macro ": white_check_mark :"

Possible fixes

I can't

Most helpful comment

Hi @HLeithner,

Thank you for this report,
Just wanted to let you know that we are working on a 4.7.2 dot release to fix this ticket. We are expecting 4.7.2 to be released this week.

All 7 comments

I am encountering the same issue after upgrading to 4.7.0 (We were previously on 4.1). We use a mattermost plugin for jenkins that is sending emojis in the fields/value section. These emojis are not being displayed, this used to work prior to the upgrade. Other formatting works though, such as bold text. I am assuming it is not expected behavior...

What jenkins is posting to the webhook:

{
  "icon_url": "",
  "attachments": [
    {
      "color": "good",
      "mrkdwn_in": [
        "pretext",
        "text",
        "fields"
      ],
      "fields": [
        {
          "short": false,
          "value": "Test-Jobs 禄 Test Mattermost Job - #6 :white_check_mark: This is some **bold** text"
        }
      ],
      "fallback": "Test-Jobs 禄 Test Mattermost Job - #6 :white_check_mark: This is some **bold** text"
    }
  ],
  "text": "This is a message from Jenkins :white_check_mark:",
  "username": "jenkins"
}

How it is displayed (notice the white-check-mark emoji text)

image

Sill not working in 4.7.1

Hi,

It looks like this broke when we added lazy loading for custom emojis in 4.7. I've filed a ticket to fix this here

Hi @HLeithner,

Thank you for this report,
Just wanted to let you know that we are working on a 4.7.2 dot release to fix this ticket. We are expecting 4.7.2 to be released this week.

@amyblais thx

Hi @HLeithner,

v4.7.2 is released so I'll close this issue off here for now and you can let us know if you still have a problem after upgrading 馃憤

@lindy65 thx I can confirm works for me with 4.7.2.

Was this page helpful?
0 / 5 - 0 ratings