Search Issue Tracker
Fixed
Fixed in 6000.0.73f1, 6000.3.14f1, 6000.4.3f1, 6000.5.0b4, 6000.6.0a1
Votes
0
Found in
6000.0.68f1
6000.3.10f1
6000.4.0b10
6000.5.0a7
6000.6.0a1
Issue ID
UUM-135389
Regression
No
ScriptableObject asset is accessed during the lookup of Build Profiles when opening the Build Profiles Window
How to reproduce:
1. Open the attached “IN-134934“ project
2. Open the Build Profiles window (File > Build Profiles)
3. Observe the Console
Actual result: “Failed to load asset at path” warning appears
Expected result: No warning appears
Reproducible with: 2023.3.0b1 (8ec5c23b39da), 6000.0.68f1, 6000.3.10f1, 6000.4.0b10, 6000.5.0a7
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Notes:
- Assigning a namespace to the BuildProfile ScriptableObject does not fix the issue
- This issue only reproduces if the ScriptableObject class is named “BuildProfile”
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
- ScrollView clips content when under an ancestor that has a filter set
- "Retrieving array element that was out of bounds" error thrown when attempting to remove a column from a Multi-Column List View
- Multi-Column List View horizontal scroll resets to left most position when scrolling vertically
- Floating License is lost for concurrent jobs
- Warning "Failed to insert item" is logged when Assigning Project to Organization's Project in the Project Settings
Resolution Note (fix version 6000.5.0b4):
Fixed in 6000.5.0b4
Resolution Note (fix version 6000.4.3f1):
Fixed in 6000.4.3f1
Resolution Note (fix version 6000.3.14f1):
Fixed in 6000.3.14f1
Resolution Note (fix version 6000.0.73f1):
Fixed in 6000.0.73f1