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

Incoming messages are not coming after a re-connection due to network change or connection reset #49

Closed
Okdone opened this issue May 20, 2020 · 2 comments
Assignees
Labels
alpha bug Something isn't working

Comments

@Okdone
Copy link

Okdone commented May 20, 2020

I am testing your Flutter Chat SDK "0.2.1-alpha+3" with offline capability which is critical for our use case. Reported a problem via GitHub page 2 days back and thanks for fixing the database exception quickly.

After trying the latest Alpha build one problem I have observed is incoming messages are not coming after a re-connection due to network change or connection reset, though outgoing messages are going after re-connection. If user manually refreshes the chats landing page by pull refresh, messages are being pulled from server by calling an API but until that is done manually messages are noting getting delivered to the client. What can we do to ensure message sent receive happens automatically as soon as server connection is established.

Also please let us know if we should report this kind of issues via support or should we post it on GitHub page, we will follow as you advise.

Steps to reproduce issue:

  1. Login in app
  2. Send messages
  3. Turn off internet connectivity
  4. Sent some messages from other device
  5. Again turn on internet connectivity
    Then that message is not received until we manually refresh the lending page or re-open app.
@imtoori imtoori self-assigned this May 20, 2020
@imtoori imtoori added alpha bug Something isn't working labels May 20, 2020
@imtoori
Copy link
Contributor

imtoori commented May 20, 2020

Thanks for the reporting, I think this is a good place to report issues so far

At the moment we are developing a backend endpoint dedicated to resync the application data after reconnection, but that can take some time before landing in production.
I think for the moment we can just refresh the channels manually using the queryChannels endpoint.
Let me check it, if that works as expected I'll release another version of the low level client

@imtoori
Copy link
Contributor

imtoori commented May 20, 2020

@Okdone I've just released a new version
It should work as expected. I think this is a good compromise as far as we are working on a more specific endpoint

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
alpha bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants