You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Android issue only: When a minimumDate and a maximumDate range of 24 or 48 hours is passed in, and a timeZoneOffsetInMinutes is also passed in, the datetime picker does not show the correct max cutoff time available on Android. When timeZoneOffsetInMinutes is removed, the datetime picker correctly reflects the date range.
Note: The datetime picker worked correctly on an older Android device, with OS Android 9.
For instance:
A date range of 24 hours (2/20 - 2/21) allows me to go from 2/20 4am up to 2/21 11:59pm (should be approximately 2/21 3:59am).
A date range of 48 hours (2/20 - 2/22) allows me to go from 2/20 4am up to 2/21 11:59pm (should be approximately 2/22 3:59am).
Expected behavior
The datetime picker should correctly observe the provided minimumDate and maximumDate range on Android devices when timeZoneOffsetInMinutes is passed in.
Im having the same issue too but only when we pass today as the maximumDate with timeZoneOffsetInMinutes when the mode of the date picker is 'dateTime'. The date picker renders dates 6 months ahead
Describe the bug
Android issue only: When a
minimumDate
and amaximumDate
range of 24 or 48 hours is passed in, and atimeZoneOffsetInMinutes
is also passed in, the datetime picker does not show the correct max cutoff time available on Android. WhentimeZoneOffsetInMinutes
is removed, the datetime picker correctly reflects the date range.Note: The datetime picker worked correctly on an older Android device, with OS Android 9.
For instance:
Expected behavior
The datetime picker should correctly observe the provided
minimumDate
andmaximumDate
range on Android devices whentimeZoneOffsetInMinutes
is passed in.To Reproduce
Smartphone (please complete the following information):
Demo with incorrect 48 hour range, including timeZoneOffsetInMinutes
Demo with correct 48-hour range, excluding timeZoneOffsetInMinutes
The text was updated successfully, but these errors were encountered: