The error "cannot publish track when not connected" occurs when you try to publish a track while the LiveKit engine is not fully connected. This often happens if you attempt to publish tracks immediately after disconnecting and reconnecting, before the connection is fully re-established. To resolve this: • Wait for the Reconnected event before publishing new tracks after a disconnect/reconnect cycle. • Check the connection state and ensure the engine is fully connected before attempting to publish tracks. • Let LiveKit's automatic track republishing handle existing tracks during reconnection. You do not need to manually republish tracks unless you are publishing new ones. Implementing event handling for connection state changes will help avoid this error and ensure smooth reconnections. Sources: src/room/participant/LocalParticipant.ts | Connecting to LiveKit | LiveKit Docs