Search Issue Tracker
By Design
By Design in 6000.5.X
Votes
0
Found in
6000.0.66f1
6000.3.5f1
6000.4.0b5
6000.5.0a5
Issue ID
UUM-132298
Regression
No
Build Profile name increments when numeric suffix is removed from duplicate Profile name
Reproduction steps:
1. Create a new project
2. File > Build Profiles
3. Press “Add Build Profile” button in the Build Profiles window
4. Select any of the Build Profiles in the Platform Browser window and press “Add Build Profile” button
5. Repeat steps 3-4 with the same Build Profile
6. Observe that newly created Build Profile has “1” in its name (e.g. “macOS 1”)
7. Remove “1” by renaming Build Profile and observe
Actual result: Build Profile has “2” in its name (e.g. “macOS 2”)
Expected result: Build Profile name remains the same
Reproducible with: 6000.0.66f1, 6000.3.5f1, 6000.4.0b5, 6000.5.0a5
Reproduced on: macOS Tahoe 26.2 (M4)
Note: “1” reappears in the Build Profile name when renaming Build Profile for the second time
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.
Resolution Note (6000.5.X):
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.