Search Issue Tracker
Active
Votes
0
Found in
6000.0.62f1
6000.2.12f1
6000.3.0b10
6000.4.0a5
6000.5.0a1
Issue ID
UUM-128282
Regression
No
Some Build Profile settings do not remain checked when launching a project without the /Library folder through the command line
How to reproduce:
1. Open the project “IN-118856_Test”
2. File → Build Profiles → select the “bprof” build profile
3. Observe that all the Platform Settings are checked
4. Close the project and delete the /Library folder
5. Open the command line in the project folder path and run the following command (make sure the Unity version path is correct):
"C:\Program Files\Unity\Hub\Editor\6000.0.62f1\Editor\Unity.exe" -activeBuildProfile Assets/Settings/Profiles/bprof.asset -projectPath .
6. File → Build Profiles → select the “bprof” build profile
7. Observe the Platform Settings
Expected result: All Platform Settings are checked
Actual result: The “Copy PDB files”, “Create Visual Studio Solution”, “Wait For Managed Debugger” Platform Settings are unchecked
Reproducible with: 6000.0.0b16, 6000.0.62f1, 6000.2.12f1, 6000.3.0b10, 6000.4.0a5, 6000.5.0a1
Could not test with: 6000.0.0b15 (ArgumentNullException error)
Reproducible on: Windows 11
Not reproducible on: No other environments tested
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Some Build Profile settings do not remain checked when launching a project without the /Library folder through the command line
- TextMeshPro gradient tags render as literal text when using a font that contains only a part of the ASCII character set
- Small rectangles appearing in the corner of title text in Editor when System Font and Bitmap are selected in preferences
- The shortcut character is typed into the name field when a [Shift + <any alphanumeric key>] shortcut is used to create the asset from "Asset/Create"
- TextMeshPro ligatures broken when Font Style setting is changed from “Lowercase” to “Uppercase”
Add comment