[
https://issues.apache.org/jira/browse/CB-10254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15070863#comment-15070863
]
Davide edited comment on CB-10254 at 12/24/15 10:45 AM:
--------------------------------------------------------
Upgrading my application to version 1.4.1-dev and removing ngCordova doesn't
fix it either. It worked for the first 3 uploads. After that there is no more
callback. Not even after a hard reset of the device.
{quote}
// update internal TransferOperation object with newly created promise
var uploadOperation = upload.startAsync();
fileTransferOps[uploadId].promise = uploadOperation;
{quote}
I was going through the debug version in this and when I look at the array of
fileTransferOps @ line 68.
The callback that I am expecting isn't happening. But the previous requests
have state 2, which I assume simply they were cancelled (aborted?) by something?
was (Author: perfectioncsgo):
Upgrading my application to version 1.4.1-dev and removing ngCordova doesn't
fix it either. It worked for the first 3 uploads. After that there is no more
callback. Not even after a hard reset of the device.
// update internal TransferOperation object with newly created promise
var uploadOperation = upload.startAsync();
fileTransferOps[uploadId].promise = uploadOperation;
I was going through the debug version in this and when I look at the array of
fileTransferOps @ line 68.
The callback that I am expecting isn't happening. But the previous requests
have state 2, which I assume simply they were cancelled (aborted?) by something?
> file-transfer for windows platform broken
> -----------------------------------------
>
> Key: CB-10254
> URL: https://issues.apache.org/jira/browse/CB-10254
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin File Transfer
> Affects Versions: 3.5.0
> Environment: Windows Phone 8.1, Nokia Lumia 520
> Reporter: Davide
> Priority: Blocker
> Attachments: FTTest.zip
>
>
> Only been able to test this on a Nokia Lumia 520. The current implementation
> of BackgroundTransfer uploads will almost always stay on pending
> indefinately, which means that there may never be a callback unless the
> operation is manually canceled.
> Notably, this is also an issue with a multitude of things. When disabling
> apps running in the background and also disabling time and date
> synchronization, this problem may not always occur.
> Perhaps it's a bug in BackgroundTransfer itself?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
