Advanced Text Auto size spams “Invalid BestFit Range” warnings when setting Min size to negative value

Unity: UI Builder

Fixed

6.5.X

6000.5.0a5

6.4.X

6000.4.0b5

6.3.X

6000.3.5f1

Steps to reproduce:
1. Create a new Unity project
2. Open UI Builder window
3. In Hierarchy add Button Element
4. Find and expand “Text” section in Inspector window
5. Change Text Generator Type to “Advanced”
6. In Advanced Test Settings enable Auto Size
7. Change Min size to -10
8. Observe the Console window

Actual results: Warnings are spammed in the Condole “Invalid BestFit Range”
Expected results: No warnings should be spammed in the Console

Reproducible with versions: 6000.3.3f1, 6000.4.0b3, 6000.5.0a4
Can’t test with versions: 6000.0.65f1 (No Advanced Text Settings)

Tested on (OS): Ubuntu 24.04, macOS Silicon Tahoe 26.2

Notes:

Invalid BestFit Range: minFontSize (-62.00) >= maxFontSize (200.00)
UnityEngine.UIElements.ATGTextJobSystem/GenerateTextJobData:Execute (int)
Unity.Jobs.IJobForExtensions/ForJobStruct`1<UnityEngine.UIElements.ATGTextJobSystem/GenerateTextJobData>:Execute (UnityEngine.UIElements.ATGTextJobSystem/GenerateTextJobData&,intptr,intptr,Unity.Jobs.LowLevel.Unsafe.JobRanges&,int) (at /Users/bokken/build/output/unity/unity/Runtime/Jobs/Managed/IJobFor.cs:47)
Unity.Jobs.JobHandle:Complete () (at /Users/bokken/build/output/unity/unity/Runtime/Jobs/ScriptBindings/JobHandle.bindings.cs:26)
UnityEditor.GUIView:ProcessEvent (UnityEngine.EntityId,intptr,bool&)

Prioritise and Follow this issue

Have a workaround or additional info about this issue?

Issues you vote on will appear here

Advanced Text Auto size spams “Invalid BestFit Range” warnings when setting Min size to negative value

Unity: UI Builder

Statuses

Fixed

Resolution Notes

Description

Prioritise and Follow this issue

Have a workaround or additional info about this issue?

Advanced Text Auto size spams “Invalid BestFit Range” warnings when setting Min size to negative value

Unity: UI Builder

Statuses

Fixed

Resolution Notes

Description

Prioritise and Follow this issue

Have a workaround or additional info about this issue?