App crashes when trying to view exercise

[Maxe83]

I start tracking a walk from the app. Right after I finish I can see the distance etc and also the map of the route.

If I then try to see it again later on, the app only shows the duration and shortly after crashes. 

I have restarted the phone and the app several times but it keeps happening.

Also unistalled and reinstalled the app with no improvement.

This started to happen like a month ago and I have not changed the Fitbit (Charge 6) or the phone (Google Pixel 7).

I have never had this issue before and I've used the app since 2018 on different phones and with different Fitbit products.

Any tips or anyone else with this issue?

[AnjanaSu]

Happens to me too! It seems like when my runnings are a bit long, like over 2h and/or over 12km, that the app crashes when I get home and want to view exercise data!

Short exercises, for instance a run for about 10km and 1.5h, does not crash

I have done so far:

-Signed in with Google

-Restarted my phone

-Reinstalled the Fitbit App

-Factory Reset the device (Sense 2)

- I have also installed the app on Secure Folder (which practically will be the same as installing it on another device), but it still crashes on Secure Folder

I have this setup:

Phone: Samsung S21 Ultra 5G 

Android version: 14 (One UI 6.1)

Fitbit App version: 4.22.2 (Newest as of 31. July 2024)

Fitbit Sense 2 FW version: 60.20001.210.26 (Newest as of 31. July 2024)

I'm not sure, but this issue started from June 2024. Also my old exercises that I was able to open before, is now crashing! Before there was no problem to view them, for example exercises from 2023, but now also they cause crash!

@Fitbit: This is getting REALLY ANNOYING! @

[SunsetRunner]

AnjanaSu - Be careful doing a factory reset. This is 100% an app issue. It has nothing to do with your device. The app is rubbish. I literally only use it now to sync my device and use a free account with Strava to look at my GPS tracked activities.

I don't know how old your device is but if it is out of warranty Fitbit would not replace it if a factory reset ruined your watch, even if it was them that told you to do it.

I have a warning in place relating to factory resets under another topic on this forum, which can be found here (at least until one of the moderators decides they don't like it):

https://community.fitbit.com/t5/Sense/Live-Chat-advocates-routinely-instructing-factory-resets-can-d...

[MH42]

Recorded and displayed a 7.65 mile walk on 4.2.2 Samsung s10e/Android 12.

But, it will not display the same walk recorded 21-July-2024 with 4.22.1.

It does, like before, display 'short' walks recorded with other versions, but for 'long' walks, apparently only displays them if recorded with the current version. And of course since the screen freezes up, you can't see the walk statistics.

From a programmers pont of view, not seeing what's going on.

[HikerSaSa]

I'm getting this exact same issue. It's very frustrating and I agree that it only seems to be happening on longer activities. It didn't used to be an issue though. 

[scot53]

My phone updated to Fitbit 2.22.2 a few days ago. As expected, the app now displays GPS data for new walks >4 miles, but not for those recorded by earlier versions. As I said in an earlier post, I'm okay with this state of affairs, but I agree that it is lame that Google/Fitbit cannot resolve this issue.

I have requested a download of all my Fitbit data, which may provide further insights into what's going on. When I receive it and have had a chance to examine it, I'll post my findings here.

[thegreatignarus]

This happened to me, too. Ran a 5k and used the app on my phone (left fitbit in the charger by accident) and now when I tey to view the run, there's a gray square with Google in the bottom left and the app freezes. Over and over and over.

I updated the app, restarted my phone, nothing. Just freezes every single time.

[fan_of_wdw]

My map is now locking up and crashing during my walks, and I lose all data but the steps. This happens once every three exercises.    And I really miss the ability to "unlock" the map so that I can zoom in during the activity to better navigate routes .  Sigh.    Time to abandoned FitBit and find an alternative.

[Rich_Laue]

@ssianky is this walk crash happening when, after your walk, and you are reviewing the map. Or when you are recording the walk with the Fitbit App? 

[markvandelaer]

After cycling activity and synchronizing the app with my Sense 2, the app shows in the main page some data but no map. When I click to see the map, or when I want to see more details, the it returns automatically to the main page. Sometimes I get the message that the app has stopped.

[coolhandphil]

For me, the app crashes while I'm walking.  If I touch the map (on screen), that will crash it much sooner but even if I just leave my phone in my pocket Fitbit crashes after about 6 to 8 miles of walking.  (I usually walk 15 - 20 miles so the app crashes every time I walk since the map update).

Also, I have noticed that if I'm walking with the app running and I open the music app (on my IOS device) this will crash the Fitbit app immediately.

Things I have tried:

- Uninstalled Fitbit app and reinstalled it

- Reset Bluetooth connection (by forgetting device)

- Installed latest version of IOS (Fitbit was crashing both before and after updating IOS)

- Making lots of extra memory free on phone

[ax4w]

I have a Z Flip 6 and a Pixel Watch 1. I wanted to view the GPS tracking of my hike but the app just crashes with that screen: 

Any Idea how to fix that?

[Franko1]

Just updated to 4.22.3. app still crashing due to GPS issue. 8.97 km activity. 

Android 15. Pixel 6a. Pixel Watch 2.

Tried on a Samsung phone. Same problem. 

[MH42]

Haven't had the opportunity to record a GPS walk yet on 4.22.3/Samsung s10e/Android 12

I did back test its ability to open 'old' recorded walks.  As before, it still has display issues with >5-ish mile walks recorded pre 4.22; it will open 'shorter' GPS walks recorded pre 4.22.

It seems to be happy with any GPS recorded walk 4.22+

Which Samsung phone/Android version did you test on?

[ssianky]

@Rich_Laue  After. Any long enough track will crash. Short tracks will not.

[Franko1]

Samsung A37. Android 13. A bit dated and slow but still shows the data correctly for shorter activities. 

Amazing that FB can't get this sorted given the vast experience and noises they make about being top of the class.

[MH42]

Ok. Succesfully recorded and displayed 7.84 mile walk with 4.22.3.

As discussed previously 4.22.3 is still unable to display 'long' walk activities recorded prior to 4.22

Fitbit 4.22.3 - Samsung s10e/Android 12 - Charge 6 with GPS=PHONE

Walk activity always initiated from the phone

[Franko1]

Hi I still have a problem with anything over 8km. 

I note your comment about initiating via the phone. I'll try that.

I also received a reply from from my comment on the Play Store.

Ill try contacting via the chat option but it has to be office hours so I'll try tomorrow.

 Thanks for troubleshooting. Please don't hesitate to contact us on our help site and let us help you in finding a better resolution. You can reach our help page here: https://goo.gle/contactfitbit

[EasilyStacked]

Came to say I'm having the same issue too. Glad Fitbit is working hard to make basic things work...

[HikerSaSa]

Good idea! I've reported too. Fingers crossed. 

In the meantime, Strava has been a lifesaver for viewing GPS tracked activities. 

[Franko1]

As an update. 

help chat was useful and he acknowledge that it appeared to be an app problem and not device related. Conclusion was wait for an update so one would think they are working on a fix. 

As said before. My data is recorded it's just you can't see it in Fitbit. It's there on Google Fit.

as closure to this post. I have good news in that today using 4.22.3 I recorded a 15km ride and the map was ok and shown. I have made 2 changes. Installed Strava but I don't think that was the reason. I also set Fitbit to record location ALL the time and not when just using the app. This was suggested as a fix in a separate Community posting. Will run another activity trw. 

However. Caution. Whilst the GPS ride distance exceeds 7km limit (at which point my system crashes) the ride duration was 50 mins - much less tha less than the 3 hours for 11km of golf where my app crashes.