Android not support below 1970 years

Question

Android not support below 1970 years

mhd-shagul opened this issue 8 months ago · comments

mhd-shagul commented 8 months ago

Bug report

mhd-shagul · Answer 1 · Thu Nov 09 2023 15:57:05 GMT+0800 (China Standard Time)

IOS supported below 1970 years android not supported below 1970 how fix it

Umar Bolatov · Answer 2 · Fri Nov 10 2023 08:34:08 GMT+0800 (China Standard Time)

I'm seeing the same issue on a Pixel 4 with version 7.6.0.

@mhd-shagul you can work around this issue by setting mininumDate={new Date(1900, 0, 1)} or some other date that's low enough. You can also downgrade the library to an earlier version (I know 7.4.2 doesn't have this bug for sure).

Umar Bolatov · Answer 3 · Fri Nov 10 2023 09:26:46 GMT+0800 (China Standard Time)

I did some more testing and looks like this bug was introduced in version 7.5.0 in this PR: #744.

The bug doesn't reproduce in 7.4.2.

Elkin Torres · Answer 4 · Wed Dec 06 2023 22:48:11 GMT+0800 (China Standard Time)

I'm having the same issue on 7.6.0, any updates, besides the workaround?

Ali Raza · Answer 5 · Tue Feb 13 2024 03:15:21 GMT+0800 (China Standard Time)

I'm seeing the same issue on a Pixel 4 with version 7.6.0.

@mhd-shagul you can work around this issue by setting mininumDate={new Date(1900, 0, 1)} or some other date that's low enough. You can also downgrade the library to an earlier version (I know 7.4.2 doesn't have this bug for sure).

I've set the version to 7.4.2 and it's working but the minimum year is 1900. Can we go below to this year as we are in IOS?

Tom Bakker · Answer 6 · Wed Apr 17 2024 15:43:01 GMT+0800 (China Standard Time)

I'm bumping this issue, as it is still a thing in version 7.6.4. The workaround does its job, but it is weird that we still need it in the first place. Any updates?

Yousha Arshad · Answer 7 · Mon May 13 2024 22:12:19 GMT+0800 (China Standard Time)

I'm seeing the same issue on a Pixel 4 with version 7.6.0.

@mhd-shagul you can work around this issue by setting minimumDate={new Date(1900, 0, 1)} or some other date that's low enough. You can also downgrade the library to an earlier version (I know 7.4.2 doesn't have this bug for sure).

Should be mininumDate={new Date(1900, 0, 1)}, there is a spelling mistake.