How to enable the Monkey C Compiler with logging enabled?

Yes, this is so typical to Garmin. They already print 2 lines instructing us to send it to that email, but cant include the instructions to how to do that or the link to the documentation of the compiler where we can see the parameters...

BTW: I had loads of these errors. Do you use some constant where this happens? If yes then these 2 things might help:

1. copy the const to a local variable and use the local variable

2. if that's not enough and it's a string then concatenate it to an empty string: var local = "" + MY_CONST;

The crash is pretty obscure:

and here's the code - that has been working fine for three years!

What would you suggest?

Remember, there are three different behaviours:

a) the build fails on vivoactive5 and fr165 with the ERROR: fr165m: A critical error has occurred

b) builds but crashes with "Unhandled execption " at run-time on fenix7

c) builds and runs fine on descentmk351mm

1.a. Fastest is probably using SDK 6.4.2 instead of the buggy 7.1.0. until they fix these things or give us workarounds.

1.b. In some cases it can help if you use https://github.com/markw65/prettier-plugin-monkeyc 'cause it rearranges the source code in a way that might pass the buggy compiler.

2. report the bug with WatchUi.Bitmap.initialize 

Thanks. Reverting to SDK 6.4.2 avoids the build error, so I'll take your advice and wait until a more stable SDK 7 before trying again.

However.....

The issue with the bitmap initialize is more worrying.

I have restored a previous, working copy of my code and it now crashes at runtime with the same error on SDK 6.4.1 and the SDK 6.2.2 that i used for my current version that I released in August last year.

So, the source code is as at Aug last year.

The SDK is as at August last year, but the runtime now creashes.

Since then I have upgraded my Mac to Mac OS 13.6.6 (Ventura). Can that have caused an incompatibility with the way  Monkey C handles bitmaps? 

Here's where the run is crashing

raceQsLogo is this  2k png image:

That I have been using for years!

Any suggestions will be gratefully received.

have you upgraded the device files in the sdk manager? If yes, then you might need to downgrade them.

Not sure what you mean there. How would I downgrade the device files in the SDK manager? All i have done with the SDK manager is to work in the SDK manager to download the SDK and Use as SDK in this UI:

just don't download (yet) any devices in the devices tab

That's a bit hard, as I have already done that! The sole reason for this phase of my work was to implement the devices released by Garmin since Aug last year.

So, my question now is how to undo that if reverting to SDK 6.2.1 doesn't achieve that? 

Here's the current state: