I would like to distribute a Tizen wearable app to a remote client. I don’t want this app to go on the Tizen app store (it is meant for public use, and I don’t want to have to go through the app review process).
Initially, they shipped a few Gear Fit 2 devices to us, we installed on them, and shipped them back, but this is not a great long-term solution.
So far, the best I can come up with is:
1) They install the development tools, connect to the devices, and get the DUIDs of any new devices. (They can do this through the IDE, or with sdb; I found somewhere on one of the forums that you can run “sdb shell /opt/etc/duid-gadget” to get the DUID on the command line.)
2) We create new certificates with the new device IDs and rebuild the apps. We send them the .tpk file.
Private distribution of Tizen wearable apps
I would like to distribute a Tizen wearable app to a remote client. I don’t want this app to go on the Tizen app store (it is meant for public use, and I don’t want to have to go through the app review process).
Initially, they shipped a few Gear Fit 2 devices to us, we installed on them, and shipped them back, but this is not a great long-term solution.
So far, the best I can come up with is:
1) They install the development tools, connect to the devices, and get the DUIDs of any new devices. (They can do this through the IDE, or with sdb; I found somewhere on one of the forums that you can run “sdb shell /opt/etc/duid-gadget” to get the DUID on the command line.)
2) We create new certificates with the new device IDs and rebuild the apps. We send them the .tpk file.
3) They install the .tpk using sdb.
Is there a better way?
-steve
BY
16 Apr 2025
Tizen Studio
BY
04 Nov 2024
Tizen Studio
BY
02 Apr 2024
Tizen Studio