WebSocket error during handshake when using Proxyman

Description

I am debugging an Android app which opens a webview, and the webview initiates a websocket connection. I have no control over the webview or the websocket connection code.

The webview is able to send parsed messages from websocket to native android code. I'd like to be able to modify this response using map remote to a locally hosted websocket server.

When I open the webview in chrome's inspector, the following happens

• If Proxy is enabled and SSL Proxy for the domain is enabled, Chrome report an error Error during WebSocket handshake: 'Sec-WebSocket-Protocol' header must not appear more than once in a response but the headers in Proxyman seem to be fine.
• If Proxy is disabled and SSL Proxy for the domain is disabled, chrome reports a successful connection and starts receiving messages in the websocket connection.

Environment

• Websocket uses STOMP protocol for message exchange.
• App version: Proxyman 4.7.1
• macOS version: macOS Ventura 13.3.1

No source files or tests are named. Start by reproducing the SSL-proxied WebSocket handshake with the Android WebView, STOMP connection, and Map Remote setup described here; done means the handshake succeeds without a duplicate Sec-WebSocket-Protocol header and messages can be modified through the local WebSocket server.