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: Stream behaviour on connection lost and reconnect #674
Comments
Thanks for opening this @coolusaHD I'm assuming the reason why you want to receive error within |
@dshukertjr So to answer your question: No I dont use it to automatically reconnect to the stream. Therefore it would be nice if the stream would automatically reconnect and recall the Thanks for asking🙌 |
@dshukertjr Any ideas when the work on making the " |
Any updates on this ? ✌️ @dshukertjr |
Is there an ETA on this? Stream is so buggy right now it is really difficult to trust it. |
@dshukertjr But thats not the only problem. If the connection fails the heartbeat should also fail and close the stream after 2 missed heartbeats. But that doesn't trigger anything. So from my perspective I see why the flooding of errors should be prevented but without any error how can I know if my stream is still connected to the source? I really like to update to the latest version but my app cant live without that 😅 Is there any change to make the error flooding optional or even fix it that it returns at least one error? Thanks in advance. ✌️ |
I would also like to vote that at least an error message is displayed when the streams stop receiving data. Supabase and the supabase_flutter package are such great products, but with faulty realtime support in certain cases, the package is simply not ready for production applications imho. This should at least be openly communicated to the customers. Any official statement would be highly appreciated. Otherwise, I love everything about Supabase and would recommend it anytime. |
Hope quick solve this issue. I also lost connect and do not receive error from stream.onError callback. It it difficult to fix it for the app developer. |
Describe the bug
With the update to
1.2.3
, losing the connection doesn't trigger any error anymore. Also reconnecting to the internet doesn't change/trigger anything.My current code (with
v1.2.2
)Expected behavior
onData
againVersion (please complete the following information):
????????? realtime_client 1.2.2
????????? supabase_flutter 1.10.18
??? ????????? supabase 1.11.5
??? ??? ????????? functions_client 1.3.2
??? ??? ????????? gotrue 1.12.4
??? ??? ????????? postgrest 1.5.1
??? ??? ????????? realtime_client...
??? ??? ????????? storage_client 1.5.3
The text was updated successfully, but these errors were encountered: