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

LiveChat-Widget adds an extra URL prefix when sending image URL #26511

Closed
SangyulCha opened this issue Aug 8, 2022 · 1 comment · Fixed by #27387
Closed

LiveChat-Widget adds an extra URL prefix when sending image URL #26511

SangyulCha opened this issue Aug 8, 2022 · 1 comment · Fixed by #27387

Comments

@SangyulCha
Copy link

Description:

I am developing a Rocket.Chat App using the AppEngine. When using the LiveChat-Widget to forward an image or audio from an external source (like botpress), it somehow adds an extra URL prefix. Is there a way to force LiveChat-Widget to not add the prefix?

Steps to reproduce:

  1. create an IMessageAttachment object with an image URL
  2. add object as an attachment to IMessageBuilder
  3. send message to LiveChat

Expected behavior:

expected

  • Bot send the Image correctly (I logged in bot account and sent the image and audio manually)

Actual behavior:

problem

cat_image_in_rc

  • But as you can see in Rocket.Chat, actually bot sent the image correctly

Server Setup Information:

  • Version of Rocket.Chat Server: 4.8.0
  • Operating System: Ubuntu 22.04.1 LTS
  • Deployment Method: Docker
  • Number of Running Instances: 7
  • DB Replicaset Oplog: Enabled
  • NodeJS Version: 14.18.3
  • MongoDB Version: 4.4.14

Client Setup Information

  • Desktop App or Browser Version: Chrome 104.0.5112.79 (Official Build) (64-bit)
  • Operating System:
@Nabhag8848
Copy link
Contributor

Hey, Would love to work, assign it to me. I am pretty new to this project. Can anyone point me out on what folder to look at. Thanks!

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

Successfully merging a pull request may close this issue.

6 participants