Can't connect via UDP on iOS and AIR 19
Posted: 07 Aug 2015, 03:54
Hi,
I'm using the latest AS3 Client API (1.6.0) and SFS2X 2.9.0 . The client does not connect via UDP on iOS with AIR 19 beta. AIR 18 works just fine. I've posted the bug onto the Adobe forums but has been unanswered for over a week now.
The API connects via UDP just fine under AIR 19 on Android / PC / Mac. Also, TCP is unaffected as the initial handshake works everywhere.
Unfortunately the UDP error messages aren't very verbose. The SFSEvent.UDP_INIT event returns a failure, that's it.
What I did observe on the server traces however is that a UDP connection seems to be established as this shows up (details obfuscated with XXXX ).
07 Aug 2015 | 03:38:13,468 | INFO | SocketReader | bitswarm.sessions.DefaultSessionManager | | Session created: { Id: 9, Type: DEFAULT, Logged: No, IP: XXXX:39893 } on Server port: 9933 <---> 39893
07 Aug 2015 | 03:38:13,556 | INFO | SFSWorker:Sys:4 | v2.api.SFSApi | | User login: { Zone: XXXX }, ( User Name: XXXX, Id: 8, Priv: 0, Sess: XXXX:39893 ) , Type: Flash
07 Aug 2015 | 03:38:16,634 | WARN | SFSWorker:Sys:4 | v2.protocol.SFSIoHandler | | Client already UDP inited: { Id: 9, Type: DEFAULT, Logged: Yes, IP: XXXX:39893 }
07 Aug 2015 | 03:38:19,685 | WARN | SFSWorker:Sys:1 | v2.protocol.SFSIoHandler | | Client already UDP inited: { Id: 9, Type: DEFAULT, Logged: Yes, IP: XXXX:39893 }
It's as if the client is not receiving the acknowledgement, which leads me to think the client API is at fault under the iOS platform, for some reason.
Can you run some tests with AIR 19 beta ( http://labs.adobe.com/downloads/air.html ) on iOS and see what the problem is? My tests were done on iOS 8.x on iPhone6 and iPad3. Thank you!
I'm using the latest AS3 Client API (1.6.0) and SFS2X 2.9.0 . The client does not connect via UDP on iOS with AIR 19 beta. AIR 18 works just fine. I've posted the bug onto the Adobe forums but has been unanswered for over a week now.
The API connects via UDP just fine under AIR 19 on Android / PC / Mac. Also, TCP is unaffected as the initial handshake works everywhere.
Unfortunately the UDP error messages aren't very verbose. The SFSEvent.UDP_INIT event returns a failure, that's it.
What I did observe on the server traces however is that a UDP connection seems to be established as this shows up (details obfuscated with XXXX ).
07 Aug 2015 | 03:38:13,468 | INFO | SocketReader | bitswarm.sessions.DefaultSessionManager | | Session created: { Id: 9, Type: DEFAULT, Logged: No, IP: XXXX:39893 } on Server port: 9933 <---> 39893
07 Aug 2015 | 03:38:13,556 | INFO | SFSWorker:Sys:4 | v2.api.SFSApi | | User login: { Zone: XXXX }, ( User Name: XXXX, Id: 8, Priv: 0, Sess: XXXX:39893 ) , Type: Flash
07 Aug 2015 | 03:38:16,634 | WARN | SFSWorker:Sys:4 | v2.protocol.SFSIoHandler | | Client already UDP inited: { Id: 9, Type: DEFAULT, Logged: Yes, IP: XXXX:39893 }
07 Aug 2015 | 03:38:19,685 | WARN | SFSWorker:Sys:1 | v2.protocol.SFSIoHandler | | Client already UDP inited: { Id: 9, Type: DEFAULT, Logged: Yes, IP: XXXX:39893 }
It's as if the client is not receiving the acknowledgement, which leads me to think the client API is at fault under the iOS platform, for some reason.
Can you run some tests with AIR 19 beta ( http://labs.adobe.com/downloads/air.html ) on iOS and see what the problem is? My tests were done on iOS 8.x on iPhone6 and iPad3. Thank you!