-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: Operation is not supported on this platform #601
Comments
I just tried to make a port of an app to UWP and I got the same error |
I'm getting the same error also. Running on .NET Core 3.1. |
I have same problem. I'm using secure connection and in one of ten cases (or so) program throws System.PlatformNotSupportedException after connect to server. When connection is nonsecure, it works fine. |
I use connectasync() to connect to server,it throws the same error, but it works fine when I use connect. |
Thanks for the suggestion, i'll give it a try.
…On Thu, 23 Apr 2020 at 18:38, brad.liu ***@***.***> wrote:
I use connectasync() to connect to server,it throws the same error, but it
works fine when I use connect.
Running on .NET Core 3.1.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#601 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAUDWYCTPN5BZPAGRKQ4MYLRN75AZANCNFSM4LMXWGUA>
.
|
@bradliuvskysoft thanks for the workaround, it indeed works without async. |
Am working on a proper fork currently. Should finish basic support in a week. @tomerpeled |
I've been running socket-sharp for 3 weeks now just fine (.net Core 2.1). Its started to throw this
System.PlatformNotSupportedException: Operation is not supported on this platform. at System.Action 1.BeginInvoke(T obj, AsyncCallback callback, Object object) at WebSocketSharp.WebSocket.open() at WebSocketSharp.WebSocket.Connect() | System.Exception {System.PlatformNotSupportedException}
I'm simply calling
using (ws = new WebSocketSharp.WebSocket(Address)) { ws.Connect(); //Other stuff after }
and it throws after connect.
The text was updated successfully, but these errors were encountered: