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

Chat status don't change from sent to delivered if sender syncs after sometimes. #568

Closed
Assadbintahir opened this issue Mar 27, 2017 · 4 comments

Comments

@Assadbintahir
Copy link

Steps:

1- Turn off internet on android device.
2- Send some messages from iOS to android device.
3- Message status will be sent.
4- Now switch off internet on iOS device.
5- Switch on internet on android device.
6- messages will be received via sync. Don't see them.
7- turn on internet on iOS device.
8- Status will always remain sent and never change to delivered.

@sumairasaeed
Copy link
Contributor

Worked to Debug this and it found that the status list was big so the push size exceeded limit. It missed the response push for status update "delivered"
I have opened server side issue for solving payload size limit issue.
It runs fine in normal case when status list is small.
We will test it again after payload size issue is resolved Cloudkibo/CloudKibo#506

@jekram
Copy link
Contributor

jekram commented Mar 29, 2017

@sumairasaeed I have asked this question on another thread Message Order disturbed when received pending messages from iOS #561

If you have sent the message via Rest why are you waiting for notification? What is notification tell us more than the Rest status?

@sumairasaeed
Copy link
Contributor

Sir, when we successfully send message, we update status to "sent". But when receiver fetches it successfuly, it sends push of "delivered" to other side. This has been fixed now

@jekram
Copy link
Contributor

jekram commented Apr 6, 2017

Great news!!!! Good work

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants