help menu

Join us on the Community Forums!

  • Community Guidelines

    The Fitbit Community is a gathering place for real people who wish to exchange ideas, solutions, tips, techniques, and insight about the Fitbit products and services they love. By joining our Community, you agree to uphold these guidelines, so please take a moment to look them over.

  • Learn the Basics

    Check out our Frequently Asked Questions page for information on Community features, and tips to make the most of your time here.

  • Join the Community!

    Join an existing conversation, or start a new thread to ask your question. Creating your account is completely free, and takes about a minute.

Not finding your answer on the Community Forums?

Cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

(versa 2)Peersocket doesnt open.developer bridge on both device and watch are on

‎08-12-2020 00:29 - edited ‎08-12-2020 04:09

‎08-12-2020 00:29 - edited ‎08-12-2020 04:09

In order to debug the fitbit app i developed i turned on developer bridge on both mobile fitbit app setting and fitbit device.both do connect to fitbit studio but both cant communicate with each other via peer socket.i tried to log readystate it shows disconnected and never connects.

also i compared readystate==OPEN .it never invokes and no response for that callback

Best Answer
0 Votes
2 REPLIES 2

‎09-02-2020 07:53

‎09-02-2020 07:53

Is this still happening? Can you confirm you're on the latest mobile app?

Best Answer
0 Votes

‎02-19-2022 17:33

In response to JonFitbit

‎02-19-2022 17:33

Hi! I am currently experiencing this problem. I had an app using a the messaging API. It went well two days ago but today I keep on getting peerSocket.OPEN = 0. Did anything change in the last two days? 

Best Answer