BUG: EDGE 1040 - CIQ 4

DaveBrillhart said:

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

I'm guessing you're talking about a CIQ data field, based on this (since it's CIQ data fields which gained the ability to use Communications in the foreground with CIQ 5). Just FYI, you can't assume everyone will automatically know that.

Same as not everyone will know that by "fetch process", you mean Communications.makeWebRequest or something similar.

DaveBrillhart said:

And all of a sudden, EDGE 1040s return monkeyVersion: 4.2.4! That is broken.

On a Windows PC, I let the SDK manager update my devices (including an update for edge1040), as I have not updated devices on that machine for a while. I found that:

- the main part number for edge1040 still has a connectIqVersion of 5.0.0 (strangely, the APAC part number has a version of 5.0.1, but that probably doesn't matter)

- DeviceSettings.monkeyVersion has the following value at runtime: [5, 0, 0]

- the simulator shows a CIQ version of 5.0.0 in the title bar. The full string is roughly "CIQ Simulator - Edge 1040 / 1040 Solar (5.0.0)"

If I delete the edge1040 device from the SDK manager and redownload it, I get the same results.

I also tested this on a Mac, which did not have any device updates in the SDK manager (as I update a bit more frequently there). So I just deleted the edge1040 device and redownloaded it, and verified that I do not see the problem there, either.

It's possible that you received some erroneous device updates which have been withdrawn by Garmin.

You could try deleting the edge1040 device folder (or moving/copying it somewhere else), then redownloading the device, to see if you still get the bad device definition.

If you still do, it would probably be worth filing a bug report.

That was true yesterday. When I ran SDK Manager today, it updated a few devices. And all of a sudden today, for me, the EDGE 1040 returns 4/2/4 when I grab the monkeyCversion.

I tried SDK 8 (beta), and I get the same thing. THANKS!! I renamed the Devices folder, and the SDK Manager rebuilt it with a new download. And now it reports 5/0/0.

Cool, so it sounds like maybe it was a bad device update that was now fixed. If that’s actually the case, it’s too bad the SDK manager seemingly wasn’t able to automatically overwrite the bad update with a good update.

Glad it’s working for you now!

I will also note that another way for you to redownload a device would be to delete it from the SDK manager (using the X button) and press the download button. I only suggested moving/copying the existing device folder so that you could preserve the evidence that the device config was broken.