-
Notifications
You must be signed in to change notification settings - Fork 115
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 Report: Event is triggered multiple times when subscribing to multiple (different) channels #55
Comments
Did you app hot-reload? That might cause the issue, hot-reload can create unexpected behavior with the websockets even when there is only one subscription. Can you try with complete hot restart and check if you still have the issue? |
@lohanidamodar it has still the same problem. It looks like it doesnt close the previous subscription, when added a new channel to the subcription. |
@Invisibleshroud ok, will test and let you know what I find. |
@Invisibleshroud hey, this only happens to me when I have either hot reloaded or hot restarted. In both cases the subscription is not closed so each time I hot restart or hot-reload, new subscription is added on top of that, so I get multiple events. |
@Invisibleshroud This seems to be a issue with the Flutter web itself on hot restart this happens on normal web-socket connection as well. This is not solvable at the moment, check this issue and comments there. |
👟 Reproduction steps
Create
,Update
&Delete
events are being triggered multiple times when subscribed to multiple channels.In the example below there are 2 create events when a userimage is added.
First subscription:
Second subscription:
👍 Expected behavior
There should be only 1 trigger event per event.
👎 Actual Behavior
The debug console shows the following:
🎲 Appwrite version
Version 4.0.x
💻 Operating system
Linux
🧱 Your Environment
No response
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: