I also need postalCode information, and the new API do not provide it. Is there any update about FB8648023 ? by the way, it's private, I can't see the details of this request. I also did see it is mentionned in a stackoverflow message in 2020 (more than 5 years ago) ! Does this reduce chances it will be considered by Apple?

Thank you for your answer You can find attached a recent crash log MyRecentCrash.crash

Hello Thanks a lot for your feedback I have delayed my CLMonitor.init function to be called after receiving didFinishLaunchingNotification notification I was expecting this to fix the issue since the didFinishLaunchingNotification is received after the app finishes launching, but what I observe is that I am still having dozens of users having CLMonitor related crashes, very similar to the initial ones. The crash is still occurring immediately after app launch, when calling CLMonitor.init function Are there any recommendations on when I should call CLMonitor.init? Should I delay my CLMonitor.init call few seconds after app launch? Thanks in advance for your help

Thank you for your answer I attached a crash log with the details I can share for the moment myCrash.crash

Thanks for your answer Here are more details about the issue: I have another thread having CLMonitor in its stacktrace: Thread 3: 0 libsystem_kernel.dylib 0x00000001d97f63e4 kevent_id + 8 1 libdispatch.dylib 0x000000019115cb00 _dispatch_kq_poll + 228 (event_kevent.c:760) 2 libdispatch.dylib 0x000000019115d50c _dispatch_event_loop_wait_for_ownership + 436 (event_kevent.c:2236) 3 libdispatch.dylib 0x0000000191149a20 __DISPATCH_WAIT_FOR_QUEUE__ + 340 (queue.c:1704) 4 libdispatch.dylib 0x00000001911495e8 _dispatch_sync_f_slow + 148 (queue.c:1799) 5 CoreLocation 0x0000000196df4a2c -[CLMonitor _getMonitoringRecords] + 188 (CLMonitor.mm:179) 6 libswiftCoreLocation.dylib 0x000000021680ae54 CLMonitor.init(_:) + 84 (CLMonitor.swift:281) 7 libswiftCoreLocation.dylib 0x000000021680a991 CLMonitor.__allocating_init(_:) + 1 (CLMonitor.swift:0) 8 MyModule 0x0000000103918f55 closure #1 in MyService.setupTask() + 1 (MyService.swift:33) 9 MyModule 0x00000001039145c1 $sxIeAgHr_xs5Error_pIegHrzo_s8SendableRzs5NeverORs_r0_lTRyt_Tg5TATQ0_ + 1 (/<compiler-generated>:0) 10 libswift_Concurrency.dylib 0x0000000194b47e39 completeTaskWithClosure(swift::AsyncContext*, swift::SwiftError*) + 1 (Task.cpp:497) no other thread mention CoreLocation or CLMonitor except these 2 threads. and here is what my setupTask function look like func setupTask() { self.myTask = Task(priority: .high) { if #available(iOS 18.0, *) { // create my session } let monitor = await CLMonitor(myIdentifier) self.myMonitor = monitor for try await event in await monitor.events { if event.state == .unsatisfied { let record = await monitor.record(for: event.identifier) // use record condition and lastEvent } else if event.state == .satisfied { let record = await monitor.record(for: event.identifier) // use record condition and lastEvent } } } }

Any update? I am facing the same issue with transformable attributes with Xcode 16 beta 6 fault: Declared Objective-C type "[Int]" for attribute named .... is not valid CoreData: fault: Declared Objective-C type "[Int]" for attribute named .... is not valid CoreData: Declared Objective-C type "[Int]" for attribute named .... is not valid