firebase-ios-sdk icon indicating copy to clipboard operation
firebase-ios-sdk copied to clipboard

[Sessions] Prevent gathering MCCMNC when under simulator

Open samedson opened this issue 3 years ago • 2 comments

Without this, customers get many failed xpc errors in their console logs.

2022-10-31 15:41:59.824110-0400 AppQualityDevApp[95667:2639392] [Client] Updating selectors failed with: Error Domain=NSCocoaErrorDomain Code=4099 "The connection to service named com.apple.commcenter.coretelephony.xpc was invalidated: failed at lookup with error 3 - No such process." UserInfo={NSDebugDescription=The connection to service named com.apple.commcenter.coretelephony.xpc was invalidated: failed at lookup with error 3 - No such process.}
2022-10-31 15:41:59.824197-0400 AppQualityDevApp[95667:2639271] [Client] Synchronous remote object proxy returned error: Error Domain=NSCocoaErrorDomain Code=4099 "The connection to service named com.apple.commcenter.coretelephony.xpc was invalidated: failed at lookup with error 3 - No such process." UserInfo={NSDebugDescription=The connection to service named com.apple.commcenter.coretelephony.xpc was invalidated: failed at lookup with error 3 - No such process.}
2022-10-31 15:41:59.824375-0400 AppQualityDevApp[95667:2639390] [Client] Updating selectors failed with: Error Domain=NSCocoaErrorDomain Code=4099 "The connection to service named com.apple.commcenter.coretelephony.xpc was invalidated: failed at lookup with error 3 - No such process." UserInfo={NSDebugDescription=The connection to service named com.apple.commcenter.coretelephony.xpc was invalidated: failed at lookup with error 3 - No such process.}
2022-10-31 15:41:59.824503-0400 AppQualityDevApp[95667:2639271] [Client] Synchronous remote object proxy returned error: Error Domain=NSCocoaErrorDomain Code=4099 "The connection to service named com.apple.commcenter.coretelephony.xpc was invalidated: failed at lookup with error 3 - No such process." UserInfo={NSDebugDescription=The connection to service named com.apple.commcenter.coretelephony.xpc was invalidated: failed at lookup with error 3 - No such process.}
2022-10-31 15:41:59.824666-0400 AppQualityDevApp[95667:2639271] [Client] Synchronous remote object proxy returned error: Error Domain=NSCocoaErrorDomain Code=4099 "The connection to service named com.apple.commcenter.coretelephony.xpc was invalidated: failed at lookup with error 3 - No such process." UserInfo={NSDebugDescription=The connection to service named com.apple.commcenter.coretelephony.xpc was invalidated: failed at lookup with error 3 - No such process.}
2022-10-31 15:41:59.824675-0400 AppQualityDevApp[95667:2639392] [Client] Updating selectors failed with: Error Domain=NSCocoaErrorDomain Code=4099 "The connection to service named com.apple.commcenter.coretelephony.xpc was invalidated: failed at lookup with error 3 - No such process." UserInfo={NSDebugDescription=The connection to service named com.apple.commcenter.coretelephony.xpc was invalidated: failed at lookup with error 3 - No such process.}
2022-10-31 15:41:59.827712-0400 AppQualityDevApp[95667:2639390] [Client] Updating selectors failed with: Error Domain=NSCocoaErrorDomain Code=4099 "The connection to service named com.apple.commcenter.coretelephony.xpc was invalidated: failed at lookup with error 3 - No such process." UserInfo={NSDebugDescription=The connection to service named com.apple.commcenter.coretelephony.xpc was invalidated: failed at lookup with error 3 - No such process.}
2022-10-31 15:41:59.827794-0400 AppQualityDevApp[95667:2639390] [Client] Updating selectors after delegate addition failed with: Error Domain=NSCocoaErrorDomain Code=4099 "The connection to service named com.apple.commcenter.coretelephony.xpc was invalidated: failed at lookup with error 3 - No such process." UserInfo={NSDebugDescription=The connection to service named com.apple.commcenter.coretelephony.xpc was invalidated: failed at lookup with error 3 - No such process.}

#no-changelog

samedson avatar Oct 31 '22 19:10 samedson

@visumickey we were seeing empty values for these calls on the Simulator.

Let me dig into the exact circumstance more. I thought it was simulator but don't see a definitive answer online.

samedson avatar Oct 31 '22 20:10 samedson

@visumickey we were seeing empty values for these calls on the Simulator.

Let me dig into the exact circumstance more. I thought it was simulator but don't see a definitive answer online.

Quite possible it is the simulator. But my question was the reasoning behind skipping them. Why would you want to skip populating these information on simulator?

visumickey avatar Oct 31 '22 20:10 visumickey

Closing - this is disabled for Crashlytics anyways so it only impacts FirePerf customers (who already experience this via the FirePerf SDK)

samedson avatar Feb 06 '23 19:02 samedson