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?

[ssianky]

Yesterday I hiked 25 kilometers and GPS tracked my route. When I open the walk screen, after several seconds it shows the map, but then when I try to interact with the map it crashes. 

The Google Fit is able to show the route.

[MH42]

I went back in my GPS walk history and found some GPS walks that actually displayed! Walks of 1.51, 2.16 and 2.8 miles displayed but failed at 4.69 miles.

It would seem to be a data quantity issue. Of course everything used to work, so this is some sort of self inflicted problem.

Perhaps somebody else could find some similar data to confirm.

[coolhandphil]

Same thing is happening for me.

[MH42]

Found another old GPS walk that displays, 3.33 miles. So the crash appears to happen somewhere between 3.33 and 4.69 miles.

[Franko1]

I'll agree on that it appears to be a GPS / distance issue to do wirh the app as the web portal was ok when we were able to access it. 
The app does not have a problem with my short walks.

[MH42]

Fitbit 4.22 (110091592) Update

Successfully recorded and displayed a 6.38 mile walk along with walk stats.  Still not 100% though, it displayed some old 5-ish mile walks, but crashes in the 7+ mile walks. 

My guess is that it's timing out on the data transfer as opposed to running out of memory. FWIW

[Franko1]

Great feedback. Pity that Fitbit appear too busy to resolve the problem.

[scot53]

I suspect that no one from goobit monitors these forums. I've had varied results since my first post, with all walks < 4 miles displaying, but also some over 4. I agree that it could be a Bluetooth/comms issue, but I still lean toward memory mgmt.  I'll take the next step and report it to Fitbit Help Center - it might help if you guys pile on.

[MH42]

Went for a 8.16 mile walk today, Fitbit 4.22 recorded and displays the GPS 8.16 mile walk just fine.

BUT, as noted before, 4.22 will display previous short (<3-4 miles) GPS walks, but not previous long GPS walks (> 5 miles).

As it stands today with FitBit 4.22, previous 'long' walk data is essentally unusable. Even the statistics are gone since the screen freezes up and won't scroll down to see them.

[scot53]

Ah - I didn't look at your previous post closely enough. So it appears the bug might be half-fixed in 4.22. I tried reinstalling, but my phone (an older Motorola) stayed on 4.21. I assume Google is doing rolling updates, as is common. I agree it's annoying that the app won't display older data that had failed to load, and it's a bit puzzling since I assume it's stored in the cloud (from which it displayed correctly in the old online dashboard). On the other hand, the new data is coming directly from your watch.

I wonder what rev Franko1 is running.

[MH42]

To be a little pedantic, in my case, I use the Samsung s10e GPS, I do not use the watch, I initiate the walks from the phone (FWIW the watch GPS setting is set to 'phone'). Earlier experiments with the watch GPS did not fare well.

One possibility on the 4.21/4.22 updates; it's not impossible that the data content in the cloud (the old stuff) may be slightly incompatible with 4.21/4.22. Then it becomes a crap-shoot what will display and what will not.

[scot53]

Not pedantic - I didn't get that from your earlier posts, and if anything makes your situation more interesting as presumably no network is involved in transferring the GPS data to the app.

Personally, I'll be satisfied if 4.22 solves the problem going forward.

[Franko1]

I'm running Pixel 6a but also had the same problems when trying to view on a Samsung phone and my Android TV box.
I had a game of golf yday but, not knowing a fix was in the air, split the walk into 3 sections with a compbined total of 8 miles. All 3 saves viewed ok on the Pixel.
Next game/stage will be a single save and touch wood all will be ok.
This morning I noted that Fitbit did give a response (22nd July 24) to a user on the Play Store - they also problems with GPS and walks. Fitbit LLC suggested a 'restart'. At least it was a response.

[MH42]

Todays update 4.22.1 (110091614) will now display an 'old' 4.61 mile GPS walk, but still not anything longer if it's 'old'. 

Hard to say if this was an improvement or just good fortune.

[Franko1]

My Pixel 6a will report a 5.4mile old walk. Above that it's a no no. I'm still running 4.21 as 4.22 isn't available to me yet.  Will be a few days before I do a new log exceeding 5.4 miles. 

[Franko1]

App failed to report tracked activity of 6.2 miles today. 10km.  Behaviour consistent with previous crashes so we must obviously wait for FB to fix the bug in order that we the app functions correctly.

[MH42]

Successfully recorded and displayed a 7.57 mile walk today with version 4.22.1 of the app on a Samsung s10e/Android 12.

However, it will not display a similar length walk recorded 3 weeks ago. Previously recorded (pre 4.22?) walks < 4 miles seem to be displayable now, but anything over 4 miles is a crap shoot.

[Mike1X]

I have the same issue since recently. Fitbit app does not show GPS tracking and becomes unresponsive.

@Fitbit: Please do the needful!

 

[Franko1]

Today running 4.2.2 I failed with regards the app activity report for a new 6.1 mile walk. Frustrating that there seems no way to give feedback to a Fitbit and generate a response that 'we/they are on the case'. Pretty poor show for supposedly top of the class app developer.

[MH42]

I am now on 4.2.2 Samsung s10e/Android 12.  I have not yet recorded a walk with 4.2.2 but it does display all walks recorded with the 4.22.x apps.

It still does not display 4-5+ mile walks recorded prior to 4.22.x. As before it will display shorter (< 4 mile) walks recorded prior to 4.22.x

I should have an opportunity tomorrow to record with 4.22.2