[ 
https://issues.apache.org/jira/browse/CB-10254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15069747#comment-15069747
 ] 

Davide edited comment on CB-10254 at 12/23/15 3:53 PM:
-------------------------------------------------------

I initially posted my problem here: 
http://stackoverflow.com/questions/34419047/cordova-file-upload-not-working-on-windows-phone.
 It contains an insight of the code and setup I am using.

I will attempt to switch to non-multipart mode and reply with my findings.

Edit:
Filesize varies betwen 0,5/8 MB depending on the quality of the picture made.
Protocol is both http for development and https for production. This happens on 
both protocols however.
When adding content-type I get "The parameter is incorrect.\r\n\r\n'boundary': 
If the 'Content-Type' header is set, the boundary cannot be empty and must 
match the boundary set in the 'Content-Type' header."


was (Author: perfectioncsgo):
I initially posted my problem here: 
http://stackoverflow.com/questions/34419047/cordova-file-upload-not-working-on-windows-phone.
 It contains an insight of the code and setup I am using.

I will attempt to switch to non-multipart mode and reply with my findings.

Edit:
Filesize varies betwen 0,5/8 MB depending on the quality of the picture made.
Protocol is both http for development and https for production. This happens on 
both protocols however.

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

Reply via email to