-
I appoligize for not updating this thread earlier. I just ran the update.
After updating to the latest version I am unfortunately still seeing the same behavior with the time being relative to midnight.
-
I too have this problem. I am using 1.0.9.8
-
I have tested this issue and I got the same result. I will report this to our engineers and see if there is a simple fix to the issue.
-
Thanks for the follow-up Adam!
With this kind of team work we'll have these bugs licked in no time!
-
This is a lower priority issue. We are working on a fix but it will not be quick and easy.
-
Great! I guess it's more complicated than just taking the estimated trip duration and adding to the current time.
Thanks guys!
-
can anyone test this on 1.1.0.0 and report back with your findings?
-
I haven't had time to run the update...I'll run it today and report back with my findings...
-
I'll recheck today...If there are other people that have this issue, feel free to chime in...
-
It still has this issue in the latest release...
