Work offline and reconnect

VNCchat keeps a local copy of your recent conversations so you can keep reading when the connection drops, and it sends what you wrote as soon as the connection returns — without ever pretending a message was delivered when it was not.

While you are offline

When the connection drops, a banner reads Offline — showing cached messages. You can keep reading recent rooms, direct messages and people. New messages you send while offline are queued; the queue size is shown as {count} queued. You do not have to do anything — queued messages are sent automatically when the connection returns.

Reading a message’s status

Next to each message you send there is a small status marker:

Marker	Meaning
Sending…	Written to the connection, waiting for the server to confirm it.
(no marker)	Delivered — the server stored the message.
Not sent	The server permanently rejected the message; it will not be retried and a Retry action is offered.

A message that is merely slow stays Sending… — it does not flip to delivered on a guess. Not sent is terminal, so you can trust that a message showing no marker has actually arrived.

Retry a message that was not sent

Open the conversation and find the message marked Not sent.
Select Retry. VNCchat sends it again; the marker clears once the server confirms it.

Some operations are not worth retrying because there is nothing left to do — for example retracting a message that someone else already removed. VNCchat recognises these and marks them as already handled rather than retrying forever.

When your device runs low on storage

Text you queued is effectively never dropped. Only the oldest queued attachments can fall out of the queue if the device runs out of space, and you are told: Some queued items could not be saved — oldest attachments were dropped. In the desktop app the local copy is stored encrypted.

Reconnect