Loader doesn't start after calling initLoader()?

Question

I have a fragment, and want to start a loader when a button is clicked:

public class MyFragment extends Fragment {

    public void onActivityCreated() {
        super.onActivityCreated();

        Button btn = ...;
        btn.setOnClickListener(new OnClickListener() {
            public void onClick(View view) {
                getLoaderManager().initLoader(500, null, mMyCallback);
            }
        });
    }  

    private LoaderManager.LoaderCallbacks<String> mMyCallback = new  LoaderManager.LoaderCallbacks<String>() {

        @Override
        public Loader<String> onCreateLoader(int arg0, Bundle arg1) {
            Log.e(TAG, "LoaderCallback.onCreateLoader().");
            return new MyLoader(getActivity());
        }
    }
}

public class MyLoader extends AsyncTaskLoader<String> {
    public MyLoader(Context context) {
        super(context);
    }

    @Override
    public String loadInBackground() {
        Log.e(TAG, "Hi, running.");
        return "terrific.";
    }
}

After clicking the button, I can see my callback's onCreateLoader method called, but the created loader never actually starts. Do we need to call forceLoad() on the loader itself to get it to actually start? None of the sample posts do this,

Thanks

score 32 · Answer 1 · answered Aug 23 '12 at 16:29

32

You need to implement onStartLoading() and call forceLoad() somewhere in the method.

See this post for more information: Implementing Loaders (part 3)

answered Aug 23 '12 at 16:29

Alex Lockwood

83,063
39
206
250

What should i actually implent in forceLoad() method? – Manikanta Ottiprolu Dec 02 '14 at 06:46
@Manikanta My answer says you should _call_ `forceLoad()`, not implement it. – Alex Lockwood Dec 02 '14 at 06:52
Actually i want to update my ListView continuously from SQLiteOpenHelper, I don't know What way is preferable. Can you please suggest any way? – Manikanta Ottiprolu Dec 02 '14 at 07:18

score 6 · Answer 2 · edited May 23 '17 at 11:47

6

In my experience it never worked unless I used forceLoad().

You may find the answer to this previous question helpful: Loaders in Android Honeycomb

edited May 23 '17 at 11:47

Community

1
1

answered Apr 25 '12 at 19:15

nohawk

61
1

score 4 · Answer 3 · edited Mar 07 '15 at 10:20

Three important points regarding Loaders are:

Always Use forceLoad() method while initialising Loaders. For Example:

getLoaderManager().initLoader(500, null, mMyCallback).forceLoad();

Always implement onStartLoading(). This function will automatically be called by LoaderManager when the associated fragment/activity is being started.
Make sure the ID of the loader is unique otherwise new Loader will not be called.

If there is still a problem you can check the state of loader by calling the isStarted() method.

score 2 · Answer 4 · answered May 01 '12 at 21:08

2

You need to keep a reference to the instance of the loader you create in the method onCreateLoader. Then, to refresh it, call yourLoader.onContentChanged();

answered May 01 '12 at 21:08

Snicolas

37,840
15
114
173

OMG, you literally just fixed my entire problem. – Alex Mar 22 '13 at 23:03

score 2 · Answer 5 · answered Oct 17 '14 at 15:23

2

If you have more than 1 loader in the same activity, make sure their id differs. I lost few hours to figure it out :)

answered Oct 17 '14 at 15:23

Golan Shay

1,250
18
15

Loader doesn't start after calling initLoader()?

5 Answers5