05-08-2024 22:15
05-08-2024 22:15
Hi,
Recently Fitbit releases mobile app version 4.16.1 and they support staff requested me to upgrade my app to that version. Since then, I lost the option to use the developer bridge. I discussed with support team and they told me that that version is buggy and they planned to release the correct version on May 8th, 2024. As of now nothing was released and support team always tell me not to use fitbit for development purpose. Now my question is to know whether Fitbit company still wants developers to use their devices or not?
Regards,
05-10-2024 20:04
05-10-2024 20:04
Hi @Paul24 - while there may be issues with the developer bridge you can still develop and load via a private GAM link.
Build the module, add it to a GAM project and then click the link. It will open in the phone browser (where your Fitbit App is running) and click the OPEN APP (hopefully, as some phones don't get the link) to install it.
Author | ch, passion for improvement.
05-10-2024 22:32
05-10-2024 22:32
Thank you.
As for GAM, we have some issues too:
1. one of my device was long ago associated with another developer that I don't even remember and that device can not be associated with another account. I tried to write to GAM team an email, it seems none monitor that and managed to talk with support team on LIVE Chat only to tell me that I have to do it on my end only.
For fitbit versa 4 on GAM, I tried but kept receiving error message whenever I try to add the build file. such error is not related to my code and I don't know where it is coming from. I have stopped my development for now due to lack of support.
05-10-2024 22:40
05-10-2024 22:40
@baptiste2k17 - gallery support is not heavily manned, you may get a response in due course.
If you have a GAM problem (for your own use) try making a new project.
Build with a new uuid and make sure your package.json matches your device and the files too.
Author | ch, passion for improvement.
05-11-2024 04:45
05-11-2024 04:45
Probably you are right. Do you know how package.json should look like for Versa-4?