06-28-2017
09:04
- last edited on
06-28-2017
10:23
by
AlessFitbit
06-28-2017
09:04
- last edited on
06-28-2017
10:23
by
AlessFitbit
My Fitbit app auto updated last night. I am using Samsung Galazy S5. On attempting to load the application this morning it went into a database update mode and came back with an error message: "Internal Service Failure ...... An internal error occurred .... Please make sure you have a good network connection." The internet connection is fine. I can access the internet, get mail, I just can't get my fitbit app to work. I tried updating on the web site with dingle dangle dongle whatever installed and nothing happens. Something is not functioning. Maybe this wasn't fulling run through Beta testing.
Moderator edit: title for clarity
Answered! Go to the Best Answer.
06-28-2017 10:29
06-28-2017 10:29
@KenVB Welcome to the Fitbit Community!
I'm sorry to hear you had some issues updating the Fitbit app on your device. I suggest restarting your phone and try opening the app again. If you're still having issues, try uninstalling the app and re-downloading to your device. Lastly, I would make sure you're on the latest app version 2.52. Keep me posted!
Want to get more steps? Visit Get Moving in the Health & Wellness Discussion Forum.
06-28-2017 10:29
06-28-2017 10:29
@KenVB Welcome to the Fitbit Community!
I'm sorry to hear you had some issues updating the Fitbit app on your device. I suggest restarting your phone and try opening the app again. If you're still having issues, try uninstalling the app and re-downloading to your device. Lastly, I would make sure you're on the latest app version 2.52. Keep me posted!
Want to get more steps? Visit Get Moving in the Health & Wellness Discussion Forum.
06-29-2017 13:01
06-29-2017 13:01
Aless -
I turned off Wifi. That didn't fix it. The new app would open and then crash. Finally I uninstalled the 2.52 (?) I don't know, I never got to point I could check this version. I updated Android. And then reinstalled 2.51, which was newer than what I had. And that works fine. And it is much faster than the previous version I had. So I am up and running again. For now. Thanks, Ken
06-29-2017
15:47
- last edited on
07-03-2017
06:03
by
RobertoME
06-29-2017
15:47
- last edited on
07-03-2017
06:03
by
RobertoME
I've been receiving an "internal service failure" message on my Samsung Galaxy 5 for the last couple of days. The frustrating thing is that I can see my updated info behind the error message, but I can't get to it. I've tried everything suggested in the other posts with no success. I have a strong network connection and can easily open every other app on my phone. I have to view my info on my computer, which is not always convenient. I see many other users are having similar problems and would like to know what steps are being taken to correct this problem. Seems to me this is clearly an issue on your end. I am receiving text and phone alerts, and I'm also receiving my hourly reminders to move. I'm on my second Fitbit, and like the product, but will not hesitate to research other fitness trackers if I can no longer check my progress on my phone.
Moderator Edit: Updated Subject For Clarity.
07-03-2017 06:02
07-03-2017 06:02
Hello @Kathy128, welcome aboard to the Fitbit Community. You can try the following workaround:
Go to Apps > Google Play Services > Permissions, then allow it to use phone and storage
If this is not helping to access to the Fitbit app, try the steps from this post. It might help to restart the app and have access to your information.
Keep me posted how it goes, I'll be around.
"Great things are done by a series of small things brought together.” What's Cooking?
07-03-2017 12:23
07-03-2017 12:23
07-06-2017 05:21
07-06-2017 05:21
Hello @Kathy128, thank you for keep me updated. I was reviewing the reports, but it doesn't figure as a glitch this scenario. Nonetheless I would like to take a closer look, so can you share with me an screenshot of what you are seeing on your app? This will be super helpful to keep investigating. (To learn more about uploading screenshots please take a look at this post.)
I'll be looking forward to your response.
"Great things are done by a series of small things brought together.” What's Cooking?
07-06-2017 08:10
07-06-2017 08:10
07-10-2017 04:39
07-10-2017 04:39
Hi there @Kathy128, thank you for letting me know the workaround you have tried to resolved the issue you were experiencing. I will keep this in mind for future occasions.
Stay awesome and see until the next time.
"Great things are done by a series of small things brought together.” What's Cooking?
09-23-2017 14:32
09-23-2017 14:32
am having the same problem as Kathy 128 describes since Fitbit update. Cannot sync any data on phone app or on computer. " Internal service error. An internal error occurred.This can be caused by a lack of network connectivity. Please make sure you have a good internet connection."
I have a good internet connection; I have uninstalled and reinstalled app x 2; I have turned blue tooth on and off; Apps: Google Play Services: Permission is turned on for phone and storage. Help! this has been going on for days.
09-25-2017 08:28
09-25-2017 08:28
am having the same problem as Kathy 128 describes since Fitbit update. Cannot sync any data on phone app or on computer. " Internal service error. An internal error occurred.This can be caused by a lack of network connectivity. Please make sure you have a good internet connection."Â
I have a good internet connection; I have uninstalled and reinstalled app x 2; I have turned blue tooth on and off;Â Apps: Google Play Services: Permission is turned on for phone and storage. Help! this has been going on for days.
10-09-2017 10:25
10-09-2017 10:25
I received the notice to update the app for my fitbit charge 2. I got the update but can't open it successfully as it keeps saying "internal service failure" as previously noted. I uninstalled and reinstalled the app several times, checked the wifi (all good), restarted my android and restarted the fitbit itself however none of these steps corrected this issue. I saw someone say they went back and got version 2.51 and it worked for them. How did you do that?