Given an arbitrary watch and an arbitrary .uapp, I'm trying to answer, "is this app supported on this watch?".
The doc says two things:
https://github.com/UNAWatch/una-sdk/blob/0f17b5c7157553ead8f091b042ab51a5e6a977c0/Docs/app-config-json.md?plain=1#L31C1-L34C1
This file is intended solely for defining supported features and displaying them in the mobile application. It should not contain runtime information or settings for the watch and should not be uploaded to the watch during application installation.
All information needed by the watch is also embedded in the *.uapp file.
minKernelVersion is the compatibility gate but it only exists in config.json. The second statement holds for the watch itself, which just runs the apps, but not for anything deciding whether it is appropriate to install it (e.g., a distributed community-authored app).
- Is
LibCVersion in the header the intended proxy for runtime compatibility?
- If so, is the firmware's LibC/kernel version discoverable outside BLE?
The context is that I'm authoring and installing my own apps and want to get ahead of any compatibility concerns if I upgrade and an app is no longer going to be valid to install.
Given an arbitrary watch and an arbitrary
.uapp, I'm trying to answer, "is this app supported on this watch?".The doc says two things:
https://github.com/UNAWatch/una-sdk/blob/0f17b5c7157553ead8f091b042ab51a5e6a977c0/Docs/app-config-json.md?plain=1#L31C1-L34C1
minKernelVersionis the compatibility gate but it only exists inconfig.json. The second statement holds for the watch itself, which just runs the apps, but not for anything deciding whether it is appropriate to install it (e.g., a distributed community-authored app).LibCVersionin the header the intended proxy for runtime compatibility?The context is that I'm authoring and installing my own apps and want to get ahead of any compatibility concerns if I upgrade and an app is no longer going to be valid to install.