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: 

On screen buttons not working when installing from CLI

‎09-13-2020 09:22

‎09-13-2020 09:22

I recently exported my project so that I can use my own IDE. Using the Command Line Interface, i was able to get my app to install, but the on screen buttons would not work. I could still use the physical buttons for the combo buttons. All of the code is exactly the same as what is in Fitbit Studio, and when I install from Fitbit Studio, the on screen buttons do work.

 

This issue happened many times to me when I was working in Fitbit Studio, so I tried my usual tactics: removing more an more things from the UI until the buttons work, but I got down to deleting everything except the Combo Buttons themselves (so nothing can be on top of them consuming the pointer event) and I still couldn't click on them.

 

Could it have something to do with the package.json (to which I added the cli dependancy)? Please share any suggestions you have.

Best Answer
Labels:
0 Votes
1 REPLY 1

‎09-16-2020 04:01

‎09-16-2020 04:01

Have you tried to group your buttons in a g element and set a higher layer, like layer="10001" for your g element?

If you can share some code, would be easier to see where the issue is.

Best Answer
0 Votes