v1.7.0.12 Release

[garyan2]

Just released a new version to address the errors in json returns from SD causing a lot of folks to fail to update their guide data.

[Space]

Have you been in contact with SD to figure out why this has happened? Did they release a new version of their server software that violates their own API?

[rkulagow]

(I work for Schedules Direct)

This has been raised to our upstream; they are sending invalid data to all of their customers for certain stationIDs. Our ingest code actually "caught" the error, just in the wrong way, because back in the ancient mists of time the broadcastLanguage field was a comma separated string, rather than a JSON array, so when we received stationIDs that didn't have the data, the code tried to correct it, but replaced the empty upstream data with a string of "en", rather than an array with a single element of "en".

The stations and lineups are being rebuilt now, and I've opened a high-priority ticket with our upstream.

[bsyd]

This new version took care of the problem for me. Thanks for the quick fix Gary.
-Bob

[IT Troll]

Thanks. The issue didn't manifest on my lineup, but I still updated anyway.