Health Check: Connection statuses

[adamantmm]

See also: Health Check: Algorithm, General Description

Connection Statuses

There are three connection statuses related to receiving and sending messages:

1. No internet connection

• Reported by the OS (no network, Wi-Fi, etc.)
• In Health-check we assume that No active nodes may actually mean No internet connection

2. No active/available ADM nodes

(same for coins/services: No active BTC services)

• At least one ADM node is enabled
• No nodes are in Active status
• Optional: Unsupported nodes do not count

3. No enabled ADM nodes

(same for coins/services: No enabled BTC services)

• A user has disabled all nodes
• Optional: Unsupported nodes do not count. There may be nodes in Unsupported status, but the status is still No enabled nodes.

Priority of Checks

1. No internet connection
2. No active/available ADM nodes
3. No enabled ADM nodes

Specific cases

General snackbar

• No internet connection Yes
• No active/available ADM nodes No
• No enabled ADM nodes No

• Type: persistent (show until a user closes it or connection restores)
• Vibro: Attention

In-chat warning popup

• No internet connection No
• No active/available ADM nodes No
• No enabled ADM nodes Yes (Connection is alive and No available ADM nodes and User has at least one manually disabled/unchecked node)

• Type: persistent (show until a user closes it or connection restores)
• Vibro: Attention

General updating spinner

(~header, meaning: data/messages are not actual)

• Yes for all connection statuses
• Including the Delegates screen (delegates are not updated)
• Including the Wallets screen (wallets are not updated)
• Including the (any) nodes screen (nodes are not updated)

• Type: persistent (show until connection restores)
• Vibro: No

See also: Health Check: General updating spinner

Data Loading spinner

Loading chat list spinner/ Specific chat spinner/ ADM tx list spinner.

• Yes for all connection statuses

Show on user request, e.g.:

• A user enters ADM tx list screen and the app tries to load txs
• A user scrolls the chat list and the app tries to load new chats
• A user enters specific chat and the app doesn’t have it, tries to load messages
• A user scrolls specific chat and the app tries to load messages
• A user enters Vote for delegates screen and the app tries to load delegates

Spinner is shown until data is updated.

• Type: persistent (show until connection restores)
• Vibro: No

Sending a new message or file

• Common for all connection statuses

No connection? Show a message in-chat with Pending tx status.

When do we switch Pending status to Failed?

• For messages and for files
• Wallets: Message sending timeouts

Note: We implemented two timeouts:

• Sending a regular message
• Sending a message with attachments. Note: this timeout refers not to uploading files (e.g., to IPFS), but to sending an ADM message with already uploaded files.

Sending in-chat ADM or other crypto

Also applies to: Sending ADM coins directly.

• Common for all connection statuses
• Prohibit sending
• Snackbar (temporary type)

For Sending non-ADM coins directly (from Account ⟶ Coin ⟶ Send):

• Don’t check ADM nodes availability for coin transfers

• Type: temporary (auto hide in a few seconds)
• Vibro: Warning

See also: In-chat Crypto transfer scenario (TODO)

Starting a new chat

• Common for all connection statuses
• Verify the ADM address is probably correct locally
• Open a new chat at once with no requests
• Show welcome in-chat special message
• If we have the public key locally, no additional messages
• If we request the public key from a node, show additional in-chat message with a spinner

• For No enabled ADM nodes additionally: Additional In-chat warning popup

On connection restore

Finish pending requests. E.g., send pending messages, update where spinners.

Login with passphrase

• No internet connection and No active/available ADM nodes Stay on the Login screen + Show snackbar/popup
• No enabled ADM nodes Go to the ADM nodes screen + Show snackbar/popup

• Type: temporary (auto hide in a few seconds)
• Vibro: Warning

Login by password/Biometrics

• Common for all connection statuses
• Log in as usual with no delay and requests, open the Chats tab
• Show locally stored messages and chats
• The General updating spinner will show that the data is not actual, And snackbar "No connection"

[dev-adamant-im]

Thanks for outlining the statuses so clearly.
I like the priority order — it makes sense to first rule out No internet, then check for No active nodes, and finally handle the No enabled nodes case.
This structure should also help avoid user and developer confusion (e.g., when “no internet” and “no active nodes” might look similar). It keeps both app logic and UX consistent across ADM nodes, coins, and services.