Automatic adding of new apac to DF

I think I know this, but wanted to be sure!

When you check to allow Garmin to add new devices to a compiled field in the store, that is just for new versions of the devices you checked in the manifest, right?

For example, I’ve got a specifically CIQ1 version that would run (very well) on many other devices, but that I want to restrict.

Obviously, I can (and will in a few minutes- now that I’ve thought of it) uncheck that box, but if I didn’t, what would be the result?

Would it stay forever as CIQ1 (as no new versions of those, I strongly suspect) or would it slowly take over the world?

0 jim_m_58 over 5 years ago

I'm not really sure what your asking. When you add targets, all you see are the ROW versions, but when you build an iq file, APAC devices are included, as long as they meet things like min CIQ version. When you upload to the store, what's in the iq are "compatible devices" that can down load the app. When you remove a target, build an iq, and upload, that (those) targets are no longer available.

What happens on the device is they won't get an update if the app is no longer compatible, and I believe on some, the app may be removed if it's no longer compatible.

0 9635560 over 5 years ago in reply to jim_m_58

I think my question boils down to what is and is not a compatible device for auto migration.

If it is, say, “different flavours of basically the same watch as selected by the developer” then I can leave it checked.

If it is instead, “anything that is same basic family but newer” then I’d see CIQ2 and CIQ3 devices being added - which I explicitly want to block.

0 jim_m_58 over 5 years ago in reply to 9635560

While APAC is what I mentioned in one post, there are other cases. For example, when the va3 came out, auto migration was used from the Approach S60

0 9635560 over 5 years ago in reply to jim_m_58

Got it. So the question becomes how are auto migration matches chosen?

Not familiar with either (though I remember getting caught out by the way s60 is an oddity that lacks :energyExpenditure I think), but it’s hard to see, logically, that there is a limit.

Eg: If it runs on a basic CIQ1 watch and doesn’t use anything beyond Activity.Info, then pretty safe to assume it can run on anything. Why not auto migrate an Fr230 app all the way to a Fr945?

I mean, clearly that doesn’t happen. But the why is interesting.

0 jim_m_58 over 5 years ago in reply to 9635560

This got to be "similar enough", and that means things like screen shape and size, memory sizes for different apps, and other things.

0 jim_m_58 over 5 years ago in reply to jim_m_58

automigration for a new APAC devices is really nothing in most cases. No new devices, just a variant of an existing devices.

When new devices like a new fenix, forerunner, etc, is added, that's when you can see how it works, where a existing device can get auto-migrated to a whole band new, just announced device. The reason that's done, is so right away, a whole bunch of apps are available for that shiny new device.

There is a setting in the store so you can turn off auto-migration for an app if that worries you.