Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.2.0
1.3.0
Issue ID
NCCBUG-198
Regression
No
"KeyNotFoundException: The given key '-96180' was not present in the dictionary." thrown when connecting to the Editor host from the Player
How to reproduce:
1. Open the attached project "MULT HOMEWORK.zip"
2. Open File>Build Settings...
3. Enable Development Build
4. Build And Run the project
5. Enter Play Mode in the Editor
6. Click the "Host" button
7. Click the "READY" button
8. Click the "Client" button in the Player
Expected results: No errors thrown in the Development Console
Actual results: "KeyNotFoundException: The given key '-96180' was not present in the dictionary." thrown in the Development Console
Reproducible with: 1.2.0 (2022.2.15f1, 2023.2.0a9), 1.3.1 (2021.3.22f1, 2022.2.15f1, 2023.1.0b12, 2023.2.0a9)
Could not test with: 2020.3.47f1 (compilation errors in the Console window)
Reproducible on: Windows 10
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
- ResolveUsePasses now extracts passes from all subshaders including fallbacks, in contrast to documented behaviour
- [UIBuilder] Changes aren't detected on types implementing IList
- [HDRP] Text is rendered with artefacts when using STP and resolution scale is set a float value
- [Settings Search] Search results not always matching search term correctly
- Crash on memcpy when opening a project that loads TSS files
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.