03-04-2022 04:41
03-04-2022 04:41
After installing an App [with Sideload or direct from Fitbit Studio] using the watch developer bridge, changing it's App Settings in the Fitbit App developer bridge works fine.
But when installing the same build via a private link from the Gallery, the App doesn't detect changes in the App Settings [changed via Fitbit App, device tab, in the Gallery tile]
Is there an extra option/permission required ?
Author | ch, passion for improvement.
03-04-2022 09:33
03-04-2022 09:33
Sideloaded apps have all permissions, so it can be a common mistake, but there isn't a permission related to settings specifically.
I would try force restarting the Fitbit mobile app and restarting your Fitbit.
03-04-2022 09:45
03-04-2022 09:45
Cleared Fitbit App cache, forced stopped, Swiped off, restarted phone, restarted watch, logged out and back into the Fitbit App.
No difference.
Going to test with SDK 6 when the back end issue is solved.
Author | ch, passion for improvement.
03-04-2022 11:31
03-04-2022 11:31
Delete the side-loaded version first, or you may not see the private-link version.
03-04-2022 11:35
03-05-2022 01:47
03-05-2022 01:47
@JonFitbit- tried with SDK 6 [and with run companion in background] still the same difference.
Can see the companion sending the settings
but in the app this doesn't seem to work when installed from the gallery but does when sideloaded, using same build
// Event occurs when new file(s) are received
inbox.onnewfile = () => {
getSettings();
}
Author | ch, passion for improvement.