Android index out of bounds error with no application code in stack trace

Question

This is the stack trace:

java.lang.IndexOutOfBoundsException: Invalid index 0, size is 0
    at java.util.ArrayList.throwIndexOutOfBoundsException(ArrayList.java:257)
    at java.util.ArrayList.get(ArrayList.java:311)
    at android.widget.HeaderViewListAdapter.isEnabled(HeaderViewListAdapter.java:164)
    at android.widget.ListView.dispatchDrawWithExcessScroll_Default(ListView.java:3354)
    at android.widget.ListView.dispatchDraw(ListView.java:3054)
    at android.view.View.draw(View.java:6936)
    at android.widget.AbsListView.draw(AbsListView.java:3022)
    at android.view.ViewGroup.drawChild(ViewGroup.java:1646)
    at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1373)
    at android.view.View.draw(View.java:6936)
    at android.view.ViewGroup.drawChild(ViewGroup.java:1646)
    at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1373)
    at android.view.ViewGroup.drawChild(ViewGroup.java:1644)
    at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1373)
    at android.view.ViewGroup.drawChild(ViewGroup.java:1644)
    at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1373)
    at android.view.ViewGroup.drawChild(ViewGroup.java:1644)
    at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1373)
    at android.view.ViewGroup.drawChild(ViewGroup.java:1644)
    at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1373)
    at android.view.ViewGroup.drawChild(ViewGroup.java:1644)
    at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1373)
    at android.view.ViewGroup.drawChild(ViewGroup.java:1644)
    at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1373)
    at android.view.ViewGroup.drawChild(ViewGroup.java:1644)
    at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1373)
    at android.view.View.draw(View.java:6936)
    at android.view.ViewGroup.drawChild(ViewGroup.java:1646)
    at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1373)
    at android.view.ViewGroup.drawChild(ViewGroup.java:1644)
    at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1373)
    at android.view.View.draw(View.java:6936)
    at android.widget.FrameLayout.draw(FrameLayout.java:357)
    at com.android.internal.policy.impl.PhoneWindow$DecorView.draw(PhoneWindow.java:1904)
    at android.view.ViewRoot.draw(ViewRoot.java:1527)
    at android.view.ViewRoot.performTraversals(ViewRoot.java:1263)
    at android.view.ViewRoot.handleMessage(ViewRoot.java:1865)
    at android.os.Handler.dispatchMessage(Handler.java:99)
    at android.os.Looper.loop(Looper.java:123)
    at android.app.ActivityThread.main(ActivityThread.java:3687)
    at java.lang.reflect.Method.invokeNative(Native Method)
    at java.lang.reflect.Method.invoke(Method.java:507)
    at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:842)
    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:600)
    at dalvik.system.NativeStart.main(Native Method)

I have absolutely no idea how to reproduce this error. I've tried randomly click at every ListView on my application and was never able to reproduce this error.

This only happened after the application was shipped to the market. I've never seen this error before.

The worst part is that it has no code from my application so I don't even know what the user was doing when this happened.

Did anyone ever see this kind of error?

Does anyone have a clue where to start fixing this?

if you do not have any code how do you plan to debug and fix it. without a code sample it is difficult to solve a array out of bound exception. — medampudi, Nov 24 '11 at 12:02
I have the code... the stack trace doesn't tell me WHERE in the code. — Draiken, Nov 24 '11 at 17:47
you are using a table/an arrayList right... is it all good there... — medampudi, Nov 24 '11 at 18:24

score 15 · Answer 1 · answered Jan 05 '15 at 23:17

I also ran into this same exception on a Nexus 5 running Lollipop. It would occur if I:

unplugged the device while a list is shown
let the device fall asleep
plugged the device back in, causing the list contents to be refreshed

Adding a dummy footer didn't fix it, it just changed the error to Invalid index 1, size is 1 :) ...but thanks to @AlexD I had a clue of where to look for workarounds.

In my case calling list.setFooterDividersEnabled(false) after the ListView is created successfully prevents the crash from occurring.

My nexus 5 has the same problem. – wangqi060934 Oct 22 '15 at 03:14 — wangqi060934, Oct 22 '15 at 03:14

AlexD · Answer 2 · 2012-10-16T05:43:11.733

12

I've got the same error sometime when listview is empty. After looking at the source code I've found the line that crashes:

return mFooterViewInfos.get(adjPosition - adapterCount).isSelectable

As you can see there's no check if mFooterViewInfos is empty, so my workaround for this issue is just adding a dummy footer:

list.addFooterView(new View(context, null, false));

edited Oct 16 '12 at 05:43

answered Jul 13 '12 at 10:30

AlexD

1,021
9
6

4

did you mean `list.addFooterView(new View(ctx), null, false);` – tomash Dec 29 '12 at 22:44

score 5 · Accepted Answer · edited May 23 '17 at 11:54

5

If you're running this on a Samsung phone, please have a look at this StackOverflow Q&A:

ListView random IndexOutOfBoundsException on Froyo

edited May 23 '17 at 11:54

Community

1
1

answered Dec 20 '11 at 20:44

igorsales

612
6
8

score 1 · Answer 4 · answered Feb 11 '15 at 20:25

Maybe a litle bit late but I think i found workaround for this. The think is to remove headerView/footerView (depending on what you use) before leaving fragment/activity:

public View onCreateView(LayoutInflater inflater, ViewGroup container, Bundle savedInstanceState) {
        ....
        getListView().addHeaderView(mHeaderView);
}


public void onDestroyView() {
    super.onDestroyView();
    if (getListView().getHeaderViewsCount() > 0) {
        getListView().removeHeaderView(mHeaderView);
    }
}

score 0 · Answer 5 · answered Nov 24 '11 at 12:08

0

Maybe your activity gets killed and then recreated (such as when screen orientation changes) so your array is being initialized to zero elements and yet some other part of your program don't know about that and expect that array to have some elements.

answered Nov 24 '11 at 12:08

Alexander Kulyakhtin

47,782
38
107
158

Our app is locked on portrait orientation, so it cannot be this :( – Draiken Nov 24 '11 at 17:48
Well yes but maybe still somehow your activity gets killed and then recreated. You can put traces in all your onResume(), onPause() etc... and wherever your array changes – Alexander Kulyakhtin Nov 24 '11 at 19:02
Yeah I guess I am gonna have to do it. Thought this could at least be a more common issue. I have tons of activities and lists... oh well. – Draiken Nov 24 '11 at 20:31

Android index out of bounds error with no application code in stack trace

5 Answers5

Linked