That popup message is coming with updateServiceNotification from Telegram backend.
[23:58:28.811 01-0001754] (dc:2) Recv: { core_message
msg_id: 6753703395900790785 [LONG],
seq_no: 85 [INT],
bytes: 184 [INT],
body: { updates
updates: [ vector<0x0>
{ updateServiceNotification
flags: 1 [INT],
popup: YES [ BY BIT 0 IN FIELD flags ],
inbox_date: [ SKIPPED BY BIT 1 IN FIELD flags ],
type: "API_ERROR_UPDATE_UNOFFICIAL" [STRING],
message: "Error. Please update your app to the latest version or switch to the official version of Telegram." [STRING],
media: { messageMediaEmpty },
entities: [ vector<0x0> ],
},
],
users: [ vector<0x0> ],
chats: [ vector<0x0> ],
date: 1572469107 [INT],
seq: 1774 [INT],
},
}
I believe we are able to backport a new version to Bionic Beaver. At least v1.8.15 is successfully compiled against Qt 5.9.5 and FFmpeg 3.4.6. Moreover, we could provide a new version via the bionic-updates repository like Firefox or Thunderbird get updates
That popup message is coming with updateServiceNo tification from Telegram backend.
[23:58:28.811 01-0001754] (dc:2) Recv: { core_message tification UPDATE_ UNOFFICIAL" [STRING],
msg_id: 6753703395900790785 [LONG],
seq_no: 85 [INT],
bytes: 184 [INT],
body: { updates
updates: [ vector<0x0>
{ updateServiceNo
flags: 1 [INT],
popup: YES [ BY BIT 0 IN FIELD flags ],
inbox_date: [ SKIPPED BY BIT 1 IN FIELD flags ],
type: "API_ERROR_
message: "Error. Please update your app to the latest version or switch to the official version of Telegram." [STRING],
media: { messageMediaEmpty },
entities: [ vector<0x0> ],
},
],
users: [ vector<0x0> ],
chats: [ vector<0x0> ],
date: 1572469107 [INT],
seq: 1774 [INT],
},
}
I believe we are able to backport a new version to Bionic Beaver. At least v1.8.15 is successfully compiled against Qt 5.9.5 and FFmpeg 3.4.6. Moreover, we could provide a new version via the bionic-updates repository like Firefox or Thunderbird get updates