Device does not support version 3.2.0

Former Member over 4 years ago

Visual Studio Code problems:

Why do I get this error?

No matter what device I use, I cant run the app.

I am using the latest SDK, although there was just an announcement that a new version is up, but the latest I see is still from October...

Top Replies

Travis.ConnectIQ over 4 years ago +2 verified

We released a new SDK manager that should fix this issue yesterday. After installing the new version, you will need to remove and re-install the problematic devices so that the fonts are properly installed…
Travis.ConnectIQ over 4 years ago +1 verified

You're encountering at least 2 different errors.

The first image indicates that you are trying to simulate a device (either the fenix6 or fenix6pro) that uses a font that is not available on your computer…
Manuel B. over 4 years ago +1

My solution is not ideal but it is better than nothing until there is a new version of the SDK Manager.

I copied one of the existing fonts which I believe is similar enough and renamed it.

In my case I…

All Replies

0 jim_m_58 over 4 years ago

It's not the SDK, it's the devices - the second tab in the SDK Manager.

And the fr935 doesn't support the 3.2 functions. It's still on a 3.1 VM.

0 jim_m_58 over 4 years ago in reply to jim_m_58

What I'm thinking is that you had the fr935 as a target but then changed the minCIQ to 3.2.0 in the manifest, then tried to use the 935 in the sim.

0 Travis.ConnectIQ over 4 years ago

You're encountering at least 2 different errors.

The first image indicates that you are trying to simulate a device (either the fenix6 or fenix6pro) that uses a font that is not available on your computer. You could look in the listed folder to see if you can find the font, but my guess is that it is not there.

I'm tinkering with SDK Manager right now and if I clear out my %AppData%\Garmin folder and download the fenix6 devices, I'm not seeing the necessary font files get downloaded. This indicates that there is some sort of problem with the device bundles that we've created. I will have to work with @Kyle to see if we can figure out what happened.

As for the second error, I'm pretty sure @jim_m_58 has hit the nail on the head.

0 Former Member over 4 years ago in reply to Travis.ConnectIQ

Travis - I'm seeing the exact same issue as I try to follow along with the tutorial. Is there somewhere else I can download the appropriate fonts? or another way to build or download the device bundles?

Thanks, -Eric

0 Former Member over 4 years ago in reply to Travis.ConnectIQ

Realized I should add to my message below - it works fine if I build for the Forerunner 935 but breaks when I run for the VENU, due to the missing fonts.

-Eric

0 Travis.ConnectIQ over 4 years ago in reply to Former Member

No, there is nothing you can do. We need to push a new SDK manager (if that hasn't already happened).

0 Manuel B. over 4 years ago

My solution is not ideal but it is better than nothing until there is a new version of the SDK Manager.

I copied one of the existing fonts which I believe is similar enough and renamed it.

In my case I want to simulate the Fenix6X Pro which is effected by the missing font FNT_FENIX6X_CDPG_ROBOTO_25B.cft.

So I copied C:\Users\<name>\AppData\Roaming\Garmin\ConnectIQ\Fonts\FNT_FENIX5_ROBOTOCONDENSEDBOLD_26PX.cft to FNT_FENIX6X_CDPG_ROBOTO_25B.cft and it works.

+1 jim_m_58 over 4 years ago in reply to Manuel B.

The problem there is in the sim, you won't see how things really look on a real device, as far as spacing, etc, I wouldn't publish any apps until this is corrected.

0 Manuel B. over 4 years ago in reply to jim_m_58

I agree!

0 Travis.ConnectIQ over 4 years ago

We released a new SDK manager that should fix this issue yesterday. After installing the new version, you will need to remove and re-install the problematic devices so that the fonts are properly installed.