Search Issue Tracker
Fixed
Fixed in 6000.0.67f1, 6000.3.5f1, 6000.4.0b5, 6000.5.0a5
Votes
0
Found in
6000.0.60f1
6000.2.8f1
6000.3.0b6
6000.4.0a2
6000.5.0a1
Issue ID
UUM-122222
Regression
No
Build Profiles window Build Profiles functionality breaks when the newly created Build Profile has a lot of symbols in the name
Steps to reproduce:
- Create a new Unity project using the Universal 3D template
- Open the Build Profiles window (File > Build Profiles)
- Click the "Add Build Profile" button
- Select the QNX platform
- Copy and paste the QNX platform name over and over again until the character limit is reached
- Click the "Add Build Profile" button
- Observe the Console window
- Try to rename or duplicate the newly created QNX Build Profile
- Observe the Build Profiles window
Actual results: "AssetDatabase file scanner found file that has a name that is too long." and "ArgumentException: Invalid path" errors are thrown and Build Profiles functionality like renaming or duplicating does not work anymore
Expected results: No errors are thrown and Build Profiles functionality like renaming or duplicating works as expected
Reproducible with versions: 6000.0.60f1, 6000.2.8f1, 6000.3.0b6, 6000.4.0a2
Tested on (OS): MacOS SIlicon Sequoia 15.6.1, Ubuntu 24.04
Notes:
- Does not reproduce with classic platforms like MacOS, Windows etc.
- Does not reproduce if the long name has no symbols
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
- Crash on FindNearestVertex when objectsToSearch array contains a null transform
- Context menu item checkmark updates only after reopening twice when using Menu.SetChecked on component context menu items
- Long Property names are not truncated in the Add Property dropdown in the Animation window when the Long Property name does not fit
- [iOS] High CPU load when device keyboard is open
- Selected Animation clip in the Animation window changes when the Domain Reload is triggered
Resolution Note (fix version 6000.5.0a5):
Fixed in 6000.5.0a5
Resolution Note (fix version 6000.4.0b5):
Fixed in 6000.4.0b5
Resolution Note (fix version 6000.3.5f1):
Fixed in 6000.3.5f1
Resolution Note (fix version 6000.0.67f1):
Fixed in 6000.0.67f1