Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: could not receive all messages in a group #921

Closed
webratte opened this issue Jan 2, 2017 · 3 comments
Closed

Bug: could not receive all messages in a group #921

webratte opened this issue Jan 2, 2017 · 3 comments
Assignees
Labels
invalid This doesn't seem right

Comments

@webratte
Copy link
Contributor

webratte commented Jan 2, 2017

Expected behavior

All group members should receive all messages

Actual behavior

In a group with 3 members one member did not receive one message. It's not the first message in this group. All following messages will received from all members.

Steps to reproduce

Currently I have not idea how to reproduce. I will try to find out what happens.
Maybe other people run into the same issue and can report.

Environment

Kontalk version: all have the same 4.0.0 Beta 5 (217)
Android version: 6.0.1

Device model: Sender and receiver who has not received the message: Sony Xperia M4 Aqua

Logs

No logs because it's to late :-(

@webratte
Copy link
Contributor Author

webratte commented Jan 2, 2017

BTW. It would be good if I would have the second check mark if all members received all messages.
So I can be sure there is no info is lost.

@CrimsonFork
Copy link
Contributor

I'm not sure how this is possible but i had a double tick in a group chat once... (beta4)

@daniele-athome
Copy link
Member

Delivery confirmation is currently disabled in groups because it needs to account for multiple users, that is, only when all users have received the message it should be double-ticked - and that is not implemented yet.

As for your issue @webratte, I've been trying for months to increase the reliability of message delivery in Tigase, a great deal of progress was made recently, still there seems to be problems.
It's very hard to debug this issue because it happens only during severe network problems (e.g. connecting and disconnecting continuously because of bad network coverage), and it's hard to produce such problems in a controlled environment. I'll do some more tests on the server, but for now I'm closing this since the problem is not with the Android client. I've opened kontalk/tigase-extension#74.

@daniele-athome daniele-athome self-assigned this Jan 4, 2017
@daniele-athome daniele-athome added the invalid This doesn't seem right label Jan 4, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
invalid This doesn't seem right
Projects
None yet
Development

No branches or pull requests

3 participants