Constant Android issues.....

[TKCMuzzer]

Is anyone else experiencing problems with android devices and in particular, when using a companion app.

I have a couple of watch faces that have multiple colour options available to the user. Now when I built these faces there was no issues either on the simulator or my ionic, key thing here is , i was using an Iphone. 

Now these watch faces have been submitted and are available in the gallery. Now, i get a lot of positive emails but recently I have had users saying that the watch face does not change colour when selected. Now after some very easy research, every user that has an issue is using an Android device.

So, I dug out my Android device which is connected to a separate ionic and hey presto I had the same issue. I had to force close the fitbit app, forget my device and reboot the watch in order to get a connection that would allow me to change the colours. One of my users said they had to do the same thing.

Now, im not surprised before I started to develop I used to have my fitbit watches connected to the app via an android device and had no end of sync and install problems.

Is there any reason for this? I know there are many android devices etc but they all use the same operating system, where the iPhone seems so stable and frankly is way better for testing watch faces.

Is there anyone else finding this and if so, is there any solution going forward to making the android version of the app more consistent?

On aside not, it seems to take substantially longer to install a watch face through android than it does IOS.

[TKCMuzzer]

I'm bumping this post to reach out to the devs. I'm still getting small issues and the they are all android related. The connection between an android device and this watches seems very inconsistent.

Thanks in advance.

[Gondwana]

I know the question wasn't directed at me, but I think that the underlying problem is that Android (and, to a lesser extent, iOS) kills the companion app periodically. Fitbit can't do much to stop that behaviour.

We could do with an API for a comms layer that performs message/file transmission verification and retransmission as required. It would need to be robust to operating system interference and users closing apps at inopportune times.

I've had an app rejected by Fitbit's reviewers as a consequence of unreliable comms. 😞

[TKCMuzzer]

Cheers, I have been reading on the play store that there are many users suffering sync issues with their devices after the latest fitbit app update (android only). I can confirm, I am running an older version off the app and all is ok when syncing.

Devs, you need to pass this on to the app team as they may have inadvertently broken something. One of my watch face users said all was fine until they updated the app, now they can not connect properly to change themes.

It would make sense, as I have only received messages about issues since the app was updated (All android)