microsoft / BotFramework-WebChat

A highly-customizable web-based client for Azure Bot Services.
https://www.botframework.com/
MIT License
1.56k stars 1.51k forks source link

Image Attachment sent from bot broken in chat history #5233

Closed 01 closed 10 hours ago

01 commented 1 week ago

Is it an issue related to Adaptive Cards?

No

Is this an accessibility issue?

No

What version of Web Chat are you using?

Latest production

Which distribution are you using Web Chat from?

NPM

Which hosting environment does this issue primarily affect?

Web apps

Which browsers and platforms do the issue happened?

No response

Which area does this issue affect?

Chat history

Which theme pack does this issue affect?

I did not test it on other theme packs

What is the public URL for the website?

No response

Please describe the bug

Messages with an image attachment sent from bot becomes broken on refresh with same token in chat history. Behavior does not occur when user sends image. Initially the attachment content url is below { "contentType": "image/png", "contentUrl": "https://directline.botframework.com/attachments/Kdox6pXdpAlHZC1a86lauB-us/0000009/0/image?t=eyJhbGciOiJSUzI1NiIsImtpZCI6ImxZd3JkMzFhdmtEckhnQ2Z5b..., "name": "image" } after refresh domain changes to below which is broken { "contentType": "image/png", "contentUrl": "https://bcdirectlineeastus3.blob.core.windows.net/at70891/EWT8syzy**6-original", "name": "image" }

Do you see any errors in console log?

No response

How to reproduce the issue?

  1. Send activity with image attachment from bot to webchat client.
  2. Reconnect to the conversation with the same token

What do you expect?

content url for image attachment not change / break.

What actually happened?

Image attachments sent from bot result in broken content url on reconnect

Do you have any screenshots or recordings to repro the issue?

image image

Adaptive Card JSON

No response

Additional context

No response

stevkan commented 1 week ago

@01 - Just a few clarifying questions:

stevkan commented 12 hours ago

Closing due to inactivity. Please feel free to reopen if the issue persists or you have new details to share.