Updates not fetched after re-logging in

Bug #1375875 reported by Michał Karnicki
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Telegram app
Fix Released
High
Penk Chen

Bug Description

Steps to repro:
1. log out
2. make some Telegram activity
3. log back in

Result:
The app does not update to the most recent state.

Tags: cqa-verified

Related branches

Changed in libqtelegram:
importance: Critical → High
Michał Karnicki (karni)
Changed in libqtelegram:
importance: High → Critical
Michał Karnicki (karni)
Changed in libqtelegram:
milestone: none → m5-beta2
Changed in libqtelegram:
importance: Critical → High
Michał Karnicki (karni)
Changed in libqtelegram:
milestone: m5 → none
Michał Karnicki (karni)
Changed in libqtelegram:
assignee: Roberto Mier Escandón (rmescandon) → Penk Chen (penk)
Penk Chen (penk)
Changed in libqtelegram:
status: Confirmed → In Progress
Revision history for this message
Penk Chen (penk) wrote :

Like @rmescandon mentioned, when after re-login, seq will be set to 0 on server, so the first updatesGetDifference is TL_UpdatesDifferenceEmpty, and message before login never got updated.

Trying to handle this in Data::onUpdatesGetStateAnswer()

Changed in libqtelegram:
status: In Progress → Fix Committed
Michał Karnicki (karni)
Changed in libqtelegram:
milestone: none → m8
Revision history for this message
Jonathan Cave (jocave) wrote :

Verified version 0.8.12.73

tags: added: cqa-verified
Michał Karnicki (karni)
Changed in libqtelegram:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.