RocketChat / RocketChat/Rocket.Chat
Emoji falsely included in URL in push notification preview when URL contains `:emoji_name:` identifier somewhere
Open
Nobody has claimed this yet.
planned
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Reproduction
- Person A sends this message to person B:
https://example.com/:x:/something
in real life I encountered this in:
https://companyname-my.sharepoint.com/:x:/g/personal/username_companyname/XXX?e=ZZZ - Person B gets a push notification.
Expected
- In the push notification preview the URL is shown as-is (as it was sent).
- A URL and also an
inline code snippetshall be exempt from any on the fly text replacements / transformations.
Actual
In the push notification preview the URL includes an Emoji Unicode symbol instead of the emoji identifier markup.
Check out: https://example.com/❌/something
| macOS | Windows |
|---|---|
Additional context
- Occurs on RocketChat Desktop app for: macOS as well as Windows.
- So I assume this bug happens server-side (text preview snippet processed before sent to push notification service)
Client Setup Information
- Desktop App or Browser Version: RocketChat Desktop app 4.1.1
- Operating System: macOS 15.1.1 Sequoia
Server Setup Information:
- Version of Rocket.Chat Server: 6.11 (reported by https://chat.example.com/api/info )
- License Type: Community
- Number of Users: ca 20
- Deployment Method: docker
- Operating System: ?
- Number of Running Instances: ?
- DB Replicaset Oplog: ?
- NodeJS Version: ?
- MongoDB Version: ?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the push notification preview with a URL containing a :emoji_name: identifier and an inline code snippet, then trace the server-side text preview processing described in the report. Confirm that URLs and inline code remain unchanged, including the :x: segment, while ordinary text transformations still work as intended.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100