I am using the makeWebRequest function to call a web site which returns some json data for the application to use. The code works fine on the watch when it is connected to the internet via an iPhone running Garmin Connect. When the device is connected to the internet via an Android device the makeWebRequest always returns a response code of -300
Any help greatly appreciated!
I would insert the code here if the forum site worked. I will keep trying :(
I've not seen this with any of my apps that do makeWebRequest calls, with a few different sites and an Android phone and the current version of GCM. the -300 error is "Network request Timed Out", which sounds like it might be the phone timing out when trying to access the internet. How is your phone doing that? Wifi or Cell data? Could it be the server is slow to respond, and that's involved?
I've not seen or measured this myself, but I've heard that iOS is a bit faster than Android when sending a request to the internet.
Yes it is a timeout error but it is returned in about 4-5 seconds for every request done every 5 minutes over an hour. Connect can access internet and the browser on the device works fine. The website responds fine if called via chrome. The watch is connected via bluetooth to Samsung tablet which is connected to internet via via wifi, I am using Connect 4.12.1 on Android 5.1.1 It has to be something with the makeWebRequest that Connect on Android does not handle.
here is the debug trace coming from the background class doing the makeWebRequest
background event registered Background: 19:02:42 makeWebRequest Background: 19:07:42 makeWebRequest Background: 19:07:47 web response: -300 Background: 19:12:42 makeWebRequest Background: 19:12:46 web response: -300 Background: 19:17:42 makeWebRequest Background: 19:18:01 web response: -300 Background: 19:22:42 makeWebRequest Background: 19:22:47 web response: -300
I had a similar issue when the certificate of my website was not trused by GCM. Here I do not know if GCM has a different white list then the internal browser, but it might be related to that.
The source of the certificate could be it. I seem to real that self-signed didn't work, but they had to come from a known registrar. Another thing that could help (starting with the 3.0.x SDK) is in the sim, under file, is "View HTTP Traffic" to get a better understanding of what's going on, at least in the sim.
Let's Encrypt certificates are working fine (I am also using them). The only thing you have to make sure is that you use the "fullchain.pem" file in your webserver configuration and not one of the other "pem"-files, as GCM needs the complete chain (root ca, intermediate, cert) of certs. I can remember when I configured it the wrong way I was also getting timeouts on Android phones.
Thanks very much to those who pointed me in the right direction of the SSL certificate. Even though I had a 'signed' certificate I was not using the certificate authority certificate bundle correctly. Once the trusted SSL certificate was in place it all worked!
Using Apache, I have to configure SSL with my SSL certificat (SslForFree - Let's Encrypt) in this way to avoid this error -300:
# Intermediate configuration, tweak to your needs SSLProtocol all -SSLv2 -SSLv3 SSLCipherSuite ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA:ECDHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-RSA-AES256-SHA256:DHE-RSA-AES256-SHA:ECDHE-ECDSA-DES-CBC3-SHA:ECDHE-RSA-DES-CBC3-SHA:EDH-RSA-DES-CBC3-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:DES-CBC3-SHA:!DSS SSLHonorCipherOrder on SSLCompression off
I don't know if all of this is necessary but with, it works for me.
