Crash when click on path to focus on map

[Echolon]

Describe the bug
Clicking on a pathway like a train path to focus is a feature I found accidentally - cool :-)
However its crashing for walking / food paths.

To Reproduce
Steps to reproduce the behavior:

1. Search a connection that includes walking / food paths
2. Click on the food path to focus (see screenshot)
3. The app crashes

Expected behavior
Focus the map view to this path

Versions (please complete the following information):

• Transportr Version: 2.1.4
• Device: HTC One M7
• Android Version: 7.1.2

Provider selected: Deutsche Bahn

[mimi89999]

Can't reproduce. What provider are you using? Do you have a logcat?

[Echolon]

@mimi89999 Provider? You mean my mobile provider?

Is there a tutorial for logcat?

[Echolon]

I can still reproduce this way

[mimi89999]

Provider?

I mean the network you chose on the start screen

[Echolon]

ah, German Deutsche Bahn

[mimi89999]

What did you enter into departure and arrival fields?

[Echolon]

What did you enter into departure and arrival fields?

Any search which contains footpath results this issue

[mimi89999]

04-06 12:36:46.967 20696 20696 E AndroidRuntime: FATAL EXCEPTION: main
04-06 12:36:46.967 20696 20696 E AndroidRuntime: Process: de.grobox.liberario, PID: 20696
04-06 12:36:46.967 20696 20696 E AndroidRuntime: com.mapbox.mapboxsdk.exceptions.InvalidLatLngBoundsException: Cannot create a LatLngBounds from 1 items
04-06 12:36:46.967 20696 20696 E AndroidRuntime: 	at com.mapbox.mapboxsdk.geometry.LatLngBounds$Builder.build(LatLngBounds.java:440)
04-06 12:36:46.967 20696 20696 E AndroidRuntime: 	at de.grobox.transportr.trips.detail.TripDetailViewModel.onLegClick(TripDetailViewModel.kt:84)
04-06 12:36:46.967 20696 20696 E AndroidRuntime: 	at de.grobox.transportr.trips.detail.LegViewHolder.bind$lambda-8(LegViewHolder.kt:105)
04-06 12:36:46.967 20696 20696 E AndroidRuntime: 	at de.grobox.transportr.trips.detail.LegViewHolder.lambda$ZO4xQ3iy5sO6sUlnAWNNXdwE_eY(Unknown Source:0)
04-06 12:36:46.967 20696 20696 E AndroidRuntime: 	at de.grobox.transportr.trips.detail.-$$Lambda$LegViewHolder$ZO4xQ3iy5sO6sUlnAWNNXdwE_eY.onClick(Unknown Source:4)
04-06 12:36:46.967 20696 20696 E AndroidRuntime: 	at android.view.View.performClick(View.java:7448)
04-06 12:36:46.967 20696 20696 E AndroidRuntime: 	at android.view.View.performClickInternal(View.java:7425)
04-06 12:36:46.967 20696 20696 E AndroidRuntime: 	at android.view.View.access$3600(View.java:810)
04-06 12:36:46.967 20696 20696 E AndroidRuntime: 	at android.view.View$PerformClick.run(View.java:28305)
04-06 12:36:46.967 20696 20696 E AndroidRuntime: 	at android.os.Handler.handleCallback(Handler.java:938)
04-06 12:36:46.967 20696 20696 E AndroidRuntime: 	at android.os.Handler.dispatchMessage(Handler.java:99)
04-06 12:36:46.967 20696 20696 E AndroidRuntime: 	at android.os.Looper.loop(Looper.java:223)
04-06 12:36:46.967 20696 20696 E AndroidRuntime: 	at android.app.ActivityThread.main(ActivityThread.java:7664)
04-06 12:36:46.967 20696 20696 E AndroidRuntime: 	at java.lang.reflect.Method.invoke(Native Method)
04-06 12:36:46.967 20696 20696 E AndroidRuntime: 	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
04-06 12:36:46.967 20696 20696 E AndroidRuntime: 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)

[Echolon]

Many thanks, so you were able to reproduce?

[mimi89999]

It's an issue with that network in public-transport-enabler. The problem is that for some walking trip legs, the reported departure and arrival coordinates are exactly the same.

[ialokim]

Interesting, thanks for investigating @mimi89999! Even if its an issue with the data, we should avoid the crash. Checking for the distance before calling the map library function would be a quick fix.

[Altonss]

It's an issue with that network in public-transport-enabler. The problem is that for some walking trip legs, the reported departure and arrival coordinates are exactly the same.

I haven't been able to trigger this situation, what departure/arrival did you choose?

[Altonss]

This seems to be a duplicate of #574