What's partNumber?

It's the part number for the watch. This info is also in devices.xml, and is used in building the .iq file - it's how builds for different devices are organized in the .iq.

each different device has it's own part number, and they differ between ROW (Rest Of World) devices and APAC (Asian-Pacific) devices, for example. A f5 ROW device has a different part number than an f5 APAC device for example.

If you are looking for a way to uniquely ID a watch, in 2.4.x there is Sys.getDeviceSettings().uniqueIdentifier

Hi Jim,

That's what I am looking for (unique identifier). How can I double check programmatically whether a device is on 2.4.+?

How can I double check programmatically whether a device is on 2.4.+?

In DeviceSettings there should be a monkeyVersion member that is an array containing version numbers. If you are wanting to verify +2.4 for a specific feature that was introduced in that version, then it might be preferred to just run a has check on that feature.

That's what I am looking for (unique identifier).

That is not really a unique identifier. The partNumber for my fenix5x is the same as the partNumber for Jim's.

This is something that has come up before, and it is definitely on our radar.

Travis

This is something that has come up before, and it is definitely on our radar.

Does this mean that the API'S description is fixed or that a really unique ID is introduced in an upcoming IQ version?

That is not really a unique identifier. The partNumber for my fenix5x is the same as the partNumber for Jim's.

Does this mean that the API'S description is fixed or that a really unique ID is introduced in an upcoming IQ version?

Travis, are you referring to the uniqueIdentifier member or the partNumber member in DeviceSettings when you say that it "is not really...unique"?

I'm thinking Travis was referencing partNumber and not uniqueIdentifier, as it seems the whole purpose of uniqueIdentifier is to be a, well, uniqueIdentifier :) Consistent for the same app on the same device even if the app is updated, but different for the same app on a different device is what I understand

Yes, sorry for the confusion. It was late, I hadn't read all of Jim's post, and I hadn't looked to see if the uniqueIdentifier field had made it into the 2.4.x release or not. I should've known better..

To summarize, partNumber has been around for a while, and it is not unique. The uniqueIdentifier field is new and is unique.. it depends on several factors including the application, developer and user. If you want to see if uniqueIdentifier is available, you don't need to check the version, should use a has check.

var deviceSettings = Sys.getDeviceSettings();
if (deviceSettings has :uniqueIdentifier) {
}


Travis

Travis,

You said above that uniqueIdentifier depends on several factors including application, developer and user.

Does the specific watch factor in ?

Two situations come to mind... If a user has to replace a watch does the uniqueIdentifier change for a given app ?

If a watch is sold to someone else, will the same app downloaded through a new user's account have a different uniqueIdentifier ?

If I have two of the same device, the part numbers will match.

If I install the same app on both, uniqueIdentifier will differ on each device.

If I install a second app on one of them, uniqueIdentifier will differ between the two apps.

If I update one of the apps involved, they will keep the same uniqueIdentifier.

if a device is replaced, it will have a new uniqueIdentifier if the same app is installed

I doubt Garmin will talk about the actual algorithm used, as if they did, that could lead to security issues.

What happens if you sell a device and someone else uses the same app is a good question, and it's something you can check out yourself by just creating a second Garmin account, deleting the apps, move the device to the second account, install the same app and checking the uniqueIdentifier.