[
https://issues.apache.org/jira/browse/CB-2235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13559131#comment-13559131
]
Max Woghiren edited comment on CB-2235 at 1/21/13 10:01 PM:
------------------------------------------------------------
I only see one failing test: download was failing when trying to do so using
file://. The test downloads the window's html file, but on the simulator, part
of that URL has spaces (Application Support/iPhone Simulator). This causes a
failure, since [NSURL urlWithString:] returns nil when the string has a space.
On iOS6, the spaces are automatically encoded, so it didn't fail. I changed
the test, replacing the spaces after retrieving the URL. The pull request is
[here|https://github.com/apache/cordova-mobile-spec/pull/4].
Andrew, check it out and make sure it works. Again, I didn't see four failing
tests so this might not resolve all the ones you were seeing.
was (Author: max.woghiren):
I only see one failing test: download was failing when trying to do so
using file://. The test downloads the window's html file, but on the
simulator, part of that URL has spaces (Application Support/iPhone Simulator).
This causes a failure, since [NSURL urlWithString:] returns nil when the string
has a space.
On iOS6, the spaces are automatically encoded, so it didn't fail. I changed
the test, replacing the spaces after retrieving the URL. The pull request is
[here|https://github.com/apache/cordova-mobile-spec/pull/3].
Andrew, check it out and make sure it works. Again, I didn't see four failing
tests so this might not resolve all the ones you were seeing.
> FileTransfer spec test failing on iOS5
> --------------------------------------
>
> Key: CB-2235
> URL: https://issues.apache.org/jira/browse/CB-2235
> Project: Apache Cordova
> Issue Type: Bug
> Components: iOS
> Reporter: Andrew Grieve
> Assignee: Max Woghiren
> Fix For: 2.4.0
>
>
> I'm seeing all tests passing on iOS 6 simulator, but 4 tests failing on iOS5
> simulator.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
