socket.data.user is undefined after login when socket connected before auth (autoConnect: true)
✅SolvedGeneral Wasp
The Problem
I'm using Wasp with
autoConnect: trueThe issue: The socket connects automatically when the app loads (before login). After the user logs in via HTTP,
socket.data.userundefinedFlow
1. User visits app → App mounts → Socket auto-connects (user NOT logged in yet)
2. User goes to
/login3. User is redirected through the app → Uses features that need WebSocket
4. Client emits event to server
5. Server checks
socket.data.user
Server Logs
What Fixes It
If the user refreshes the page after login, the socket reconnects and NOW has
socket.data.userMy Understanding
From the docs:
"Wasp automatically injects the JWT into the connection, and if present/valid, the server adds a user to the socket."
This injection happens only at connection time. If the socket connects before login (which happens with
autoConnect: trueQuestions
1. Is this expected behavior? Should
socket.data.user2. What's the recommended pattern for apps with login flows? Should I:
- Force reconnect after login? (
socket.disconnect()socket.connect()- Use
autoConnect: false- Something else?
3. Is there a built-in way to refresh socket credentials without a full reconnect?
