1126 & 1127 throw internal errors on unsuccessful connections

Solar2D Daily Builds and Public Releases
#1

Hi,

This is what I get in console when I receive error from a remote server on 1126:

2013-05-25 12:59:24.046 Corona Simulator[2768:f03] -[CoronaURLConnection reportErrors]: unrecognized selector sent to instance 0x10078af60 2013-05-25 12:59:24.047 Corona Simulator[2768:f03] -[CoronaURLConnection reportErrors]: unrecognized selector sent to instance 0x10078af60 2013-05-25 12:59:24.048 Corona Simulator[2768:f03] ( 0 CoreFoundation 0x00007fff91644f56 \_\_exceptionPreprocess + 198 1 libobjc.A.dylib 0x00007fff8e177d5e objc\_exception\_throw + 43 2 CoreFoundation 0x00007fff916d11be -[NSObject doesNotRecognizeSelector:] + 190 3 CoreFoundation 0x00007fff91631e23 \_\_\_forwarding\_\_\_ + 371 4 CoreFoundation 0x00007fff91631c38 \_CF\_forwarding\_prep\_0 + 232 5 network.dylib 0x000000010aa2404a -[CoronaConnectionDelegate connection:didFailWithError:] + 206 6 Foundation 0x00007fff8aca1b3b \_\_\_NSURLConnectionDidFail\_block\_invoke\_1 + 125 7 Foundation 0x00007fff8aca1ab8 \_NSURLConnectionDidFail + 85 8 CFNetwork 0x00007fff8862c75d \_ZN19URLConnectionClient23\_clientDidFailWithErrorEP9\_\_CFErrorPNS\_26ClientConnectionEventQueueE + 667 9 CFNetwork 0x00007fff8862b915 \_ZN19URLConnectionClient26ClientConnectionEventQueue33processAllEventsAndConsumePayloadEP20XConnectionEventInfoI12XClientEvent18XClientEventParamsEl + 885 10 CFNetwork 0x00007fff88556259 \_ZN19URLConnectionClient13processEventsEv + 185 11 CFNetwork 0x00007fff885560fe \_ZN17MultiplexerSource7performEv + 212 12 CoreFoundation 0x00007fff915b34f1 \_\_CFRUNLOOP\_IS\_CALLING\_OUT\_TO\_A\_SOURCE0\_PERFORM\_FUNCTION\_\_ + 17 13 CoreFoundation 0x00007fff915b2d5d \_\_CFRunLoopDoSources0 + 253 14 CoreFoundation 0x00007fff915d9b49 \_\_CFRunLoopRun + 905 15 CoreFoundation 0x00007fff915d9486 CFRunLoopRunSpecific + 230 16 HIToolbox 0x00007fff8b39e2bf RunCurrentEventLoopInMode + 277 17 HIToolbox 0x00007fff8b3a556d ReceiveNextEventCommon + 355 18 HIToolbox 0x00007fff8b3a53fa BlockUntilNextEventMatchingListInMode + 62 19 AppKit 0x00007fff8b97d779 \_DPSNextEvent + 659 20 AppKit 0x00007fff8b97d07d -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 135 21 AppKit 0x00007fff8b9799b9 -[NSApplication run] + 470 22 AppKit 0x00007fff8bbf5eac NSApplicationMain + 867 23 Corona Simulator 0x0000000100001804 start + 52 )
#2

Can you expand on what you mean by “receive error from a remote server”?  Do you mean when a connection times out because the server isn’t responding or something else?

#3

Hello Perry,

sorry it took so long.

What I mean is receiving response with a status different than 200, or not receiving it at all.

For example I got this error when DNS was unable to determine ip of the hostname I provided [I wasn’t connected to my vpn at that time].

#4

Sam thing happening in 1127.

Really annoying, there’s no way to recover.

#5

Case 23739 created

#6

Still happening in 1128

Guys… this is a showstopper!

#7

We’re looking into it.  

Does it only happen in the Mac Simulator or does it happen on devices too? (not that this makes any difference to the importance, just trying to gather all available information)

#8

Dammit.

I was 100% sure it happened on the device as well, but I’ve run the attached [to the case] project and it only failed on simulator.

Not a showstopper then, however extremely annoying.

#9

It’s fixed in the next Daily Build.  Thanks for the report!

#10

Can you expand on what you mean by “receive error from a remote server”?  Do you mean when a connection times out because the server isn’t responding or something else?

#11

Hello Perry,

sorry it took so long.

What I mean is receiving response with a status different than 200, or not receiving it at all.

For example I got this error when DNS was unable to determine ip of the hostname I provided [I wasn’t connected to my vpn at that time].

#12

Sam thing happening in 1127.

Really annoying, there’s no way to recover.

#13

Case 23739 created

#14

Still happening in 1128

Guys… this is a showstopper!

#15

We’re looking into it.  

Does it only happen in the Mac Simulator or does it happen on devices too? (not that this makes any difference to the importance, just trying to gather all available information)

#16

Dammit.

I was 100% sure it happened on the device as well, but I’ve run the attached [to the case] project and it only failed on simulator.

Not a showstopper then, however extremely annoying.

#17

It’s fixed in the next Daily Build.  Thanks for the report!