Search Issue Tracker
Not Reproducible
Not Reproducible in 1.4.X
Votes
0
Found in [Package]
1.4.0-pre.3
Issue ID
MTTB-1207
Regression
No
Virtual Player throws assembly conflict error when renaming .asmdef file
How to reproduce:
1. Open “IN-91144_Testasmdef“ project
2. Open Window > Multiplayer > Multiplayer Play Mode
3. Enable Virtual Player 2
4. Navigate to Assets > Autopilot > Scripts > Tests
5. Rename AutopilotTest.asmdef file
6. Observe Virtual Player Console
Expected result: no errors appear
Actual result: Assembly conflict errors appear
Reproducible with: 1.3.0-pre.3(6000.0.22f1), 1.3.3(6000.0.36f1, 6000.1.0b5, 6000.2.0a2), 1.4.0-pre.3(6000.1.0b5, 6000.2.0a2)
Not reproducible with: 1.3.0.pre2(6000.0.22f1)
Could not test with: 2021.3.48f1, 2022.3.56f1 (package not available in these streams)
Reproducible on: macOS 15.2 (M1 Max), Windows 11
Not reproducible on: no other environments tested
Note: Turning Virtual player off and on again removes the errors
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
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
Resolution Note:
Thank you for reporting a bug to Unity.
We have investigated the issue but were unable to reproduce it with the information provided. This can happen due to differences in environment, project setup, or steps taken.
We will close this case for now. If you're able to share additional details such as different projects, steps, hardware/software configuration, or logs - please let us know, and we'll be happy to re-evaluate.
Resolution Note (1.4.X):
Thank you for reporting a bug to Unity.
We have investigated the issue but were unable to reproduce it with the information provided. This can happen due to differences in environment, project setup, or steps taken.
We will close this case for now. If you're able to share additional details such as different projects, steps, hardware/software configuration, or logs - please let us know, and we'll be happy to re-evaluate.