This bug is not coming from Android code. It is either coming from Apache or from Ubuntu (look for the first exception in the stack at your link).
Since only the first reported NPE is reported as fixed in Froyo, but the "Bad address" is not, my guess is that despite the problems you mention, you are better off using SSL instead of TLS. That works. On Aug 5, 10:49 am, Kostya Vasilyev <[email protected]> wrote: > Hello, > > I am implementing some NIO based code with SSL support, using SSLEngine. > > Working nicely along, I ran into a NullPointerException inside SSLEngine > during SSL handshaking. > > This bug is described here: > > http://code.google.com/p/android/issues/detail?id=4914 > > and is reported as fixed in Froyo. > > However, I'm building my app for the devices that are out there, > starting with 1.5. > > Would anyone have any suggestions for working around this bug, instead > of limiting the app to Froyo and greater? > > It's certainly possible to use SSLSocket, but they don't support > non-blocking operation, and so I'd rather not go down that route. > > -- > Kostya Vasilev -- WiFi Manager + pretty widget --http://kmansoft.wordpress.com -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
