-
-
Notifications
You must be signed in to change notification settings - Fork 344
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
minimumDate with minuteInterval uses the last valid time instead of the one selected automatically #721
Comments
Update: After removing |
Update: Switching between AM and PM works when pressing "Confirm" for a longer time, but does not get saved when tapping the button. |
@cosminpwd I am having the same problem, I am using |
heyy I also encounter problem with enabling The calendar UI is automatically corrected based on Version: |
No solution yet @owlfrancesco. |
@cosminpwd @rein96 thanks. OS: Android 13 |
good news I tested on version I think we need to figure it out what changes after probably this one (but still not sure): but for a quick fix, we can downgrade to |
@rein96 @owlfrancesco @cosminpwd |
Thanks @yfyau, I will take a look at it! |
@yfyau's fix is released in version 4.3.6. Please check it out and if your original issue still exists @cosminpwd we can take another look at it. |
Describe the bug
When I use
minimumDate
withminuteInterval
in a modal and I select the minimum date, it automatically increases byminuteInterval
. But when I confirmonConfirm
returns the last valid time instead of what was set automatically.For example, with
minimumDate=8:00am
andminuteInterval=5
I select 7:00pm then 7:00am. This triggersminimumDate
and it changes to 8:05am, the next possible value withminuteInterval
. NowonConfirm
returns 7:00pm instead of 8:05am.Expected behavior
onConfirm
should return the automatically selected time.To Reproduce
Add example code that reproduces the behavior.
Smartphone (please complete the following information):
The text was updated successfully, but these errors were encountered: