Critical error from compiler

I get critical compiler errors relatively regularly. It is not really reproducible, when it occurs I just need to rerun the compiler and it works fine.

 *  Executing task: monkeyc: Building For Device 

java -Xms1g -Dfile.encoding=UTF-8 -Dapple.awt.UIElement=true -jar c:\Users\Robert\AppData\Roaming\Garmin\ConnectIQ\Sdks\connectiq-sdk-win-8.1.1-2025-03-27-66dae750f\bin\monkeybrains.jar -o bin\evccg.prg -f d:\ProjectsLocal\evccg\monkey.jungle -y d:\Projects\evcc-garmin\ciq-developer-key\developer_key  -d epix2pro47mm_sim -w --debug

ERROR: epix2pro47mm: A critical error has occurred. Please re-run the Monkey C Compiler with logging enabled and file a report with the Connect IQ support team ([email protected]).

 *  The terminal process terminated with exit code: 100. 
 *  Terminal will be reused by tasks, press any key to close it.

What is meant exactly by enable logging? I already activated the --debug option, but the output above is all I get.

Top Replies

FlowState 30 days ago +1

https://developer.garmin.com/connect-iq/monkey-c/compiler-options/

All Replies

0 FlowState 30 days ago

https://developer.garmin.com/connect-iq/monkey-c/compiler-options/

0 the-ninth 30 days ago in reply to FlowState

Thanks, I only checked the first table with the --debug option and did not see the section below.

Have the debug activated now, so next time it happens I can report an issue.

0 the-ninth 30 days ago in reply to the-ninth

This put me in a real catch-22:

With SDK 7.1.1 and my current code, enabling debugging causes the compiler to crash. In the log.zip/error.txt file, I see an error like "Compiler internal exceptions: 1 Cannot determine parent for type checking," though I'm not sure if that's the actual cause.

If I disable debugging, the code compiles fine.

In SDK 8.1.1, the code compiles without issues even with debugging enabled. However, there are other (simulator-related) problems with 8.1.1, so I need to stick with 7.1.1 for testing. I know there are ways to combine the newer compiler with the older simulator, but I’d rather avoid complicating the setup. For now, I'll forgo debug logging. Besides, the chances of Garmin responding to a bug report on this seem pretty slim.

0 flocsy🤠 29 days ago

I think Garmin should just add that to the same sentence... Brandon.ConnectIQ

As for critical errors: I do have lot of them since SDK 8.x. Unfortunately I'm less lucky, my problems seem to be more consistent. There was 1 case where I could avoid it by refactoring my code, but in other cases I'm still waiting for Garmin to release a fix and those apps can't be compiled/updated

0 the-ninth 29 days ago in reply to flocsy🤠

When discussing the 8.1.1 compiler issues, there’s another temporary problem I’ve noticed: the code tree lights up like a Christmas tree - many files turn red, and the compiler reports a bunch of errors. However, if I compile again, everything is fine: the red disappears and the build succeeds.

Regarding this issue, I’m wondering if it could be related to the project using Git - perhaps Git is blocking some files while the compiler is running.

Both of these issues happen when I compile in VS Code, either using F5 or the “Build for Device” command.

0 flocsy🤠 29 days ago in reply to the-ninth

I use git and have t seen this