RocketChat / RocketChat/Rocket.Chat

Omnichannel - Telegram Integration - Sending Excel Files, CSVs is not delivered to contacts

Open
#25,942 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
46.1k
Forks
13.9k
Avg merge
3d 3h
Merged PRs (30d)
130

Description

Description:

I'm using the community version of Rocket.Chat
I installed telegram app to my Omnichannel
I configured the telegram app to accept all media file types (left the field empty)
When I try to send excel or csv files, the system accepts them, but they are not delivered to the contact

Steps to reproduce:
  1. Install Telegram App
  2. Configure the app to accept all media files ( keep the field empty)
  3. Start a conversation with the telegram bot from a contact
  4. As an agent, try to send excel or csv
Expected behavior:

The excel or the csv should be delivered to the contact

Actual behavior:

The system accepts the file and marks it as sent, but the file is not delivered to the contact

Server Setup Information:
  • Version of Rocket.Chat Server: 4.6.3
  • Operating System: Windows 11
  • Deployment Method:
  • Number of Running Instances: 1
  • DB Replicaset Oplog:
  • NodeJS Version: v14.18.3
  • MongoDB Version: 5.0.9 / wiredTiger (oplog Enabled)
Client Setup Information
  • Desktop App or Browser Version: Chrome
  • Operating System: Windows
Additional context
Relevant logs:

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Start by reproducing the Telegram Omnichannel flow with an Excel file and a CSV while reviewing the Telegram app's accepted-media configuration; done means both file types are delivered to the contact rather than merely marked as sent.

Written by the indexing model from the issue text.

Assessment

Domain
api, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.