I had the same problem with managed Cursors when updating my project for honeycomb.
One solution was to not close the managed cursor myself. In other words if your managed cursor is called "cur" than do not ever call cur.close() in your code. Let the system manage the managed cursor and everything will be fine. A better solution is to replace managedCursor with an normal unmanaged cursor and continue to call cur.Close() yourself. I suspect that this is a bug that was introduced in honeycomb in that it appears that the system is trying to access some property of the managed cursor without first checking to see if it is closed, and since we closed it ourselves it is in fact closed. -- 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
