search

chaosbastler / opentraining

Android App for planing your fitness training.
GNU General Public License v3.0
80 stars 57 forks source link

IllegalArgumentException causes crash in FExListActivity #33

Closed chaosbastler closed 10 years ago

chaosbastler commented 10 years ago

java.lang.RuntimeException: Unable to start activity ComponentInfo{de.skubware.opentraining/de.skubware.opentraining.activity.start_training.FExListActivity}: java.lang.IllegalArgumentException: Entry not contained. at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2305) at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2359) at android.app.ActivityThread.access$700(ActivityThread.java:165) at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1326) at android.os.Handler.dispatchMessage(Handler.java:99) at android.os.Looper.loop(Looper.java:137) at android.app.ActivityThread.main(ActivityThread.java:5455) at java.lang.reflect.Method.invokeNative(Native Method) at java.lang.reflect.Method.invoke(Method.java:525) at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1187) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1003) at dalvik.system.NativeStart.main(Native Method) Caused by: java.lang.IllegalArgumentException: Entry not contained. at de.skubware.opentraining.basic.FitnessExercise.isTrainingEntryFinished(FitnessExercise.java:327) at de.skubware.opentraining.activity.start_training.FExListFragment.setWorkout(FExListFragment.java:135) at de.skubware.opentraining.activity.start_training.FExListActivity.onCreate(FExListActivity.java:81) at android.app.Activity.performCreate(Activity.java:5372) at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1104) at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2267) ... 11 more

App Version: 0.6.2 Android Version: 4.3

chaosbastler commented 10 years ago

Should be fixed with this commit: https://github.com/chaosbastler/opentraining/commit/0e972debf3d15d0e78e340f9d084709efc6c2778

(Could reproduce this bug like described there. Did not realize that there was already an issue for this bug.)