ERROR: venusq: 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]).

Hi everyone,

This is a little urgent

I was making builds for debugging my app. Everything was working fine yesterday. Today, I wanted to change a single variable in my code and rebuild, but I am getting the error: ERROR: venusq: 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]). Even when I change the variable back to what It was yesterday, I cannot rebuild it.

I tried going back to previous App projects that worked perfectly and I left them untouched, but the same error is appearing when I try to make another build of them. I have no idea how to re-run the compiler, and I have urgent work I needed to finish today.

I was hoping someone could help. I have the most recent SDK (6.2.1) and have verified the Monkey C extension. I have also tried switching to older SDKs, but still no luck.

  • For anyone looking back on this forum with the same issue, I was able to kinda fix the problem. Here are some bullet point tips I would go through until something worked:

    - When choosing a directory to save the debug build, make it the auto folder the computer prompts you to save in.

    - If the prompted folder still gives issues, try the last folder you saved a debug build in. (if you don't want to rewrite the old build, put the old one in a new folder first -- sometimes I had no choice but to rewrite on the old build)

    - Unforchantly, you may have to start a new project. When you do, copy/paste old lines one by one (or chunk by chunk), and every time your project is in a runnable state try to run a simulation. (one issue I had was a new error found in a line that wasn't detected in the last project -- even though the simulation ran perfectly in the old project)

    Overall, I think this issue starts happening when you make more than one build (with slight differences) and/or start saving the builds in different folders. This issue is very annoying because even when you comment out recent changes so it's in a state that worked previously, the error still appears. Practically forcing you to re-do everything and delay the debugging process.

    Hopefully, someone in Garmin sees this post and tries to address the issue.

    Best of luck

  • idk if this helps, but I think:

    - "Build Current Project" is meant for simulator builds (and is equivalent to what happens when you Run a project that needs to be built). In this case you're not even able to choose an output folder

    - "Build For Device" is meant for sideloads (and in this case you're prompted for an output folder - typically I choose a folder that's different from the default of bin\)

    YMMV. In another post, someone fixed their build issues by selecting "Delete All Apps" in the simulator.

  • Thank you! I'll try that out next time I see the error. 

    To clarify for other readers -- my issue was only when I built for a device.

  • , if you can still reproduce this can you run the compiler again using the --debug-log-level and --debug-log-output options and email the output to [email protected]? This will help us determine why it wasn't building and allow us to fix the problem.

    --debug-log-level  <arg>  Debug logging verbosity [0=errors, 1=basic,
                              2=intermediate, 3=verbose]
    --debug-log-output <arg>  Output log zip file

  • I just encountered this kind of error, because my project name has Chinese characters, change to English will be fine. I hope it helps

  • Are there specific Chinese characters in the project name that were causing a problem? We haven't been able to reproduce so far, so if you have additional information that might be helpful, we'd appreciate it!

  • I had same problem because of exclamation mark in path of project folder (!)

  • I also got this error message, so I wanted to do the build with the debug enabled, but there are 2 issues:

    1. I'm not sure if VSC or the Monkey C plugin writes this to the terminal when I build, but it would be useful if the parameters that contain spaces would be either escaped or put in double quotes, so we can copy&paste it and use it. In my case the stupid Mac folders include a space:

    Executing task: java -Xms1g -Dfile.encoding=UTF-8 -Dapple.awt.UIElement=true -jar /Users/me/Library/Application Support/Garmin/ConnectIQ/Sdks/connectiq-sdk-mac-6.4.2-2024-01-04-a1dd13ee0/bin/monkeybrains.jar -o bin/MyDataField.prg -f /Users/me/MyDataField/monkey.jungle;/Users/me/MyDataField/barrels.jungle -y /Users/me/garmin_developer_key.der -d epix2pro42mm_sim -w

    2. The bigger problem is that when I copy&paste it to a terminal (and fix the space issue) then I get an error:

    ERROR: The private key was not specified. Use command line option: -y.

    This would be bad enough just for the fact that I just copy&pasted it and I expect it to work as is. But it's even worse that the error message doesn't make sense, as the command already includes: -y /Users/me/garmin_developer_key.der

    Please advise

  • not sure what shell macos uses, did you tried like this? :

    "/Users/me/Library/Application\ Support/Garmin/ConnectIQ/Sdks/connectiq-sdk-mac-6.4.2-2024-01-04-a1dd13ee0/bin/monkeybrains.jar"


    or 

    /Users/me/Library/Application\\ Support/Garmin/ConnectIQ/Sdks/connectiq-sdk-mac-6.4.2-2024-01-04-a1dd13ee0/bin/monkeybrains.jar

    maybe tripple backslash

  • You didn't get my point. I added the backslash myself. My problem is that it doesn't compile because:
    ERROR: The private key was not specified. Use command line option: -y.