The response from the API endpoint is coming back malformed -- but it is coming back. This suggests its not dead, just broken.
I'll continue to investigate. A fix may be possible on the app side, or it could be some transient problem with the web service.
Update:
The server says:
Code:
XML Parsing Error: no root element found
Location: http://blstreamhptablet.accu-weather.com/widget/blstreamhptablet/weather-data.asp?location=cityId:11111
Line Number 691, Column 16:
<sunrise>
---------------------------------------------------------^
But that's a result error, not a body error, so we can't repair it with a proxy, or some pre-parse patch on the client side.
The client (app) says:
Code:
info: AccuWeather.WeatherModel.xmlRequestCallback_(): received server response: null, /usr/palm/frameworks/enyo/1.0/framework/build/enyo-build.jsjsjs:$72$
$error$: $Uncaught$ $TypeError$: $Cannot$ $call$ $method$ '$getElementsByTagName$' $of$ $null$, $app$/$src$/$WeatherModel$.$js$:$179$
Update with conclusions: This is an issue with their "legacy API"; the app depends on an XML response, which is somehow getting mangled on the server-side. Likely someone pushed a breaking change at the end of their work-day (never deploy on a Friday!)
I've emailed their support, we'll see if anyone there still cares. Fortunately, other legacy users are probably impacted -- since I doubt anyone is doing maintenance just on the webOS endpoint -- so there's a good chance this will get repaired...although maybe not until after the holidays :(
Don't give up your TouchPads yet, folks. We're keeping this platform alive! Previous repair thread here.
Originally Posted by GLO
