tobbentm / hig-timeedit-reader Goto Github PK

java.lang.RuntimeException: An error occured while executing doInBackground()
at android.os.AsyncTask$3.done(AsyncTask.java:299)
at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:352)
at java.util.concurrent.FutureTask.setException(FutureTask.java:219)
at java.util.concurrent.FutureTask.run(FutureTask.java:239)
at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:230)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1080)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:573)
at java.lang.Thread.run(Thread.java:841)
Caused by: java.lang.NullPointerException
at android.database.sqlite.SQLiteOpenHelper.getDatabaseLocked(SQLiteOpenHelper.java:224)
at android.database.sqlite.SQLiteOpenHelper.getWritableDatabase(SQLiteOpenHelper.java:164)
at com.tobbentm.higreader.db.DSLectures.open(DSLectures.java:45)
at com.tobbentm.higreader.db.DBUpdate.doInBackground(DBUpdate.java:46)
at com.tobbentm.higreader.db.DBUpdate.doInBackground(DBUpdate.java:15)
at android.os.AsyncTask$2.call(AsyncTask.java:287)
at java.util.concurrent.FutureTask.run(FutureTask.java:234)
... 4 more

No intensions of creating a special interface for this, other than to provide an in-app webview to Feide login and timeedit reservations.

WIP

In HiG-TimeEdit-Reader/Network.java you aren't escaping illigal characters. You commented that you're aware of it but haven't done anything about it, it's actually quite trivial to solve.

You can solve this rather easily by properly escaping the GET parameters.

Direct SQLite communication is a headache. A content provider will also make loaders easier to implement.

Wanted settings:

Timespan of timetable (default: 14 days)
Size of recent list (default: 4)

..more?

Whenever more than one is active (keyguard and desktop).
WIP