Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
0
Found in
2022.3.2f1
2023.1.0f1
2023.2.0a18
Issue ID
UUM-39971
Regression
Yes
Weaving fails when Hosting in the Player
Reproduction steps:
1. Open the attached project “WeavingErrors”
2. Build and run (File > Build And Run)
3. In the Player Click on “Host (Server + Client)” button
4. Observe the Player
Expected result: The server and client is hosted without any errors
Actual result: Weaving errors are generated
Reproducible with: 2022.1.0a4, 2022.3.2f1, 2023.1.0f1, 2023.2.0a18
Not reproducible with: 2021.3.27f1, 2022.1.0a1
Couldn't test with: 2022.1.0a2, 2022.1.0a3 (D:/Unity' is not recognized as an internal or external command)
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
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
Resolution Note:
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, please contact your account manager or PRM if you’d like to discuss this specific case in more detail, or if you would like to provide additional information relating to the severity of this bug.
Resolution Note (2023.2.X):
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, please contact your account manager or PRM if you’d like to discuss this specific case in more detail, or if you would like to provide additional information relating to the severity of this bug.