search

cometchat / chat-sdk-javascript

Voice & Video Calling and Text Chat SDK for JavaScript/Web
Other
30 stars 24 forks source link

Leave Group - user leaving the group is not notified via GroupListener #44

Closed rshubbard closed 4 years ago

rshubbard commented 5 years ago

When a user leaves the group via https://prodocs.cometchat.com/v2.0/reference#user-leavegroup, they do not receive the action via CometChat.GroupListener. Other users see the action message via onGroupMemberLeft but not the user who is leaving the group. If the user does a subsequent call to fetchPrevious() they do see the action message { action: "left" } but there is currently no active listener event to notify that the user has left the group.

I would expect the user leaving the group to also receive a onGroupMemberLeft via the CometChat.GroupListener to let them know they have been removed from the group.

ketanyekale commented 5 years ago

Thank you for reporting this issue. The fix will be made live early next week.

rshubbard commented 5 years ago

This is still broken on my end. When a user is removed from a group they are not receiving the GroupListener callback.

Robert Hubbard CTO Mobile: 919-606-0799 REVERBNATION why we rock https://www.youtube.com/watch?v=MHPz0zUNPPc

On Thu, Oct 17, 2019 at 4:44 PM ketan.cometchat notifications@github.com wrote:

The issue has been fixed. Please check and confirm so that we can close the issue.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/cometchat-pro/javascript-chat-sdk/issues/44?email_source=notifications&email_token=AACK46JIA7NIN6OUY45AZ3DQPDFDDA5CNFSM4JA7JFKKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBROZXI#issuecomment-543354077, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACK46LOLA7HDWOK4RJE6STQPDFDDANCNFSM4JA7JFKA .

mayur-bhandari commented 4 years ago

Hello @rshubbard , we have released a new SDK v2.0.0-beta10 and have fixed this issue. Can you please check it on your end and let us know if this issue is resolved?

mayur-bhandari commented 4 years ago

This issue has been fixed in v2.0.0-beta10. If the issue still persist, please feel free to re open the issue.