[Story] UTD events display incorrect encryption info in their UI

[bmarty]

Description

• As a user
• I do not want to see the crypto information if the message cannot be decrypted
• So that the UI is more user firendly

Example: in the screen below, just render the timestamp of message, not in read, not with a picto:

This need a product confirmation (@mxandreas ) and a confirmation from the crypto team.

The change can occur in the application (iOS and Android), this does not necessarily require changes in the SDK.

Acceptance criteria

• When a message cannot be decrypted, no information about the crypto status is displayed.

Leads

• Tech: @bmarty
• Design: NA

Size estimate

None

Dependencies

• None

Out of scope

• Nothing

Open questions

Questions

Beta Give feedback

No tasks being tracked yet.

Subtasks

Android

Beta Give feedback

No tasks being tracked yet.

iOS

Beta Give feedback

No tasks being tracked yet.

Rust

Beta Give feedback

No tasks being tracked yet.

Other

Beta Give feedback

No tasks being tracked yet.

Sign-off

Android

• Design sign-off on completion
• QA sign-off on completion
• Product sign-off on completion

iOS

• Design sign-off on completion
• QA sign-off on completion
• Product sign-off on completion

[jmartinesp]

Just to clarify:

I do not want to see the crypto information if the message cannot be decrypted

This is because the encryption info is incorrect. When you tap on the red lock icon the UI says 'this message is not encrypted', but the message is encrypted, it just couldn't be decrypted.

[mxandreas]

I found a better way to ask a clarifying question, it is more of a confirmation:

1. If I read the user story in the description, it sounds like minor UX enhancement towards user-friendliness.
2. If I read the title of the ticket, it sounds like something is incorrect or heavily misleading - e.g like @jmartinesp mentioned above. We show that message was not encrypted while in fact it was (we just could not decrypt).

If it is 2. then it is worth responding to "now". If I look at this case in isolation - e.g. then the suggested UI makes sense (e.g. just a timestamp without any warning side or red).