websocket CONNECT method calls on android 15

[ericcbm]

Description

Proxyman Version 5.16.0 (51600)

I'm experiencing a different behavior only when proxying an android 15 device.
While our app have a stablished websocket connection with our API, if I move the app to background, then foreground, I can see a CONNECT request to our base URL (for example, if our socket url is wss://foo.com/path, the CONNECT is done to wss://foo.com). Then, when the request is done and failed with Internal Error status, the previous stablished wss connection is aborted and I receive an onFailure callback on the app websocket implementation with java.net.SocketException: Software caused connection abort message.

Checking the application, we are not doing any CONNECT request whatsoever, and it happens only when proxying.

Is that CONNECT call expected on android 15 devices?
To keep the stablished wss connection stablished, our API needs to implement the CONNECT request?

[NghiaTranUIT]

When using a proxy, your network library will make a CONNECT request first.

Can you try the new script from Android Emulator that installs the Proxyman certificate to system-level store?