Search Issue Tracker
Fixed in 6000.4.0b2
Fixed in 6000.3.5f1, 6000.4.0b5, 6000.5.0a5
Votes
0
Found in
6000.3.3f1
6000.4.0a6
6000.5.0a3
Issue ID
UUM-128985
Regression
Yes
Unsaved changes prompt is not shown when building a project with a dirty Scene
How to reproduce:
1. Create a new project using the URP template
2. Add any object in the "SampleScene"
3. Start a build for the project
4. Observe the Editor
Actual result: "Scene(s) Have Been Modified" warning prompt is not shown and unsaved changes are removed from the Scene
Expected result: "Scene(s) Have Been Modified" warning prompt is shown
Reproducible with: 6000.5.0a2
Not reproducible with: 6000.0.66f1, 6000.3.5f1, 6000.4.0b5, 6000.5.0a1, 6000.5.0a5
Fixed in: 6000.3.5f1, 6000.5.0a5
Reproducible on: Windows 11
Not reproducible on: No other environments 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 (fix version 6000.4.0b2):
The PR causing this regression has been reverted, a different way of solving the issue in the original PR will be investigated.
Resolution Note (fix version 6000.5.0a5):
The PR causing this regression has been reverted, a different way of solving the issue in the original PR will be investigated.
Resolution Note (fix version 6000.4.0b5):
Fixed in 6000.4.0b5
Resolution Note (fix version 6000.3.5f1):
Fixed in 6000.3.5f1