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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Resolution Note:
This port is cancelled.