What steps will reproduce the problem?
1. bring up domus.link on a new config with an x0.config with aliases
2. bring down domus.link
3. edit x10.conf by hand and remove old aliases and create new ones
4. bring up domus.link
5. assign locations to new aliases
6. start android app against config.
Error occurs with null pointer for JSON array
I/global (32671): Loaded time zone names for en_US in 2441ms.
E/DomusLink.DomusHandler(32671): Error getting aliases on location from
JSONObject
E/DomusLink.DomusHandler(32671): org.json.JSONException: Value null at
unknown of type org.json.JSONObject$1 cannot be converted to JSONArray
E/DomusLink.DomusHandler(32671): at
org.json.JSON.typeMismatch(JSON.java:96)
E/DomusLink.DomusHandler(32671): at
org.json.JSONObject.getJSONArray(JSONObject.java:548)
E/DomusLink.DomusHandler(32671): at
com.domuslink.api.DomusHandler.getAliasesByLocation(DomusHandler.java:162)
E/DomusLink.DomusHandler(32671): at
com.domuslink.api.DomusAsyncTask.doInBackground(DomusAsyncTask.java:116)
E/DomusLink.DomusHandler(32671): at
com.domuslink.api.DomusAsyncTask.doInBackground(DomusAsyncTask.java:1)
E/DomusLink.DomusHandler(32671): at
android.os.AsyncTask$2.call(AsyncTask.java:185)
E/DomusLink.DomusHandler(32671): at
java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:306)
E/DomusLink.DomusHandler(32671): at
java.util.concurrent.FutureTask.run(FutureTask.java:138)
E/DomusLink.DomusHandler(32671): at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1088)
E/DomusLink.DomusHandler(32671): at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:581)
E/DomusLink.DomusHandler(32671): at
java.lang.Thread.run(Thread.java:1019)
E/DomusLink(32671): InitializeFloorPlan - Exception - showing settings
dialog
E/DomusLink(32671): org.json.JSONException: Value null at unknown of
What is the expected output? What do you see instead?
No error should occur on android and the aliasmap should be rewritten with the
old aliases removed.
Please use labels and text to provide additional information.
Original issue reported on code.google.com by bwsamuels@gmail.com on 15 Jun 2011 at 1:38
Original issue reported on code.google.com by
bwsamuels@gmail.com
on 15 Jun 2011 at 1:38