-
Notifications
You must be signed in to change notification settings - Fork 2
Invalid DateTime under Android #2
Comments
Hi, I am using the I now have implemented showing the original log timestamp in case that date parsing leads to an invalid date. I hope that this yields an acceptable workaround, as supporting all possible ways the timestamp could be possibly formatted is beyond my capacity (if someone has a pointer for a library capable of automatic this, I am happy to get a pointer). |
Hi,
This is exactly the core of the problem and I fully agree that the blame here lies squarely with Google. Regarding the format I mentioned in
Turns out this was actually caused by a language setting (Chinese) + manual editing of the EN log before sharing.
I think that's a great idea 👍.
Unfortunately I can't provide any real pointer only an observation: I've noticed is that Microsoft Excel seems to have some way of parsing timestamps. When I select "Datatype -> Date/Time" for the timestamp column when importing EN logs, it's actually properly parsing them even with the OP logs. But as Excel is closed source, it's very unlikely that their parser would be openly available unfortunately . |
Hi,
Thanks for the feedback. I haven't tested the workaround as I didn't have a proper example. Thanks for the pointer to the example. I was a bit too quick in implementing and checked the validity of the wrong object --- it is fixed by now and is working for me. Can you confirm this?
Yes, I am sure that commercial products can handle this and probably there is also an open version ( |
Yes! works perfectly now, thanks 😊.
I see, makes sense. I think the approach you've chosen is a really good idea in this context 👍. |
Hi,
I just noticed two issues under Android when it comes to the format
timestamp
which seem to throw ENA off:ENA seems to expect English names for the months. e.g.
3. October 2020, 02:54
will work but not3. Oktober 2020, 02:54
but the latter is what my EN log contains: me-03.txt. Therefore I will see "Invalid DateTime" for the matches in October.I recently came across someone who's
timestamp
had a totally different format:2020.10.3 09:40
(ArgentinaRDX-03.txt). I'm not entirely sure what's going on there, but I'll try to investigate and will let you know as soon as I know more.The text was updated successfully, but these errors were encountered: