A rider reported getting an error message "Error: unknown error from server ..."
It turns out this was due to a bookmark for a stop that had changed in the meantime. It would be good to have a better error message for incorrect stop IDs. Adding this enhancement might involve a server change, or if the server is returning an appropriate error, getting the app to recognize that error condition. Not sure which -- for the web version of the OneBusAway interface, changing the URL to a nonexistent stop does give a reasonable error message.
A rider reported getting an error message "Error: unknown error from server ..."
It turns out this was due to a bookmark for a stop that had changed in the meantime. It would be good to have a better error message for incorrect stop IDs. Adding this enhancement might involve a server change, or if the server is returning an appropriate error, getting the app to recognize that error condition. Not sure which -- for the web version of the OneBusAway interface, changing the URL to a nonexistent stop does give a reasonable error message.