Search Issue Tracker
Not Reproducible
Not Reproducible in 6000.4.X
Won't Fix in 6000.4.X
Votes
0
Found in
6000.4.0b11
Issue ID
UUM-135115
Regression
No
Build Steps in Project Auditor show no Logs after project is built until Project Auditor is reopened
How to reproduce:
1. Open the attached “IN-135902“ project
2. Open the “Scene“ scene
3. Build and Run the Player
4. In the Editor, open the Project Auditor window (Window > Analysis > Project Auditor) and click “Start Analysis“
5. In the Project Auditor window, open the Build Steps section (Build > Build Steps)
6. Observe the listed Build Steps
Actual result: No Build Steps are visible
Expected result: Build Steps are visible
Reproducible with: 6000.4.0b11, 6000.5.0a2
Not reproducible with: 6000.5.0a8
Fixed in: 6000.5.0a3
Reproducible on: Windows 11, Ubuntu 24.04
Not reproducible on: No other environments tested
Workaround: After restarting the Editor the Build Steps will be visible
Notes:
- For the 6000.0; 6000.3 streams, Project Auditor is a separate package and is therefore filled as a separate issue
- The .buildreport in the Library folder is valid and generated correctly
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
- Required SpriteMask class (ID 331) is stripped when "Strip Engine Code" is enabled
- “Maximized serialized file backup not found” error is thrown when minimizing a window in a newly opened project
- Build stack trace contains invalid lines when building with IL2CPP using scripts with delegates containing generic types in the signature
- Entities Systems window has a “Show Full Player Loop” dropdown which does nothing when clicked after enabling “Show Full Player Loop”
- Entities Hierarchy Search “Show/Hide” button’s Lens Icon is blurry when the Editor is on an external monitor
Resolution Note:
Does this still happen in 6000.6 ?
Resolution Note (6000.4.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (6000.4.X):
Does this still happen in 6000.6 ?