Issues with SDK 8.1.x and glance on Fenix 6

I have issues with getting my glance to run with Fenix 6 on SDK 8.1.x.

On SDK 7.4.3 everything works as it should, code builds and glance is shown.

On SDK 8.1.0, I get the following error when building:

 *  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.0-2025-03-04-7ae1ed1cb\bin\monkeybrains.jar -o bin\evccgarmin.prg -f d:\Projects\evcc-garmin\evcc-garmin\monkey.jungle -y d:\Projects\evcc-garmin\ciq-developer-key\developer_key -d fenix6_sim -w

ERROR: null

On SDK 8.1.1 the build works again, but getGlanceView() is not called, instead it goes directly into getInitialView(). Glance Launch Mode is set to Launch in Glance Mode.

If I run the same configuration on a Fenix 6 Pro, the glance works with all three SDK versions.

What do you guys think, is this a bug, or am I missing something else?

  • I saw there were updates to the fenix6, fenix7 devices today.

  • It doesn't seem like this problem was addressed by the device updates (nor would I expect it to be)

    --

    It looks like the changes were:

    - For all of the fenix6*, fenix6*pro, fenix7*, and fenix7*pro devices

    1) update simulator.json layouts for "actionMenu" and "toast"

    2) rebuild [device].bin file (I assume this is the executable that emulates the device in the sim), and update [device].api.debug.xml

    - obviously I'm not sure exactly what changed in the bin file

    - in the debug file, the symbols KEY_ACTION_MENU and BEHAVIOR_ON_ACTION_MENU were added, but not the functions onActionMenu or setActionMenuIndicator

    - For fr165/fr165m:

    3) update simulator.json layouts for "toast" 

    4) same as 2)

    For any who are curious, the devices which now have the KEY_ACTION_MENU and BEHAVIOR_ON_ACTION_MENU symbols in *.api.debug.xml are:

    fenix6*, fenix6*pro, fenix7*, fenix7*pro, fr165, fr165m and vivoactive6

    Only vivoactive6 has setActionMenuIndicator and onActionMenu.

  • It doesn't seem like this problem was addressed by the device updates

    I don't think so as well, I already had the device updates installed during testing of this issue.