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
In certain situations, the initial presence is sent with show=away and never becomes fully available, even after opening the chat window. This is probably due to the recently introduced mFirstStart.
Found cause: when the message center restarts and reference counting is zero (e.g. out of the app), show=away is sent at login while the state is still "active". This will be rectified after an inactive/active cycle, but until then the information sent is wrong. Although it should also be fixed when HOLDing to the message center, however because state is active, no available presence will be sent.
The text was updated successfully, but these errors were encountered:
In certain situations, the initial presence is sent with show=away and never becomes fully available, even after opening the chat window. This is probably due to the recently introduced
mFirstStart
.Found cause: when the message center restarts and reference counting is zero (e.g. out of the app), show=away is sent at login while the state is still "active". This will be rectified after an inactive/active cycle, but until then the information sent is wrong. Although it should also be fixed when HOLDing to the message center, however because state is active, no available presence will be sent.
The text was updated successfully, but these errors were encountered: