peter-iakovlev / Telegram

Telegram Messenger for iOS
3.25k stars 862 forks source link

Telegram X: no audible/visual notification #229

Open Edsol opened 6 years ago

Edsol commented 6 years ago

I use Telegram X about from 2 month, I don't know how but in some times the notification system don't work propertely, when receive a message I don't see any notification in the bar and any sound alert me, only vibration works.

tguyette commented 6 years ago

@Edsol - What platform is this happening on?

On Android, I find this happens if I have Telegram open on my desktop.

Also, are you noticing that when you launch Telegram you sometimes suddenly see a bunch of messages you didn't know you had / didn't get notifications for? On Android, I've seen sometimes Telegram doesn't do a good job at keeping its data connection open, so when you open it you get a flood of backlogged messages.

Edsol commented 6 years ago

@tguyette sorry, the issue is on android. I thought the problem is Telegram Desktop open but when it happens I'm sure I have all the PCs turned off.

tguyette commented 6 years ago

@Edsol - Are you turning all the PCs off for the night by chance? The Android Do Not Disturb feature, which one some phones turns on automatically, will stop notifications from popping up and will mute sounds.

Edsol commented 6 years ago

The problem is only on Telegram X version, on classic version notification work perfectly. I have a Oneplus 3 and the related physical button can turn on "not disturb" mode. there may be conflic with this?

attenzione commented 6 years ago

I have the same issue, and we are not alone - https://www.reddit.com/r/Telegram/comments/7ug205/telegram_x_notifications_disappear_immediately/

Desktop is not really a problem. I've cleared all sessions on telegram, including phone, uninstalled app and closed all desktop versions. Installed app again, still no notifications, just vibration.

mmvidigal commented 6 years ago

Do you guys have Passcode Lock active? When I disable it, I start getting notifications.

dwiprawira commented 6 years ago

Try uninstall android wear. I did and my notification came back..

lukasresch commented 6 years ago

@dwiprawira1989 do u mean the app "Android Wear" (or now "Wear OS") on the phone, or the Telegram app on the watch itself?

behrooz-zahedi commented 6 years ago

Yaaay, that is correct, for fix notifications problem in telegram x you need to remove "wear os" app (old name "android wear"), thanks 👍

AlejandroHCruz commented 6 years ago

Removing the notifications permission from the Wear OS Android app is enough to fix the problem... Rendering the smartwatch unusable.


From: BehrOOz notifications@github.com Sent: Tuesday, April 3, 2018 3:31:17 PM To: peter-iakovlev/Telegram Cc: Alejandro H. Cruz; Manual Subject: Re: [peter-iakovlev/Telegram] Telegram X: no audible/visual notification (#229)

Yaaay, that is correct, for fix notifications problem in telegram x you need to remove "wear os" app (old name "android wear"), thanks 👍

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/peter-iakovlev/Telegram/issues/229#issuecomment-378250741, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AB0Kus2hf8B5hrNle4E0Xja5reyl3GR-ks5tk3mlgaJpZM4SMmHq.

mmvidigal commented 6 years ago

For me it was fix with last update.

giard-alexandre commented 6 years ago

Kinda sucks that I have to choose between a functioning smartwatch or getting my notifications from my messaging app... PS: confirmed that removing WearOS fixes the Telegram X notification issues.

1danmi commented 6 years ago

Same issue here. Prevent notification access from Wear OS all solves the problem but it makes the watch unusable. Please fix it.

giard-alexandre commented 6 years ago

Most recent update seems to have fixed it for me. Running V 0.20.7.918-arm64-v8a

behrooz-zahedi commented 6 years ago

i can confirm, new version "0.20.7.918-arm64-v8a" solved this bug

MrGarri commented 6 years ago

Version "0.20.7.918-arm64-v8a" solves this issue