You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: