Acknowledged
5 months ago

BUG: EDGE 1040 - CIQ 4

Something changed today. SDK Manager downloaded some new devices. And all of a sudden, EDGE 1040s return monkeyVersion: 4.2.4! That is broken.

Yesterday they properly returned 5.0.0.

EDGE 840 devices still do the right thing, returning 5.0.0.

So my fetch process is relegated to the background when emulating a 1040 now, rather than the foreground.

JUST FYI - use an 840 when testing in the simulator so you aren't limited by the 5 min delay.

DaveBrillhart
  • 5 months ago in reply to FlowState

    I haven't seen any evidence that suggests a device config with 4.2.4 was pushed for the Edge 1040. There are systems in place that prevent backdating device configs, but it isn't entirely impossible to be updated to with an earlier CIQ version number.

    I am unsure what could have occurred to cause this to happen, but I redownloaded the Edge 1040 device configs and they are on 5.0.0 currently.

  • 5 months ago

    Thanks @richard.connectiq, that explains the other bug that was referenced.

    I'm curious about what might've happened here, where OP reported that edge1040 has apparently been reverted to 4.2.4 in its device config file. It seems that this problem was only rectified when OP deleted the existing device config and redownloaded it.

    Is it possible that a bad device update was actually pushed for edge1040?

  • 5 months ago in reply to FlowState

    The instinct3solar45mm device config folder was briefly named instinct3solar and then later updated. Having both would have duplicate part numbers and cause build errors. At the moment the SDK manager doesn't have a process for automatically deleting devices that are no longer relevant. This was intentional in the case that someone wanted to continue developing with an old preview device. A way to improve this is being explored.

  • 5 months ago

    As per the other thread, this problem was resolved by moving away the existing device folder and re-downloading it via the SDK manager.

    Which raises the question: was a bad device update temporarily made available? If so, how many people did this affect? Was it not possible for the SDK manager to replace the bad update with a good update, if and when the problem was found on Garmin’s end?

    I’m just wondering how widespread and frequent this kind of problem is, and whether it’s possible in principle for the SDK manager to automatically recover from it, rather than the dev taking manual steps.

    After all, not everyone will necessarily know that they received a bad update.

    This also reminds me of another bug where a developer apparently received a bogus device that nobody else has (“instinct3solar”) in addition to the valid device everyone else has (“instinct3solar45mm”), which caused export issues when both were selected. If in fact the SDK manager received a bad device at one point, it seems that again, there was no way for the SDK manager to automatically recover from this issue.

    https://forums.garmin.com/developer/connect-iq/i/bug-reports/connect-iq-sdk-7-4-3-export-duplicate-entry-error-for-instinct-3

  • 5 months ago

    Did you try deleting the device folder (or moving it away) and re-downloading it?

    As I mentioned in the other thread, I don't see this problem in Windows or Mac for the edge1040 device..