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
Thanks for the bug report. I believe the correct behaviour is for the library to throw an exception or raise the exception event, and not raise the time event providing an incorrect time in the scenario described. Unfortunately this is not something I've experienced myself, so I will need to find time to reproduce and/or study the code to find a way to detect the problem and handle it appropriately.
Hi,
I use this library in an application (Xamarin) deployed on mobile devices, which may have network connection reliability issues.
It works great 99.99%, but sometime in my api, I receive call from the app with invalid dates.
For example :
I found in the code here that the default time is 01/01/1900, so I suspect an incomplete buffer to cause this issue.
My question is how to handle this case ?
A/ An exception must be raised by the library
B/ Date must be verified by user code
The text was updated successfully, but these errors were encountered: