When updating a previous message with chat.update, uploaded images are not visible

[gregghz]

I'm sending a message to a user with the sdk. After sending the message, I generate an image thumbnail and would like to update the previously sent message to include the thumbnail when it is ready.

The Slack SDK version

1.42.0

Java Runtime version

openjdk version "21.0.6" 2025-01-21 LTS
OpenJDK Runtime Environment Corretto-21.0.6.7.1 (build 21.0.6+7-LTS)
OpenJDK 64-Bit Server VM Corretto-21.0.6.7.1 (build 21.0.6+7-LTS, mixed mode, sharing)

OS info

(sw_vers doesn't exist for me)

$ uname -v
#53-Ubuntu SMP PREEMPT_DYNAMIC Sat Jan 11 00:06:25 UTC 2025

Steps to reproduce:

1. chat.postMessage the initial message
2. files.upload the image, leaving the channel field empty
3. poll files.info until the image is ready (currently just checking for the original height field)
4. chat.update on the initial message to add an ImageBlock with the id of the previously uploaded image

At this point, the original message is updated but the image is this rather than the image I uploaded:

If I use chat.postMessage with the previously upload and unshared image, it shows up correctly. If I do a chat.postMessage with the image and then update the original, it also shows up correctly. If I do chat.update with the original message, then do a chat.postMessage to also post the message directly, the update shows the broken image, the postMessage shows the image correctly, and if I click to zoom on the udpate image, it also shows correctly but only if i've done a chat.postMessage withe the same image sometime after the chat.update.

Expected result:

I expect the image to show correctly after updated the previously posted message

Actual result:

The image is broken

[gregghz]

I beileve this issue might be related: slackapi/node-slack-sdk#2100

[WilliamBergamin]

Hi @gregghz thanks for writing in 💯

Yess this appear to be the same issue as slackapi/node-slack-sdk#2100, it is a server side issue I will raise this internally again

You can also also reach out to [email protected] in order to report this issue