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
Describe the bug
The Transit app only displays the origin, the walking transfer from the bus to the train, and the destination. It does not show the in-station train transfer or the traced path of the journey. City Mapper has a similar issue.
Additionally, when attempting to edit the endpoint in City Mapper, clicking the 'End' field briefly expands the search menu, but it immediately collapses. The only way to get it to work is by dragging the endpoint to any location on the map and then clicking 'End' again. This brings up the search menu properly, allowing the user to search or select a destination. The traced route appears briefly but then disappears, leaving only the intermediate station and transfer point markers. After clicking 'GO,' the traced route returns.
Since these apps serve the same purpose and have similar issues, they may share the same root cause.
To Reproduce
For Transit App:
Plan a journey involving a bus-to-train transfer.
Observe that the in-station train transfer is missing.
Notice that the traced route of the journey is not displayed.
For City Mapper:
Attempt to edit the endpoint by clicking the 'End' field.
Observe that the search menu briefly expands but immediately collapses.
Drag the endpoint to any location on the map and click 'End' again.
Notice that the search menu now works properly.
Observe that the traced route appears briefly but then disappears.
Click 'GO' and see that the traced route reappears.
Expected behavior
The Transit app should display the in-station train transfer and the traced route of the journey.
City Mapper’s search menu should remain open when clicking 'End' without requiring a workaround.
The traced route in City Mapper should remain visible instead of disappearing.
Screenshots
This is a screenshot of the Transit app. The in-station transfer is missing, and the traced route of the journey is not displayed
This is a screenshot of City Mapper. It is missing the traced route of the journey
This is a screenshot of City Mapper after 'GO' is clicked. The traced route of the journey returns.
Android Version: 15
Custom ROM: LineageOS for MicroG v22.1-20250212-microG-lemonadep
microG Version: 0.3.6.244735
City Mapper Version: 11.30.1
Transit Version: 5.17.10
Additional context
These issues occur in both Transit and City Mapper, suggesting a common underlying cause. Does anyone know what might be causing this behavior?
The text was updated successfully, but these errors were encountered:
Describe the bug
The Transit app only displays the origin, the walking transfer from the bus to the train, and the destination. It does not show the in-station train transfer or the traced path of the journey. City Mapper has a similar issue.
Additionally, when attempting to edit the endpoint in City Mapper, clicking the 'End' field briefly expands the search menu, but it immediately collapses. The only way to get it to work is by dragging the endpoint to any location on the map and then clicking 'End' again. This brings up the search menu properly, allowing the user to search or select a destination. The traced route appears briefly but then disappears, leaving only the intermediate station and transfer point markers. After clicking 'GO,' the traced route returns.
Since these apps serve the same purpose and have similar issues, they may share the same root cause.
To Reproduce
For Transit App:
For City Mapper:
Expected behavior
Screenshots



This is a screenshot of the Transit app. The in-station transfer is missing, and the traced route of the journey is not displayed
This is a screenshot of City Mapper. It is missing the traced route of the journey
This is a screenshot of City Mapper after 'GO' is clicked. The traced route of the journey returns.
This is a video of me replicating the bug in City Mapper.
https://github.com/user-attachments/assets/5f5b5a06-035f-4de1-88a9-48cf441d5b76
System
Additional context
These issues occur in both Transit and City Mapper, suggesting a common underlying cause. Does anyone know what might be causing this behavior?
The text was updated successfully, but these errors were encountered: