You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by "Andrew Grieve (JIRA)" <ji...@apache.org> on 2012/09/27 17:40:07 UTC
[jira] [Resolved] (CB-1476) Failed to load resource:
file:///!gap_exec
[ https://issues.apache.org/jira/browse/CB-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Grieve resolved CB-1476.
-------------------------------
Resolution: Fixed
Fix Version/s: 2.2.0
I changed the bridge so that the XHRs do not fail:
https://git-wip-us.apache.org/repos/asf?p=incubator-cordova-ios.git;a=commit;h=ca0cb89150eaeaa0246981f131acd495794235de
This is 20% slower than failing request, but I agree that having it spam the console log is a big deal. I think the speed still falls within the "good enough" category, and if bridge speed is critical to an app, they should use the iframe bridge anyways.
> Failed to load resource: file:///!gap_exec
> ------------------------------------------
>
> Key: CB-1476
> URL: https://issues.apache.org/jira/browse/CB-1476
> Project: Apache Cordova
> Issue Type: Bug
> Components: iOS
> Affects Versions: 2.1.0
> Environment: iOS 6 GM, Safari 6 Web Inspector
> Reporter: Joseph Farfel
> Assignee: Andrew Grieve
> Priority: Minor
> Labels: safari, web-inspector
> Fix For: 2.2.0
>
>
> Whenever I run cordova.exec with an empty command queue, I get this error in the new iOS 6 Web Inspector in Safari:
> {color:red}file:///!gap_exec Failed to load resource: The requested URL was not found on this server.{color}
> It's caused by this XMLHttpRequest:
> {code:title=cordova-2.1.0.js (line 974)}
> execXhr.open('HEAD', "file:///!gap_exec", true);
> {code}
> Looks like the Obj-C code hears this request as a signal to begin executing the command queue, but it doesn't return a success response, so Web Inspector complains about not being able to load the resource.
> It doesn't seem to affect functionality, but it sure is annoying to have all those "failed to load resource" errors in the console.
--
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