Testing regionalized OBA Android app - Selected region not working, NPE on "Show Arrivals", No stops found

[Sean Barbeau]

Paul,
I'm finally getting around to testing the regionalized version of the OBA Android app (https://github.com/paulcwatts/onebusaway-android/tree/feature/MultiRegion) here in Tampa.  I've added the OBA Android app API key to our server instance via the data-sources.xml file and tested our REST API using this key, and it works.

I'm having a few issues browsing through the app:

1. Selected region from list not recognized - When I go to "Help->Preferences->Your Location", I see the list of OBA regions from the Google Doc directory.  However, if I select Tampa and return to the main screen, I still see Seattle routes.  For example, if I search for route "5", I get "Greenwood/Scc/Northgate" for Seattle, not "40th Street" for Tampa.  However, if I go to "Help->Preferences->OBA API Server" and manually set it to "onebusaway.forest.usf.edu/onebusaway-api-webapp", then it does display Tampa bus icons on the map.  But then...
   
2. NPE when trying to view arrival times - When I tap on a bus icon and tap on "Show Arrivals", the app crashes and I get a NullPointerException:
   

11-26 15:06:50.346: E/AndroidRuntime(20094): FATAL EXCEPTION: main
11-26 15:06:50.346: E/AndroidRuntime(20094): java.lang.NullPointerException
11-26 15:06:50.346: E/AndroidRuntime(20094):     at com.joulespersecond.oba.request.ObaArrivalInfoResponse$Data.access$1(ObaArrivalInfoResponse.java:51)
11-26 15:06:50.346: E/AndroidRuntime(20094):     at com.joulespersecond.oba.request.ObaArrivalInfoResponse.getSituations(ObaArrivalInfoResponse.java:80)
11-26 15:06:50.346: E/AndroidRuntime(20094):     at com.joulespersecond.seattlebusbot.ArrivalsListFragment.onLoadFinished(ArrivalsListFragment.java:207)
11-26 15:06:50.346: E/AndroidRuntime(20094):     at com.joulespersecond.seattlebusbot.ArrivalsListFragment.onLoadFinished(ArrivalsListFragment.java:1)
11-26 15:06:50.346: E/AndroidRuntime(20094):     at android.support.v4.app.LoaderManagerImpl$LoaderInfo.callOnLoadFinished(LoaderManager.java:424)
11-26 15:06:50.346: E/AndroidRuntime(20094):     at android.support.v4.app.LoaderManagerImpl$LoaderInfo.onLoadComplete(LoaderManager.java:392)
11-26 15:06:50.346: E/AndroidRuntime(20094):     at android.support.v4.content.Loader.deliverResult(Loader.java:103)
11-26 15:06:50.346: E/AndroidRuntime(20094):     at com.joulespersecond.seattlebusbot.ArrivalsListLoader.deliverResult(ArrivalsListLoader.java:49)
11-26 15:06:50.346: E/AndroidRuntime(20094):     at com.joulespersecond.seattlebusbot.ArrivalsListLoader.deliverResult(ArrivalsListLoader.java:1)
11-26 15:06:50.346: E/AndroidRuntime(20094):     at android.support.v4.content.AsyncTaskLoader.dispatchOnLoadComplete(AsyncTaskLoader.java:221)
11-26 15:06:50.346: E/AndroidRuntime(20094):     at android.support.v4.content.AsyncTaskLoader$LoadTask.onPostExecute(AsyncTaskLoader.java:61)
11-26 15:06:50.346: E/AndroidRuntime(20094):     at android.support.v4.content.ModernAsyncTask.finish(ModernAsyncTask.java:461)
11-26 15:06:50.346: E/AndroidRuntime(20094):     at android.support.v4.content.ModernAsyncTask.access$500(ModernAsyncTask.java:47)
11-26 15:06:50.346: E/AndroidRuntime(20094):     at android.support.v4.content.ModernAsyncTask$InternalHandler.handleMessage(ModernAsyncTask.java:474)
11-26 15:06:50.346: E/AndroidRuntime(20094):     at android.os.Handler.dispatchMessage(Handler.java:99)
11-26 15:06:50.346: E/AndroidRuntime(20094):     at android.os.Looper.loop(Looper.java:137)
11-26 15:06:50.346: E/AndroidRuntime(20094):     at android.app.ActivityThread.main(ActivityThread.java:4918)
11-26 15:06:50.346: E/AndroidRuntime(20094):     at java.lang.reflect.Method.invokeNative(Native Method)
11-26 15:06:50.346: E/AndroidRuntime(20094):     at java.lang.reflect.Method.invoke(Method.java:511)
11-26 15:06:50.346: E/AndroidRuntime(20094):     at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1004)
11-26 15:06:50.346: E/AndroidRuntime(20094):     at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:771)
11-26 15:06:50.346: E/AndroidRuntime(20094):     at dalvik.system.NativeStart.main(Native Method)

3.  If I search for a route (e.g. "5"), "40th Street" shows up.  When I tap on the route, it gives me the option to "Show list of stops" and "Show on Map".  When I tap on either, it says no stops are found.

Do you want me to file these as issues on Github?

Thanks,
Sean

[Evgeni Makarov]

Hi Sean

If you're interested in mobile apps for OBA, probably we could collaborate?

We have created a mobile app with cloud-vased server support that can use different formats, including OneBusAway and successfully integrated OneBusAway NYC MTA data. Does that interesting for you?

The iOS version is here https://itunes.apple.com/us/app/dorogatv-transport/id570667398?ls=1&mt=8

Also releasing soon an Android app

Regards

Evgeny

понедельник, 26 ноября 2012 г., 23:30:00 UTC+3 пользователь Sean Barbeau написал:

[Barbeau, Sean]

Evgeny,

We’d welcome collaboration on the project.  In what ways are you thinking of contributing?  Also, is your app open-source?

 

One of the reasons we’re aiming at regionalizing the original Android/iPhone/WP7 mobile apps is that they are open-source, and have been evaluated extensively with the general public in the Puget Sound deployment of OneBusAway.  Open-source is important so that others can modify/improvement upon the apps, without relying on a single party to continue development.  Also, open-source apps can easily be modified to serve as research tools by the academic community for particular purposes.

 

I’m going to be working on completing the regionalization that Paul started on the Android OBA app, and we’re also currently looking into regionalizing the iPhone and WP7 OBA apps too.  If you’d like to help with the iPhone or WP7 app improvements, please let me know.

 

Sean

--
You received this message because you are subscribed to the Google Groups "onebusaway-developers" group.
To view this discussion on the web visit https://groups.google.com/d/msg/onebusaway-developers/-/bag2z0QhuSAJ.
To post to this group, send email to onebusaway...@googlegroups.com.
To unsubscribe from this group, send email to onebusaway-devel...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/onebusaway-developers?hl=en.