Acknowledged

BluetoothLowEnergy.registerProfile() crashes simulator with segmentation fault on Mac with M1 Max, macOS 14.5

SDK: 7.4.3

Macbook Pro 16-Inch, 2021 (M1 Max)

macOS 14.5 (23F79)

Recreation procedure:

- Use M* Mac

- Open NordicThingy52 SDK sample

- Build and run the app for any supported device (not fr645), such as fenix5plus. (fr645 does not support BLE, therefore it's a different bug that the sample has this product in its manifest.xml)

- The simulator will crash with a segmentation fault (the system will offer to send a report to Apple - press Report... to see the details of the crash)

- The exact line of the crash can be narrowed down by adding printlns before and after line 37 in ProfileManager.mc

public function registerProfiles() as Void {
  System.println("before crash"); // <== new println
  BluetoothLowEnergy.registerProfile(_envProfileDef); // <== (originally) line 37
  System.println("after crash"); // <== new println
}

In this case, "before crash" will be printed to the console, but not "after crash". If I comment out the line with registerProfile, the app does not crash. I am also able to run other (non-BLE) apps just fine.

I would post the full crash log, except the forum won't accept it.

Crashed Thread:        9  ant_main

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Codes:       0x0000000000000001, 0x0000000000000000

Termination Reason:    Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process:   exc handler [40065]

Looks like a null pointer exception to me.

Idk if this line near the end is relevant:

> Bluetooth: Version (null), 0 services, 0 devices, 0 incoming serial ports

Note that bluetooth is in fact enabled on my Macbook.

Parents
  • For what it is worth I have also tried calling this same function within a custom app, and experienced the same crash while using SDK 7.4.3 on my M1chip MacBook Air. 

    The app is intended to load to the Edge1030 device in the simulator.

Comment
  • For what it is worth I have also tried calling this same function within a custom app, and experienced the same crash while using SDK 7.4.3 on my M1chip MacBook Air. 

    The app is intended to load to the Edge1030 device in the simulator.

Children
No Data