TelegramMessenger / TelegramMessenger/Telegram-iOS

Message doesn't get marked as read when using CarPlay

Open
#361 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

bug
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

When using CarPlay a notification badge will appear when you have unread messages. When you let CarPlay read the message, this badge isn't removed and the message is not marked as read. This means that if I get new messages, it doesn't register that.

Expected Behavior

When CarPlay (SiriKit) reads the message, it should be marked as read and all notifications should be removed.

Actual Behavior

The notification badge stays and the message is not marked as read. If I open the app, it show the message as unread as well. I need to force close the app and reopen it to have it be marked as read.

Steps to Reproduce
  1. Connect to CarPlay
  2. Receive message
  3. Let CarPlay read the message and even respond
  4. Message is not marked as read.
Environment

Device: iPhone 11

iOS version: 13.6.1

App version: 7.0.1

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

Start by locating the CarPlay/SiriKit message-handling entry points and the code that updates read state and notification badges. Reproduce the listed steps on the stated iPhone and iOS setup if possible; done means a message read by CarPlay is marked read and its notifications are removed without reopening the app.

Written by the indexing model from the issue text.

Assessment

Tech stack
ios, swift
Domain
mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.