Calling stopManagingCursor() also solved this issue for me. In my onResume(), I was rebuilding the cursor since it was likely data had been added. Needed to add a call to stopManagingCursor() on the current instance before creating the new one. Seems like I should have been doing this all along.
On Mar 18, 12:29 am, Matt M <[email protected]> wrote: > I had the same error as well. startManagingCursor() was used in > Activity A which launched Activity B. When Activity B was saved and > Activity A returned to the forefront the app force closed. Calling > stopManagingCursor() in Activity A solved it. > > Obviously my fault for not reading enough, but when I was learning the > Android SDK and reading the dev guides I remember learning you should > use startManagingCursor() so that the Cursor will be managed by the > OS, implying nothing else was needed. Interesting that is not so! > > Matt. > > On Mar 3, 10:09 am, al <[email protected]> wrote: > > > > > > > > > I saw the same error. In my case, I told the activity to manage acursor > > (Activity.startManagingCursor(cursor) and later on replaced thecursor > > with > > a new one due to changes in my filter settings without stopping > > themanagement > > of the previouscursor(i.e. without calling > > Activity.stopManagingCursor(cursor)). > > performRestart() then tried to requery the old and already closedcursor. > > > Maybe, you forgot stopManagingCursor() too? -- 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
