engaging-computing / engaging-computing/MYR-backend

Mismatch socket-io version between frontend and backend cause connection issue between client and server

Open
#325 0 comments 0 reactions 1 assignee Claimed by @Jlu18 View on GitHub
bug High Priority
Dominant language
JavaScript
Stars
0
Forks
12
PR merge metrics
No merged PRs in 30d

Description

Currently the frontend has "socket.io-client" running on version ^4.4.1, but the backend socket.io server is running with version ^2.3.0. This mismatch version between client and server cause the client not able to communicate to the server via socket (Go to production and open network tab on inspector, notice how socket.io keep trying to connecting and disconnecting from the server ).

All the feature using socket.io are currently unavailable (ie. notifying devices when scene is updated).

To fix this, we have to bump the version of socket.io to match with the client. But to do so, migration from 2.x to 4.x must be done. [migration guide](https://socket.io/docs/v4/migrating-from-2-x-to-3-0/)

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.