If you designed your application with TMS WEB Core, there is a separate TTMSFNCWebCoreClientBrowser component for that purpose. It will setup a handshake and then allow you to communicate with the webclientsocket server and client. If your web application is developed outside TMS WEB Core, we'll need more information on what exactly you want to achieve when using the TTMSFNCWebBrowser. Which flags are you referring to exactly?
the app is trying to connect to the backend via websocket,
if I run it on edge, chrome or any supported browser the websocket call returns,
but if I try to load the same app in the TTMSFNCWebBrowser those calls get stuck and never return,
when I look them in the console window I see they are still pending for response.
My backend does not care who is calling (I tried a native websocket control to see if the call returns and that is working).
I think it is some permission I'm not setting for the control or some thing else.
Hi, we found a few issues regarding websocket support in the embedded chromium webview 2 control:
It basically tells there is a security issue when using custom URL schemes other than HTTP & HTTPS. Can you perhaps try to capture the exception or error? Do you actually get a connection in the backend and then hangs or is it hanging inside the client?