search

AndreiLux / Synapse

Please read the introduction to create a working backend:
https://github.com/AndreiLux/Synapse/wiki
Other
38 stars 22 forks source link

Crash on Synapse start #25

Open ffolkes opened 10 years ago

ffolkes commented 10 years ago

Not sure what causes this, but it's consistently crashing after I added a new element (checkbox), although it looks like a seekbar caused it.. Anyway, as I suspected, resetting the appdata fixes it.

W/dalvikvm( 5221): threadid=12: thread exiting with uncaught exception (group=0x414e1ba8)
E/AndroidRuntime( 5221): FATAL EXCEPTION: Thread-121
E/AndroidRuntime( 5221): Process: com.af.synapse, PID: 5221
E/AndroidRuntime( 5221): java.lang.ArrayIndexOutOfBoundsException: length=12; index=-1
E/AndroidRuntime( 5221):    at java.util.ArrayList.get(ArrayList.java:310)
E/AndroidRuntime( 5221):    at com.af.synapse.elements.SSeekBar.getView(SSeekBar.java:363)
E/AndroidRuntime( 5221):    at com.af.synapse.MainActivity$TabSectionFragment.prepareView(MainActivity.java:379)
E/AndroidRuntime( 5221):    at com.af.synapse.MainActivity$TabSectionFragment.setArguments(MainActivity.java:399)
E/AndroidRuntime( 5221):    at com.af.synapse.MainActivity$SectionsPagerAdapter.buildFragment(MainActivity.java:252)
E/AndroidRuntime( 5221):    at com.af.synapse.MainActivity$SectionsPagerAdapter.access$800(MainActivity.java:244)
E/AndroidRuntime( 5221):    at com.af.synapse.MainActivity$SectionsPagerAdapter$2.run(MainActivity.java:289)
E/AndroidRuntime( 5221):    at com.af.synapse.utils.NamedRunnable.run(NamedRunnable.java:28)
E/AndroidRuntime( 5221):    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
E/AndroidRuntime( 5221):    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
E/AndroidRuntime( 5221):    at java.lang.Thread.run(Thread.java:841)
W/ActivityManager( 3684):   Force finishing activity com.af.synapse/.MainActivity
AndreiLux commented 10 years ago

If you can reproduce this, please check the actionValueStore for the value of the element that is referenced next time it crashes. I don't see how resetting app data would prevent this from happening...