SlackNotifier message notification popup says "no preview available" in Slack desktop client for Windows

[andre-engelbrecht]

I've setup the SlackNotifier in my GCP build pipeline, everything is working pretty well but when messages come through in the Slack desktop client for Windows, the notification popup says "no preview available" even though the actual message in Slack appears fine.

This seems to be due to the fact that in the WebhookMessage post, the "Text" property is not included and Windows / Slack (on Windows) not supporting rich-text content. Slack documentation suggests including the "Text" property in the payload which will be used as fallback when rich-text is not supported.

More details are available in the StackOverfow issue I posted: https://stackoverflow.com/questions/76657027/google-cloud-build-slack-notifier-message-no-preview-available

The posted answer explains the (suspected) problem and solution and he even created a fork with suggested code changes - onix@e83dab3

[jkumara]

It would be great to get this solved!

[scr4bble]

I am getting the same thing [No preview available] in notification inside Fedora linux (using web browser slack app) and the same also applies to android mobile slack application.

Our slack json looks like this:

[
    {
        "type": "section",
        "text":
        {
            "type": "mrkdwn",
            "text": "Cloud Build in *{{.Build.ProjectId}}* for service *{{.Build.Substitutions._SERVICE_NAME}}* has finshed with status *{{.Build.Status}}*"
        },
        "accessory":
        {
            "type": "button",
            "text":
            {
                "type": "plain_text",
                "text": "Build Logs"
            },
            "value": "click_me_123",
            "style": "primary",
            "url": "{{.Build.LogUrl}}",
            "action_id": "button-action"
        }
    }
]

[universal-jewellery]

Same on MacOS 13.7.1 with Slack 4.41.105.

Looking at what returned here it would seem "Blocks" are catered for your slack.json as well as the colors outlined here. What we would also need is a way to pass in a text string which would act as your preview text.

[universal-jewellery]

Same on MacOS 13.7.1 with Slack 4.41.105.

Looking at what returned here it would seem "Blocks" are catered for your slack.json as well as the colors outlined here. What we would also need is a way to pass in a text string which would act as your preview text.

Looking at the data available. We have tmplView which contains the Build object. Assuming the slack-go client is able to accept Text: <string> it in theory it could be modified it so that any string Build properties could occupy that string... OR we could set up a dedicated ENV or similar in the yml that would take precedence if set - we also have access to Build in the string could be templated there.

[universal-jewellery]

Same on MacOS 13.7.1 with Slack 4.41.105.
Looking at what returned here it would seem "Blocks" are catered for your slack.json as well as the colors outlined here. What we would also need is a way to pass in a text string which would act as your preview text.

Looking at the data available. We have tmplView which contains the Build object. Assuming the slack-go client is able to accept Text: <string> it in theory it could be modified it so that any string Build properties could occupy that string... OR we could set up a dedicated ENV or similar in the yml that would take precedence if set - we also have access to Build in the string could be templated there.

Which all looks exactly like its been taken care of by this PR already:

[psyanite]

I've got the same problem unfortunately, and it seems there's no workaround aye?

[Hainguyen1210]

I'm having the same issue. Hopefully, it will be resolved soon.

[Hainguyen1210]

@universal-jewellery The PR#91 was closed because they claim the logic has been included in the main image. Have you tried it and fixed the no preview available issue? I've tried myself but still can't make the preview message show up.

[Hainguyen1210]

cc @edwardthiele

[Hainguyen1210]

My approach for this at the moment is building the image myself.