Can I download the new SDK on linux without SDK manager.

Ah I found

I don't see the download link for debian.

Where did you get it?

The SDK by itself won;t really do much good, as you also need the devices, which are separate as of 3.2, and that's done with the SDK Manager in addition to the SDK.

Before I had the possibility to work on debian with the SDK 3.1.8, now since the update of exclipse plugins,  the SDK manager is removed  and there are no link to download it.

Odd, it breaks the development env.

See https://forums.garmin.com/developer/connect-iq/b/news-announcements/posts/connect-iq-3-2-now-available

The SDK is only part of what you need as of the 3.2 SDK to be able to run,  The devices and fonts have been separated from the SDK, and they must also be downloaded.  The SDK Manager handles both.

The problem is that there is no need for a GUI to use the SDK and devices, so why is one needed to download them?

The sdkmanager doesn't work for me anyway, but I can download the SDK by using https://developer.garmin.com/downloads/connect-iq/sdks/sdks.json to get its name. There is also another json file here: https://developer.garmin.com/downloads/connect-iq/sdk-manager/sdk-manager.json referenced in sdkmanager but that doesn't work (without auth maybe).

There are also several docker images that use a non-interactive download mechanism. It would be good for them to be able to work too.

You can download the SDK, via that link, but you will need the device configuration files to be able to compile an app. These files can change quite often, so the SDK manager was created so that we have the ability to update them without having to do another SDK release. Unfortunately, this makes it more difficult to do automated builds that want to fetch all necessary tools to do the automated build.

If you're building a docker image, you could download the SDK and the device configuration files to your local machine (using the SDK manager) first and then include them in the docker image or you could expose the files to the docker image via a bind mount or something similar.

Thx, yes at the end I do this. Downloaded the sdk on some live linux and move the files to my server, set the path and now working fine. Sometimes need update when come new device or sdk version but now ok

The only way to do things reliably is to automate them. Having to run a GUI to perform an update is not something you can usefully automate. Nobody can publish a Dockerfile that produces an IQ SDK build system unless they reverse engineer your sdkmanager and reimplement it. Which I would do if it even worked for me at all which it doesn't.