fix(iOS): clamp Double values before converting to Integer. #4621
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After investigation, I discovered that when
UIDatePicker
is set toUIDatePickerStyle.wheels
(Spinner mode), it assigns unusual coordinate values for off-screen wheel cells (falling belowInt.min
and aboveInt.max
). This leads to a conversion error inViewHierarchyGenerator
when attempting to cast theseDouble
values toInt
, resulting in:To address this, I kept the
Int
conversion but applied clamping (instead of representing it as aDouble
in the string) for the following reasons:Int
ranges from -2,147,483,648 to 2,147,483,647, and on 64-bit systems, from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807, indicating an internal issue with these extreme values.Int
bounds is irrelevant to our use case, so these values can safely be ignored without impacting functionality.