03-22-2020 07:21
03-22-2020 07:21
Hello,
I've just now (literally in the last hour) started FitBit development. I've installed the OS simulator and connected both my Versa 2 and simulator to the Developer Studio. I am using a base app (console output one) to start and it builds successfully. Both my simulator and Versa 2 show green in the studio.
Despite all of the above, the Run button is disabled and, when I hover my mouse over it, it shows a crossed circle icon and tells me to "Connect your phone in order to run your companion". It shows this whether I have selected /app/index.js or /companion/index.js.
Neither my Versa 2 or the simulator show the app as sideloaded. I'm sure I'm missing something simple but I haven't any idea what it is.
03-22-2020 12:27
03-22-2020 12:27
Have you connected your phone?
03-22-2020 12:47 - edited 03-22-2020 12:47
03-22-2020 12:47 - edited 03-22-2020 12:47
Yes, you're right. I figured it out shortly after posting.
I was running a FitBit only app (no companion app) but what wasn't clear was that I still had to connect both a phone and a FitBit to get it to allow me to run (thus the message about companion). Wish that had been made more plain in the getting started guide and in the message in the studio.
Though I was able to complete the app I wanted, sadly, it won't work as I can't set it as the shortcut the long press button triggers, so it's pointless.
03-24-2020 05:51
03-24-2020 05:51
Does your project contain a "companion" folder? If so, you'd need to have a phone connected. If you mouseover the "Run" button it should explain why it's greyed out.