Developer menu in Fitbit app disappeared

[Theodorus]

It seems that the developer menu in the Fitbit app disappeared. How do I now change settings of my self developed apps or install new apps?

[jonhallur]

I am using a google account, and I could not attach a screenshot as the forum system says that it is a "11-somenumbers" content that is not allowed in this community.
Oh, and Google Gemini feels that it is important that I tell you that I currently live in the European economic area.

[Gondwana]

A screenshot of the relevant page could be useful. Could you please try changing the filename of the screenshot so that it doesn't fall foul of the forum's filter, or use something like imgur.

EEA is probably not relevant. Users in EEA can no longer install third-party apps from the Fitbit Gallery, but devs in EEA are still allowed to develop them.

[jonhallur]

[Gondwana]

@jonhallur Thanks; I'll pass that on.

[eekpi]

Same issue. Same version. Same screenshot. Factory reset. Repaired. With or without account migration

Considering throwing it the bin. I only have it for my personal app. Noticed when the companion app stopped working 

[Gondwana]

@eekpi Thank you for the info. I'm quietly confident that the dev menu will reappear in a Fitbit app update sometime soon.

[Theodorus]

Is Google aware of the missing developer menu in the Fitbit app or is there a way to report this to Google?

[Gondwana]

@Theodorus 

Google is aware, hence my quiet confidence.

[jonhallur]

I have been pushing this through with (Google) support, and they are now asking me to proof to them that the older software had this feature.

I am at a loss for words.

[Theodorus]

It is the only way to develop your own apps. I hope there is someone at Google who will understand that. Is there a way I can contact Google support?

[Gondwana]

---

@jonhallur wrote:

I have been pushing this through with (Google) support, and they are now asking me to proof to them that the older software had this feature.

---

Some devs are still using older versions of the app (eg, @Guy_ ?). One of those may be able to provide a screenshot. I don't think it will help though, because Google's technical people know about the issue and customer support won't understand.

[eekpi]

Not that I have lost all faith but installing 4.09.3 works fine. As a typical developer I use lineage on a second phone and it's a test account so nothing to steal. Works great again. Was all configured still.

My only real use for this watch is sending heart rate over websocket but it's nice to have back

No permission to add image: https://imgur.com/a/utTlZzV

Edit: You will have to reinstall the companion app since it seems to have been removed

[jonhallur]

Thanks for that, but I did what they asked, hunted down and older (bad word for android software installer, not allowed on these forums) and took some screenshots. Then I got an email back, thanking me for the screenshots, and telling me that someone one the team had "already been consulted on my case"

Here is hoping that this will be fixed in the next app update.

[jonhallur]

I rewrote the HR over WS for Wear OS (using the wearable message service), since this platform is not longer being supported, but that was not fun and not quick. I am really going to miss the fitbit sdk.

[Gondwana]

I think a fix will come, but Google definitely sees Wear OS as the successor to Fitbit. I've made the move too. Wear OS is harder to develop for, but OTOH I could never get Fitbit SDK comms to work reliably for extended periods.

[Guy_]

Hi @Theodorus , @jonhallur  and all.

In version 3 of the Fitbit App the developer menu exists.

However an alternative approach is to install anything via a private link in the Fitbit App after using the OS Simulator for testing of your GAM project.

If the project is already published make an alternate project with a different UUID for testing.

Upgrading the current version 4 Fitbit App is likely to come with more things that change or stop working. Once you upgrade the app you can't restore the previous working version. The rationale behind this approach is a mystery.

[jonhallur]

@Guy_ the private link method, does it require you to upload the build artefacts to the fitbit gallery.

[Guy_]

@jonhallur - it is still a GAM project only that it isn't submitted for publishing, only you know the link or anyone you wish to share it with, so it remains private only.

[jonhallur]

Thanks @Guy_ that might be the most agreeable solution for me right now.

[jonhallur]

This is what I get when I try to use a private link. (I tried other ppls GAM links, same thing)
So it looks like my only option is to daily uninstall my freshly updated fitbit app and replace it with an older version.