IllegalStateException while scrolling while updating about android-amazing-listview

[GoogleCodeExporter]

Wrapping the adding/updating code in PostExecute in runOnUiThread has no effect

Original comment by [email protected] on 22 Sep 2012 at 5:29

[GoogleCodeExporter]

Calling listView.requestLayout instead of notifyDataSetChanged fixes the problem

Original comment by [email protected] on 22 Sep 2012 at 6:33

[GoogleCodeExporter]

listView.requestLayout this solve the problem but still y its not working for 
notifyDataSetChanged .

Original comment by [email protected] on 11 Dec 2012 at 3:49

[GoogleCodeExporter]

I am experiencing the same issue, and even forcing listView.requestLayout 
resolves the issue.  I'm testing on a Nexus 7 tablet with Android 4.2.  If I 
scroll up and down while my AsyncTask is grabbing the next chunk of data, the 
app crashes as soon as the data adapter is updated with the new elements.  The 
adapter update is called from my AsyncTask.onPostExecute, and I am calling 
notifyDatasetChanged() right after the data is updated. I have removed the 
loading view so the app won't crash, and replaced it with a loading view drawn 
on top of the listview instead.  It would be good to get a resolution for this 
though.  The footer view loading indicator is nicer than my solution.

Original comment by [email protected] on 30 Jan 2013 at 2:25

[GoogleCodeExporter]

I think this issues stems from the fact that getAdapter is returning the 
AmazingAdapter instead of the wrapped HeaderListViewAdapter causing a 
difference in count at times.  I simply removed the getAdapter method from 
AmazingListView and haven't got the exception since.

Original comment by [email protected] on 20 Mar 2013 at 8:30

[GoogleCodeExporter]

Confirms removing getAdapter in AmazingListView solves this annoying bug. 

Original comment by [email protected] on 25 May 2013 at 10:44

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Confirmed removing getAdapter in AmazingListView solves this annoying bug. 

Original comment by [email protected] on 5 Aug 2013 at 3:25

[GoogleCodeExporter]

Confirmed removing getAdapter in AmazingListView solves this annoying bug. 

Original comment by [email protected] on 21 Aug 2013 at 8:07

[GoogleCodeExporter]

Confirmed removing getAdapter in AmazingListView solves this annoying bug.  =)

Original comment by [email protected] on 24 Aug 2013 at 3:25

[GoogleCodeExporter]

Damn it! I wish i come here earlier!

Confirmed removing getAdapter in AmazingListView solves this annoying bug.

Original comment by [email protected] on 31 Oct 2013 at 8:54

[GoogleCodeExporter]

Confirmed removing getAdapter in AmazingListView solves this annoying bug.

Original comment by [email protected] on 3 Dec 2013 at 8:49

[GoogleCodeExporter]

Confirmed removing getAdapter in AmazingListView solves this annoying bug.

Original comment by [email protected] on 6 Dec 2013 at 11:26

[GoogleCodeExporter]

Confirmed removing getAdapter in AmazingListView solves this annoying bug.

Original comment by [email protected] on 9 Dec 2013 at 1:17

[GoogleCodeExporter]

Thanks a lost. I spent hours to get it works and finally found this blessing 
solution to fix issue. 

Original comment by [email protected] on 21 Dec 2013 at 5:16

[GoogleCodeExporter]

That s the solution!!!!!!!!!! Cheeeeerss!!

Original comment by [email protected] on 26 Jan 2014 at 5:03

[GoogleCodeExporter]

That's the Solution!!!! Gracias xD

Original comment by [email protected] on 16 Mar 2014 at 9:14

[GoogleCodeExporter]

Confirmed removing getAdapter in AmazingListView solves this annoying bug.

Original comment by [email protected] on 4 Jun 2014 at 11:52