For the record, Becky did point me to the matching decoder in the js:
https://github.com/apache/cordova-js/blob/master/lib/ios/plugin/ios/FileReader.js#L65

So yes, now I see that URL encoding the result message is desired.

-- Marcel

On 12/13/2012 2:15 PM, Marcel Kinard wrote:
Yup, I see that file-transfer.jitsu.com <http://file-transfer.jitsu.com> is returning a page saying:
An error has occurred: 
{"code":"ECONNREFUSED","errno":"ECONNREFUSED","syscall":"connect"}
Something is obviously dead there. So yeah, ignore those test failures as an infrastructure problem.

Your File API failures look like the ones I was getting. If I modify readAsText: from

messageAsString:[pNStrBuff stringByAddingPercentEscapesUsingEncoding:NSUTF8StringEncoding]

to

messageAsString:[NSStringstringWithString:pNStrBuff]

then those failures disappear. So I'm still puzzled if it is really supposed to be URL encoding the result message.

BTW, I noticed in your screenshot that your testsuite has 95 tests. Mine has 238. Are we using the same version of mobile-spec?

-- Marcel

Reply via email to