-
Notifications
You must be signed in to change notification settings - Fork 30
🐛 Bug Report: Realtime doesnt get connected #47
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
Comments
I came up with a workaround for this and it works well with Realtime connections. The trick is to install both packages and conditionally use one over the other depending on the platform. The RN SDK currently doesn't work on the web for real-time connections. It seems like it fails on chrome, but works on Firefox. The Web SDK works on chrome, Firefox (tested desktop and mobile chrome), but it won't work with the expo go app (tested on android). So conditionally use both based on the platform as a workaround
|
@nmpereira hi there, is this issue still relevant with the latest release of the sdk? we recently added realtime ping pong messages to tackle the realtime issues |
I've since moved away from appwrite for my current project and also added a workaround to make it work. I don't have a way to test it at the moment unless you really need me to. |
👟 Reproduction steps
With expo react-native, when i try using realtime connection, it fails on chrome. It seems to work on firefox.
The connection gets instantly disconnected and it tries reconnecting, but fails over and over (Chrome)
Use the below code to test:
👍 Expected behavior
When using the react-native-appwrite sdk, i expect it to work on android, apple, and Web (all browsers)
👎 Actual Behavior
It doesnt work on Chrome web browser, but works on firefox
🎲 Appwrite version
Version 0.7.x
💻 Operating system
MacOS
🧱 Your Environment
Using cloud appwrite, with react native expo.
Also tried with vite react and it works fine since it uses "appwrite" sdk, when switching to "react-native-appwrite", it fails
👀 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: