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: 

Does anyone have tips on memory management?

‎11-22-2021 20:47 - edited ‎11-22-2021 20:57

‎11-22-2021 20:47 - edited ‎11-22-2021 20:57

I'm having trouble keeping my app under the limit

Best Answer
Labels:
1 REPLY 1

‎11-22-2021 22:33

‎11-22-2021 22:33

Hi, me too. This came about in the transition from SDK 4.2 to 4.3.

The generated code is different [for the same program] than before and no longer fits in memory, simply rebuilding an app that worked in 4.2 won't even load with 4.3, though the original [4.2] app is running fine.

Even removing some of the original code didn't help make it fit memory.

You may have to give up supporting older watches [pre Versa 2].

Most annoying.

Author | ch, passion for improvement.

Best Answer
0 Votes