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: 

Question about the best approach for updating an older app to new SDK 5.0

ANSWERED

‎10-02-2020 04:58

‎10-02-2020 04:58

I have an app that was built for the Ionic and Versa using SDK 4.2. I would like to update the app to use SDK 5.0 to support Sense and Versa3. Is it best to create a new project using SDK 5.0 or update the older project and update the code to take advantage of the new features? I'm afraid if I update the older project, then need to go back to make bug fixes for the Ionic, I would loose my older code. I'm just looking for suggestions to the best approach to take.

thanks

Best Answer
0 Votes
1 BEST ANSWER

Accepted Solutions

‎10-02-2020 09:48

‎10-02-2020 09:48

Right now, it is left up to the developer to manage two separate 4.2 and 5.0 projects, and to create two separate builds. Both builds can be uploaded to the same GAM app entry, but the developer must manually update the UUID in one of the builds to match the other, creating a shared UUID. The UUID value is contained in the project package.json file. If using Fitbit Studio, before you can manually edit the UUID, you must rename the package.json file so that it gets handled as a text file, rather than with the Project Configuration user interface.

 

From what I've seen, the approach works well for smaller projects. However, it can become complicated with large or multiple projects. Hopefully, the process will be streamlined in the future -- for example, Fitbit incorporating targeted builds in the development tools.

View best answer in original post

Best Answer
1 REPLY 1

‎10-02-2020 09:48

‎10-02-2020 09:48

Right now, it is left up to the developer to manage two separate 4.2 and 5.0 projects, and to create two separate builds. Both builds can be uploaded to the same GAM app entry, but the developer must manually update the UUID in one of the builds to match the other, creating a shared UUID. The UUID value is contained in the project package.json file. If using Fitbit Studio, before you can manually edit the UUID, you must rename the package.json file so that it gets handled as a text file, rather than with the Project Configuration user interface.

 

From what I've seen, the approach works well for smaller projects. However, it can become complicated with large or multiple projects. Hopefully, the process will be streamlined in the future -- for example, Fitbit incorporating targeted builds in the development tools.

Best Answer