IssueTracker

Having a similar problem, are we missing something? :)

Did anyone find a solution for this?
(except calling forceLoad())

[Comment deleted]

Loaders are used extensively in Android 3.0, so I doubt there is such a problem.  Please look at the fragment static library, it also includes an implementation of loaders for pre-HC platforms.  In there you can look at the CursorLoader to see how it is implemented on top of AsyncTaskLoader.  Do the same thing as it.

I just checked the CursorLoader from the static library.
It seems we have to implements some methods, one of them being onStartLoading(), that actually calls forceLoad() the first time:

protected void onStartLoading() {
    if (mCursor != null) {
        deliverResult(mCursor);
    }
    if (takeContentChanged() || mCursor == null) {
        forceLoad();
    }
}

Thanks.

Here is a nice little class that basically does what CursorLoader does but in a generic way.

Dianne: Can the docs får AsyncTaskLoader be clearer about how to handle this?

onStartLoading() is called in two places:
1. LoaderManagerImpl.doStart()->LoaderInfo.start(), which will happen when the hosting fragment is started.
2. LoaderManagerImpl.installLoader(LoaderInfo)->if the hosting fragment is started, call LoaderInfo.start().

So basically, your custom class extending AsyncTaskLoader will have to override onStartLoading(), and call forceLoad() within when necessary.

Loader::startLoading() will be called when the hosting fragment is started, and your onStartLoading() will be called as consequence.

Thank you for your feedback. We assure you that we are doing our best to address the issue reported, however our product team has shifted work priority that doesn't include this issue. For now, we will be closing the issue as won't fix obsolete. If this issue currently still exists, we request that you log a new issue along with latest bug report here https://goo.gl/TbMiIO.