devinbraun

Changing trip options causes a blank interface in some cases

3

**Summary:** Blank interface is shown when changing trip options from a successful trip plan to an unsuccessful trip plan. **Steps to reproduce:** Create a valid trip plan, then change the...

Show trip-based alerts on trip details screen

3

**Summary:** OBA Android doesn't show an indication that a trip-level alert exists **Steps to reproduce:** View the arrivals including a trip with an active alert. **Expected behavior:** Show an indication...

"Style A" Arrivals are partially hidden with large text sizes

1

**Summary:** When the Android text size is set at its highest, the "Style A" arrivals in the green area and partially hidden because they don't seem to fit in the...

arrival-and-departure-for-stop API Call Returns Invalid Predicted Values in OBA 2.0

5

In OBA 2.0, when reviewing responses from arrivals-and-departures-for-stop, we receive invalid values where the predicted field is "true" but the predictedArrival and predictedDeparture are 0. The bus has already passed...

schedule-for-stop API call has incorrect headsigns

1

The API call schedule-for-stop doesn't provide correct trip headsign values for short lines. Take, for example, the following call (any date will work): http://realtime.sdmts.com/api/api/where/schedule-for-stop/MTS_75042.xml?key=org.onebusaway.iphone&date=2016-09-18 There is only one entry for...

Alerts are Shown Multiple Times

1

San Diego... Viewing Stop #10115 in iOS version shows 19 alerts. Many are the same alerts shown many times. Also view comparable Android alert which correctly shows 4 alerts.