Versa 2 won't sync with my LG K40

[hmathias3680]

I have unstalled and reinstall the app more times then I can count and the i did a reset on the watch and now it won't sync to the app on my phone any suggestions please I am very desperate for any i have talk to support last night and that didn't help I may end up getting a new watch or send this one back ??

Moderator Edit: Clarified subject

[MarreFitbit]

Hi @hmathias3680! We acknowledge the limitation we have on our part particularly on what you have experienced. We‘re taking into consideration your comments and sentiments with regards to our products and services. 

Since you've contacted our Support Team and they started handling your issue, please reach out to them again with the so they can continue to help you.

In addition, please note that your LG K40 is not yet officially supported with the Fitbit app which would explain the syncing difficulties you're running into. To see the list of compatible devices, click here Which phones and tablets can I use with my Fitbit watch or tracker?

Please keep in mind that when a device is not supported and does not meet the require OS we cannot guarantee its functionality with the Fitbit app. It might work at a certain time and then it can stop working out of nowhere after an update. This is because the app is not optimized to that device and any change could impact the performance. 

Thanks for your understanding. 

[hmathias3680]

I had bought this phone after I got the watch 1 year ago for Christmas it
worked fine then now why isn't it working

[SunsetRunner]

I have the same phone and synching was NOT an issue before the update

[hmathias3680]

So its the update thats causing the issues

[MarreFitbit]

@SunsetRunner @hmathias3680 Please keep in mind the compatibility of the phone may cause syncing difficulties anytime and cannot be only related to a Fitbit update.

However, our team is aware of a syncing issue on Andriod 3.37 affecting users with compatible and non-compatible devicesand is currently working on a fix. Thank you very much for your report and patience. Please stay tuned to this thread for updates.