Search Issue Tracker
Won't Fix
Fixed in 6000.0.57f1, 6000.2.2f1, 6000.3.0a5
Votes
0
Found in
6000.0.52f1
6000.1.10f1
6000.2.0b8
6000.3.0a1
Issue ID
UUM-110446
Regression
No
Assertion fail when running a script debugging build from an exported project
How to reproduce:
1. Open the “Ticket-2254816-Repro.zip“ project
2. Open the File > Build Settings
3. Enable “Create Visual Studio Solution“, “Development Build”, and “Script Debugging”
4. Build the project
5. Open the generated solution in Visual Studio 2022
6. Start debugging
7. Observe the Visual Studio
Expected result: No dialog box pops up, and the Player is launched
Actual result: A “Debug Assertion Failed“ dialog box pops up
Reproducible in: 6000.0.52f1, 6000.1.10f1, 6000.2.0b8, 6000.3.0a1
Could not test in: 2022.1.0a1, 2022.3.64f1 (IL2CPP caused issues on step 6)
Reproduced on: Windows 11 Pro (24H2), macOS 15.5 (24F74) (by the reporter)
Not reproduced on: No other environment tested
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
- Capacity-size memory is copied instead of Length-size when using UnsafeUtility.memCpy()
- Console displays "SerializedObjectNotCreatableException: Object at index 0 is null" error during Unity theme change while "Tile Palette" window is opened
- Details are not shown when Error Message is still selected after changing Log Entry Count in the Console
- Disabling Unity VCS in Project Settings unfocuses the Project Settings Window
- [Linux] Unity Version Control Project Setting labels aren't Humanized on Linux
Resolution Note:
This port is cancelled.