NordicThingy52 Crashes - ConnectIQ SDK 4.2.4

I'm a windows user and don't know all the mac variations, but see this post and the thread it's in.

https://forums.garmin.com/developer/connect-iq/f/discussion/232420/connectiq-simulator-does-not-work-on-macos-catalina/1882531#1882531

If it doesn't crash the same way with the 645, try replacing the 645 with the 645m.

In VSC, go to the Command Palette and select Monkey C:edit products to make the change.

Did you check out the thread I linked about sim crashes on macs?

It seems as though that thread is describing a completely different problem. In that thread, the simulator does not start at all.

The comment you are replying to seems to be describing a situation where apps that use the BluetoothLowEnergy module, such as the NordicThingy52 sample, are causing the sim to crash, even for devices which do support BLE.

I do see two different crashes, one which is related to fr645 vs fr645m (as you said), but still indicates a problem (in the NordicThingy52 sample).

On Windows, with fr645, the app (not simulator) crashes on the following line:

public const THINGY_ENVIRONMENTAL_SERVICE = BluetoothLowEnergy.longToUuid(0xEF6802009B354933L, 0x9B1052FFA9740042L);

And the error is:

Error: Symbol Not Found Error
Details: Failed invoking <symbol>

(Just as in the OP)

Regarding the difference between fr645 and fr645m:

- yes, for me, the crash occurs with fr645 and not with fr645 (or edge1030), on Windows

- yes, the supported devices list at the top of the BluetoothLowEnergy doc says that Forerunner 645 Music is supported (and does not list Forerunner 645). It also lists Venu Sq 2 Music, but not the Venu Sq 2 (non-music) version. These differences are also reflected in *.api.debug.xml (the BLE symbols are missing for fr645 and venusq2)

It seems that the NordicThingy52 SDK sample should be changed so that fr645 is not one of the products listed in the manifest.

So yes, the problems with the app crashing with Venu Sq 2 (non-music) and FR645 (non-music) are due to lack of support for BLE.

However, on Mac, I am finding that if I run the NordicThingy52 sample on a device that supports BluetoothLowEnergy (such as fr645m or fr965), the simulator itself crashes. This is not the same as the app crashing in the simulator as described above.

To be clear, I can run other apps in the simulator just fine. But as soon as I run the NordicThingy52 sample, the simulator crashes with a segmentation fault.

By adding strategic printlns, I was able to find that the crash occurs on line 37 of ProfileManager.mc:

public function registerProfiles() as Void {
    BluetoothLowEnergy.registerProfile(_envProfileDef); // <==== crash here
}

I'm gonna open a bug report for this (and also for the bad product in the NordicThingy52 sample). Thanks for reporting this mmcleod

[https://forums.garmin.com/developer/connect-iq/i/bug-reports/nordicthingy52-sdk-sample-should-not-support-fr645-product-because-sample-requires-ble-but-product-doesn-t-support-ble]

[https://forums.garmin.com/developer/connect-iq/i/bug-reports/bluetoothlowenergy-registerprofile-crashes-simulator-with-segmentation-fault-on-mac-m1-max]

For what it's worth, a similar problem occurs when attempting to run the sample app NordicThingy52CoinCollector.

In this sample app the following attempting device just pop up the simulator window before the simulator crashes, with no Debug Console message:

- Edge1030

- fr645m

- Venu Sq 2 Music

When running the Fenix 5 in the app loads up in the simulator with a blank screen,

Where the following appears in vsc Debug Console:

This looks very similar to the NordicThingy52 issue.  However, I was unable to narrow the issue further using the System.println() strategy FlowState describes.

To my knowledge, these two sample apps are the only ones showcase the BLE API.

All other sample apps I have loaded worked outside the above two listed BLE API sample apps.

Looks like you're using the 7.3.0 SDK.  When reporting things, you really want to use the latest production SDK - 7.4.3.

I've run many of my BLE apps with the 8.0.0 beta SDK, but there also seem to be changes there for the EU-RED stuff.  See https://www.dcrainmaker.com/2025/01/the-begining-of-the-end-for-ant-wireless.html

Here's a video of the breakout session where CIQ BLE was first introduced: https://forums.garmin.com/developer/connect-iq/b/news-announcements/posts/adding-bluetooth-connectivity-to-your-connect-iq-projects

Here's a blog post I did (with code) about using CIQ BLE to talk to a Raspberry Pi: https://forums.garmin.com/developer/connect-iq/b/news-announcements/posts/would-you-like-some-raspberry-pi-with-your-connect-iq

And here's a thread where I have an example of a watch face using a background service to talk to a Thingy52: https://forums.garmin.com/developer/connect-iq/f/discussion/8182/a-very-simple-wf-with-a-background-that-talks-ble-to-the-thingy52

mmcleod said:

When running the Fenix 5 in the app loads up in the simulator with a blank screen,

mmcleod said:

Where the following appears in vsc Debug Console:

As with fr645 and venusq2, fenix5 does not support BluetoothLowEnergy, so it's expected. The app itself is crashing (not the simulator) with a completely expected error message - "Symbol not found" - on the first line that tries to use BluetoothLowEnergy.

public const THINGY_CONFIGURATION_SERVICE = BluetoothLowEnergy.longToUuid(0xEF6801009B354933L, 0x9B1052FFA9740042L); <== line 10 of ProfileManager.mc

Despite the fact that BluetoothLowEnergy is listed as being available since CIQ 3.1.0, it's not the case that all devices with CIQ >= 3.1.0 support it.

To see the list of devices that support BluetoothLowEnergy, you have to visit https://developer.garmin.com/connect-iq/api-docs/Toybox/BluetoothLowEnergy.html and click View Devices (under Supported Devices).

mmcleod said:

For what it's worth, a similar problem occurs when attempting to run the sample app NordicThingy52CoinCollector.

In this sample app the following attempting device just pop up the simulator window before the simulator crashes, with no Debug Console message:

- Edge1030

- fr645m

- Venu Sq 2 Music

This looks like the exact same bug that occurs with NordicThingy52 sample, discussed above. The simulator itself is crashing (which indicates a bug in the sim), not the app within the simulator (which usually indicates a bug in the program).

I narrowed down the crash to BluetoothLowEnergy.registerProfile() by using printlns, as before:

    //! Register the bluetooth profile
    public function registerProfiles() as Void {
        System.println("before crash");
        BluetoothLowEnergy.registerProfile(_soundProfileDef); // <=== crash (previously line 27)
        System.println("after crash");
    }

On my Mac, only "before crash" is printed to the console and not "after crash". This is the full console output:

before crash
[FSocket Error in packet header 0

The 2nd line suggests that the Monkey C extension had trouble communicating with the sim when the sim crashed.

jim_m_58 said:

Looks like you're using the 7.3.0 SDK.  When reporting things, you really want to use the latest production SDK - 7.4.3.

I already recreated the issue with 7.4.3 and reported it, as mentioned above.