Skip to content
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: Realtime Issue with `WebSocketException: .... was not upgraded to websocket' in FLUTTER #211

Open
2 tasks done
moshOntong-IT opened this issue Jun 27, 2024 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@moshOntong-IT
Copy link

moshOntong-IT commented Jun 27, 2024

👟 Reproduction steps

I release my app in 'release mode' for QA test. These are the reproduce step with our QA tester:

  1. She goes to the thread page (This page has Appwrite Realtime integrate)
  2. She tries to send a thread. (When the thread has been sent then the realtime in appwrite must be triggered then her device must be receive the new event)

But she wonder why she did not receive any realtime event. So I try to go our Sentry log. Then I shocked that the Websocket issue is also occur in 'release mode'. I thought that this error was only occur on debug mode because it might be the hot reload or hot restart in flutter is the root cause.

image

👍 Expected behavior

It should not receive the WEBSOCKET issue

👎 Actual Behavior

It actually occurred to me that.

🎲 Appwrite version

Appwrite Cloud

💻 Operating system

Something else

🧱 Your Environment

No response

👀 Have you spent some time to check if this issue has been raised before?

  • I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

@moshOntong-IT moshOntong-IT added the bug Something isn't working label Jun 27, 2024
@moshOntong-IT
Copy link
Author

Sorry for mention you here @stnguyen90 . Why not putting the try in above of line 36?
image

@stnguyen90 stnguyen90 transferred this issue from appwrite/appwrite Jul 4, 2024
@lohanidamodar lohanidamodar self-assigned this Jul 8, 2024
@stnguyen90
Copy link
Contributor

@moshOntong-IT

It should not receive the WEBSOCKET issue

Can you clarify what the expected behavior is if the websocket isn't successfully connected?

Sorry for mention you here @stnguyen90 . Why not putting the try in above of line 36? image

How does this change things?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants