search

TwitchLib / TwitchLib.Unity

TwitchLib repository representing all code belonging to the implementation of TwitchLib for Unity. Maintained primarily by LuckyNoS7evin.
164 stars 33 forks source link

Client & PubSub is not compatible with certain versions of the Unity Editor #36

Open RRickkert opened 6 years ago

RRickkert commented 6 years ago

Issue resolved

As of Unity 2018.2.5f1 (and possibly a few versions earlier), this issue has been fixed.

The issue

As of Unity 2018, most versions so far are no longer compatible with the TwitchLib Client and PubSub for Unity. This has to do with the WebSocket4Net dll that TwitchLib's Client and PubSub uses.

Please note: This only affects the TwitchLib Client and PubSub. Not the TwitchLib Api,

Please vote for a fix!

~~A Unity bug report has been created in the hope that Unity will be fixing this issue soon. Please vote on the bug report to put a bit more pressure on the Unity developers to get this fixed! You can find the bug report here: https://issuetracker.unity3d.com/issues/opened-event-of-a-websocket4net-dot-websocket-does-not-get-called-when-opening-a-web-socket~~

Please note that even though it says it's fixed in 2018.2, according to our tests, it's not.

Supported Unity versions

Official releases:

Beta releases:

Unsupported Unity versions

Official releases:

Beta releases:

Testing your Unity version's compatibility

To figure out whether version of Unity that you're using should be compatible, you can use the following method:

Instructions

If your version of Unity is compatible. It should show a message "opened" in the Debug Log. If your version of Unity is not compatible. It should show no message in the Debug Log.

Solutions

The Unity versions listed under the supported Unity versions should work just fine. So you can always switch your Unity project to one of those versions.

Currently there are no solutions available for the listed unsupported Unity versions.

MrTwister242 commented 6 years ago

Looks like this is still an issue in Unity 2018.2.1f1

swiftyspiffy commented 6 years ago

As I understand it, the move to .net core 2.1 should resolve this issue as we remove the external dependency on websocket4net

RRickkert commented 5 years ago

As of Unity 2018.2.5f1 (and possibly a few versions earlier), this issue has been fixed. Might be best to keep this issue open for a little while though since people might still use older versions.