Loader restarts on orientation change
<p>In the Android documentation for Loaders found at <a href="http://developer.android.com/guide/components/loaders.html" rel="nofollow">http://developer.android.com/guide/components/loaders.html</a> it says one of the properties of loaders is that:</p>

<blockquote>
  <p>They automatically reconnect to the last loader's cursor when being recreated after a configuration change. Thus, they don't need to re-query their data.</p>
</blockquote>

<p>The following code does not seem to mirror that behaviour, a new Loader is created an finishes querying the ContentResolver, then I rotate the screen and the Loader is re-created!</p>

<pre><code>public class ReportFragment extends Fragment implements LoaderCallbacks&lt;Cursor&gt; {

    @Override
    public void onCreate(Bundle savedInstanceState) {
        super.onCreate(savedInstanceState);
        getLoaderManager().initLoader(1, null, this);
    }

    @Override
    public View onCreateView(LayoutInflater inflater, ViewGroup container,
            Bundle savedInstanceState) {
        View v = inflater.inflate(R.layout.fragment_report, container, false);
        return v;
    }

    public Loader&lt;Cursor&gt; onCreateLoader(int arg0, Bundle arg1) {
        Log.d("TEST", "Creating loader");
        return new CursorLoader(getActivity(), ResourcesContract.Reports.CONTENT_URI, null, null, null, null);
    }

    public void onLoadFinished(Loader&lt;Cursor&gt; arg0, Cursor arg1) {
        Log.d("TEST", "Load finished");
    }

    public void onLoaderReset(Loader&lt;Cursor&gt; arg0) {

    }

}
</code></pre>

<p>Here is the output from my logcat:</p>

<pre><code>08-17 16:49:54.474: D/TEST(1833): Creating loader
08-17 16:49:55.074: D/TEST(1833): Load finished
*Here I rotate the screen*
08-17 16:50:38.115: D/TEST(1833): Creating loader
08-17 16:50:38.353: D/TEST(1833): Load finished
</code></pre>

<p>Any idea what I'm doing wrong here?</p>

<p><strong>EDIT:</strong></p>

<p>I should note that I'm building to Android Google API's version 8, and using the v4 support library. </p>

<p><strong>2nd EDIT:</strong></p>

<p>This is most likely due to a bug in the support library, take a look at this bug submission if you want further information:</p>

<p><a href="http://code.google.com/p/android/issues/detail?id=20791&amp;can=5&amp;colspec=ID%20Type%20Status%20Owner%20Summary%20Stars" rel="nofollow">http://code.google.com/p/android/issues/detail?id=20791&amp;can=5&amp;colspec=ID%20Type%20Status%20Owner%20Summary%20Stars</a></p>
