[
https://issues.apache.org/jira/browse/CB-7735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14168729#comment-14168729
]
Christophe Benoit commented on CB-7735:
---------------------------------------
I uploaded a project where the issue is reproduced.
During the creation of this project I found out that the issue is only
occurring when I use a setTimeout to start the application. I sometime use this
approach to debug the start of an application. If you remove the setTimeout and
just call the start function things work as expected.
It seems to me as some sort of timing issue. No idea if the setTimeout was
causing it or if it is random. Maybe you can tell me that?
> Callbacks not being executed when calling requestFileSystem
> -----------------------------------------------------------
>
> Key: CB-7735
> URL: https://issues.apache.org/jira/browse/CB-7735
> Project: Apache Cordova
> Issue Type: Bug
> Components: CordovaJS
> Affects Versions: 3.7.0
> Environment: iOS
> Reporter: Christophe Benoit
> Priority: Blocker
> Labels: bridge, callback, filesystem
> Attachments: filesystem-issue.zip
>
>
> When calling window.requestFileSystem(LocalFileSystem.PERSISTENT, 0, success,
> error) none of the callback functions are executed.
> Several calls to window.requestFileSystem are made during the initialization
> of the application, after the deviceready event. All those calls are being
> queued in the command queue.
> If I set the bridge mode to XHR_NO_PAYLOAD in the deviceready handler with
> following call,
> cordova.exec.setJsToNativeBridgeMode(cordova.exec.jsToNativeModes.XHR_NO_PAYLOAD),
> the callbacks are executed as expected and my application is beinig
> initialized.
> If I change the bridge mode back to IFRAME_NAV when the first view is
> rendered, any following calls to requestFileSystem are being handled as
> expected.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
