[Bug, UX/UI] Incorrect display of unavailable attachments in chat

[al-onyxprotocol]

Summary

When a chat includes messages with unavailable attachments, they are displayed incorrectly.

Steps to reproduce

1. Open a chat containing messages with unavailable attachments (chat with ..55297 in test account)
2. Tap on the red circle with arrow icon near the message
3. Observe the incorrect display/behavior

Expected behavior

• On tap, Icon behavior should follow this sequence:
  • Red circle with arrow → Clock (downloading) → Red circle with arrow (if download fails again)
• Show a temporary popup (Popup should disappear automatically after a short delay) if downloading fails again
  • Two kinds of message depending whether all files unavailable or some files:
    • All files
      • Files are not currently accessible
      • Файлы недоступны
    • Some files
      • Some files are not currently accessible
      • Некоторые файлы недоступны
  • Style:

• Add vibration feedback (“Error” type)

Actual behavior

On "Unavailable icon" tap, Nothing happen

Screenshots or videos

Environment

Platform: iOS app
Version: Build 3.11.0 (20)

[Lainaaa]

@al-onyxprotocol Thanks for the detailed explanation.

I tried to fix this bug, but noticed that the behavior is expected.

Our file have state as follow:

    case uploading
    case downloading
    case success
    case failed
    case unableToDownload
    case needToDownload(failed: Bool)

In your particular example it has unableToDownload state, which we assign if file nonce is empty.

So I would say in this I think we still not able to download it, right? So maybe we can just show an pop-up for user that file was damaged and is not possible to download it instaed of making flow that you described earlier? What do you think about it?

[al-onyxprotocol]

@Lainaaa

So I would say in this I think we still not able to download it, right?

Right.

So maybe we can just show an pop-up for user that file was damaged and is not possible to download it instaed of making flow that you described earlier?

Yes and no.

This task is to fix UX/UI, not the actual re-download flow, so yes, you are right.

But if we already have "re-download" or "re-try" flow that will show UI "Red circle with arrow → Clock (downloading) → Red circle with arrow (if download fails again)", we can use it. There is no problem that the app will actually send another download request.

"Re-download" scenario is useful, and can be used in different cases. This way is recommended.
Imagine that unableToDownload state was set because of IPFS node error or connection error. It means user will not get the file anymore, but it actually can be fetched.

If there is no "re-download" flow yet, and coding it requires significant efforts, we can choose only UI update (popup).

Please use popup style, texts and vibro as described in the task.