Cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Settings not applying consistently

ANSWERED

I added setting to my watch face and they appear to work. When I install the app and click on the settings on the companion app, they work, but at that point I am still connected to the developer bridge on both my phone and watch.

 

If I disconnect the phone from the developer bridge, the settings still work, however as soon as I disconnect the phone, from the developer bridge they no longer work. Even if I reconnect the developer bridge, they don't work. The only way to get a new setting to apply is to reinstall the app and change settings will still connected to the developer bridge.

 

Is this just a developer issue that will go away when the app is published, or am I missing something?

Best Answer
0 Votes
1 BEST ANSWER

Accepted Solutions

Over the weekend, my watch stopped getting notifications, so I uninstalled the app on my phone, the watch on the app, and the watch face that I created. When I reinstalled everything, the settings are now working as they should.


I don't know why they didn't work before, but I am guessing that disconnecting and reconnecting the watch to the app fixed it.

View best answer in original post

Best Answer
0 Votes
6 REPLIES 6

It shouldn't be dependent upon the bridge at all. Perhaps just try relaunching your app after the bridge is off.

Best Answer
0 Votes

No luck. I have tried many things and I can't get the settings to send once I disconnect the watch from the developer's bridge after loading it.

 

I tried restarting the app, restarting my phone, restarting the developer bridge, but still nothing. I am essentially using the settings template for the companion app and using the connection pieces in the device file.

 

When I do reconnect the developer's bridge, I get the following messages:

19:19:04  Loaded and evaluated: file:///android_asset/bootstrap.js
19:19:04  Loaded and evaluated: file:///data/user/0/com.fitbit.FitbitMobile/app_companions/8938aafa-bcd6-47a3-8a2d-bca1c3e996f5/0x027da8e49a5ac79b/companion.js
19:19:06  Data not sent

 

The Data not sent is the else condition for peerSocket not being open.

 

The settings send find when I delete the watch face and reload.

Best Answer
0 Votes

Can you put your project on Github so we can take a look?

Best Answer
0 Votes

Sure, here is a link:

https://github.com/drb116/BearTimeWatchFace

 

I am a high school teacher, so the program is basically a countdown program aligned to the bell schedule. The options correspond to the different bell schedules we use. The program could use a little refactoring, but everything works except the options updates. 

Best Answer
0 Votes

Over the weekend, my watch stopped getting notifications, so I uninstalled the app on my phone, the watch on the app, and the watch face that I created. When I reinstalled everything, the settings are now working as they should.


I don't know why they didn't work before, but I am guessing that disconnecting and reconnecting the watch to the app fixed it.

Best Answer
0 Votes

ok, thanks for letting us know.

Best Answer
0 Votes