Network error code -1001

Solar2D Network
#1

I’ve recently upgraded my project to use the Corona Network V2.0 code. I’m developing for iOS and monitor logs by using the iPhone Configuration Utility. Ever since upgrading the Network codebase, I’ve noticed this message displaying somewhat often after making network requests:

\<Warning\>: ERROR: Error during request, code: -1001, details: The request timed out. &nbsp;

This seems like a simple “request has timed out” message. Can anyone confirm that this the extent of the error? I ask because I seem to now have some duplicate requests going out (sending a message to one of my users results in getting one message near-instantly and another copy of that same message several moments later – usually around 30 seconds later).

The duplicate message could be a client- or server-side logic error on my part, but I’m becoming more and more suspicious of this constantly occurring error. I never had this error logged when using the old Corona Network code.

#2

Are there other errors or messages around it?

I’ve never used the iPhone Configuration Utility, I use XCode’s organizer to see the full console log.  I don’t know if that matters on what you see.  Is there more to like the app that generated it?

#3

Hey, Rob. Unfortunately, this seems to be the only error that prints. I’ve taken a look at the XCode organizer console and the information appears the same as the iPhone Configuration Utility.

I remember reading there is a 30 second default timeout period for network requests, which seems to be holding true here. My timestamps in the configuration utility console show the error appearing exactly 30 seconds after my original network request:

Aug 30 11:01:40 AppName[3478] \<Warning\>: message: {"type":"turn","sentBy":4,"gameID":"716","message":"It's your turn!"} Aug 30 11:02:10 AppName[3478] \<Warning\>: ERROR: Error during request, code: -1001, details: The request timed out.

The first print is just logging the network request to send a message to another player. At that time, another player will receive a pop-up on their device with the given message. The issue I’m experiencing now is that around 30 seconds later, I sometimes get the same message again (only sometimes, though – which is very strange behavior since I get this timeout log every time).

I could be completely off-track here and this error log may have no impact on my current issue. However, I was hoping to gain more insight into this error (if there is any to be had) so I could determine if it is the cause of the issue.

#4

Are there other errors or messages around it?

I’ve never used the iPhone Configuration Utility, I use XCode’s organizer to see the full console log.  I don’t know if that matters on what you see.  Is there more to like the app that generated it?

#5

Hey, Rob. Unfortunately, this seems to be the only error that prints. I’ve taken a look at the XCode organizer console and the information appears the same as the iPhone Configuration Utility.

I remember reading there is a 30 second default timeout period for network requests, which seems to be holding true here. My timestamps in the configuration utility console show the error appearing exactly 30 seconds after my original network request:

Aug 30 11:01:40 AppName[3478] \<Warning\>: message: {"type":"turn","sentBy":4,"gameID":"716","message":"It's your turn!"} Aug 30 11:02:10 AppName[3478] \<Warning\>: ERROR: Error during request, code: -1001, details: The request timed out.

The first print is just logging the network request to send a message to another player. At that time, another player will receive a pop-up on their device with the given message. The issue I’m experiencing now is that around 30 seconds later, I sometimes get the same message again (only sometimes, though – which is very strange behavior since I get this timeout log every time).

I could be completely off-track here and this error log may have no impact on my current issue. However, I was hoping to gain more insight into this error (if there is any to be had) so I could determine if it is the cause of the issue.