'""C:\Program' is not recognized as an internal or external command, operable program

Hi,

When I have the 1.2.11 SDK set, I can start and run the Simulator on all my projects. When I set the 2.1.2 SDK, I get the error below. The simulator starts, put the Project is not loaded (Simulator is empty).
'""C:\Program' is not recognized as an internal or external command, operable program or batch file.


Anybody any ideas? I looks related to a space in the file path (as I've put the SDK's under C:\Program Files). I've checked all the paths in the Preferences etc.

Cheers
Chris
  • Former Member
    Former Member over 9 years ago
    Sounds like a missing quotation mark at the end of the path.
  • I've got a feeling one, of the automated generated paths, like the one which calls the compiler, isn't working correctly. Especially, as the 1.2.11 SDK works, and not the 2.1.2 on the same setup.

    Plus, I think the double double-quoting at the start of the message is a clue, as it may be added too many quotes.

    None of the UI paths have quotes around.

    Cheers
    Chris
  • Solved: Well workaround for those reading later

    Well, the obvious solution/work-around, was the one. When I moved the Garmin Connect IQ folder to a path without spaces it all worked.

    Garmin Team: This is clearly something that has been introduced in 2.1.x, as it's never been a problem before. It would be worth fixing urgently, otherwise it's going to catch a lot of newbies out.


    Cheers
    Chris
  • Hi,

    Please add a note about this in your "Getting started" instructions, or somehow fix it so that it can be installed to a regular windows "Program Files" subdirectory! Or many "newbies" like myself may have trouble getting it to work on Windows...

    This is not meant as a rant, it is meant as a recommendation for Garmin to follow, in order to get more people like myself programming for Garmin's Connect IQ platform...
  • Former Member
    Former Member over 8 years ago
    Instantly knew this one .. yes, a space. Been there, seen that. This is not new at all but yes, it could be from 2.1.* as that goes back to June 2016. When I got it .. the response was "remove the space".
  • Former Member
    Former Member over 8 years ago
    Hey Everyone,

    If I remember correctly this is working as intended. I have created a ticket in the hopes that this will either be changed to be more user friendly or to have the documentation updated to reflect any changes that were made to spaces in filepaths.

    Thanks,
    Coleman
  • We've updated things to properly handle spaces in paths. This fix will be available in the 2.3.1 SDK release.