If a maximumDate is provided, but a minimumDate is not, the Android date picker does not allow the user to go earlier than the Unix epoch (1970-01-01 00:00).
The workaround I found was to manually set an unrealistic minimumDate. You can also remove the maximum date, but in our case that is not an option.
Facing the same issue. We have our maximum date set to three years from the current date and no minimum date. However what @czycha suggested does work and is a temporary workaround for thus
Bug report
Summary
If a
maximumDate
is provided, but aminimumDate
is not, the Android date picker does not allow the user to go earlier than the Unix epoch (1970-01-01 00:00).The workaround I found was to manually set an unrealistic
minimumDate
. You can also remove the maximum date, but in our case that is not an option.Reproducible sample code
https://github.com/czycha/rn-datepicker-min-date-bug has this code here
Steps to reproduce
Describe what you expected to happen:
Environment info
npx react-native info
output:datetimepicker version: 8.2.1
Android version: 15
Expo: 51.0.36