TelegramMessenger / TelegramMessenger/Telegram-iOS
Old message being pushed as an unread notification
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 9k
- Forks
- 2.9k
- PR merge metrics
- No merged PRs in 30d
Description
Checklist
- I am reporting an issue in existing functionality that does not work as intended
- I've searched for existing GitHub issues
Description
Notification may delay or not showing.
When a message is read (and marked as read), the app may push the message notification again after 5 or 10 minutes.
Expected Behavior
Old message should not be notified again.
Actual Behavior
Old messages are notified again in 5~10 minutes after reading it.
Steps to Reproduce
Environment
Device: iPhone 8 Plus
iOS version: 14.0.1
App version: 7.1.2
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
The issue names no source files, tests, or entry points. Start by reproducing the delayed notification on an iPhone 8 Plus running iOS 14.0.1 and app version 7.1.2, then trace the notification and read-state behavior. Done means a message marked as read is not pushed again after 5–10 minutes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100