Fitbit Product Experts Alumni are retired members of the Fitbit Product Expert Program. Learn more
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.
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
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.
Fitbit Product Experts Alumni are retired members of the Fitbit Product Expert Program. Learn more
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.
Best AnswerDelete the side-loaded version first, or you may not see the private-link version.
Best Answer
Fitbit Product Experts Alumni are retired members of the Fitbit Product Expert Program. Learn more
Fitbit Product Experts Alumni are retired members of the Fitbit Product Expert Program. Learn more
@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.