I'm actually not calling any AsyncTasks at all in any part of the application *yet* and thats why the error was confusing me. That exception appears to be inside the Android API and popped up when I made the provider multiprocess (via the manifest).
When you have that setting true, you are essentially telling the OS that it can create threads as needed for the provider, but the new threads don't have a proper environment. So, my guess its a bug in android, but I never had the time to go and try and find out if that is the case or not. I can tell you it was happening in ICE but not JB, which makes me think it was eventually fixed. - Brill On Tuesday, December 18, 2012 5:25:34 PM UTC-5, Jonathan S wrote: > > I am wondering why you are calling AsyncTask in SyncAdapter or > ContentResolver? It is very odd. AsyncTask supposed to do run CPU heavy > tasks on background then update it to UI threads. > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
