TelegramMessenger / TelegramMessenger/Telegram-iOS
"No archived" folder filter is handled inconsistent with tdesktop app when a chat is both included and excluded
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
Behavior between iOS and tdesktop clients regarding chat filtering in folders is inconsistent (telegramdesktop/tdesktop#8427) and tdesktop devs say that their behavior is correct.
Steps to Reproduce
- Choose an arbitrary chat X.
- Archive the chat X.
- Create a folder which "includes" the chat X (as an individual chat, not by chat type), but "excludes" all archived chats.
- Check whether the folder shows the chat X in tdesktop.
- Check whether the folder shows the chat X in mobile app (I've used iOS).
Expected Behavior
Behavior should be consistent between tdesktop and iOS app: either chat X is consistently shown both in tdesktop and mobile app, or the folder is consistently empty.
Actual Behavior
Behavior is inconsistent: tdesktop 2.3 shows the chat X (i.e. its exclusion by "archived" does not work), but iOS app 7.0 does not (i.e. it excludes all archived chats, even if they're explicitly listed in the "archived" section).
Environment
Device: iPhone
iOS version: 13.3.1
App version: 7.0
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
Start by reproducing the listed folder-filter scenario on the iOS app with an archived chat that is explicitly included and all archived chats excluded. Compare the result with the linked tdesktop behavior and trace the iOS chat-folder filtering area; done means the two clients handle this case consistently, with a regression check for the reproduction steps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100