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
A user had some confusion over a trip plan, and here is Sound Transit's analysis:
We tested this scenario in the OBA Mobile application last night to duplicate the user’s route schedule options for his trip. We noted that the trip plan request URL provided by the user was not an ‘ArriveBy’ trip plan request URL. Our tester did happen to have the Beta version on his phone with Trip Planning enabled. I too tried to test this scenario.
The results of our tests are that the user appears to be having trouble setting the ArriveBy setting on OBA API’s Beta Trip Planner Interface. We are not sure why the user was struggling with this. Our tester concluded that the issue is user error and explaining that user has to set the ArriveBy option every time he submits the trip planning request (it is not saved on OBA Mobile) should resolve the issue.
So it sounds like it would help if we saved the last "arrive by" option preference when the user is planning trips
Steps to reproduce:
Plan a trip
Expected behavior:
Save my last preference for "arrive by"
Observed behavior:
Trip planner always reverts to default
Device and Android version:
Unknown
The text was updated successfully, but these errors were encountered:
Summary:
A user had some confusion over a trip plan, and here is Sound Transit's analysis:
So it sounds like it would help if we saved the last "arrive by" option preference when the user is planning trips
Steps to reproduce:
Plan a trip
Expected behavior:
Save my last preference for "arrive by"
Observed behavior:
Trip planner always reverts to default
Device and Android version:
Unknown
The text was updated successfully, but these errors were encountered: