On os x 11.1 the simulator crashes with a seg fault. Is it something I did?

I went through the connect iq setup found here:

developer.garmin.com/.../

The simulator crashes with a seg fault. What have I done?

Process: simulator [2715]
Path: /Users/USER/Library/Application Support/Garmin/*/ConnectIQ.app/Contents/MacOS/simulator
Identifier: com.garmin.connectiq.simulator
Version: 3.1.9 (3.1.9)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: simulator [2715]
User ID: 501

Date/Time: 2020-12-28 09:55:01.809 -0600
OS Version: macOS 11.1 (20C69)
Report Version: 12
Anonymous UUID: 9A86E6D9-E3F2-7B5A-FB08-596C65CB0C37


Time Awake Since Boot: 3300 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000008
Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [2715]

VM Regions Near 0x8:
--> 
 __TEXT 10a064000-10b9da000 [ 25.5M] r-x/r-x SM=COW /Users/*/Library/Application Support/Garmin/*/ConnectIQ.app/Contents/MacOS/simulator

mkpaa over 4 years ago

I am getting the same error. Latest Visual studio code, Connect IQ SDK and MacOS.

Apart of the usual steps I got rid of the space in the path, but that didn't change anything.

Edit: To clarify the setup. Connect IQ SDK 3.2.2 works from command line but Connect IQ SDK 3.2.3 crashes with segmentation fault 11. Visual code obviously doesn't work with either because it requires minimum version 3.2.3.

mkpaa over 4 years ago

A workaround is:

1) Start 3.2.2 simulator from the command line

2) Have current-sdk.cfg set to 3.2.3 in a path without spaces

Good use of quite a few hours to figure out what was wrong...