No transit connections found caused by outdated departure time

[hbruch]

Describe the bug Opening the app a few days after last usage seems not to reset the departure date (probably this happens when the last search was for a specified time/date). Still worse, opening the departure time picker showing "Departure "today" and the current time and leaving via ok does not reset departure time.

In consequence, no results are found for past days

To Reproduce Steps to reproduce the behavior:

1. Search a connection for e.g. today at a later hour
2. Leave the app (sending it to the background, not closing it)
3. Wait a day or two
4. Reopen app and see the outdated weekday is still shown.

Expected behavior Reopening the app should, in case the departure date is in the past (probably more than a specific duration) be reset to current ate/time.

As a later improvement idea: Other apps ask (perhaps only if search time is only a few minutes/hours in the past), if the original or current time should be used...

Screenshots not necessary

Smartphone (please complete the following information):

• Device: iPhone12 mini
• OS: iOs
• Browser Safari
• Version 1.5.1

[MartinH-open]

I second this issue as I ran into the same problem using the Herrenberg StadtNavi App. Last time I used it before was 16.6.2022 and now I was locking for a public transport from Böblingen to Tübingen (40km distance) and got such surprising results: trip for 9h and more than 2000km travel.

[GustavoTCh]

@MartinH-open We are fixing the bug in the datepicker, the app will prevent the request in the past. On the results (2000 km), I can't reproduce the error, but the application shows the response from the backend.