Search Issue Tracker
Active
Under Consideration for 6000.5.X
Votes
0
Found in
6000.0.65f1
6000.3.4f1
6000.4.0b4
6000.5.0a4
Issue ID
UUM-131958
Regression
No
Newly added Build Profile is not set to Active when there are existing Build Profiles added
Steps to reproduce:
- Create a new Unity project using the Universal 3D template
- Open the Build Profiles window (File > Build Profiles)
- Add Build Profile and name it "222"
- Add Build Profile and name it "111"
- Observe the "111" Build Profile
- Delete the "222" Build Profile
- Add Build Profile and name it "333"
- Observe the "333" Build Profile
Actual results: "333" Build Profile is not set Active, if there are any existing Build Profiles the newly created Build Profiles are not set Active
Expected results: "333" Build Profile is set Active, newly added Build Profiles are set active as they are focused
Reproducible with versions: 6000.0.65f1, 6000.3.4f1, 6000.4.0b4, 6000.5.0a4
Tested on (OS): MacOS Silicon Tahoe 26.1, Ubuntu 24.04
Notes:
- Even when the Active added Build Profile is deleted and a new Build Profile is added, it is not selected as Active if there are existing Build Profiles
- On 6000.3.4f1 and 6000.0.65f1, even the first added Build Profile is not set as Active
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Add comment