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/10/05 16:02:03 UTC

[jira] [Resolved] (CB-1589) XHR mode does not work with my Application

     [ https://issues.apache.org/jira/browse/CB-1589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Grieve resolved CB-1589.
-------------------------------

    Resolution: Duplicate
      Assignee: Andrew Grieve  (was: Shazron Abdullah)

Thanks for the report. The issue has been fixed and there's another work-around listed in:
https://issues.apache.org/jira/browse/CB-1525

If IFRAME_NAV is works for you though, I'd stick with what you have.




                
> XHR mode does not work with my Application
> ------------------------------------------
>
>                 Key: CB-1589
>                 URL: https://issues.apache.org/jira/browse/CB-1589
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: iOS
>    Affects Versions: 2.1.0
>         Environment: iOS 6.0 Phonegap 2.1.0(release) XCode 4.5.1
>            Reporter: Jason Dove
>            Assignee: Andrew Grieve
>              Labels: iframe, ios, javascript, plugins, xhr
>
> I'm in the process of moving from 1.9 to 2.1.  After moving over, I could no longer make plug-in calls once changing domains.
> The app we have, starts with pages served on a the local device, then switches to pages served on a remote webserver server once the user provides connection information.  
> With the change to XHR_NO_PAYLOAD, my Javascript can no longer make successful plugin calls after switching from local html/js to remote html/js.
> After I switched cordova-2.1.0.js to be (I'm lazy, but you see the point):
> bridgeMode = navigator.userAgent.indexOf(' 4_') == -1 ? jsToNativeModes.IFRAME_NAV : jsToNativeModes.IFRAME_NAV,
> My Application started working correctly again.

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