Health Check: General updating spinner

[adamantmm]

See also: Health Check: Algorithm, General Description

How to Check if the “Chats are Loading” Spinner Should Be Shown in the Header

The absence of a spinner in the header guarantees to the user that they are seeing the latest list of chats and messages.

Algorithm

1. Show spinner in any of the three connection absence statuses:

   • No internet connection
   • No active ADM nodes
   • No enabled ADM nodes

2. If connection and active nodes exist — check further:

   • When fresh messages are received (request /chats/get?fromHeight= returned the newest messages, meaning no newer ones exist), save in the store the timestamp chatActualUntil

const chatsActualUntil = adamant.toTimestamp(nodeTimestamp) + INTERVAL + CHAT_ACTUALITY_BUFFER_MS

• INTERVAL = polling interval for new chats over REST (may differ depending on whether a socket connection is available)

INTERVAL: (state, getters, rootState) => {
  return rootState.options.useSocketConnection ? SOCKET_ENABLED_TIMEOUT : SOCKET_DISABLED_TIMEOUT
},

3. Subscriptions:

   • Chat and Chat List screens observe chatActualUntil
   • They also subscribe to the hook chatActual = chatActualUntil > currentTime
   • This hook runs every 500 ms to trigger the spinner even if chatActualUntil has not changed (no new messages)

4. Show spinner if:

   • No internet connection, or
   • No nodes online, or
   • !chatActual

5. On restore from background:

   • No tweaks needed — still rely on chatActualUntil
   • If the device time > chat validity timestamp, the user will see the spinner

Worst Case

If the connection is lost, the user may not see the spinner (and mistakenly think everything is up-to-date) for a maximum of:
INTERVAL + CHAT_ACTUALITY_BUFFER_MS seconds.