No notifications are received

After reboot, they seem to work.

Currently, Telegram launches System Settings > Online Account, instead
of using the OA helper to introduce the credentials directly, which is
odd.

Could not reproduce using:

com.ubuntu.telegram 0.9.28.78
current build number: 184
device name: krillin
channel: ubuntu-touch/ubuntu-rtm/14.09.es-proposed

However we take into account the suggestion of using OA helper to configure u1 account

During last test pass I found that a device reboot was required before push notifications would start working.

I have found a similar problem, but I dont think is just telegram. All notifications seem to stop at some point and a reboot is needed

Could you get us the logs from ~/.cache/upstart/ubuntu-push-client.log* from when you noticed the problem?

We suspect this could be a symptom of a re-connection deadlock bug in ubuntu-push-client that occurs when the network connection is flapping, and have been working on a fix.

Initial patch is a mitigation that should significantly reduce occurrences of this but not directly fix the root cause. We would like to get that fix in ASAP for the w05/RTM milestone, and then target a root-cause fix for a later time.

Sorry, without logs there is no real indication that the connection deadlock is indeed the problem behind this bug. I'm tracking progress for that in lp:1390663. Given logs, we can mark this a dupe.

Unassigning myself and setting this back to Incomplete/High.

With the (partial) fix of lp:1390663 (now in silo 7, soon in rtm) this issue seems to go away.

Things are too murky for me to be sure it's a dupe, though. Would still welcome those logs.

How this currently works:
- Start Telegram
- Log in
- Select to configure notifications
- Sign in to Ubuntu One
[Next is crucial]
- Switch back to Telegram (or open it if it has been killed by the user)

From now on, you will get push notifications. This has been tested with 1.0.0.87 version (in the store) and the Ubuntu for phones image from the Friday's big event.

Since last telegram upgrade (v1.1.2.95) notifications stoped to working (bq phone). Karni solution (start telegram, log in, etc) did'nt work. Reset to factory settings didn't work. Other notifications are received, only fails with telegram.

Here logs:

https://www.dropbox.com/s/9yikndf5l8g1jxv/application-click-com.ubuntu.telegram_telegram_1.1.2.95.log?dl=0
https://www.dropbox.com/s/wab2hxndvxhdybw/ubuntu-push-client.log?dl=0

This is very confusing, because I can see this in the log file:
push - token changed: present
push - registering with Telegram now
tg.telegram: registering device for push - app version "1.1.2.95"
tg.plugin.logic: accountRegisterDeviceAnswer: true
push - registered with Telegram
tg.plugin.logic: push notifications list received

John, opinion?

Currently the problem is we switched our SSL certificates to TLS, and Telegram was attempting to use SSLv3. We've contacted them and are working on resolving this problem.

Ubuntu 15.04 (r23) on phone.

Restart phone, launch Telegram, first Telegram incoming message gives notification (vibrate, sound, icon).
Subsequent incoming messages, no notifications.

It appears I receive one notification per phone restart. Need to check if it is related to (a) leaving conversation open that receives next incoming message, (b) leaving Telegram app open, or other.

Thanks!

In both cases (a) and (b), the notifications will not show. They only show when the app is not in foreground or not running at all.

If you can clarify for which of the following 14 cases I should receive notifications, I can create a more specific FEATURE request.

1) A has entered password (screen is on), Telegram app has not been opened by A, B sends telegram to A
2) A has entered password (screen is on), Telegram app opened by A, no specific conversation opened by A, B sends telegram to A
3) A has entered password (screen is on), Telegram app opened by A, conversation between A and C opened by A, B sends telegram to A
4) A has entered password (screen is on), Telegram app opened by A, conversation between A and B opened by A, B sends telegram to A
5) A has entered password (screen is on), Telegram app opened by A, no specific conversation opened by A, A then switches to another app or "Home" screen, etc., B sends telegram to A
6) A has entered password (screen is on), Telegram app opened by A, conversation between A and C opened by A, A then switches to another app or "Home" screen, etc., B sends telegram to A
7) A has entered password (screen is on), Telegram app opened by A, conversation between A and B opened by A, A then switches to another app or "Home" screen, etc., B sends telegram to A
1b) Telegram app not opened by A, A's password timed out (screen is off, phone is on), B sends telegram to A
2b) Telegram app opened by A, no specific conversation opened by A, A's password timed out (screen is off, phone is on), B sends telegram to A
3b) Telegram app opened by A, conversation between A and C opened by A, A's password timed out (screen is off, phone is on), B sends telegram to A
4b) Telegram app opened by A, conversation between A and B opened by A, A's password timed out (screen is off, phone is on), B sends telegram to A
5b) Telegram app opened by A, no specific conversation opened by A, A then switches to another app or "Home" screen, etc., A's password timed out (screen is off, phone is on), B sends telegram to A
6b) Telegram app opened by A, conversation between A and C opened by A, A then switches to another app or "Home" screen, etc., A's password timed out (screen is off, phone is on), B sends telegram to A
7b) Telegram app opened by A, conversation between A and B opened by A, A then switches to another app or "Home" screen, etc., A's password timed out (screen is off, phone is on), B sends telegram to A

Thanks!

You should only receive a notification if:
1) you have already signed in
2) the application is not visible
3) someone sends you a message to a chat, that is not muted

You will not see notifications if the application is visible.