Open BloodPawHD opened 9 months ago
I vaguely remember the MVV app is using Defas (BayernProvider) these days. Does Transportr show delays when switching it to "Bayern"?
I tested your advice to switch the Transportr network to BayernProvider and it really works so thank you for this (although all the S-Bahn lines are displayed in the same color and the description in Transportr for this network is just for Würzburg and Regensburg, but both should be an own issue). Switching to BayernProvider works but is just a work around, the bug of the MVV network still exists and the MVV app uses https://efa.mvv-muenchen.de/ not Defas. Maybe it is time to drop the support of MVV and make the description of BayernProvider (in Transportr called "BEG") more accurate.
I just found out that there is an old open pull request about this topic (https://github.com/schildbach/public-transport-enabler/pull/414). What happened with changing the endpoint?
I just found out that there is an old open pull request about this topic (#414). What happened with changing the endpoint?
Looking at it again.
I found it strange that my Transportr App always says 0 departure and arrival delays while using the MVV network. So I tried to reproduce this with public-transport-enabler and still wrong delays. The official MVV App supports showing delays and so does the API public-transport-enabler uses (https://efa.mvv-muenchen.de/mobile).
My Transportr App:
Experimenting with public-transport-enabler tests:
Test with the official MVV Website used by public-transport enabler:
As you see there is a real departure delay of 2 minutes at the trip from Marienplatz to Pasing at 15:13.
Versions I tested: Transportr 2.2.1 public-transport-enabler Github Repo Clone from 30.01.2024