Skip to content
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

[Bug]: Doesn't connect using newest WS4NetProvider #2940

Open
3 tasks done
hitmanex opened this issue Jun 9, 2024 · 0 comments
Open
3 tasks done

[Bug]: Doesn't connect using newest WS4NetProvider #2940

hitmanex opened this issue Jun 9, 2024 · 0 comments
Labels

Comments

@hitmanex
Copy link

hitmanex commented Jun 9, 2024

Check The Docs

  • I double checked the docs and couldn't find any useful information.

Verify Issue Source

  • I verified the issue was caused by Discord.Net.

Check your intents

  • I double checked that I have the required intents.

Description

Stuck on connecting when using WebSocketProvider = WS4NetProvider.Instance on discord.net 3.15.0, using latest Discord.Net.Providers.WS4Net. on .NET Framework 4.8.1.
Using .NET 8.0 This issue doesn't exist

Another project using discord.net 1.0.2, WebSocket4Net 0.14.1, and Providers.WS4Net 1.0.2 connects just fine still...

Version

3.15.0

Working Version

1.0.2

Logs

[    Info] Gateway: Connecting

Sample

No response

Packages

No 3rd party packages.

Environment

Tested on
Windows 10 22H2,
Server 2008 R2

@hitmanex hitmanex added the bug label Jun 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant