Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (athena.apache.org: domain of shazron@gmail.com designates
 209.85.216.54 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <4763A1C0-182F-436E-A7CD-3E4FBA47A5DF@gmail.com>
References: 
 <CADZEuyEq+rK=29PP+KseTYNe33EDkaZhb5EvvQ7-JsjQF+eBcQ@mail.gmail.com>
 <CAE6O_-ZzQKGY0koSCxmiZTG8QoB8aZQ6G6-iBZy0LcS=VKQG8Q@mail.gmail.com>
 <CAE6O_-aPWo3E9G6qYV3uq60AQBrCCmoGgJYsfVMg42WHXEd4+A@mail.gmail.com>
 <CAE6O_-a6by9Zcz8YRRQr1znt1CJ58f99cyQqm==7+vZJ54uQBQ@mail.gmail.com>
 <CADZEuyGiLmMmzxmcT+2ZBSwCM8J6sEP0SjhsCN5FdfOkMrxTaQ@mail.gmail.com>
 <4763A1C0-182F-436E-A7CD-3E4FBA47A5DF@gmail.com>
From: Shazron <shazron@gmail.com>
Date: Thu, 13 Dec 2012 13:08:38 -0800
Message-ID: 
 <CAE6O_-YX1KH7ut6SCx9FYcFFa8HwFHR_JXA=wxmDgcdOsZS+BA@mail.gmail.com>
Subject: Re: mobile-spec failures on iOS 6.0.0
To: "dev@cordova.apache.org" <dev@cordova.apache.org>
Content-Type: multipart/alternative; boundary=bcaec51b18e70eea6c04d0c25413

--bcaec51b18e70eea6c04d0c25413
Content-Type: text/plain; charset=ISO-8859-1

Thanks Becky -- i'll take a peek as well. Filed:
http://issues.cordova.io/2058


On Thu, Dec 13, 2012 at 12:18 PM, Becky Gibson <gibson.becky@gmail.com>wrote:

> 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 <cmarcelk@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
>

--bcaec51b18e70eea6c04d0c25413--