Glance clock face used by Diabetics not working

[fittestbyte]

Heads up: Fitbit 3.64.5 on Android seems to have broken the glance watchface  which Diabetics use to monitor their blood glucose values published by the xDrip+ Android app; note that 3.64.5 hasn't reached everyone yet - a pinned thread here still refers to Fitbit 3.63.

Technical details follow

The watchface tries do fetch() a URL like 

http://127.0.0.1:17580/sgv.json?count=47&steps=7003&heart=73&all_data=true

to retrieve blood glucose readings from the xDrip+ app; it seems like on Fitbit 3.64.5, this request no longer goes through. However, the fetch API documentation still says (emphasis mine):

Please note: fetch() can only be used to access https endpoints and resources, except when accessing resources on a local network by IP address.

Since the above does involve accessing resources on a local network by IP address, this should still work. Perhaps it was accidentally broken in Fitbit 3.64.5?

Many users of Glance report the breakage on the Glance Facebook group.

Moderator edit: Subject for clarity.

[LZeeW]

Hello @fittestbyte and welcome to the Community.  I’m going to flag your post to get a moderator’s attention to report this bug.

[tibtif73]

Is it possible to download the prior revision from somewhere reliable?

(What is the prior revision filename?)

Thank you

[RodrigoMFitbit · Accepted solution]

@LZeeW Thanks for your help. 

@tibtif73 Nice to see you again in the forums!

@fittestbyte Welcome to the forums! Thanks for your post regarding the Glance clock face. 

I have now reported this situation. As soon as I have news about it, I will let you know. I greatly appreciate you taking the time to report this and explain in detail. Would you be so kind to share the error message you receive when trying to retrieve data? Please also let me know which Android version is your smartphone running. Thanks so much in advance!

@tibtif73 Officially there is no way to make a roll back to the previous version of the app, unless Fitbit withdraws the latest release and enables the previous version. Else you will have to download and install the app from untrustworthy sources. I do not recommend that in any way, you could compromise your personal information. I have now reported this. I appreciate your patience. 

Have a nice day!

[tibtif73]

I appreciate that the development team has resolving this somewhere in their queue.  Thank you for that.  But, waiting isn't really a resolution to the problem.

After searching for downgrade instructions, I've found a sequence that worked for me & confirm that my Glance data flow is restored.

The steps are:

1) logout of the Fitbit app on your device.  (This is very important.  If you skip this the downgrade may not work.)

2) uninstall your current Fitbit app

3) search for "Fitbit 3.52 download" and select a site you're willing to trust.  Download  & install this version.  (Other versions may work, I confirm 3.52 works with Glance.)

If you have any malware scanning software on your device, let the scan complete after the download & before installing.

4) start the Fitbit app.  You'll be prompted to login, allow your watch to pair, allow location privileges, etc.

5)  within a few moments, you should see your data in Glance.

6) you must turn off auto updates in play store settings::network to prevent the newer (broken) version from reinstalling.  You can return to auto updates after Fitbit releases a fix for this problem.

[dannyadamo]

Hopefully they will be able to fix your issue soon. My issue with the notifications was fixed after I followed the steps above with the new app 3.64.5. Careful with 3rd party apps.

Get Outlook for Android<>

[RodrigoMFitbit]

@dannyadamo I am glad to read that the notifications are now working. Have a nice day!

@tibtif73 Thanks for the explanation. However, I do not recommend installing the Fitbit app from unknown or unofficial sources. These maz seem harmless but you could compromise the information on your smartphones. 

Have a nice day!

[lauraphey]

Hello, should we wait already to solve this problem? It is almost 5 days for me and it's very difficult the control. Is there any solution at that point to solve this E 404??? 

Thanks a lot. 

[fdsm]

When can we expect an update on that issue? Literally two weeks have passed and my average blood glucose values have significantly got higher than before due to the lack of the monitoring on the watch.

[fittestbyte]

Several users have reported that app version 3.65 fixes the issue. That version seems to currently be rolling out (I don't see it yet on Play Store but other users do). If you also don't see it yet then it will probably appear in the next days.

[tibtif73]

I can confirm that v3.65 resolved this issue for me (at last).

This was the 3rd time since I've been a Fitbit user that http communication has been broken by a Fitbit app update.  Is it possible to request that passing tests for basic device http data transfer from the app to all Fitbit devices is a requirement for future releases?

Thanks to the team for listening to this issue & repairing!

[fittestbyte]

Heads up, version 3.65 is now available to my device and I can confirm that it fixes this issue. Thanks a lot! After installing it and confirming that it works, I've for now turned off automatic updates for the Fitbit app in Play Store to prevent it potentially breaking again in future 🙂

[BJBFit]

I installed Glance on my Sense 2 which is supposed to be a supported device for Glance according to the FitBit app page. I'm using the Dexcom G6 sensor with the Dexcom database. All settings are correct, I have "follow" in the G6 app activated. It begins to pull the data so it has access to the database, it updates a few times then stops updating even when you press the clock to do a manual update. I end up with a "Stale Data" error and the Sence 2 keeps alarming. The Sence 2 is running the latest update, I just downloaded Glance over the last week or two so it's the newest version available. I joined GitHub to leave an issue about it with the developers but I have not had a response. It looks like it hasn't been worked on for some time actually. Displaying my glucose data is a big reason I got the Sence 2 although with so many other features it's still worth it by far but it would be great if it worked with my glucose data. Others on Reditt's Dexcom page have the same issue.

[t.parker]

@BJBFit if you look at the Gallery, there is a tag "not optimized". This is because Fitbit took number of clock faces from original Sense and kind of ported them to Sense 2 without involvement of developers. Now, there is no SDK for Sense 2 and no thridparty apps/clock faces support. It means that developer won't be able to help you as he has no tools needed to do it.

[BJBFit]

Ok, thanks for the information. I appreciate it.

[nobeac]

ok mine worked fine for a few months now it's not sending the numbers to the watch just getting a line through the number. watch face maker doesn't respond to emails. what is going on here?