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.
@andfan22 - I am seeing the same thing. I've been able to get past it,
but only by comment out all code using FilterQueryProvider. I've tried
all I can think of to manage the lifecycle, but can't get it right.
Are you using FilterQueryProvider? I see that they are mapping the 2.x
calls into 3.0
2 matches
Mail list logo
