You'll notice
Useful3 Signal2
A malformed message from a worker or remote session is dropped instead of crashing your client.
What's wrong with this entry?
Anonymous. No account, no email.
What
Three guards land together so a malformed or handler-crashing message is dropped rather than crashing or producing an empty error.
Details
- A worker control response with a non-string or unrecognized error now yields a described Error instead of
Error(undefined) - Every incoming message in the SDK and sessions client goes through a wrapper that catches handler exceptions, logs the dropped message's type and subtype, continues, and reports
remote_connect_frame_handler_threw - Thin-client control replies are validated against their schema; a mismatch returns null and logs the first schema problem instead of the payload being trusted
- History prefetch converts each message in its own try/catch and skips the ones that fail
Evidence
Malformed control_response from worker
Strings lifted out of the shipped bundle, so the claim above can be checked against them.