Unknown Exit Code

Former Member
Former Member
When trying to use the app export wizard it returns an error with the following text.

Package Manager: The compiler returned an unknown exit code: 143

I'm using SDK 1.2.1 in eclipse on Mac OS X
  • Former Member
    Former Member over 9 years ago
    I was able to solve this problem by removing Epix from supported devices, I tested it several times and every time I removed it, it exported correctly and when it was selected I got the error.
  • I'm glad you were able to get that working. I've done some testing here with building packages with subsets of devices, and unfortunately, I'm not able to eliminate the unknown exit code error simply by removing epix. I'll mention it on our bug report, just in case there's some significance.

    Thanks!
  • I've found that if I get the error when exporting, if I just try again without changing anything, it will work.

    Same type of thing doing a run in the simulator. I'll get an error message at the end, but no errors in the compile itself. If I simply just do the "run" again, it may work, but if not a 3rd "run" will - again, without changing anything. It's like there are time that either the compiler is returning a bogus error code, or the CIQ plug-in is looking at the wrong status code.

    Eclipse Luna, CIQ 1.2.1, Windows 10, and JRE 1.8.0_31.
  • I'm glad you were able to get that working. I've done some testing here with building packages with subsets of devices, and unfortunately, I'm not able to eliminate the unknown exit code error simply by removing epix. I'll mention it on our bug report, just in case there's some significance.

    Thanks!


    Hello Garmin Team,
    Since SDK 1.2.1 I do also get the error code for many of my watch faces:

    "The compiler returned an unknown exit code: 1"

    I made some experiments with my watch faces. For all my watchfaces where I use "more" bitmaps than just the watchface background, I do get the error code and I can't make the build anymore. If I take out the additional bitmaps, at one point the build is possible.
    Perhaps this gives you an indication where to look to fix this problem.
    It would be great if you have a solution for this problem soon.

    (I am aware of the "console" workaround, mentioned in the different thread)


    Best Regards
    Christoph
  • Former Member
    Former Member over 9 years ago
    I'm glad you were able to get that working. I've done some testing here with building packages with subsets of devices, and unfortunately, I'm not able to eliminate the unknown exit code error simply by removing epix. I'll mention it on our bug report, just in case there's some significance.

    Thanks!


    I haven't actually been able to get it to work again after this one time even if epix is removed so I think it just randomly worked that time and don't think that had anything to do with it.
  • Hi, there seems to be a timeout error. The workaround is simple:
    Copy the execution command line from the console window and execute it in the console.
    There shpould be something like this:

    BUILD: C:\Program Files\Java\jre7\bin\java -Dfile.encoding=UTF-8 -Dapple.awt.UIElement=true -classpath C:\Program Files\Java\jre7\lib\tools.jar;C:\Users\wawando\Downloads\connectiq-sdk-win-1.2.1\bin\monkeybrains.jar; com.garmin.monkeybrains.Monkeybrains -e -a C:\Users\wawando\Downloads\connectiq-sdk-win-1.2.1\bin\api.db -i C:\Users\wawando\Downloads\connectiq-sdk-win-1.2.1\bin\api.debug.xml -o C:\Users\wawando\Desktop\AppWizard\MAMILwatchface.iq -z C:\Users\wawando\workspace\MAMILwatchface\resources\bitmaps.xml;C:\Users\wawando\workspace\MAMILwatchface\resources\resource\resources.xml;C:\Users\wawando\workspace\MAMILwatchface\resources\strings.xml -m C:\Users\wawando\workspace\MAMILwatchface\manifest.xml -u C:\Users\wawando\Downloads\connectiq-sdk-win-1.2.1\bin\devices.xml -p C:\Users\wawando\Downloads\connectiq-sdk-win-1.2.1\bin\projectInfo.xml C:\Users\wawando\workspace\MAMILwatchface\source\Analog.mc
    BUILD: Complete
    Package Manager: The compiler returned an unknown exit code: 1

    Copy this part:
    C:\Program Files\Java\jre7\bin\java -Dfile.encoding=UTF-8 -Dapple.awt.UIElement=true -classpath C:\Program Files\Java\jre7\lib\tools.jar;C:\Users\wawando\Downloads\connectiq-sdk-win-1.2.1\bin\monkeybrains.jar; com.garmin.monkeybrains.Monkeybrains -e -a C:\Users\wawando\Downloads\connectiq-sdk-win-1.2.1\bin\api.db -i C:\Users\wawando\Downloads\connectiq-sdk-win-1.2.1\bin\api.debug.xml -o C:\Users\wawando\Desktop\AppWizard\MAMILwatchface.iq -z C:\Users\wawando\workspace\MAMILwatchface\resources\bitmaps.xml;C:\Users\wawando\workspace\MAMILwatchface\resources\resource\resources.xml;C:\Users\wawando\workspace\MAMILwatchface\resources\strings.xml -m C:\Users\wawando\workspace\MAMILwatchface\manifest.xml -u C:\Users\wawando\Downloads\connectiq-sdk-win-1.2.1\bin\devices.xml -p C:\Users\wawando\Downloads\connectiq-sdk-win-1.2.1\bin\projectInfo.xml C:\Users\wawando\workspace\MAMILwatchface\source\Analog.mc

    Note: because of the problems with the spaces in windows, I do a CD: C:\Program Files\Java\jre7\ and remove the parts indicated highlighted in blue

    I hope this helps!

    And garmin, please fix this, it is annoying and leaves developers with no way to publish if they don't use this workaround
  • To complement what WAWANDO said, i've created a ".bat" file to be executed and Replaced in Notepad "Program Files" to "Progra~1"

    Simple as 1, 2, 3 and worked fine as workaround.

    Garmin Please!
  • This has proven to be a tricky bug because it's not 100% reproducible, and we think the problem is somewhere in the Java VM (we don't receive much information in the console logs when debugging that point to the cause). We're actively re-working the Eclipse plug-in to address this issue, however. I run into it often myself, so I'll be just as happy as you will be once this is fixed. :)
  • This has proven to be a tricky bug because it's not 100% reproducible, and we think the problem is somewhere in the Java VM (we don't receive much information in the console logs when debugging that point to the cause). We're actively re-working the Eclipse plug-in to address this issue, however. I run into it often myself, so I'll be just as happy as you will be once this is fixed. :)


    Brandon,
    Thanks for the feedback! I'm sure this will be past very soon!