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
On some investigation the likely cause seems to be a non-Gregorian calendar setting (e.g. Buddhist), which changes the year from 2022 to something like 2565 BE
We are using v2.1.2 with a maxDate (which I suspect is causing the range exception)
I understand this is a rare use case, but wondering if there might be a simple fix that doesn't result in a crash
The text was updated successfully, but these errors were encountered:
There are ways to supporting it but requires reasonable work and specifically testing. It would need to be configurable through options and explicitly provided, or otherwise inferred from the locale/country (although this is less flexibel and limited through being coupled to this locale, also for representation/localization).
I am open to contributions.
In iOS it is not hardcoded (IIRC), and you possibly can address it by setting the correct locale in the plugin options, but I cannot confirm this. Alternatively it could also be modified to either support locale or setting a specific calendar format: https://stackoverflow.com/a/33373396
[edit] note that if you do not specify a locale in the options, it will use the user/device default
iOS user was experiencing a crash on opening datepicker:
On some investigation the likely cause seems to be a non-Gregorian calendar setting (e.g. Buddhist), which changes the year from
2022
to something like2565 BE
We are using v2.1.2 with a
maxDate
(which I suspect is causing the range exception)I understand this is a rare use case, but wondering if there might be a simple fix that doesn't result in a crash
The text was updated successfully, but these errors were encountered: