Again, the message is not sent

Describe your environment

Please specify the following:

• Jami version: 20240206-01
• Device model: Motorola Macro
• Android version: Android 10
• What build you are using: F-droid

Steps to reproduce

• Can you reproduce the bug: occasionally
• Steps:
  1. Send a text message to a contact 2. That contact shown as online (green dot) 3. That contact does not receive the message

Additional information

I could not understand what is the purpose of Online dot. Does it mean that the contact has Jami running and reachable? If yes why the contact does not receive my message? Also my local desktop version does not show that that message was sent from Android, there is not history.

Desktop:

Contact shown as online:

Android:

Contact shown as online:

The contact didn't receive that last message. He is using Android.

Is there any way to produce a bug report? What is going on with that message?

It is no first time. It is happening constantly and it is so annoying.

Please fix it.

Related issues: #1379 (closed), #1378 (moved)

changed the description

Could not understand what is the purpose of Online dot. Does it mean that the contact has Jami running and reachable?

Yes, it means the contact is reachable.

Edit: see Sébastien's answer below

Really? jami-project#393 (comment 35130)

I could not understand what is the purpose of Online dot. Does it mean that the contact has Jami running and reachable?

No it's not. Generally in applications (e.g. Whatsapp, Monal XMPP or other messenger where there is a green dot), you can consider a online dot like "seems to be connected". For more explanations, https://forum.jami.net/t/synchronisations-notifications-dht-point-vert/2386/6 (French) - https://github.com/monal-im/Monal/wiki/FAQ---Frequently-Asked-Questions

Basically for Jami, it's just that the device certificate is found on the DHT. It doesn't mean you have a p2p connection ready with this peer. So, basically if you send a message, some reason on failures can be:

• Incorrect firewall
• Other peer got no internet (the presence got a TTL of 10min without proxy, several hours with push/proxy due to the fact that mobile will kill the app anyway but push may work)
• Push notifications is not delivered
• p2p connection fails
• App is killed to soon
• Message is rejected by the app
• A deadlock on one side or the other side.
• etc.

Without log/details it's pretty irrelevant to try to reproduce/give a random reason. https://docs.jami.net/en_US/user/bug-report-guide.html#bug-report-guide can help to produce a better report.

But for now, with the information given here, I can't really say any reason. With the logs of your peer, I may be able to.

Or the other peer (accidentally) blocked you / removed you from the contact list?

(The green dot would still be visible?)

No, definitely not blocked, we are in constant contact with each other, so it is not possible.

added wait-for-answer label

We implemented a message status indicator: https://jami.net/improved-reliability-presence-and-message-status/

This would help to understand what worked and what didn't. See also more info about presence.

Next version should improve this too.

Mass changes in two months and no clear scenario.

closed