So, I thought the encoding was necessary for internationalization and any
special characters in the file data (for example a URL)? Do all of the other
file tests still run with this change? We're there any changes to the file
tests themselves? I try to take a look this afternoon.
- Becky
Sent from my iPad
On Dec 13, 2012, at 2:15 PM, Marcel Kinard <cmarc...@gmail.com> wrote:
> Yup, I see that 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:[NSString stringWithString: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
