[android-developers] Re: Scenario where initLoader() does not call onLoadFinished()

2011-10-14 Thread Jeremy Drake
On Oct 14, 7:01 am, Mark Murphy mmur...@commonsware.com wrote: I can definitely reproduce the problem. It feels like a bug with the Android Compatibility Library. If I switch your sample to use API Level 11 and the built-in fragment implementation, it works successfully, at least in the

[android-developers] Re: Scenario where initLoader() does not call onLoadFinished()

2011-10-10 Thread Jeremy Drake
This sounds suspiciously like the issue I am having http://groups.google.com/group/android-developers/browse_thread/thread/ca3a0c174d284263 I was able to reproduce the bug with pushing a new activity in my own app, which uses an AsyncTaskLoader instead of a CursorLoader. Hopefully somebody

[android-developers] lifetime issues with loaders created from fragments with setRetainInstance(true)

2011-10-07 Thread Jeremy Drake
Hello, I am currently working on a tab-based app. I am using Fragments for the tabs, and in some of these fragments I am using a Loader to perform background loading of data from the internet. This seems to currently be the most recommended way to go. In order to prevent the data from