Installing / Updating eclipse Connect-IQ module

Am i the only one unable to update the Connect-IQ modules within eclipse ?

I had a working 2019.3 eclipse with Connect-IQ 3.x, i was able to update eclipse but not the Connect-IQ module.

The update tool list the 4.0.4 version but any attempt fail with:

An error occurred while collecting items to be installed
...
No repository found containing: osgi.bundle,IQ_AppSettingsEditor,4.0.4
No repository found containing: osgi.bundle,IQ_IDE,4.0.4
No repository found containing: osgi.bundle,IQ_PackageWizard,4.0.4
No repository found containing: osgi.bundle,IQ_SdkManager,4.0.4
No repository found containing: org.eclipse.update.feature,connectiq.feature.ide,4.0.4
No repository found containing: org.eclipse.update.feature,connectiq.feature.sdk,4

Same thing on a fresh installation...

jim_m_58 over 5 years ago

Have you looked at:

https://developer.garmin.com/connect-iq/connect-iq-basics/getting-started/

about loading the plugin?

6077006 over 5 years ago

Same issue and error message for me running a brand new install of Eclipse 2021.03 and SdkManager. Followed the getting started guide.

FCS7 over 5 years ago

+1

I updated Eclipse a few minutes ago successfully (to version 2021-03) but I can't update the ConnectIQ plugin to version 4.0.4 getting the same error above.

I checked the repository URL in Eclipse and it's fine.

Running the SDK Manager (1.0.2) works fine as well, I was able to update the SDK and the device files.

Only problem is updating the Eclipse plugin.

5770232 over 5 years ago

Same with Eclipse 2021.03 and 2020.12. The latest SDK version for download is 4.0.3. So it seems like the eclipse plugin version was bumped one patch version too high. Hopefully the eclipse plugin version 4.0.4 is being uploaded to the repository and we'll have to wait (shortly) for it being available.

6077006 over 5 years ago

Working now. Based on the history of these errors over the past 4 years on this forum, seems the bulk of the issues are on the Garmin dev side and get resolved after they've done something on their side to fix. So I'm guessing that's the case here as well.

silmaril34 over 5 years ago in reply to 6077006

Indeed !

They probably failed a deploiement ...