Is this app using apptype='RhoElements' which would use Motorola Webkit or is it using the native webkit?
What happens when you just try connect with the real device's browser? is the server in a public accessible location for me to try?
Moto Webkit only supports a limited number of Cypher strengths and if your server does not allow these then it will not work:
- TLS_DHE_RSA_WITH_AES_256_CBC_SHA (0x0039)
- TLS_DHE_DSS_WITH_AES_256_CBC_SHA (0x0038)
- TLS_RSA_WITH_AES_256_CBC_SHA (0x0035)
- TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA (0x0016)
- TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA (0x0013)
- TLS_RSA_WITH_3DES_EDE_CBC_SHA (0x000a)
- TLS_DHE_RSA_WITH_AES_128_CBC_SHA (0x0033)
- TLS_DHE_DSS_WITH_AES_128_CBC_SHA (0x0032)
- TLS_RSA_WITH_AES_128_CBC_SHA (0x002f)
- TLS_RSA_WITH_RC4_128_SHA (0x0005)
- TLS_RSA_WITH_RC4_128_MD5 (0x0004)
- TLS_DHE_RSA_WITH_DES_CBC_SHA (0x0015)
- TLS_DHE_DSS_WITH_DES_CBC_SHA (0x0012)
- TLS_RSA_WITH_DES_CBC_SHA (0x0009)
- TLS_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA (0x0014)
- TLS_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA (0x0011)
- TLS_RSA_EXPORT_WITH_DES40_CBC_SHA (0x0008)
- TLS_RSA_EXPORT_WITH_RC2_CBC_40_MD5 (0x0006)
- TLS_RSA_EXPORT_WITH_RC4_40_MD5 (0x0003)
- TLS_EMPTY_RENEGOTIATION_INFO_SCSV (0x00ff)
we are using rhoelement application and we have web application version of the rhoelement application, so basically every functionality is the same except that our web application version is of course navigatable(if there such a word) on a browser. File upload with https connection on normal browser is working with our server, http file upload is also working in rhoelement app.
is this cyper strength related to ssl certificate verification? cause with the suggestion of motorola support, we just have set it to false.
1 of 1 people found this helpful
The 'false' setting basically just ignores verifying and trys to connect. You know when you browse to a website that it can't verify the certificate and then the browser prompts you 'Do you really want to do this'. Well this setting basically is the same as if you clicked 'yes go ahead and connect anyway'. We just don't show the prompt.
I am not an SSL expert, but one way you can see if this is a Motorola Webkit problem is to just build the app with stock webkit and see if it connects. if it does, then it is most likely an issue with Moto Webkit not having the right cypher strength included.
There are a few more settings in the config.xml for (Android only) provding cert files:
The docs are pretty light on this because it is an edge case, but you provide a path local on the device where you would copy the needed certs. Support should have more information on this.
When you say stock webkit, not a rhoelement app right?
Another thing is we have tested the same generated apk on android emulator and it is working, so what would be the difference then if they also use the same moto webkit?
I am confused, is it working or not on real devices? Some or all? I thought you said it was not working on devices at all. yes, when I say stock webkit that means to not use rhoelements apptype
I'm sorry, its a typo, i mean android emulator. Edited the previous comment.
The real Android emulator, I believe should be using the same Moto Webkit, where as the RhoSimulator is definitely not using the Moto Webkit. So maybe it is a problem with certs not being on the device and they are on your PC, or maybe just a simple thing as you do not have your date and time set properly on the device
Does the certificate issue related to file upload? in our rhoelement app, we actually been successful on downloading, posting form without multipart, and a normal get http request using the AsyncHttp API. So im confused why this certificate issue affects only the file upload if it is really the issue?