[iOS] Fixed the UIStepper Value from being clamped based on old higher MinimumValue - Candidate PR test failure fix- 33363

[Ahamed-Ali]

Root Cause of the issue

• Stepper_SetIncrementAndVerifyValueChange and Stepper_SetIncrementValue_VerifyIncrement in the candidate failed because the previous test, Stepper_ResetToInitialState_VerifyDefaultValues, updated the Minimum value to 10.

• When the next test (Stepper_SetIncrementAndVerifyValueChange) runs, a new ViewModel is created and the default values (Value = 0, Minimum = 0) are set in StepperFeature. However, MapValue is called first during the time, the Minimum value still retains the value 10 from the previous test. Although MAUI correctly updates PlatformStepper.Value, the native UIStepper automatically clamps the value based on the old Minimum value, causing the test to fail.

Description of Change

• Before updating platformStepper.Value, the code first checks if MinimumValue needs updating and applies it. This ensures iOS always clamps against the current/correct MinimumValue, not a stale one.

Example Scenario

Old state: Min=5, Value=5
New state: Min=0, Value=2
Without fix: If Value is set first (to 2), iOS sees Min=5 (stale) and clamps Value back to 5
With fix: Min is updated to 0 first, then Value is set to 2 successfully

Regressed PR

#32939

Issues Fixed

Fixes #

Tested the behaviour in the following platforms

• Android
• Windows
• iOS
• Mac

Screenshot

Before Issue Fix	After Issue Fix
BeforeFixStepper.mov	AfterFixStepper.mov