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: 

Background Refresh iOS

ANSWERED

‎09-02-2017 08:21

‎09-02-2017 08:21

In my experience, the Pebble iOS companion app has to be relaunched about once a day to keep it running for background refresh tasks.  Will the fitbit iOS app be able to overcome Apple's restrictions in this regard, or might users have a similar experience with the fitbit iOS companion app?

Best Answer
0 Votes
1 BEST ANSWER

Accepted Solutions

‎09-04-2017 04:24

‎09-04-2017 04:24

The Pebble and Fitbit mobile applications are very different, so it's not a direct comparison.

 

The Fitbit application doesn't attempt to run in the background constantly, but if it's not running, events will wake the application, and subsequently execute queued tasks. 

 

The iOS ecosystem is a bit more restrictive when it comes to background execution, but it wouldn't explain why you had to relaunch the app once a day. Maybe the Pebble app was misbehaving, and the background or the bluetooth communication got stuck.

 

I hope this helps resolve your question.

 

View best answer in original post

Best Answer
1 REPLY 1

‎09-04-2017 04:24

‎09-04-2017 04:24

The Pebble and Fitbit mobile applications are very different, so it's not a direct comparison.

 

The Fitbit application doesn't attempt to run in the background constantly, but if it's not running, events will wake the application, and subsequently execute queued tasks. 

 

The iOS ecosystem is a bit more restrictive when it comes to background execution, but it wouldn't explain why you had to relaunch the app once a day. Maybe the Pebble app was misbehaving, and the background or the bluetooth communication got stuck.

 

I hope this helps resolve your question.

 

Best Answer