Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue: Uploaded Image URL Becomes Invalid After Updating Message with Select Block #2100

Open
martirook opened this issue Nov 25, 2024 · 2 comments

Comments

@martirook
Copy link

martirook commented Nov 25, 2024

@slack/web-api version

7.7.0

Node.js runtime version

v20.18.0

Steps to reproduce:

  1. Upload multiple image blobs using the files.uploadV2 API and retrieve their permalink values.
  2. Use these permalinks as value options in a static_select block.
  3. Send an initial message that includes:
  • A select block with the uploaded image URLs as options.
  • An image block showing the first uploaded image.
  1. Handle the selection action:
  • Update the message by replacing the image block with the URL of the selected option using chat.update.
  1. Observe the updated message.

Expected result:

  • The first message shows the first image correctly.
  • When a user selects a new option, the message updates to display the new image from the static_select block.

Actual result:

  • The first message shows the first image correctly.
  • After selecting a new image, the chat.update call fails to display the updated image. The image_url (permalink from files.upload) becomes invalid., but the shown size is correct.
Screenshot 2024-11-25 at 14 27 41 Screenshot 2024-11-25 at 14 30 44
@martirook
Copy link
Author

Additional Observation
When using chat.postMessage instead of chat.update, the provided image_url (permalink from files.upload) works as expected, and the image is displayed correctly.

@WilliamBergamin WilliamBergamin transferred this issue from slackapi/bolt-js Nov 25, 2024
@WilliamBergamin WilliamBergamin added pkg:web-api applies to `@slack/web-api` server-side-issue labels Nov 25, 2024
@WilliamBergamin
Copy link
Contributor

WilliamBergamin commented Nov 25, 2024

Hi @martirook thanks for writing in 💯

I was able to reproduce this behavior a placed my test script and results in this GIST

This seems to be a server side issue, I will raise it internally, but you can also use the /feedback command in slack to raise your concern

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants