Bug: New FR 255 Software Crashes CIQ App

Kyle.ConnectIQ, that solved the problem! Thanks for pointing me in the right direction.

For others who may have the same issue, removing things like `System.getDeviceSettings().screenWidth;` and `Math.rand()`, and `(Communications has :startSync)` from the global namespace seemed to fix the issue for me. (I'm not sure removing the has check did anything, I just removed it to be safe).

I confirm the fact that the F7 and FR255 series watches crashed after updating the firmware.

The crash occurs when trying to createBufferedBitmap with a 1x1 pixel two-color palette.

         var DC = bufferedBitmapFactory(
         {
             :width=>1,
             :height=>1,
             :palette=> [
                 0,
                 0xffffff
             ]
        });
        var tDc=DC.getDc();
        if (tDc.getTextWidthInPixels(v, $.DFont)<=l) {
            return v;
        }

//===============================================================================================
//! Factory function to create buffered bitmap
function bufferedBitmapFactory(options as {
            :width as Lang.Number,
            :height as Lang.Number,
            :palette as Lang.Array<Gfx.ColorType>,
            :colorDepth as Lang.Number,
            :bitmapResource as Ui.BitmapResource
        }) as Gfx.BufferedBitmapReference or Gfx.BufferedBitmap {
    if (Gfx has :createBufferedBitmap) {
        return Gfx.createBufferedBitmap(options).get();
    } else {
        return new Gfx.BufferedBitmap(options);
    }
}

Also.

I receive approximately the following letters:

手表更新新系统之后不显示中文了。

After the watch is updated to the new system, it no longer displays Chinese.

There was a similar letter about the Romanian language.
According to the observations of another user, after resetting the watch to the factory state, the date was displayed in Chinese, but after reboot the date is displayed in English.

See if https://forums.garmin.com/developer/connect-iq/i/bug-reports/app-with-api-6-4-2-doesn-t-start-since-firmware-16-22-anymore is the cause of the problem.