Badge counts not keeping sync with app/notifications

Any progress with this bug?

Noemi, we're investigating this now, sorry for the delay.

Roberto, this line of code:
pushClient.count = 0;

results in:
tg.plugin.logic: push notification error: "Unknown method"

This bug was fixed in the package ubuntu-push-qml - 0.1+15.04.20150119-0ubuntu1

---------------
ubuntu-push-qml (0.1+15.04.20150119-0ubuntu1) vivid; urgency=low

  [ Roberto Alsina ]
  * Fix a typo that prevented setting the icon badge counter value from
    QML (LP: #1397396)
 -- Ubuntu daily release <email address hidden> Mon, 19 Jan 2015 18:56:25 +0000

This bug was fixed in the package ubuntu-push-qml - 0.1+15.04.20150120~rtm-0ubuntu1

---------------
ubuntu-push-qml (0.1+15.04.20150120~rtm-0ubuntu1) 14.09; urgency=low

  [ Roberto Alsina ]
  * Fix typo that prevented setting the badge counter from QML (LP:
    #1397396)
 -- Ubuntu daily release <email address hidden> Tue, 20 Jan 2015 17:10:55 +0000

@michal whats the status on this, is a telegram app change required?

Hi Pat,

We have a fix for this. We plan to release on Monday (Tuesday the latest?) - depending on what's the deadline for the final tarball. I know it's late, but I assure you I'm completely dedicated to this (and a stable release).

For this next release, I'm actively working on a fix for another more serious bug [1], which I'm considering a blocker (thus working over the weekend). I have the fix, but we have a crash deep in the source when the app is opened multiple times from the notifications (and from the notifications only, not from the launcher). In the worst case, we'll land the fix for this bug, and trim the mentioned [1] so that the app launches, but does not open a dedicated dialog (which is a workaround I would very much prefer to avoid).

[1] https://bugs.launchpad.net/libqtelegram/+bug/1412921

For now, we'll zero the badge counter when the app is launched. We'll later improve this to reflect the actual unread messages count as the user reads through them in the app (and perhaps has some still left to read).

Forgot to say - yes, we'll want to release a click to the custom tarball. Perhaps by the end of the day. (That depends if we have some time tomorrow for other fixes).

Telegram update will go to the store, so no longer tracking

Correct. We've handed over to QA to reflect the actual count of unread messages (not just zero'ing when app launched).

Was this bug going to be implemented in this new version?
It still keeps the counter up to 0 even if you have already read the messages.

We had to hold the previous release (regression in notifications), and this week's was delayed mostly because QA resources preoccupied with BQ image QA. We plan to publish Telegram to the store before mid next week, so it's ready for Feb 6th as an update. In my understanding, we also plan to include the click in the upcoming custom tarball. Effectively, there was no release last week, and this week's release has been delayed, apologies. This version however addresses multiple issues, please see here:
https://launchpad.net/libqtelegram/+milestone/m15

Ok, thank you Michal.
If it is going to be via OTA next week, then there's no matter.