Streaming events have been failing silently with JSON::ParserError: Empty input (after ) at line 1, column 1 when trying to parse a streaming event containing a payload missing a leading curly brace. The client did not automatically fallback to polling. The errors were only logged in debug mode and so we weren't alerted to the issue in our production logs. This led to large delays (>30min) from the time a flag definition was updated to the time our application would pick up the change. Only new deploys of the application would pick up new changes.
We are on v8.2.0 of the SDK.
This is happening here
Example payload missing leading curly brace:
'data:{"id":"6FMuBkchWr:0:0","timestamp":1710261542842, ... data":"{\"type\":\"SPLIT_UPDATE\", ...