-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Notification problems on release-5.9, 5.10 and 5.11 #88
Comments
@laktyushin can you look into this issue? As Telegram is an Instant Messaging app, notifications are really important for the users. Thanks a million. |
The issue is still happening on 5.11 |
Update: After testing of many test cases, the Notification is partially working. Criteria of receiving notifications: If you added 1 more Telegram account in v5.11, that account will receive notifications normally, just like the official app, given that the Notification settings in Telegram Fork enabled receiving notifications from all accounts. Strange, as the primary account (the first logged-in account) received no notification at all. |
Hello, I have reported this issue in 956 and 899 I had also had a second telegram account and deleted it and that's when my notifications stopped working. This is still a bug. |
Notifications have been a problem in Fork. Here are the major issues:
1. Badge count missing / not reflecting correct numbers / not updating at background (problem addressed in #74.
Temporary Solution: Ask the users to terminate other Telegram session in the same iOS device & reboot.
2. No banner alert even if all notification types (Alerts in Lock Screen, Notification Center, Banners, Banner Style: Temporary, Sound & Badge enabled) are enabled in iOS Settings > Notifications.
For problem 2, I still don't figure out a solution yet. In TelegramUI's
AppDelegate.swift
line 1858, it registers all types of notifications by default. Anyone can share some lights?What is the difference between Fork and official app regarding notifications? do the Telegram servers marked Fork clients having lower priority to receive notifications / updates?
3. Background update task used too much battery (problem addressed in #81), and solved in
release-5.9
.The text was updated successfully, but these errors were encountered: