Wire-android: Delivered tag

[Da0012]

The problem

When I send to my friend messages when he's ONLY on his smartphone,that messages don't have "delivered tag".

Environment

• Wire version that exhibits the issue: 442
• Last Wire version that did not exhibit the issue (if applicable):
• Android OS version used to run Wire:6.0.1
• Is this a custom firmware or a stock one:custom
• Mobile phone model/manufacturer:Samsung SM-G532M
• Mobile network type (EDGE/LTE/Wi-Fi/Offline):LTE/WIFI

Details

If he restart the Smarphone, this problem will be fixed.But this happens again at a random moment.

Link to Debug logs

i will send the email

Screenshots

[TubaOrNotTuba]

This has been a problem for a year or two. Sent/Delivered tags work about 50% of the time. They've never addressed it. They need a 3rd tag, viewed, but they've not added that either.

[TubaOrNotTuba]

I was able to solve this with someone I was chatting with. We'd been chatting all day and dozens of msgs I'd sent just said "Sent" while I knew they'd been received and replied to. I had them Force Stop Wire and when it was reopened all the statuses changed to "Delivered". Clearly the code exists to do this properly, but it gets hung. Maybe that'll help hunt this down.

Now if we could get a "Seen" or "Read" notification.

[Da0012]

Yes, when my friend restart his smartphone all messages changes to "delivered".

[Da0012]

The bug persists on 3.14.628,I waited an hour and that was fixed.
No reboot,No force stop.

[TubaOrNotTuba]

I concur. 3.14.628. If the messages say "sent" but the recipient has clearly received them, the only two fixes are to either force stop Wire or reboot the phone. Very annoying.

[Da0012]

do you have this bug?
https://github.com/wireapp/wire-android/issues/1556

[TubaOrNotTuba]

It looks like the problem may be related to IP addressing. If you start a conversation on one network and move to another network with a different IP address this happens immediately. Rebooting or force stopping on the new network solves it until you move again.

[Da0012]

I've noticed this between two desktop wire (without smartphones)