search

Unity-Technologies / com.unity.netcode.gameobjects

Netcode for GameObjects is a high-level netcode SDK that provides networking capabilities to GameObject/MonoBehaviour workflows within Unity and sits on top of underlying transport layer.
MIT License
2.13k stars 433 forks source link

[Netcode] Received a packet with an invalid Hash Value (iOS) #2739

Open sandordost opened 11 months ago

sandordost commented 11 months ago

Error Message [Netcode] Received a packet with an invalid Hash Value. Please report this to the Netcode for GameObjects team at https://github.com/Unity-Technologies/com.unity.netcode.gameobjects/issues and include the following data: Received Hash: 3049800023012508954, Calculated Hash: 5552551004536440314, Offset: 4, Size: 112, Full receive array: 70 00 00 00 60 11 01 00 70 00 00 00 1a 85 a3 5f f6 10 53 2a 09 d2 02 02 01 7d 9a e2 a5 01 b2 36 17 b3 01 46 c4 ca 04 01 39 3b e8 2c 01 ab c9 50 60 01 53 a3 38 44 01 d3 f6 1c b8 01 a6 22 89 97 01 b5 fe 01 74 01 be 97 be 73 01 9d 9a 5c 01 01 e9 51 97 17 01 8a f7 e7 83 01 42 7f 88 c6 01 97 a3 f5 46 01 00 00 00 00 01 5c fc ed 91 42 32 07 a3 00 00 00

How it happens This problem only happens on iOS devices. I am using Relay Unity Transport. The problem does not occur on Android or Standalone devices. When the scene loads, someone hosts the game, and when the other (iOS device) joins, the exception occurs.

Device combinations [ OK ] Standalone -> joins -> Android [ OK ] Android -> joins -> Standalone [ OK ] Standalone -> joins -> Unity Editor [ OK ] Android -> joins -> Unity Editor [ OK ] Unity Editor -> joins -> Android [ OK ] Unity Editor -> joins -> Standalone

[ WARN ] iOS -> hosts -> any device -> joins: [Netcode] Server detect a transport connection from Client-1, but timed out waiting for the connection request message

[ ERR ] iOS -> joins -> any device: [Netcode] Received a packet with an invalid Hash Value.

Package versions Unity Transport 1.3.4 Netcode for GameObject 1.5.2 Multiplayer Tools 1.0.0 Authentication 2.7.2 Relay 1.0.5

sandordost commented 11 months ago

This bug was replicated on Unity Version is 2022.3(LTS). I am now going to switch to 2021.3(LTS) and see if the error still occurs.

Edit: Downgrade is not possible with current project.

ShadauxCat commented 3 months ago

com.unity.transport version 2.3.0 has released today that I think should have a fix for this issue. A new release for the 1.x line of com.unity.transport should be out soon as well, I'll post again when that is out in case you can't or don't want to update to 2.3.0.

Can you retest and confirm for us?