ReadonlyclientOptionaldateOptionalkeepOptionaloldOptionaloldOptionaloldOptionaloldReadonlyparamsOptionalptsOptionalqtsOptionalseqOptionalupdates: TypeUpdatesOptionalfallbackPts: numberOptionalpts: numberADVANCED
Notify the updates manager that some channel was "closed". Basically the opposite of notifyChannelOpened. This is a low-level method, prefer using closeChat instead.
Bare channel ID
true if the chat was closed for the last time, false otherwise
ADVANCED
Notify the updates manager that some channel was "opened". Channel difference for "opened" channels will be fetched on a regular basis. This is a low-level method, prefer using openChat instead.
Channel must be resolve-able with resolvePeer method (i.e. be in cache);
base chat PTS must either be passed (e.g. from Dialog), or cached in storage.
Bare ID of the channel
Optionalpts: numberPTS of the channel, if known (e.g. from Dialog)
true if the channel was opened for the first time, false if it is already opened
Start updates loop.
You must first call enableUpdatesProcessing to use this method.
It is recommended to use this method in callback to start, or otherwise make sure the user is logged in.
Note: If you are using UpdatesManagerParams.catchUp option, catching up will be done in background, you can't await it. Instead, listen for the
updatingandconnectedconnection state events.
ADVANCED
Manually stop updates loop. Usually done automatically when stopping the client with close
Catch up with the server by loading missed updates. .