Cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Fitbit app crash on Xiaomi Mi5

Replies are disabled for this topic. Start a new one or visit our Help Center.

I have a charge2 device. It works fine with my Mi5 phone till yesterday. And the APK version is 2.52 which is the latestone I can find. Now the fitbit apk keep crashing when press weekly exercise button. I captured log as below. would you please double check?

 

07-06 01:12:02.526 2638 7123 D MiuiPerfServiceClient: interceptAndQueuing:2790|com.fitbit.FitbitMobile|698|418|unknown|null
--------- beginning of crash
07-06 01:12:05.942 2790 2790 E AndroidRuntime: FATAL EXCEPTION: main
07-06 01:12:05.942 2790 2790 E AndroidRuntime: Process: com.fitbit.FitbitMobile, PID: 2790
07-06 01:12:05.942 2790 2790 E AndroidRuntime: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.fitbit.FitbitMobile/com.fitbit.runtrack.ui.ExerciseListActivity}: java.lang.IllegalArgumentException: No view found for id 0x7f13057b (com.fitbit.FitbitMobile:id/map) for fragment SupportMapFragment{c754bde #0 id=0x7f13057b}
07-06 01:12:05.942 2790 2790 E AndroidRuntime: at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2688)
07-06 01:12:05.942 2790 2790 E AndroidRuntime: at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2749)
07-06 01:12:05.942 2790 2790 E AndroidRuntime: at android.app.ActivityThread.-wrap12(ActivityThread.java)
07-06 01:12:05.942 2790 2790 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1498)
07-06 01:12:05.942 2790 2790 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:102)
07-06 01:12:05.942 2790 2790 E AndroidRuntime: at android.os.Looper.loop(Looper.java:160)
07-06 01:12:05.942 2790 2790 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:6200)
07-06 01:12:05.942 2790 2790 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
07-06 01:12:05.942 2790 2790 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:874)
07-06 01:12:05.942 2790 2790 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:764)
07-06 01:12:05.942 2790 2790 E AndroidRuntime: Caused by: java.lang.IllegalArgumentException: No view found for id 0x7f13057b (com.fitbit.FitbitMobile:id/map) for fragment SupportMapFragment{c754bde #0 id=0x7f13057b}
07-06 01:12:05.942 2790 2790 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.moveToState(SourceFile:1293)
07-06 01:12:05.942 2790 2790 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.moveFragmentToExpectedState(SourceFile:1528)
07-06 01:12:05.942 2790 2790 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.moveToState(SourceFile:1595)
07-06 01:12:05.942 2790 2790 E AndroidRuntime: at android.support.v4.app.BackStackRecord.executeOps(SourceFile:758)
07-06 01:12:05.942 2790 2790 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.executeOps(SourceFile:2363)
07-06 01:12:05.942 2790 2790 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.executeOpsTogether(SourceFile:2149)
07-06 01:12:05.942 2790 2790 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.optimizeAndExecuteOps(SourceFile:2103)
07-06 01:12:05.942 2790 2790 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.execPendingActions(SourceFile:2013)
07-06 01:12:05.942 2790 2790 E AndroidRuntime: at android.support.v4.app.Fragment.performStart(SourceFile:2214)
07-06 01:12:05.942 2790 2790 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.moveToState(SourceFile:1340)
07-06 01:12:05.942 2790 2790 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.moveFragmentToExpectedState(SourceFile:1528)
07-06 01:12:05.942 2790 2790 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.moveToState(SourceFile:1595)
07-06 01:12:05.942 2790 2790 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.dispatchStart(SourceFile:2907)
07-06 01:12:05.942 2790 2790 E AndroidRuntime: at android.support.v4.app.Fragment.performStart(SourceFile:2224)
07-06 01:12:05.942 2790 2790 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.moveToState(SourceFile:1340)
07-06 01:12:05.942 2790 2790 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.moveFragmentToExpectedState(SourceFile:1528)
07-06 01:12:05.942 2790 2790 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.moveToState(SourceFile:1595)
07-06 01:12:05.942 2790 2790 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.dispatchStart(SourceFile:2907)
07-06 01:12:05.942 2790 2790 E AndroidRuntime: at android.support.v4.app.FragmentController.dispatchStart(SourceFile:212)
07-06 01:12:05.942 2790 2790 E AndroidRuntime: at android.support.v4.app.FragmentActivity.onStart(SourceFile:613)
07-06 01:12:05.942 2790 2790 E AndroidRuntime: at android.support.v7.app.AppCompatActivity.onStart(SourceFile:178)
07-06 01:12:05.942 2790 2790 E AndroidRuntime: at android.app.Instrumentation.callActivityOnStart(Instrumentation.java:1249)
07-06 01:12:05.942 2790 2790 E AndroidRuntime: at android.app.Activity.performStart(Activity.java:6762)
07-06 01:12:05.942 2790 2790 E AndroidRuntime: at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2651)
07-06 01:12:05.942 2790 2790 E AndroidRuntime: ... 9 more
07-06 01:12:06.233 1430 25548 I chatty : uid=1000 system_server expire 1 line
07-06 01:12:06.934 1430 1490 I chatty : uid=1000(system) batterystats-sy expire 1 line
07-06 01:12:07.043 3095 4294 D PowerKeeper.Sensor: setUidState, uid = 10055 allow = false
07-06 01:12:07.049 3095 4318 D PowerKeeper.AppStandby: setUidState, uid = 10055 allow = false
07-06 01:12:07.737 1430 1507 I chatty : uid=1000(system) android.io expire 2 lines
07-06 01:12:08.107 1430 1626 I chatty : uid=1000(system) InputReader expire 8 lines
07-06 01:12:08.615 1430 20411 I chatty : uid=1000(system) Binder:1430_18 expire 1 line
07-06 01:12:09.167 24486 24486 W ViewRootImpl[MainTabActivity]: Cancelling event due to no window focus: KeyEvent { action=ACTION_UP, keyCode=KEYCODE_BACK, scanCode=139, metaState=0, flags=0x68, repeatCount=0, eventTime=11130817, downTime=11130780, deviceId=8, source=0x101 }
07-06 01:12:09.167 24486 24486 W ViewRootImpl[MainTabActivity]: Cancelling event due to no window focus: KeyEvent { action=ACTION_UP, keyCode=KEYCODE_BACK, scanCode=139, metaState=0, flags=0x68, repeatCount=0, eventTime=11130817, downTime=11130780, deviceId=8, source=0x101 }
07-06 01:12:09.167 24486 24486 W ViewRootImpl[MainTabActivity]: Cancelling event due to no window focus: KeyEvent { action=ACTION_UP, keyCode=KEYCODE_BACK, scanCode=139, metaState=0, flags=0x68, repeatCount=0, eventTime=11130817, downTime=11130780, deviceId=8, source=0x101 }
07-06 01:12:09.193 24486 24486 W ViewRootImpl[MainTabActivity]: Cancelling event due to no window focus: KeyEvent { action=ACTION_UP, keyCode=KEYCODE_BACK, scanCode=139, metaState=0, flags=0x68, repeatCount=0, eventTime=11130817, downTime=11130780, deviceId=8, source=0x101 }
07-06 01:12:09.194 24486 24486 W ViewRootImpl[MainTabActivity]: Cancelling event due to no window focus: KeyEvent { action=ACTION_UP, keyCode=KEYCODE_BACK, scanCode=139, metaState=0, flags=0x68, repeatCount=0, eventTime=11130817, downTime=11130780, deviceId=8, source=0x101 }
07-06 01:12:09.194 24486 24486 W ViewRootImpl[MainTabActivity]: Cancelling event due to no window focus: KeyEvent { action=ACTION_UP, keyCode=KEYCODE_BACK, scanCode=139, metaState=0, flags=0x68, repeatCount=0, eventTime=11130817, downTime=11130780, deviceId=8, source=0x101 }
07-06 01:12:09.194 24486 24486 W ViewRootImpl[MainTabActivity]: Cancelling event due to no window focus: KeyEvent { action=ACTION_UP, keyCode=KEYCODE_BACK, scanCode=139, metaState=0, flags=0x68, repeatCount=0, eventTime=11130817, downTime=11130780, deviceId=8, source=0x101 }
07-06 01:12:09.194 24486 24486 W ViewRootImpl[MainTabActivity]: Cancelling event due to no window focus: KeyEvent { action=ACTION_UP, keyCode=KEYCODE_BACK, scanCode=139, metaState=0, flags=0x68, repeatCount=0, eventTime=11130817, downTime=11130780, deviceId=8, source=0x101 }
07-06 01:12:09.194 24486 24486 W ViewRootImpl[MainTabActivity]: Cancelling event due to no window focus: KeyEvent { action=ACTION_UP, keyCode=KEYCODE_BACK, scanCode=139, metaState=0, flags=0x68, repeatCount=0, eventTime=11130817, downTime=11130780, deviceId=8, source=0x101 }
07-06 01:12:12.494 2638 7123 D MiuiPerfServiceClient: interceptAndQueuing:25559|com.fitbit.FitbitMobile|637|385|unknown|null
07-06 01:12:14.634 2638 2661 D MiuiPerfServiceClient: interceptAndQueuing:25559|com.fitbit.FitbitMobile|188|89|unknown|null
07-06 01:12:19.273 2638 2678 D MiuiPerfServiceClient: interceptAndQueuing:25559|com.fitbit.FitbitMobile|253|196|unknown|null
07-06 01:12:24.431 1430 1485 I chatty : uid=1000(system) ActivityManager expire 15 lines
07-06 01:12:36.915 1430 20412 I chatty : uid=1000(system) Binder:1430_19 expire 5 lines
07-06 01:12:39.089 1430 2873 I chatty : uid=1000(system) Binder:1430_C expire 11 lines
07-06 01:12:39.091 2638 7123 D MiuiPerfServiceClient: interceptAndQueuing:25559|com.fitbit.FitbitMobile|180|107|unknown|null
07-06 01:12:40.788 1430 20410 I chatty : uid=1000(system) Binder:1430_17 expire 3 lines
07-06 01:12:40.789 2638 2661 D MiuiPerfServiceClient: interceptAndQueuing:25559|com.fitbit.FitbitMobile|172|106|unknown|null
07-06 01:12:56.255 1430 3241 I chatty : uid=1000(system) Binder:1430_12 expire 6 lines
07-06 01:12:56.509 25559 25559 E AndroidRuntime: FATAL EXCEPTION: main
07-06 01:12:56.509 25559 25559 E AndroidRuntime: Process: com.fitbit.FitbitMobile, PID: 25559
07-06 01:12:56.509 25559 25559 E AndroidRuntime: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.fitbit.FitbitMobile/com.fitbit.runtrack.ui.ExerciseListActivity}: java.lang.IllegalArgumentException: No view found for id 0x7f13057b (com.fitbit.FitbitMobile:id/map) for fragment SupportMapFragment{f4b7d5f #0 id=0x7f13057b}
07-06 01:12:56.509 25559 25559 E AndroidRuntime: at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2688)
07-06 01:12:56.509 25559 25559 E AndroidRuntime: at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2749)
07-06 01:12:56.509 25559 25559 E AndroidRuntime: at android.app.ActivityThread.-wrap12(ActivityThread.java)
07-06 01:12:56.509 25559 25559 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1498)
07-06 01:12:56.509 25559 25559 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:102)
07-06 01:12:56.509 25559 25559 E AndroidRuntime: at android.os.Looper.loop(Looper.java:160)
07-06 01:12:56.509 25559 25559 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:6200)
07-06 01:12:56.509 25559 25559 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
07-06 01:12:56.509 25559 25559 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:874)
07-06 01:12:56.509 25559 25559 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:764)
07-06 01:12:56.509 25559 25559 E AndroidRuntime: Caused by: java.lang.IllegalArgumentException: No view found for id 0x7f13057b (com.fitbit.FitbitMobile:id/map) for fragment SupportMapFragment{f4b7d5f #0 id=0x7f13057b}
07-06 01:12:56.509 25559 25559 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.moveToState(SourceFile:1293)
07-06 01:12:56.509 25559 25559 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.moveFragmentToExpectedState(SourceFile:1528)
07-06 01:12:56.509 25559 25559 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.moveToState(SourceFile:1595)
07-06 01:12:56.509 25559 25559 E AndroidRuntime: at android.support.v4.app.BackStackRecord.executeOps(SourceFile:758)
07-06 01:12:56.509 25559 25559 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.executeOps(SourceFile:2363)
07-06 01:12:56.509 25559 25559 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.executeOpsTogether(SourceFile:2149)
07-06 01:12:56.509 25559 25559 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.optimizeAndExecuteOps(SourceFile:2103)
07-06 01:12:56.509 25559 25559 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.execPendingActions(SourceFile:2013)
07-06 01:12:56.509 25559 25559 E AndroidRuntime: at android.support.v4.app.Fragment.performStart(SourceFile:2214)
07-06 01:12:56.509 25559 25559 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.moveToState(SourceFile:1340)
07-06 01:12:56.509 25559 25559 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.moveFragmentToExpectedState(SourceFile:1528)
07-06 01:12:56.509 25559 25559 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.moveToState(SourceFile:1595)
07-06 01:12:56.509 25559 25559 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.dispatchStart(SourceFile:2907)
07-06 01:12:56.509 25559 25559 E AndroidRuntime: at android.support.v4.app.Fragment.performStart(SourceFile:2224)
07-06 01:12:56.509 25559 25559 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.moveToState(SourceFile:1340)
07-06 01:12:56.509 25559 25559 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.moveFragmentToExpectedState(SourceFile:1528)
07-06 01:12:56.509 25559 25559 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.moveToState(SourceFile:1595)
07-06 01:12:56.509 25559 25559 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.dispatchStart(SourceFile:2907)
07-06 01:12:56.509 25559 25559 E AndroidRuntime: at android.support.v4.app.FragmentController.dispatchStart(SourceFile:212)
07-06 01:12:56.509 25559 25559 E AndroidRuntime: at android.support.v4.app.FragmentActivity.onStart(SourceFile:613)
07-06 01:12:56.509 25559 25559 E AndroidRuntime: at android.support.v7.app.AppCompatActivity.onStart(SourceFile:178)
07-06 01:12:56.509 25559 25559 E AndroidRuntime: at android.app.Instrumentation.callActivityOnStart(Instrumentation.java:1249)
07-06 01:12:56.509 25559 25559 E AndroidRuntime: at android.app.Activity.performStart(Activity.java:6762)
07-06 01:12:56.509 25559 25559 E AndroidRuntime: at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2651)
07-06 01:12:56.509 25559 25559 E AndroidRuntime: ... 9 more
07-06 01:12:56.514 1430 1461 I chatty : uid=1000(system) Binder:1430_1 expire 3 lines
07-06 01:12:56.559 1430 2878 I chatty : uid=1000(system) Binder:1430_F expire 6 lines
07-06 01:12:56.560 1430 2725 I chatty : uid=1000(system) Binder:1430_8 expire 7 lines
07-06 01:12:56.560 1430 1430 I chatty : uid=1000 system_server expire 38 lines
07-06 01:12:56.583 1430 2833 I chatty : uid=1000(system) Binder:1430_A expire 8 lines
07-06 01:12:56.654 1430 25749 I chatty : uid=1000 system_server expire 1 line
07-06 01:12:57.593 1430 1786 I chatty : uid=1000(system) Binder:1430_3 expire 1 line
07-06 01:12:57.680 1430 20418 I chatty : uid=1000(system) Binder:1430_1F expire 4 lines
07-06 01:12:57.955 1430 1507 I chatty : uid=1000(system) android.io expire 6 lines
07-06 01:12:58.437 1430 20417 I chatty : uid=1000(system) Binder:1430_1E expire 2 lines
07-06 01:12:59.375 1430 20413 I chatty : uid=1000(system) Binder:1430_1A expire 3 lines
07-06 01:12:59.694 1430 1989 I chatty : uid=1000(system) Binder:1430_5 expire 4 lines
07-06 01:12:59.757 1430 1508 I chatty : uid=1000(system) android.display expire 9 lines
07-06 01:13:00.266 1430 2877 I chatty : uid=1000(system) Binder:1430_E expire 3 lines
07-06 01:13:00.267 2638 2678 D MiuiPerfServiceClient: interceptAndQueuing:25755|com.fitbit.FitbitMobile|564|445|unknown|null
07-06 01:13:02.915 2638 7123 D MiuiPerfServiceClient: interceptAndQueuing:25755|com.fitbit.FitbitMobile|217|115|unknown|null
07-06 01:13:02.915 2638 7123 D MiuiPerfServiceClient: interceptAndQueuing:25755|com.fitbit.FitbitMobile|157|137|unknown|null
07-06 01:13:04.563 1430 1626 I chatty : uid=1000(system) InputReader expire 12 lines
07-06 01:13:06.302 25755 25755 E AndroidRuntime: FATAL EXCEPTION: main
07-06 01:13:06.302 25755 25755 E AndroidRuntime: Process: com.fitbit.FitbitMobile, PID: 25755
07-06 01:13:06.302 25755 25755 E AndroidRuntime: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.fitbit.FitbitMobile/com.fitbit.runtrack.ui.ExerciseListActivity}: java.lang.IllegalArgumentException: No view found for id 0x7f13057b (com.fitbit.FitbitMobile:id/map) for fragment SupportMapFragment{2bfeaca #0 id=0x7f13057b}
07-06 01:13:06.302 25755 25755 E AndroidRuntime: at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2688)
07-06 01:13:06.302 25755 25755 E AndroidRuntime: at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2749)
07-06 01:13:06.302 25755 25755 E AndroidRuntime: at android.app.ActivityThread.-wrap12(ActivityThread.java)
07-06 01:13:06.302 25755 25755 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1498)
07-06 01:13:06.302 25755 25755 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:102)
07-06 01:13:06.302 25755 25755 E AndroidRuntime: at android.os.Looper.loop(Looper.java:160)
07-06 01:13:06.302 25755 25755 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:6200)
07-06 01:13:06.302 25755 25755 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
07-06 01:13:06.302 25755 25755 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:874)
07-06 01:13:06.302 25755 25755 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:764)
07-06 01:13:06.302 25755 25755 E AndroidRuntime: Caused by: java.lang.IllegalArgumentException: No view found for id 0x7f13057b (com.fitbit.FitbitMobile:id/map) for fragment SupportMapFragment{2bfeaca #0 id=0x7f13057b}
07-06 01:13:06.302 25755 25755 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.moveToState(SourceFile:1293)
07-06 01:13:06.302 25755 25755 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.moveFragmentToExpectedState(SourceFile:1528)
07-06 01:13:06.302 25755 25755 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.moveToState(SourceFile:1595)
07-06 01:13:06.302 25755 25755 E AndroidRuntime: at android.support.v4.app.BackStackRecord.executeOps(SourceFile:758)
07-06 01:13:06.302 25755 25755 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.executeOps(SourceFile:2363)
07-06 01:13:06.302 25755 25755 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.executeOpsTogether(SourceFile:2149)
07-06 01:13:06.302 25755 25755 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.optimizeAndExecuteOps(SourceFile:2103)
07-06 01:13:06.302 25755 25755 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.execPendingActions(SourceFile:2013)
07-06 01:13:06.302 25755 25755 E AndroidRuntime: at android.support.v4.app.Fragment.performStart(SourceFile:2214)
07-06 01:13:06.302 25755 25755 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.moveToState(SourceFile:1340)
07-06 01:13:06.302 25755 25755 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.moveFragmentToExpectedState(SourceFile:1528)
07-06 01:13:06.302 25755 25755 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.moveToState(SourceFile:1595)
07-06 01:13:06.302 25755 25755 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.dispatchStart(SourceFile:2907)
07-06 01:13:06.302 25755 25755 E AndroidRuntime: at android.support.v4.app.Fragment.performStart(SourceFile:2224)
07-06 01:13:06.302 25755 25755 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.moveToState(SourceFile:1340)
07-06 01:13:06.302 25755 25755 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.moveFragmentToExpectedState(SourceFile:1528)
07-06 01:13:06.302 25755 25755 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.moveToState(SourceFile:1595)
07-06 01:13:06.302 25755 25755 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.dispatchStart(SourceFile:2907)
07-06 01:13:06.302 25755 25755 E AndroidRuntime: at android.support.v4.app.FragmentController.dispatchStart(SourceFile:212)
07-06 01:13:06.302 25755 25755 E AndroidRuntime: at android.support.v4.app.FragmentActivity.onStart(SourceFile:613)
07-06 01:13:06.302 25755 25755 E AndroidRuntime: at android.support.v7.app.AppCompatActivity.onStart(SourceFile:178)
07-06 01:13:06.302 25755 25755 E AndroidRuntime: at android.app.Instrumentation.callActivityOnStart(Instrumentation.java:1249)
07-06 01:13:06.302 25755 25755 E AndroidRuntime: at android.app.Activity.performStart(Activity.java:6762)
07-06 01:13:06.302 25755 25755 E AndroidRuntime: at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2651)
07-06 01:13:06.302 25755 25755 E AndroidRuntime: ... 9 more
07-06 01:13:06.306 1430 2723 I chatty : uid=1000(system) Binder:1430_7 expire 7 lines
07-06 01:13:06.356 1430 2876 I chatty : uid=1000(system) Binder:1430_D expire 3 lines
07-06 01:13:06.394 1430 25902 I chatty : uid=1000 system_server expire 1 line
07-06 01:13:08.983 1430 2870 I chatty : uid=1000(system) Binder:1430_B expire 3 lines
07-06 01:13:09.673 3095 3983 D PowerKeeper.Location: setUidState, uid = 10101 allow = false
07-06 01:13:10.806 1430 2726 I chatty : uid=1000(system) Binder:1430_9 expire 3 lines
07-06 01:13:10.807 2638 2661 D MiuiPerfServiceClient: interceptAndQueuing:25908|com.fitbit.FitbitMobile|551|322|unknown|null
07-06 01:13:16.373 1430 20416 I chatty : uid=1000(system) Binder:1430_1D expire 3 lines
07-06 01:13:16.373 2638 7123 D MiuiPerfServiceClient: interceptAndQueuing:25908|com.fitbit.FitbitMobile|525|228|unknown|null
07-06 01:13:18.470 2638 2661 D MiuiPerfServiceClient: interceptAndQueuing:25908|com.fitbit.FitbitMobile|169|98|unknown|null
07-06 01:13:21.146 1430 1462 I chatty : uid=1000(system) Binder:1430_2 expire 3 lines
07-06 01:13:21.463 1430 20406 I chatty : uid=1000(system) Binder:1430_14 expire 7 lines
07-06 01:13:25.527 2638 2661 D MiuiPerfServiceClient: interceptAndQueuing:25908|com.fitbit.FitbitMobile|356|188|unknown|null
07-06 01:13:44.060 1430 1626 I chatty : uid=1000(system) InputReader expire 20 lines
07-06 01:13:48.136 1430 20407 I chatty : uid=1000(system) Binder:1430_15 expire 2 lines
07-06 01:14:15.360 1430 20409 I chatty : uid=1000(system) Binder:1430_16 expire 2 lines
07-06 01:14:15.592 25908 25908 E AndroidRuntime: FATAL EXCEPTION: main
07-06 01:14:15.592 25908 25908 E AndroidRuntime: Process: com.fitbit.FitbitMobile, PID: 25908
07-06 01:14:15.592 25908 25908 E AndroidRuntime: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.fitbit.FitbitMobile/com.fitbit.runtrack.ui.ExerciseListActivity}: java.lang.IllegalArgumentException: No view found for id 0x7f13057b (com.fitbit.FitbitMobile:id/map) for fragment SupportMapFragment{3d7ecd7 #0 id=0x7f13057b}
07-06 01:14:15.592 25908 25908 E AndroidRuntime: at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2688)
07-06 01:14:15.592 25908 25908 E AndroidRuntime: at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2749)
07-06 01:14:15.592 25908 25908 E AndroidRuntime: at android.app.ActivityThread.-wrap12(ActivityThread.java)
07-06 01:14:15.592 25908 25908 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1498)
07-06 01:14:15.592 25908 25908 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:102)
07-06 01:14:15.592 25908 25908 E AndroidRuntime: at android.os.Looper.loop(Looper.java:160)
07-06 01:14:15.592 25908 25908 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:6200)
07-06 01:14:15.592 25908 25908 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
07-06 01:14:15.592 25908 25908 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:874)
07-06 01:14:15.592 25908 25908 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:764)
07-06 01:14:15.592 25908 25908 E AndroidRuntime: Caused by: java.lang.IllegalArgumentException: No view found for id 0x7f13057b (com.fitbit.FitbitMobile:id/map) for fragment SupportMapFragment{3d7ecd7 #0 id=0x7f13057b}
07-06 01:14:15.592 25908 25908 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.moveToState(SourceFile:1293)
07-06 01:14:15.592 25908 25908 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.moveFragmentToExpectedState(SourceFile:1528)
07-06 01:14:15.592 25908 25908 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.moveToState(SourceFile:1595)
07-06 01:14:15.592 25908 25908 E AndroidRuntime: at android.support.v4.app.BackStackRecord.executeOps(SourceFile:758)
07-06 01:14:15.592 25908 25908 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.executeOps(SourceFile:2363)
07-06 01:14:15.592 25908 25908 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.executeOpsTogether(SourceFile:2149)
07-06 01:14:15.592 25908 25908 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.optimizeAndExecuteOps(SourceFile:2103)
07-06 01:14:15.592 25908 25908 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.execPendingActions(SourceFile:2013)
07-06 01:14:15.592 25908 25908 E AndroidRuntime: at android.support.v4.app.Fragment.performStart(SourceFile:2214)
07-06 01:14:15.592 25908 25908 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.moveToState(SourceFile:1340)
07-06 01:14:15.592 25908 25908 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.moveFragmentToExpectedState(SourceFile:1528)
07-06 01:14:15.592 25908 25908 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.moveToState(SourceFile:1595)
07-06 01:14:15.592 25908 25908 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.dispatchStart(SourceFile:2907)
07-06 01:14:15.592 25908 25908 E AndroidRuntime: at android.support.v4.app.Fragment.performStart(SourceFile:2224)
07-06 01:14:15.592 25908 25908 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.moveToState(SourceFile:1340)
07-06 01:14:15.592 25908 25908 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.moveFragmentToExpectedState(SourceFile:1528)
07-06 01:14:15.592 25908 25908 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.moveToState(SourceFile:1595)
07-06 01:14:15.592 25908 25908 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.dispatchStart(SourceFile:2907)
07-06 01:14:15.592 25908 25908 E AndroidRuntime: at android.support.v4.app.FragmentController.dispatchStart(SourceFile:212)
07-06 01:14:15.592 25908 25908 E AndroidRuntime: at android.support.v4.app.FragmentActivity.onStart(SourceFile:613)
07-06 01:14:15.592 25908 25908 E AndroidRuntime: at android.support.v7.app.AppCompatActivity.onStart(SourceFile:178)
07-06 01:14:15.592 25908 25908 E AndroidRuntime: at android.app.Instrumentation.callActivityOnStart(Instrumentation.java:1249)
07-06 01:14:15.592 25908 25908 E AndroidRuntime: at android.app.Activity.performStart(Activity.java:6762)
07-06 01:14:15.592 25908 25908 E AndroidRuntime: at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2651)
07-06 01:14:15.592 25908 25908 E AndroidRuntime: ... 9 more
07-06 01:14:15.596 1430 1995 I chatty : uid=1000(system) Binder:1430_6 expire 2 lines
07-06 01:14:15.653 1430 2881 I chatty : uid=1000(system) Binder:1430_10 expire 3 lines
07-06 01:14:15.696 1430 26166 I chatty : uid=1000 system_server expire 1 line
07-06 01:14:15.739 2638 2678 D MiuiPerfServiceClient: interceptAndQueuing:2838|com.miui.home|241|173|unknown|null
07-06 01:14:17.355 1430 1485 I chatty : uid=1000(system) ActivityManager expire 11 lines
07-06 01:14:17.433 1430 20411 I chatty : uid=1000(system) Binder:1430_18 expire 4 lines
07-06 01:14:18.340 1430 20415 I chatty : uid=1000(system) Binder:1430_1C expire 2 lines
07-06 01:14:20.257 2638 7123 D MiuiPerfServiceClient: interceptAndQueuing:26176|com.fitbit.FitbitMobile|612|388|unknown|null
07-06 01:14:27.165 2638 2661 D MiuiPerfServiceClient: interceptAndQueuing:26176|com.fitbit.FitbitMobile|237|92|unknown|null

 

 

Moderator edit: updated subject for clarity

Best Answer
0 Votes
9 REPLIES 9

Hello @kingmoon!

 

Thanks for bringing this up. This seems to be happening because the Mi5 is not currently a supported devices. Since the tracker is not supported, issues with the software can absolutely happen and we cannot guarantee that it will work 100% of the time. 

 

If you have any further questions, please let me know.

Lanuza | Community Moderator

Remember to vote for posts that helped you out! Tired of the same workout music? Try a Podcast! 🙂

Best Answer
0 Votes
Will you fix this issue soon? Since this issue was not met in previous APK
version. It's very inconvenient with this crashing

--
BR
Chen Yue
Best Answer
0 Votes

Hello @kingmoon.

 

If the Xiaomi Mi5 is added to the compatibility list, this shouldn't happen anymore. Having said that, we do not have any specific details on when can we expect any specific device to be added. 

 

Thanks for your understanding. If you have any questions or need any help you can let me know.

Lanuza | Community Moderator

Remember to vote for posts that helped you out! Tired of the same workout music? Try a Podcast! 🙂

Best Answer
0 Votes
But this function was ok in the previous version, crash only happened after
upgrade to the latest fitbit APK. Hope you can fix it ASAP, Xiaomi is very
popular in China.

--
BR
Chen Yue
Best Answer
0 Votes

I guarantee this issue is not only on Mi phone, I have exactly same issue on Huawei P10.

I know the  standard answer is P10 is not currently supported device

but please be aware of basic logic

- Issue only on new version app 2.52

- Not only on one brand or one type Android device

It is clear that app update bring this issue to customer.

As end customer, we are not able to solve the problem, only thing we can do is to waiting for your update.

Or stop to use Fitbit.

Best Answer
0 Votes

Hello @backguard and @kingmoon!

 

I completely understand where you are coming from. I can assure you that no comment is going unnoticed. Having said that, please take into consideration that any app update or release has to be tested and optimized to work with each specific device's software and hardware. Since those devices are not on the compatibility list, it means that the app is not optimized for those devices. 

 

We're always looking for ways to improve our overall service and experience. Thanks for bringing this up!

 

Let me know if there are any other questions. 

Lanuza | Community Moderator

Remember to vote for posts that helped you out! Tired of the same workout music? Try a Podcast! 🙂

Best Answer
0 Votes

Hello @LanuzaFitbit

 

I also understand it's impossible to have 100% perfect app and you are improving every time.

I am back to 2.51 temporarily and waiting for update.

It's good experience here that my issue get your attention and positive feedback.

Thanks.

Best Answer
0 Votes

Hi,

I received a fitbit flex 2, but my phone a xiaomi redmi 5 plus does not support your app. Can you tell me if you are working on making the app compatible with this phone or should i sell my flex 2?

 

Thanks

Best Answer

Welcome to the Forums @caliasatti.

 

Thanks for sharing your thoughts on the matter.

 

At this time we do not have any news on what devices are being tested or will be added in the future. At the moment the Xiaomi RedMi 5 plus is not a supported device, as you mentioned.

 

Having said that, you could potentially sync with a different device or even a computer

 

If you have any other questions, please let me know.

Lanuza | Community Moderator

Remember to vote for posts that helped you out! Tired of the same workout music? Try a Podcast! 🙂

Best Answer
0 Votes