peterdedecker said:

beva said:

wonder if System.getDeviceSettings().uniqueIdentifier is constant and unique for each installed simulator.

...not a bad idea at all.

Yeah, this idea is is the best one since it would be supported for CIQ >= 2.4.1 and doesn…

The thing is that there are (at least?) 7 "types" of apps:

1. $ on the button (Garmin Pay / new merchant app):

2. old Payment Required banner:

3. sneaky apps that never worked without a subscription or payment, but Garmin let them because they…

From context and your other recent posts, I assume you are talking about a full-screen data field (i.e. it's used in a 1-field layout). (I assume that the timer overlay and bell feature are only available for activities, for one thing, which means that…

I suspect the limitation has to do with the fact that they can not handle the launching aspect of the complication.

That could be part of it but I think the overall reason is that complications are only meant for watchfaces, by design. It's in the name…

I think the only viable solution here is to catch any exception that's thrown by DataField.showAlert().

The fact that the "Alert/Settings is active for current datafield" exception is not documented is annoying. Who knows if it's Lang.OperationNotAllowedException…

flocsy said:

Or instead of multiple sources you can keep it in source/Foo.mc only and use similar logic with excludeAnnotations

This is what I do but tbh excludeAnnotations are a huge pain when you have multiple "dimensions" of exclusion (e.g. screen…

The logo dimensions differ on almost all devices. IMHO you don't need to scale it, when you build for any device you'll see the "warning" in the console that it's being automatically resized. I usually make it big enough for the biggest size needed, so…

My apologies, this is, really, a follow on question from another in which I had mentioned what I was using.  I'm using the Analog sample project from the 3.1.9 SDK as my starting point and coding for a Vivoactive 4s.

Analog.prg does, in fact, use a…