Obi and Eric got this on first load. I think this is because they had installed old APK and the database conflicted. Would be interesting to try to replicate this by installing old APK and then installing new APK.
Perhaps we could handle failures to load the database and present a more understandable error. Since we don't support migrations yet, we wouldn't have any option other than offering to delete the database and start over ...
