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
Showing results for 
Show  only  | Search instead for 
Did you mean: 

File transfer bug if companion opened before app on initial installation

‎01-10-2018 05:28 - edited ‎02-04-2018 20:20

‎01-10-2018 05:28 - edited ‎02-04-2018 20:20

 

 

 

I have an app, that requires authorisation in the settings to fetch data. If after installation the user opens the settings first and then authorises the service, the resulting data is never sent to the device.

It appears the App must first be opened before the file can be found using the inbox.nextFile.

 

The file transfer works when using the developer bridge because the app is opened automatically as part of the build and deploy process. Once you are using the GAM link, there is nothing forcing the app to be opened first. 

I can reproduce this bug.

Best Answer
Labels:
0 Votes
2 REPLIES 2

‎01-11-2018 21:20

‎01-11-2018 21:20

It appears that the staging area is created when the app is first run, so therefore a file cannot be transferred prior to the App having being first run on the watch.

Best Answer
0 Votes

‎01-17-2018 05:45

In response to allyann

‎01-17-2018 05:45

We are investigating this possible issue and will get back to you as soon as we know more. Thanks for reporting this @allyann.

Best Answer