Initial data: Telegram is the foreground active app. In the chats list, a chat with another user is selected, the correspondence is displayed on the right.
So, if close the window right there (using cmd+w in my case), then new incoming messages from this chat continue to be marked as read and notifications about them do not come.
If I click the application icon in the dock, a window is displayed with no chats selected and prompts me to choose who I would like to write to.
Messages coming this moment still marking as read.
Steps to reproduce
open the app
select chat with another user
close the app window using cmd+w
wait for new message notification from that, step 2, chat
fail
Device info
Telegram macOS 9.0.1 (237033) APP_STORE, MacBook Pro 13" M1, 13.0
I'm also seeing this: chats are being read, no notifications. I've restarted both devices, reset notifications, ensured background refresh was on, notification permission is on, Focus modes off, low battery mode off, switched between mobile data vs Wi-Fi. No difference.
MacBook Air (2020) M1 Telegram 9.0.1.237033 (via the AppStore) // macOS 12.6
iPhone 12 Pro Telegram 9.0.2 (24217) // iOS 16.0.2
.
...
The developer of the macOS version has replied! It'll be fixed in the next beta and stable soon-ish?
Log in here to report bugs or suggest features. Please enter your phone number in the international format and we will send a confirmation message to your account via Telegram.
MacOS Telegram still reads messages after closing #21226
Messages are marked as read even if the window ... #21090
Incoming messages continue to be marked as read... #21060 (this bug)
I'm also seeing this: chats are being read, no notifications. I've restarted both devices, reset notifications, ensured background refresh was on, notification permission is on, Focus modes off, low battery mode off, switched between mobile data vs Wi-Fi. No difference.
MacBook Air (2020) M1
Telegram 9.0.1.237033 (via the AppStore) // macOS 12.6
iPhone 12 Pro
Telegram 9.0.2 (24217) // iOS 16.0.2
https://github.com/overtake/TelegramSwift/issues/847