05-01-2021 06:20
05-01-2021 06:20
How do you take an existing *.FBA file and load it over the developer bridge?
Similar to the Sideload in OS simulator.
Author | ch, passion for improvement.
Answered! Go to the Best Answer.
05-02-2021 00:02
05-02-2021 00:02
Thanks, my thought too!.
However you can't do that because the UUID already exists [for the published clock] and it won't let you upload it.
What worked was to create a test clock in GAM, take the UUID and edit the FBA with the test UUID.
To do that it was necessary to rename the FBA to ZIP and extract and update all the elements in the internal Zips with the test GAM clock UUID and rename it back to FBA and then it was possible to upload it GAM and then install it from a private GAM link.
Would be simpler if there was a way to do it directly from Studio, as you proposed too, in order to verify past, present [or future] versions of a published clock or App on a watch where the Simulator does not handle testing the features, eg vibration
In addition, unless you remove the clock with the FBA UUID, from the production watch, you must be using a test watch, which necessitates a test account, so the FBA is all you really have to work with!
If you try to create a mirror project and build that, there is no process to import the exported ZIP [equivalent to the FBA].
Surely there must be a way to Sideload to developer bridge an existing FBA to avoid those complicated processes?
Author | ch, passion for improvement.
05-01-2021 19:21
05-01-2021 19:21
I don't think you can.
You would have to upload the .fba to gam.fitbit.com and then download it from the link, or export the project if you have the code and then sideload it from studio.fitbit.com or the cli.
I think this should be a feature though.
05-02-2021 00:02
05-02-2021 00:02
Thanks, my thought too!.
However you can't do that because the UUID already exists [for the published clock] and it won't let you upload it.
What worked was to create a test clock in GAM, take the UUID and edit the FBA with the test UUID.
To do that it was necessary to rename the FBA to ZIP and extract and update all the elements in the internal Zips with the test GAM clock UUID and rename it back to FBA and then it was possible to upload it GAM and then install it from a private GAM link.
Would be simpler if there was a way to do it directly from Studio, as you proposed too, in order to verify past, present [or future] versions of a published clock or App on a watch where the Simulator does not handle testing the features, eg vibration
In addition, unless you remove the clock with the FBA UUID, from the production watch, you must be using a test watch, which necessitates a test account, so the FBA is all you really have to work with!
If you try to create a mirror project and build that, there is no process to import the exported ZIP [equivalent to the FBA].
Surely there must be a way to Sideload to developer bridge an existing FBA to avoid those complicated processes?
Author | ch, passion for improvement.