-
Notifications
You must be signed in to change notification settings - Fork 61
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
"createGroup" method creates duplicate group on invoke (Javascript) #73
Comments
You can give any name to the group, even the same name. The group ID will be different. It is like two different users of your app have created groups name "Family". Regarding group 124028, it was created by you using backend API from IP address "120.29.23x.xx2" and hence you have two groups. |
The problem is it is "accidentally" created twice when |
It is because it does not have members. |
Is it possible to see whether |
124028 was created by backend API - you have passed expiry here - please check your code before posting queries. Below is the parameter you have passed.
124027 was created by some user, you must know which user. I am closing this. |
Platform: Javascript
Build date: Sep 26, 2021 12:31 GMT
I implement
createGroup
method as documented on https://mesibo.com/documentation/api/real-time-api/groups/ .My code snippet:
For example, I created a group called "ExampleGroup". On the console,
![image](https://user-images.githubusercontent.com/44438299/135213502-96887189-d9c1-4fb5-886d-6639a7453007.png)
GroupListener listener
only prints once with group ID124027
:But when I checked on Mesibo console, there are two groups with the same name with neighboring ID (
124028
and124027
) but very distant Expiry Date.124028
expires on Oct 17, 2021 07:18 PM while124027
expires on Sep 28, 2024 01:18 PM as shown below.On the other hand, when I called
getSortedProfiles
, only one "ExampleGroup" with group ID124027
appeared. I could not find group ID124028
.What do I need to do? And please let me know if you need more information. Thank you.
The text was updated successfully, but these errors were encountered: