You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 12, 2022. It is now read-only.
When the application is already launched, the client manages properly the presence : it detects that it is a catchup but when it is a cold start, it seems that the client send an online event (whereas it should not).
The text was updated successfully, but these errors were encountered:
ylecollen
changed the title
Send online presence when the client is cols started by a notification
Send online presence when the client is cold started by a notification
Jun 3, 2016
ylecollen
changed the title
Send online presence when the client is cold started by a notification
Send an online presence when the client is cold started by a notification
Jun 6, 2016
-> The client used to never go back to offline after performing the catchup so the client was always seen as online.
With the issue 167 fix, the client triggers an "online" event but an "offline" event is quickly sent when the catchup is done. So, this fix should be enough.
When the application is already launched, the client manages properly the presence : it detects that it is a catchup but when it is a cold start, it seems that the client send an online event (whereas it should not).
The text was updated successfully, but these errors were encountered: