We are also experiencing similar NSXPCConnection issue, not on the authorization status request though, but when reading latest location property on CLLocationManager.
Here is the stacktrace:
0 libsystem_kernel.dylib_mach_msg_trap
1 libsystem_kernel.dylib_mach_msg
2 libdispatch.dylib__dispatch_mach_send_and_wait_for_reply
3 libdispatch.dylib_dispatch_mach_send_with_result_and_wait_for_reply$VARIANT$mp
4 libxpc.dylib_xpc_connection_send_message_with_reply_sync
5 Foundation___NSXPCCONNECTION_IS_WAITING_FOR_A_SYNCHRONOUS_REPLY__
6 Foundation-[NSXPCConnection _sendInvocation:orArguments:count:methodSignature:selector:withProxy:]
7 CoreFoundation____forwarding___
8 CoreFoundation___forwarding_prep_0___
9 CoreLocation0x1871cefe0 (0x1871cef38 + 168)
10 CoreLocation_CLClientRetrieveLocationWithDynamicAccuracyReductionAndAlteredAccessoryLocations
11 CoreLocation0x1871cc8f4 (0x1871cc5ec + 776)
12 Lyft<compiler-generated>
@nonobjc CLLocationManager.location.getter
13 LyftCoreLocationManager.swift:108:30
CoreLocationManager.location.getter
14 Lyft<compiler-generated>
protocol witness for CoreLocationManagerProtocol.location.getter in conformance CoreLocationManager
...
In our case, there is no clear pattern on app state, device or iOS version. The distribution between foreground and background app state is 3:1, i.e. in 75% reports the app is in foreground. Around 55% is iOS 15+, the rest is the earlier versions.
Any clue on possible root cause is much appreciated.
OleksandrStepanovLyft
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen