CIQ Simulator shows "A debugging check in this application has failed" after upgrade Connect IQ SDK 4.2.4

I haven't been able to reproduce this, so I probably need more details. Does this occur with any app, or just a specific one? Since it sounds like this is a problem with the simulator itself, does this occur when launching the simulator without running an app?

I haven't been able to reproduce this, so I probably need more details. Does this occur with any app, or just a specific one? Since it sounds like this is a problem with the simulator itself, does this occur when launching the simulator without running an app?

This info may help. I am on the latest SDK and have the latest device files.  I built a prg file for fenix7 which works fine.  If I run monkeydo changing only the device from fenix7 to fenix7x I get the assert errors.  I moved the fenix7x Devices files to a tmp dir and copied the fenix7 files to the fenix7x dir. I renamed the fenix7x/fenix7.bin to fenix7x/fenix7x.bin and I still get the assert failures with the fenix7x device, so the error has nothing to do with the files in the Devices directory. nor the prg file. 

I am facing the same issue and could reproduce it in the following fresh configuration:
- Ubuntu 22.04, up to date as of 2023-09-16 running in VirtualBox 7.0.10 on a Linux host
- SDK Manager v1.0.8
- SDK Connect IQ 6.3.0
- Devices Epix Pro (Gen 2) 47mm
- Visual Studio Code from Snap
- Sample empty project, following [1] "Getting Started" and [2] "Your First Connect IQ App"

[1] https://developer.garmin.com/connect-iq/connect-iq-basics/getting-started/#gettingstarted
[2] developer.garmin.com/.../

Here is a video capture of the issue: https://ipfs.io/ipfs/QmaaLKzuo6h7nnkqtuFoidRkA2jN9vEgFV5zTc3GvGuYU8

I can share my Virtualbox image for if I learn how to remove my credentials from it, but recreating it should be trivial since I just followed the instructions from the "Connect IQ Basics" pages above.

Seems like those are duplicates:
- https://forums.garmin.com/developer/connect-iq/i/bug-reports/simulator-assertion-failed-in-menucmn-cpp-308-for-some-devices (on Windows 10) 
- https://forums.garmin.com/developer/connect-iq/i/bug-reports/fenix-7x-simulator-crashes-when-i-try-to-run-any-app

I see it on the latest SDK 6.2.2 on all of my widgets and apps on Epix devices and Fenix 7X PROs.  I get the assertion failures when launched from vscode or CLI.  When launched from CLI, the app/widget will run correctly if 'continue'ing on assertion failures.  The app/widget does not start when launched from vscode.  These failures occur on linux but not on Windows.

I just had the same issue. I was trying to implement a TimePicker / NumberFactory (I think they originally are examples from you at garmin) and the crash happened on Fenix7 in simulator. Fenix5plus and FR230 worked.

Since I'm a newbie I thought a implemented functions that were deprecated and only works on older devices, but it works on Fenix7S (in simulator) and crashes on e.g. Fenix 7 and Fenix 7X (also in simulator).

Before I started fiddling with the timepicker, simulation worked on all devices I tried. If i remove the source files, simulation still doesn't work. Does this help narrowing down the root cause?

Hi I'm getting the same two errors on:

- A fresh Ubuntu VM

- With the SDKManager and devices newly-installed for the first time this morning

- Using SDK 4.2.4

../src/common/menucmn.cpp(308): assert "wxIsStockID(GetId())" failed in SetItemLabel(): A non-stock menu item with an empty label?                                                                              
../src/common/stockitem.cpp(219): assert ""Assert failure"" failed in wxGetStockLabel(): invalid stock item ID

But it depends on which device I use, so I do not get the errors with:

`monkeyc -o bin/APP.prg -f monkey.jungle -y ~/connect-iq-developer-key -r -d fenix5plus & monkeydo bin/APP.prg fenix5plus`

but I do get the errors with:

`monkeyc -o bin/APP.prg -f monkey.jungle -y ~/connect-iq-developer-key -r -d fenix7xpro & monkeydo bin/APP.prg fenix7xpro`

If I ignore/close the errors (they appear in popups) the app seems to work correctly. I do use `menuItem.setSubLabel()` in my app and it continues to work as expected despite the errors.