From be23322acb2866ad20a5ce9fd7cc8c51c38c9900 Mon Sep 17 00:00:00 2001
From: Nuwan <nuwanchaturanga@gmail.com>
Date: Thu, 15 Jan 2026 17:24:47 +0530
Subject: [PATCH] fix(05-jamtrack): get subscribe/unsubscribe methods from
 context correctly

Issue: "WebSocket connection not available" error
Root cause: Getting 'server' object instead of subscribe/unsubscribe methods

Fix: Extract subscribe/unsubscribe directly from useJamServerContext()
and create jamServer object with those methods for the thunks.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
---
 jam-ui/src/components/client/JKSessionJamTrackPlayer.js | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/jam-ui/src/components/client/JKSessionJamTrackPlayer.js b/jam-ui/src/components/client/JKSessionJamTrackPlayer.js
index 193534d76..0623459b3 100644
--- a/jam-ui/src/components/client/JKSessionJamTrackPlayer.js
+++ b/jam-ui/src/components/client/JKSessionJamTrackPlayer.js
@@ -38,7 +38,13 @@ const JKSessionJamTrackPlayer = ({
   const [selectedMixdownId, setSelectedMixdownId] = useState(initialMixdownId);
 
   // Context
-  const { server: jamServer } = useJamServerContext();
+  const { subscribe, unsubscribe } = useJamServerContext();
+
+  // Create jamServer object with subscribe/unsubscribe for thunks
+  const jamServer = useMemo(() => ({
+    subscribe,
+    unsubscribe
+  }), [subscribe, unsubscribe]);
 
   // Redux state
   const dispatch = useDispatch();