Are there any plans to support this functionality in the future?

Here's some more info of the 2nd crash I listed in my comment: Exception Type:	EXC_BAD_ACCESS (SIGSEGV) Exception Subtype: KERN_INVALID_ADDRESS at 0x5d5cc0004c297280 VM Region Info: 0x5d5cc0004c297280 is not in any region.	Bytes after previous region: 6727463042841932417	 			REGION TYPE											START - END						 [ VSIZE] PRT/MAX SHRMOD	REGION DETAIL 			MALLOC_NANO (reserved) 00000001d8000000-00000001e0000000 [128.0M] rw-/rwx SM=NUL	...(unallocated)-->	 			UNUSED SPACE AT END

I found a better example with Symbolicated values. Here's the thread that crashed: Thread 0 Crashed: 0	 libsystem_c.dylib						 0x000000018440e38c strlen + 12 1	 CoreLocation									 0x000000018b226cc4 CLCommonEnTrHashReduceInjest + 60 (CLCommon.mm:2023) 2	 CoreLocation									 0x000000018b209068 CLClientTraceDelegateMonitorCallback + 52 (CLClient.mm:2624) 3	 CoreLocation									 0x000000018b21b57c -[CLLocationManager onClientEventRegion:] + 1500 (CLLocationManager.m:2141) 4	 CoreLocation									 0x000000018b219f70 -[CLLocationManager onClientEvent:supportInfo:] + 1064 (CLLocationManager.m:0) 5	 CoreLocation									 0x000000018b2039e8 invocation function for block in CLClientInvokeCallback(__CLClient*, CLClientEvent, objc_object*) + 140 (CLClient.mm:745) 6	 CoreFoundation								 0x0000000184a232bc CFRUNLOOP_IS_CALLING_OUT_TO_A_BLOCK + 20 (CFRunLoop.c:1840) 7	 CoreFoundation								 0x0000000184a22a7c __CFRunLoopDoBlocks + 264 (CFRunLoop.c:1881) 8	 CoreFoundation								 0x0000000184a20abc __CFRunLoopRun + 2004 (CFRunLoop.c:3176) 9	 CoreFoundation								 0x0000000184940da8 CFRunLoopRunSpecific + 552 (CFRunLoop.c:3245) 10	GraphicsServices							 0x0000000186926020 GSEventRunModal + 100 (GSEvent.c:2245) 11	UIKit												 0x000000018e960758 UIApplicationMain + 236 (UIApplication.m:3965) 12	MyApp												 0x0000000104e9c534 0x104e94000 + 34100 13	libdyld.dylib								 0x00000001843d1fc0 start + 4

Is there any update to this? I'm having the same problem