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?

[Franko1]

My caution was warranted.

Today app failure with a 10km walk.  Limited activity data shown in Google fit so my data reaches googles servers but can't be presented correctly in the FB  app.

My gut feel is that the issue is activity time related and may not be GPS.  Today's 10km was 4 hour activity (app failed) whereas yday was 14km 50mins (app reported correctly).

I contacted FB help who advised that revision 4.23 should be available next week and the problem will be fixed.

Fingers crossed 

[Triletics]

@Franko1 it is related to GPS and number of waypoints stored. Waypoints are created every second so the longer activity (by duration) then more likely it will crash the app. Distance has nothing to do with it because it doesn't directly impact number of GPS waypoints.

[MH42]

Initiated a 7-ish mile walk today from the Charge 6 (with GPS=PHONE).  After about 10 minutes, the Charge 6 gave me a 'GPS Off' warning. This particular route is not tree covered, plenty of blue sky, no reason for a GPS problem.As expected, the walk GPS track was not recorded, but the app estimated the distance.

I checked the Android Location GPS setting; I have Fitbit set to access the GPS 'while in use'. I assumed (never a good idea) that initiating the walk from the Charge 6 would start FitBit and it would acccess the GPS. Perhaps, Fitbit needs GPS access 'all the time' for the Charge 6 to be able to start the GPS track?

Note, I have never been able to initiate from the Charge 6, so what I see is not new.

Seems to multiple 'GPS' issues with different root causes?  If I may ask, what is your FitBit GPS access set to?

[Franko1]

Thanks for that useful insight. Let's hope 4.23 gets things sorted.

[Franko1]

Location set as 'always' but my issue appears to be time related which FB are working on. 

[Triletics]

@MH42 the Charge 6 GPS is the worst I have experienced among all Fitbits I owned. The builtin never worked (or worked for a short while), dynamic didn't seem to use the phone and kept trying to use builtin hence never worked either (same symptoms as builtin). Phone setting worked most of times however Charge 6 tends to drop BT connection between phone and tracker and isn't able to recover it. If that happens, GPS goes off. The "Phone" settings was most reliable (bar not set very high considering other settings just don't work) yet still not great. Switching back to Sense watch made a day and night difference. Bottom line is that if you look reliable GPS then Charge 6 isn't it.

[Franko1]

I'm pixel watch 2 and other than the FB activity issue I can't complain and don't have issues - to date 

[MH42]

Another small test. Set Android GPS permission for FitBit to 'all the time' and intiated a short walk from the Charge 6 (GPS=PHONE).

This worked, the walk around the yard was recorded and the GPS track displayed correctly. It will be a couple of days before I can try a proper length walk activity.

At this point, the only known issue with my specific configuration of Charge 6 and Samsung s10e/Android 12 is the display of 'long' pre 4.22 GPS activites.  Whether a 'long' GPS activity initiated from the Charge 6 records and displays correctly remains to be seen.

The reliability of the BlueTooth connection also remains to be seen, although the Samsung s10e has pretty good range when used for music with BT earbuds

[LumiaUser]

I just got v4.23 pushed to my phone and I can now again open the detailed map on hiking activities > 4hrs.

They also load a lot faster. Also when tapping the small map, although I then cannot zoom in and out nor can I move the map around...

[Franko1]

That sounds promising so thanks for the comment. It's not available to me yet but hopefully it will in the next few days. I note the function restrictions but outweighed by the gain in that you can view activity details correctly. Tks again. 

[Fabrice_A]

I'm really fed up with this app, I can't understand that such a problem isn't resolved after several weeks.

I've just checked, I'm already with the 4.23 and the problem is still the same. I'm a full Google user (Pixel Watch 2 and Pixel 6), and the app still crashing.

After reading some of the messages here, mentioning the duration of the activity, I realise that my 2 activities of the day might be interesting as I can read only one of them. Both are walking activities with GPS,  the 3h20 one works fine, but the 3h38 is still crashing.

I agree with a previous message saying that (when it works), loading the activity is quicker and smoother.

[LumiaUser]

*Update*

As mentioned, now I can at least view my activities. Yesterday had a Hiking activity of 4h22m. Smoothly opens the map: great.

But: since the update my activity is no longer synced to Strava... 😞 
Already tried to update the connected app within the Fitbit app. Even removed all connected apps and then added Strava again.

As I did not convert my Fitbit account to a Google account (wanted to postpone the conversion as long as possible - end of August I thought), I'm now thinking this has maybe something to do with (possible?) preparation of moving the backing systems to Google services? Just a guess...

I've completed the conversion from Fitbit account to Google this morning, see if this wil fix the syncing (it was a great hike yesterday :)).  

[Triletics]

4.23 seems to solve the problem (although I didn't notice any performance improvement). I noticed new metric "Cardio load" which for now is just 0.

 

[MH42]

Agree, just got 4.23. The Fitbit app will now load and display all pre 4.22 walk activities. Also received an update for the Charge 6, unsure what functionality it has fixed/added.

Still need to do a proper walk activity initiated from the Charge 6 (GPS=PHONE), but I'm very confident it will work. The difficulty I had been having was with the Samsung GPS permission, nothing to do with the app.

For my somewhat limited use case, it seems the 4.23 update has resolved all my outstanding issues. YMMV

FitBit 4.23/Charge 6 66.20001.210.26/Samsung s10e/Android 12

[Franko1]

Same here..4.23. is reading and presenting all activity which were previously causing the app to crash.

[Franko1]

Same with me. All good other than carbo reading 0. Evolution so we'll get there soon

[MH42]

I have now successfully recorded and displayed several walk activities which were initiated from the Charge 6 (Setting GPS=PHONE).  There was an initial issue which turned out to be the Charge 6 Walk Activity Configuration where GPS=OFF. I suspect, but do not know, that the Charge 6 GPS configuration may have been modified by the Charge 6 update (66.20001.210.26) I carried out along with the FitBit app update to 4.23.

Anyway, FitBit 4.23 and the Charge 6 (66.20001.210.26) seem happy (enough) together at this point in time.

FitBit 4.23/Charge 6 66.20001.210.26/Samsung s10e/Android 12

[Franko1]

That's great news. Same here with my PW2 - all works ok although cardio does show as 0. Not sure whether that is a bug or a correct reflection of the activity. I can live with 4.23 as is.

[Popinjay]

I am currently having this same problem.  Any solutions?

I just got the thing and am starting to have buyers remorse.

[MH42]

Make sure you have FitBit app version 4.23; it seems to fix all known issues, at least with the previous thread partcipants.

When you post with issues it is helpful if you include the hardware and software versions you are having trouble with.  There are so many combinations and permutations of wrist devices/phones/software versions that trouble reports really need to be specific these days.

For example, the hardware/software combination below is working perfectly for me at the moment. YMMV

FitBit 4.23/Charge 6 66.20001.210.26/Samsung s10e/Android 12