potentially solving disconnection on idling

packages/desktop/src/providers/SocketProvider.tsx

@@ -19,7 +19,8 @@ export function SocketProvider({ children }: { children: React.ReactNode }) {
 
   const [$ws, set$ws] = useState<Socket>(null);
 
-  const initiateSocketStabilityListeners = useCallback((socketConnection: Socket) => {
+  const initiateSocketStabilityListeners = useCallback(
+    (socketConnection: Socket) => {
       socketConnection.on('connect', () => {
         toast.success('sockets connected');
       });
@@ -27,6 +28,9 @@ export function SocketProvider({ children }: { children: React.ReactNode }) {
       socketConnection.io.on('close', () => {
         console.error('SOCKET | connection closed likely due to idling or manual disconnect');
         toast('unplugging');
+
+        socketConnection.disconnect();
+        set$ws(undefined);
       });
 
       // client-side errors
@@ -34,7 +38,9 @@ export function SocketProvider({ children }: { children: React.ReactNode }) {
         console.error(`SOCKETS | ${err.message}`);
         toast.error('sorry...this is our bad...please refresh with cmd + r');
       });
-  }, []);
+    },
+    [set$ws],
+  );
 
   useEffect(() => {
     if (!jwtToken) {