what causes XPC error Connection interrupted - ios

I have piece of code that fires couple of requests using NSURLsession and sometimes I get the below message on debugger of xcode
received XPC error Connection interrupted for message type 3
kCFNetworkAgentXPCMessageTypePACQuery
I am thinking what causes this issue ?
Is it something to be worried about ?
Googling doesn't help much

Maybe it is caused by Network Proxy like VPN/VPS ,close them and Command R again.

I got exactly the same error.
During the first attempt I had the VPN on. After turning it off the message did not appear.

Related

AudioOutputUnitStart() fails with error 268451843

I had the call to AudioOutputUnitStart() fail once with error code 268451843.
The only information I was able to find is from ossstatus.com, error description is
Didn't get a message within the timeout value.
There were no errors during AudioUnit initialisation and the error has happened once. I don't know how to proceed to debug it. Have you ever encountered similar problems?
AudioUnit is initialised and started by the CallKit thread on audio session activation.
The problem has occurred after removing and inserting back the headphones.

Maximo cannot deliever message to endpoint

I've created an interaction in maximo 7.6 and when I try to run it, I get this error message:
BMXAA1481E - Cannot deliver the message to the endpoint. Internal
Error
I've tried fixing it, but nothing works, does anyone how to fix this or even why does it pop up?

Upload task using the NSURLSessionUploadTask causing NSURLErrorDomain error -999

I am using the NSURLSessionUploadTask to upload a file to a server. Once the task is resumed, everyone now and then it fails with the error code
NSURLErrorDomain error -999
Now there is no cancel code anywhere in the app. What causes this to get canceled?
I've run into a similar issue before, the answer for me was that another same request was made before the previous request completed. I would check with breakpoints to see if your method that is uploading the file to the server might be hitting twice. Of course it could be another problem, hard to know without seeing any code but I would start there.
So the -999 in my case was a red herring. There were few misleading information on the iOS side :
The -999 error saying it was cancelled, which is user cancellation. This is not true.
The error message had the NSURLErrorBackgroundTaskCancelledReasonKey set to NSURLErrorCancelledReasonUserForceQuitApplication which was again not correct.
The actual problem was the upload file was too big for the server to accept, so the server cancelled the upload. However the translation of the server canceling the event made the error be -999 with the NSURLErrorCancelledReasonUserForceQuitApplication being the reason.

Apple Push - didReceiveIncomingPushWithPayload not called - instead error: Failed sending message to client

I have an app that uses pushkit (voip push).
Most of the time the pushes get through. But when there is a lot of traffic, the pushes don't get through to the app.
I am in a state where I can somehow reproduce the error.
I used the extended logging from here:
https://developer.apple.com/library/ios/technotes/tn2265/_index.html
And I found this to examine the logging:
http://iosdevelopertips.com/core-services/debug-failed-push-messages-by-logging-apsd-process.html
Still, I got two different cases, where I just don't get further:
- In the apsd-log I get
Received message for enabled topic ...
and in the app the didReceiveIncomingPushWithPayload is not called. I produce a log entry right at the start of the function and do nothing special that could prevent the function from finishing.
- In the apsd-log I get
Stream error occurred ...
but do not find any other error messages, why this error occurs.
The Port seems ok
After restarting the app the pushes get through again.
EDIT:
The relevant error in the log file seems to be:
apsd[82]: Failed sending message to client: com.apple.telephonyutilities.callservicesdaemon.voip.push.development
There seems to be two types of cases: In some cases, which are reproducable with large traffic, reregistering the pushkit seems to help.
In other cases, which occur random, it simply does not. Restarting the app does not help here either.
All helps so far, is restarting the iphone.
EDIT:
I am still struggling with this problem.
In some cases I get a memory warning before the push seems to fail.
In other cases I get a xpc communication warning like this:
SpringBoard[43] <Warning>: Communications error: <OS_xpc_error: <error: 0x3b7ef614> { count = 1, contents =
"XPCErrorDescription" => <string: 0x3b7ef86c> { length = 22, contents = "Connection interrupted" }
}>
In some cases none of the above happens, but push still does not work.
EDIT:
In developer archive I found this very interesting thread, but still no answer:
https://devforums.apple.com/thread/257354?start=50&tstart=0
Does anybody know if there is a connection between xpc and push?
And is there a way to detect a xpc error in code?

Trouble with GCDAsyncSocket ReadTimeoutError

I'm using XMPP & OpenFire for my iOS project. The internet connection is stable.
Everything is fine on the first sign in. However from the second time on (sign out then sign in again), it rarely works.
I oftens get readTimeoutError after 10-15s :
Error Domain=GCDAsyncSocketErrorDomain Code=4 "Read operation timed out" UserInfo=0xa8db6a0 {NSLocalizedDescription=Read operation timed out}
Because of that, the app doesn't jump to - (void)xmppStreamDidConnect:(XMPPStream *)sender, thus i'm not connected with OpenFire.
I've spent the whole day on this issue but still can't find the solution. Can anyone help me ?
Found the problems you are facing. Please close your sockets correctly, it will be fine.

Resources