Skip to content
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.

Sign up for GitHub

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

Jump to bottom

fix(android): min/max dates not always correct when timezoneOffsetInMinutes is set #635

Merged
merged 38 commits into from
Apr 18, 2023
Merged

fix(android): min/max dates not always correct when timezoneOffsetInMinutes is set #635

merged 38 commits into from
Apr 18, 2023

Conversation

henninghall
Copy link
Owner

@henninghall henninghall commented Apr 10, 2023 •
edited

@henninghall henninghall changed the title fix: min/max dates not always correct when timezoneOffsetInMinutes is set fix: min/max dates not always correct when timezoneOffsetInMinutes is set (android) Apr 13, 2023
@henninghall henninghall changed the title fix: min/max dates not always correct when timezoneOffsetInMinutes is set (android) fix(android): min/max dates not always correct when timezoneOffsetInMinutes is set Apr 13, 2023
@henninghall henninghall marked this pull request as ready for review April 17, 2023 19:01
@henninghall henninghall merged commit 40e74b2 into master Apr 18, 2023
4 checks passed
@rein96 rein96 mentioned this pull request Jan 31, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Incorrect maximumDate cutoff on Android when timeZoneOffsetInMinutes is used
1 participant
@henninghall