Thanks — you're asking what the log "ignoring incoming text stream due to no handler for topic jitterBuf:false" means. I can help — a few quick clarifying questions so I give a precise answer: • Which LiveKit component or SDK logged this message (server, room service, publisher, or which client SDK: JS, iOS, Android)? • When does it appear (on join, when a participant sends data/text, intermittently)? • Are you using DataChannels / data messages or any custom text-stream/topic feature? • Any other nearby log lines you can share (a couple before/after) and the timestamp/room ID (if available)? High-level likely meaning while you gather that info: • It indicates an incoming text/data stream was received for a topic that currently has no registered handler, so the system dropped/ignored the stream. • The "jitterBuf:false" portion likely shows a flag about jitter buffering being disabled for that stream. • This is not necessarily a crash — it means the runtime didn't find code to process that specific topic/message type. If you share the component/SDK and nearby logs, I’ll give exact troubleshooting steps (how to register a handler, where topics are declared, or how to enable/inspect jitter buffering).