I hit the same exception. From reading about SQLite it appears to be creating separate database connections from two different threads can lead to this. I'm not sure if that's the case, but from the previous poster talking about posting the events at a later time I could see that might be.
While catching the exception at least prevents the app from crashing, it means that some small percentage of events may go unreported which is not all that great either. Unfortunately I think the fix probably has to be done within the Google Analystics sdk itself. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
