search

Manevolent / ts3j

An open-source Java Teamspeak 3 client library using the TS3 full client protocol
Apache License 2.0
107 stars 15 forks source link

client is modified error #27

Closed ghost closed 4 years ago

ghost commented 4 years ago

[DEBUG] Problem reading packet java.io.IOException: com.github.manevolent.ts3j.command.CommandProcessException: client is modified at com.github.manevolent.ts3j.protocol.packet.handler.client.LocalClientHandlerFull.handlePacket(LocalClientHandlerFull.java:40) at com.github.manevolent.ts3j.protocol.socket.client.AbstractTeamspeakClientSocket$NetworkHandler.run(AbstractTeamspeakClientSocket.java:935) at java.lang.Thread.run(Unknown Source) Caused by: com.github.manevolent.ts3j.command.CommandProcessException: client is modified at com.github.manevolent.ts3j.protocol.packet.handler.client.LocalClientHandlerRetrievingData.handleCommand(LocalClientHandlerRetrievingData.java:24) at com.github.manevolent.ts3j.protocol.packet.handler.client.LocalClientHandlerFull.handlePacket(LocalClientHandlerFull.java:35) ... 2 more java.io.IOException: com.github.manevolent.ts3j.command.CommandProcessException: client is modified at com.github.manevolent.ts3j.protocol.packet.handler.client.LocalClientHandlerFull.handlePacket(LocalClientHandlerFull.java:40) at com.github.manevolent.ts3j.protocol.socket.client.AbstractTeamspeakClientSocket$NetworkHandler.run(AbstractTeamspeakClientSocket.java:935) at java.lang.Thread.run(Unknown Source) Caused by: com.github.manevolent.ts3j.command.CommandProcessException: client is modified at com.github.manevolent.ts3j.protocol.packet.handler.client.LocalClientHandlerRetrievingData.handleCommand(LocalClientHandlerRetrievingData.java:24) at com.github.manevolent.ts3j.protocol.packet.handler.client.LocalClientHandlerFull.handlePacket(LocalClientHandlerFull.java:35) ... 2 more

Manevolent commented 4 years ago

This usually happens if your client version name string and signature string don't match cryptographically, at least according to the server. What code are you using to connect?

ghost commented 4 years ago

This usually happens if your client version name string and signature string don't match cryptographically, at least according to the server. What code are you using to connect? 3.5.3 [Build: 1586353391],Windows,knmVmUvvQTTfOUCWlQncjWFWHXFqZMntUbIPIi/YLcxdW4iP3woJQgVTaIZPEiluMT5A7tb2lSk/r+Byh5R6Dw==

Manevolent commented 4 years ago

I took a look at the source code I have on my end, and this version signature doesn't seem to match what I have in the repository by default (https://github.com/Manevolent/ts3j/search?q=3.5.3&unscoped_q=3.5.3). If you are using your own version signature, please make sure it is valid -- there is only one "key" (in your case, your key/signature is knmVmUvvQTTfOUCWlQncjWFWHXFqZMntUbIPIi/YLcxdW4iP3woJQgVTaIZPEiluMT5A7tb2lSk/r+Byh5R6Dw==) for a given "build" (3.5.3 [Build: 1586353391],Windows). These are signed by TeamSpeak. I suggest either using the default version signature in TS3j or using one that is correct.

ghost commented 4 years ago

I have the same error with the default key of TS3j. :/