How to enable the Monkey C Compiler with logging enabled?

II have returned after  a few months to update my app with the new devices and while testing, received the following:

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

My question is: how do I enable logging in the compiler? I don't see that  option in the Monkey C extensions settings. I have enabled Compiler warnings.

SDK 7.10, Mac Ventura 13.6.6 

P.S. I get the same error when testing with my default device : fenix7 ERROR: fenix7: A critical error has occurred. so there's something odd happening 

It compiles and runs fine on the (new) descentmk343mm 

I'll revert to an older SDK and see what happens

Fenix 7 builds but crashes at run-time!

OK, found the command line to generate the log: --debug-log-level 3 --debug-log-output "log.txt"

Run, build failed, log generated and sent to Garmin Support.:  [email protected]

  • You need to close it (the window) and then change to another version in SDK Manager, then run, and it'll not only commpile with the selected SDK but also use its simulator.

  • HMMMM, just tried that, but SIM still crashes Feels like something is being "cached" between transitions between SDK versions.

    I have restarted the Mac, but still have the SIM  running SDK 6.4 and crash on the : a configuration that runs fine on the device at the same place with

    "Error: Unhandled Exception Exception: UnexpectedTypeException: Expected Graphics.BitmapType or bitmap ResourceId"

  • Here's an odd feature: The app runs in the on a fenix5 simulator without a crash.

    The crashing line of code is common to both devices and uses the same resource: the png file mentioned above.

     It runs fine on both devices and on the Fenix5 sim, but crashes on the Fenix7 sim.

    So there is something very odd happening.

  • There was an issue in our device configs that were uploaded for devices that support 5.0.0. We're currently uploading new configs that should fix this issue. If you're still having problems after downloading the new configs, file a bug report in the bug report forum and we'll take another look at it.

  • Could you clarify the procedure for “downloading the new configs “ please?

    I, along with many other developers, am a single-app developer using Garmin devices to host my application algorithms for which I get no financial reward but have generated significant sales income for Garmin. I am not a geeky millennial with enthusiasm to "get under the hood" of the Garmin ecosphere.

    Please just make your bit work reliably and intelligibly so that we can continue to deploy our algorithms on the evermore bewildering array of devices. 

    And deal with us transparently as peers, not as mushrooms.

    [END RANT]

  • Could you clarify the procedure for “downloading the new configs “ please?

    Open the SDKManager, click on the devices tab.  You can see if there are updates in any of the 3 categories, or drill down and see if there is an update for a specific device.

  • The problem is this:

    he app runs in the on a fenix5 simulator without a crash.

    The crashing line of code is common to both devices and uses the same resource: the png file mentioned above.

     It runs fine on both devices and on the Fenix5 sim, but crashes on the Fenix7 sim.

    So there is something very odd happening.

     has suggested "downloading the new configs"

    You are suggesitng 

    Open the SDKManager, click on the devices tab.  You can see if there are updates in any of the 3 categories, or drill down and see if there is an update for a specific device.

    I have the devices tab open, but the Fenix7 does not appear as a "New" (or updated) device.:

    I am confused.

    [EDIT]

    I am still confused, but now, without doing anything, my app runs on fenix7_sim.

  • The Fenix7 series are devices with CIQ 5 (System 7), like Kyle mentioned.  Won't see "new" unless you didn't have the device in the past.

    I don't see "new" for the f7 pro (no wifi) as I've had that devices since it was first announced

  • I don't see "new" for the f7 pro (no wifi) as I've had that devices since it was first announced

    That's because I have just this week returned to do the housekeeping since my last update back in September.