Fix for clients whose local clock runs ahead; no other changes since v0.165.0.
Fixes
- mtproto: start a new session after
msg_idtoo high (#1976). With the local clock ahead of the server (seen with +10 min), v0.165.0 corrected its time offset afterbad_msg_notification17 but kept the same session, whose message ids must stay increasing, so every request was refused again and the client never became ready (initConnectionfailed in a loop). Like TDLib, gotd now resets the message id generator, starts a new session and resends the request. Verified on production with the clock ±10 min off.
Full Changelog: v0.165.0...v0.165.1