Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.0.0
1.0.2
1.1.0
Issue ID
NCCBUG-189
Regression
No
"KeyNotFoundException" and "ArgumentException" are thrown when trying to connect to the server using Netcode for GameObjects as a client and exceeding the "Disconnect Timeout MS" limit
How to reproduce:
1. Open the user’s attached project “NetCode-Test.zip”
2. Build the project
3. Enter the Play Mode
4. Press the “Server” button in the Game view
5. Open the “Bootstrap Manager” script and add breakpoints to 67, 75, and 81 lines → press “Attach to unity”
6. Run the build and in the Player press the “Client” button and wait for 5 sec. After that press continue 2 more times
7. Stop debugging and observe the Console in the Editor
Expected result: no errors in the Console
Actual result: errors in the Console
Reproducible on: 1.0.0, 1.0.2, 1.1.0 (2020.3.42f1, 2021.3.15f1, 2022.1.23f1, 2022.2.0f1, 2023.1.0a16)
Reproducible on: Windows 10 Pro
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- EditorGUILayout.PropertyField foldout icon inside Vertical Layout Group has an incorrect indent when used with OnInspectorGUI()
- [Android] [iOS] "NullReferenceException: Object reference not set to an instance of an object" throws when entering the Play Mode/opening the application
- The Player freezes on load when building Web platform
- Animator "Conditions" tab breaks when the only Parameter is deleted and another one is created
- "Shader error in 'Universal Render Pipeline/Lit': maximum ps_5_0 sampler register index (16) exceeded" error thrown after a build is completed when the "LOD Cross Fade" parameter is enabled
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Our ISS customers’ bug reports have a higher weight than normal, and this is accounted for in the decision. We hope to be able to work with you on finding a suitable workaround in the short term. Today, however, we will be closing this case.
Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.