• Replies 18 replies
  • Subscribers 14 subscribers
  • Views 2337 views
  • Users 0 members are here
Options
Related

Unable to build with Connect IQ 2.4.1

abs0d
over 7 years ago
I have a project working fine with Connect IQ 2.3.5 (and earlier versions).

Just tried to switch the SDK to 2.4.1 and have two issues

a) When I select 2.4.1 in the Connect IQ SDK Manager it does not switch to "Current SDK"
b) Attempting to build or clean the project fails with the following error
Errors occurred during the build. Errors running builder 'Connect IQ Builder' on project 'trainasone-connectiq'. File 'bin\devices.xml' does not exist File 'bin\devices.xml' does not exist File 'bin\devices.xml' does not exist File 'bin\devices.xml' does not exist


This is under Windows 10, latest Eclipse and Java8
  • over 7 years ago
    I tried updating another system.

    I saw the prompt to update to the 2.4.1 SDK first, and clicked through to the SDK manager, downloaded 2.4.1 and it was shown as the current SDK, I then ran the Eclipse update which pulled down the 2.4.1 plugin, after which the SDK manager no longer indicated 2.4.1 as current (and switching back and forth did not fix that).

    Looks like I'm stuck with 2.3.5 for now. If there was anything I really needed in 2.4.1 I'd create a copy of 2.3.5, confirm it worked then piecemeal merge 2.4.1 into it to workout where the problem was, but I've been down a fair number of quite deep rabbit holes related to SDK issues from when I started writing a ConnectIQ app, so I'll come back to this some other time.

    (Obviously I'll try switching again if there is a new SDK or plugin and update this post)

  • over 7 years ago
    Make a backup copy of this file (in the 2.4.1 SDK folder tree): "bin\api.debug.xml" Then edit the original file by replacing all occurrences of 'D:\\jenkins\\workspace\\Tech-CIQ-Rel-Win\\mbsimulator' with '..'. This should make your 2.4.1 SDK installation be recognized as valid.
  • Former Member
    Former Member over 7 years ago
    Just an update. A change got merged today that should address this bug. I don't know specific details on when a release will be available but it should be included in the 2.4.2 release.

    We believe the issue is that the build server that generates SDK releases checks out and builds on the D drive which is why you are seeing the paths that start with "D:\\jenkins..". This causes a problem within the plug-in if you don't have a D drive mounted on your local machine when we attempt to read the api.debug.xml file while validating the SDK directory.
  • over 7 years ago
    Make a backup copy of this file (in the 2.4.1 SDK folder tree): "bin\api.debug.xml" Then edit the original file by replacing all occurrences of 'D:\\jenkins\\workspace\\Tech-CIQ-Rel-Win\\mbsimulator' with '..'. This should make your 2.4.1 SDK installation be recognized as valid.


    that worked great for me - thanks!
  • over 7 years ago
    Thanks for the update (and for the workarounds). Will pickup with 2.4.2

    David
  • over 7 years ago
    Make a backup copy of this file (in the 2.4.1 SDK folder tree): "bin\api.debug.xml" Then edit the original file by replacing all occurrences of 'D:\\jenkins\\workspace\\Tech-CIQ-Rel-Win\\mbsimulator' with '..'. This should make your 2.4.1 SDK installation be recognized as valid.


    Just updated to SDK 2.4.2: still needed to use this workaround :(
  • over 7 years ago
    Just updated to SDK 2.4.2: still needed to use this workaround :(

    According to the comments from Ken, the fix requires an update to the plugin. Are you using the 2.4.2 plugin?