Question

I have a mobile app that I targeted for iOS and Android. It makes a login request via HTTPS (using a POST with HTTPService)..Everything works fine while debugging on my development box via ADL and when compiled and tested on iOS 4.2 and iOS 5.

The Android devices also work correctly when making HTTPS requests to other domains, like Twitter, etc. from within my test app or in the device’s browser.

I only have a couple of test Android devices and they’re running 2.3.3 but none will make a successful connection. While debugging via USB, I can see that the HTTPService call is returning a FaultEvent with IOErrorEvent #2032.

After researching, I found that Android OS has some issues with certain SSL certificates, and the issuer thats being used on the server is ‘VeriSign Class 3 International Server CA – G3’ but I haven’t really found any viable workarounds/solutions. Has anyone else encountered this? I know its pretty specific.

Just wanted to add that an HTTP Status code of 0 is being returned immediately before the ioErrorEvent 2032 is being dispatched. I’ve checked Adobe’s API docs for the HTTPStatusEvent and 0 seems to be a default. http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/flash/events/HTTPStatusEvent.html

HTTPStatusEvent objects are always sent before error or completion events. An HTTPStatusEvent object does not necessarily indicate an error condition; it simply reflects the HTTP status code (if any) that is provided by the networking stack. Some Flash Player environments may be unable to detect HTTP status codes; a status code of 0 is always reported in these cases. Just wanted to add additional findings...through testing we were able to use that same certificate on another server - and despite security warnings, I was able to get data on my test Android device. This makes me think that the issue may be related to the server....It's hosted by Rackspace so we're going to reach out to them to attempt more troubleshooting.

Answer 1

I was having the same problem, Stream error 2032 on https: requests, and was able to resolve it by upgrading to a newer AIR runtime. I had noticed the error occurring on one test device and not the other, the main difference being that the one with errors had AIR 3.1 installed, the one without errors had AIR 3.2.

We are now packaging the app with captive AIR runtime (version 3.3). Since FlashBuilder came with AIR 3.1 pre-installed, it was necessary to download a new AIR SDK and overlay it on FlashBuilder.