Hi,
all of sudden my app started to give errors (300, NETWORK_REQUEST_TIMED_OUT) on the following code:
Log(url);
// Make the request
Comm.makeWebRequest(
url,
{
},
{
"Content-Type" => Comm.REQUEST_CONTENT_TYPE_URL_ENCODED
},
method(:onReceive)
);
}
Hi,
all of sudden my app started to give errors (300, NETWORK_REQUEST_TIMED_OUT) on the following code:
@FlowState, indeed, switching to Let's Encrypt certificate has cleared the "Network Timeout -300" error, the widget is now working correctly.
It would be nice to:
1) have a more descriptive…
HI,
GCM version i do not know. Is this part of Google play services (my version is 17.7.85).
I indeed do have parameters in there. I will try to move them to the empty {} in the call
Kind Regards
Arn…
Ask in the bug report thread I linked to, And "up" the first post in that thread, as it shows how many people are having problems with 4.20.
The question is: has Garmin changed anything in GCM recently? It suddenly stopped working couple of days ago for many users. Do we have any Garmin feedback on that or we are helping ourselves? Just before our widgets get to one star in reviews...
Something did change in GCM/Android with version 4.20
a new ticket was opened yesterday on the localhost issue.
Hey All,
Just wanted to make sure that everyone knows that we are tracking this issue here: https://forums.garmin.com/developer/connect-iq/i/bug-reports/connect-version-4-20-broke-local-http-access
That will be our main place to make updates on this. Please see the report for more details on the current status.
Hi i posted the info of this problem in the thread you mentioned. In that thread a garmin developer now responed that locahost access will be fixed. That does not solve this problem, which as you can see has quite some impact. HOw to proceed to get this one fixed as well?