-
Notifications
You must be signed in to change notification settings - Fork 0
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
Bug: Weird chat behavior #617
Comments
@OrAbramovich I'll need your help here. |
hi @idanyadgar |
@alonttal Same. |
Probably caused by a merge issue - there were 2 handlers for each message. Anyway - added another check (to != current user). #617
Hi @idanyadgar , Reproduced on my machine. Probably caused by a merge issue - there were 2 handlers for each message. Anyway - added another check (to != current user) - I pushed the changes to private-messaging branch (only). Can you verify it? (pay attention! checking it on Azure requires a merge with your branch and with the master since the Azure site uses the cloud db that contains new types of notifications, etc. hence - you can get errors with your branch because your back-end is not familiar with those types). Shabat Shalom. |
Yes, that was it. |
Messages sent from A to B appear once from A point of view but are received 4 times at B and are not saved in the DB (on refresh we don't see them).
The text was updated successfully, but these errors were encountered: