Search Issue Tracker

Active

Votes

0

Found in

6000.0.63f1

6000.2.15f1

6000.3.0f1

6000.4.0b1

6000.5.0a3

Issue ID

UUM-129228

Regression

No

Build Profiles modified by script require manual "Apply" when the Build Profiles window is open

-

How to reproduce:

  1. Open the “2438076.zip“ project
  2. Open the ‘File → Build Profiles’ window
  3. Create a new Build Profile and click ‘Switch Platform’ to the new profile
  4. Close the window
  5. Run ‘Tools → Debug Defines’ in the Editor toolbar
  6. Click on the “DEBUG_MODE: OFF” button
  7. Open the Build Profiles window and observe the ‘Scripting Defines’ (the 'Apply' button is disabled)
  8. Click on the “TESTING: OFF” button
  9. Open the Build Profiles window and observe the ‘Scripting Defines’ section

Actual result: Apply button is enabled (indicates a dirty/modified profile)
Expected result: Apply button is disabled (indicates an unmodified profile)

Reproducible in: 6000.0.0f1, 6000.0.63f1, 6000.2.15f1, 6000.3.0f1, 6000.4.0b1, 6000.5.0a3
Could not test in: 2023.3.0a19 (Build profiles are not a thing)

Reproduced on: Windows 11 Pro (25H2), macOS 26.1 Arm64
Not reproduced on: No other environment tested

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.