[Bug]: iOS crash: -[RNDatePicker setMaximumDate:] unrecognized selector on RN 0.81.4 with v5.0.12

[Richard-HeadCoach]

Describe the bug

Description:
After upgrading to React Native 0.81.4, I had to pin react-native-date-picker to 5.0.12 (see #940) to get iOS to build.

However, when opening the date picker modal with maximumDate set, the app immediately crashes on iOS.

Error log:

*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason:
'-[RNDatePicker setMaximumDate:]: unrecognized selector sent to instance'

Cause:
In ios/RNDatePickerManager.m, the native code still calls:

[view setMaximumDate:date];

…but UIDatePicker no longer exposes setMaximumDate:. The correct way is to assign the property directly:

view.maximumDate = date;

The same applies for minimumDate.

Reproduction:

React Native 0.81.4

react-native-date-picker 5.0.12

iOS 17 simulator

Open a

Expected behavior:
Date picker should open and respect the maximumDate.

Actual behavior:
App crashes with unrecognized selector exception.

Proposed fix:
Update RNDatePickerManager.m to use property assignment instead of non-existent setter methods. Example:

RCT_CUSTOM_VIEW_PROPERTY(maximumDate, id, DatePicker) {
NSDate *date = [self convertToNSDate:json];
if (date) {
view.maximumDate = date;
}
}

Expected behavior

The app doesn't crash!

To Reproduce

<DatePicker
                                mode="date"
                                date={tempDate}
                                maximumDate={latestValidDate}
                                onDateChange={setTempDate}
                                theme='light'
                                style={{ height: WINDOW_HEIGHT * 0.25, width: WINDOW_WIDTH * 0.8 }}
                            />

Operating System

• Android
• iOS

React Native Version

0.81.4

Expo Version (if applicable)

No response

react-native-date-picker version

5.0.12

React Native Architecture

• Old Architecture (Paper)
• New Architecture (Fabric)

Relevant log output

[Richard-HeadCoach]

It looks like the problem may go deeper than just swapping setMaximumDate: for maximumDate =. The native view here is an RNDatePicker wrapper, not the system UIDatePicker. From what I can tell, RNDatePicker itself doesn’t currently expose maximumDate/minimumDate as passthrough properties to its underlying UIDatePicker. That could explain why even with property assignment the selector isn’t recognized. I haven’t proved this out or tested a fix end-to-end, but it seems likely that RNDatePicker.h/.m would need to declare and implement these properties so the manager can assign them safely.

[ramazanarslan]

I'm having a similar problem. I don't know how to solve it. I'm getting the same error even though I set the minimumDate. How can we solve it?

[Richard-HeadCoach]

I couldn't find a work around thst didn't require rewriting of the package. There were other issues after I stopped using min and max. In the end I removed the package and went with community date picker.

[falkop]

Issue was fixed by @burakharun -> comment

I created a patch based on PR #939.
Tested with:
"react-native": "0.81.4" "react-native-date-picker": "5.0.13"

Works as expected

[AbdullahZareen]

+1