WebSocket connection [...] failed: Could not decode a text frame as UTF-8.
One of our clients can't load report data because of this error we're receiving from WebSocket, which happens after we call getHyperCubeData(). We've done our best to verify that all of our input parquet and CSV files have utf-8 encoding, and our qlik app reloads without any issue. We can't sanitize the response from Qlik because the error happens at the WebSocket level, before we'd have a chance to intercept it.
Is this something that should be encoded on the Qlik side before sending the data over WebSocket? Is this something that can be influenced by a configuration or setting somewhere? This is fairly urgent for us, because this client can't access their reports right now.
All messages coming from the engine are UTF-8 encoded. My best guess here is that there is some value in your file that is corrupted or contains some unexpected value. Can you identify which field the problem comes from? If you haven't done so yet, I'd recommend that you write a small program that simply tries does GetHyperCubeData one field at a time, and then see which one causes it to fail. Then look at what's special about that particular field.
