[jira] [Commented] (CB-6992) iOS platform add/prepare fails if app display name contains unicode characters.
[
https://issues.apache.org/jira/browse/CB-6992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14182681#comment-14182681
]
Vladimir Kotikov commented on CB-6992:
--
After additional investigation i've found that we need apply NFD normalization
in the other place of ios_parser: it is necessary to normalize 'name' parameter
from config.xml, rather then the originalName (name of project file), since it
(originalName) potentially may be already in NFD form.
Also it is necessary to add additional normalization of 'name' parameter in
platform.js script since it will be written then to .pbxproj and this may
potentially break the ios build.
FYI: Git has the same problem on Mac OS:
http://stackoverflow.com/questions/5581857/git-and-the-umlaut-problem-on-mac-os-x
Mac encoding problems on TWiki: http://twiki.org/cgi-bin/view/Codev/UnicodeMac
> iOS platform add/prepare fails if app display name contains unicode
> characters.
> ---
>
> Key: CB-6992
> URL: https://issues.apache.org/jira/browse/CB-6992
> Project: Apache Cordova
> Issue Type: Bug
> Components: CLI
>Affects Versions: 3.5.0
> Environment: uname: Darwin 13.1.0 Darwin Kernel Version 13.1.0: Thu
> Jan 16 19:40:37 PST 2014; root:xnu-2422.90.20~2/RELEASE_X86_64 x86_64
> cordova-dev -v: 3.5.0-0.2.4
> cordova-lib: 0.21.3
> Node 0.10.26
> iOS
>Reporter: Vladimir Kotikov
>Assignee: Shazron Abdullah
>Priority: Critical
> Labels: cli, configParser, ios
>
> Repro steps:
> # cordova create test-umlaÜt com.test.umlaÜt umlaÜt
> # cd test-umlaÜt/
> # cordova platform add ios
> Platform add fails with following error:
> {noformat}
> mv: dest file already exists:
> /Users/user/test/test-umlaÜt/platforms/ios/umlaÜt/umlaÜt-Info.plist
> mv: dest file already exists:
> /Users/user/test/test-umlaÜt/platforms/ios/umlaÜt/umlaÜt-Prefix.pch
> shell.js: internal error
> Error: EINVAL, invalid argument
> '/Users/user/test/test-umlaÜt/platforms/ios/umlaÜt.xcodeproj'
> at Object.fs.renameSync (fs.js:543:18)
> at
> /usr/local/lib/node_modules/cordova/node_modules/cordova-lib/node_modules/shelljs/shell.js:495:8
> at Array.forEach (native)
> at Object._mv
> (/usr/local/lib/node_modules/cordova/node_modules/cordova-lib/node_modules/shelljs/shell.js:471:11)
> at Object.mv
> (/usr/local/lib/node_modules/cordova/node_modules/cordova-lib/node_modules/shelljs/shell.js:1491:23)
> at pbxProject.
> (/usr/local/lib/node_modules/cordova/node_modules/cordova-lib/src/cordova/metadata/ios_parser.js:145:27)
> at pbxProject.EventEmitter.emit (events.js:98:17)
> at pbxProject.
> (/usr/local/lib/node_modules/cordova/node_modules/cordova-lib/node_modules/xcode/lib/pbxProject.js:30:18)
> at ChildProcess.EventEmitter.emit (events.js:98:17)
> at handleMessage (child_process.js:318:10)
> {noformat}
--
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
[jira] [Created] (CB-8089) File plugin fails to resolve local filesystem root
Vladimir Kotikov created CB-8089:
Summary: File plugin fails to resolve local filesystem root
Key: CB-8089
URL: https://issues.apache.org/jira/browse/CB-8089
Project: Apache Cordova
Issue Type: Bug
Components: Plugin File
Environment: windows
Reporter: Vladimir Kotikov
This can be reproduced by running file spec 15
file.spec.15 should have a root that is a DirectoryEntry: error in
resolvingLocalSystemURL.
Function try to resolve local URL like “C:\\Users\\...” but cannot find it
because the following code searches index of incorrect root/prefix
{noformat}
if (uri.indexOf("file:///") === 0 ) {
path = msappdataLocalPath + uri.substr(8).replace('/', '\\');
} else if (uri.indexOf(msappdataLocalPrefix) === 0) {
path = msappdataLocalPath + uri.replace(msappdataLocalPrefix,
'').replace('/', '\\');
} else if (uri.indexOf(msappdataTempPrefix) === 0) {
path = msappdataTempPath + uri.replace(msappdataTempPrefix,
'').replace('/', '\\');
--
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
[jira] [Updated] (CB-8089) File plugin fails to resolve local filesystem root
[
https://issues.apache.org/jira/browse/CB-8089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Kotikov updated CB-8089:
-
Description:
This can be reproduced by running file spec 15
{{file.spec.15 should have a root that is a DirectoryEntry: error in
resolvingLocalSystemURL.}}
Function try to resolve local URL like “C:\\Users\\...” but cannot find it
because the following code searches index of incorrect root/prefix
{noformat}
if (uri.indexOf("file:///") === 0 ) {
path = msappdataLocalPath + uri.substr(8).replace('/', '\\');
} else if (uri.indexOf(msappdataLocalPrefix) === 0) {
path = msappdataLocalPath + uri.replace(msappdataLocalPrefix,
'').replace('/', '\\');
} else if (uri.indexOf(msappdataTempPrefix) === 0) {
path = msappdataTempPath + uri.replace(msappdataTempPrefix,
'').replace('/', '\\');
{noformat}
was:
This can be reproduced by running file spec 15
file.spec.15 should have a root that is a DirectoryEntry: error in
resolvingLocalSystemURL.
Function try to resolve local URL like “C:\\Users\\...” but cannot find it
because the following code searches index of incorrect root/prefix
{noformat}
if (uri.indexOf("file:///") === 0 ) {
path = msappdataLocalPath + uri.substr(8).replace('/', '\\');
} else if (uri.indexOf(msappdataLocalPrefix) === 0) {
path = msappdataLocalPath + uri.replace(msappdataLocalPrefix,
'').replace('/', '\\');
} else if (uri.indexOf(msappdataTempPrefix) === 0) {
path = msappdataTempPath + uri.replace(msappdataTempPrefix,
'').replace('/', '\\');
> File plugin fails to resolve local filesystem root
> --
>
> Key: CB-8089
> URL: https://issues.apache.org/jira/browse/CB-8089
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin File
> Environment: windows
>Reporter: Vladimir Kotikov
>
> This can be reproduced by running file spec 15
> {{file.spec.15 should have a root that is a DirectoryEntry: error in
> resolvingLocalSystemURL.}}
> Function try to resolve local URL like “C:\\Users\\...” but cannot find it
> because the following code searches index of incorrect root/prefix
> {noformat}
> if (uri.indexOf("file:///") === 0 ) {
> path = msappdataLocalPath + uri.substr(8).replace('/', '\\');
> } else if (uri.indexOf(msappdataLocalPrefix) === 0) {
> path = msappdataLocalPath + uri.replace(msappdataLocalPrefix,
> '').replace('/', '\\');
> } else if (uri.indexOf(msappdataTempPrefix) === 0) {
> path = msappdataTempPath + uri.replace(msappdataTempPrefix,
> '').replace('/', '\\');
> {noformat}
--
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
[jira] [Created] (CB-8090) File plugin returns incorrect error when trying to resolve invalid URI with leading slash
Vladimir Kotikov created CB-8090:
Summary: File plugin returns incorrect error when trying to
resolve invalid URI with leading slash
Key: CB-8090
URL: https://issues.apache.org/jira/browse/CB-8090
Project: Apache Cordova
Issue Type: Bug
Components: Plugin File
Reporter: Vladimir Kotikov
This is very formal but still...
Bug can be reprod by file.spec.12
{{should error (ENCODING_ERR) when resolving invalid URI with leading /”}}
--
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
[jira] [Created] (CB-8092) File plugin on windows doesn't encode URIs when using toUrl() method
Vladimir Kotikov created CB-8092:
Summary: File plugin on windows doesn't encode URIs when using
toUrl() method
Key: CB-8092
URL: https://issues.apache.org/jira/browse/CB-8092
Project: Apache Cordova
Issue Type: Bug
Components: Plugin File
Reporter: Vladimir Kotikov
This can be reprod by file.spec.52
{{Entry.toURL on directory: entryFile.toURL() return URL with “\\” slashes and
non-encoded spaces in folder’s names}}
This issue consists of 2 parts. First, windows is missing
{{filesystem.__format__()}} method which is common place to handle URI
encoding. Second, methods in FileProxy for windows can't handle encoded URIs
--
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
[jira] [Updated] (CB-8092) File plugin on windows doesn't encode URIs when using toUrl() method
[
https://issues.apache.org/jira/browse/CB-8092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Kotikov updated CB-8092:
-
Description:
This can be reprod by file.spec.52
{{Entry.toURL on directory: entryFile.toURL() return URL with “” slashes
and non-encoded spaces in folder’s names}}
This issue consists of 2 parts. First, windows is missing
{{filesystem.__format__()}} method which is common place to handle URI
encoding. Second, methods in FileProxy for windows can't handle encoded URIs
was:
This can be reprod by file.spec.52
{{Entry.toURL on directory: entryFile.toURL() return URL with “\\” slashes and
non-encoded spaces in folder’s names}}
This issue consists of 2 parts. First, windows is missing
{{filesystem.__format__()}} method which is common place to handle URI
encoding. Second, methods in FileProxy for windows can't handle encoded URIs
> File plugin on windows doesn't encode URIs when using toUrl() method
>
>
> Key: CB-8092
> URL: https://issues.apache.org/jira/browse/CB-8092
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin File
>Reporter: Vladimir Kotikov
> Labels: plugin-file, windows
>
> This can be reprod by file.spec.52
> {{Entry.toURL on directory: entryFile.toURL() return URL with “” slashes
> and non-encoded spaces in folder’s names}}
> This issue consists of 2 parts. First, windows is missing
> {{filesystem.__format__()}} method which is common place to handle URI
> encoding. Second, methods in FileProxy for windows can't handle encoded URIs
--
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
[jira] [Updated] (CB-8092) File plugin on windows doesn't encode URIs when using toUrl() method
[
https://issues.apache.org/jira/browse/CB-8092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Kotikov updated CB-8092:
-
Description:
This can be reprod by file.spec.52
{{Entry.toURL on directory: entryFile.toURL() return URL with “\\\” slashes and
non-encoded spaces in folder’s names}}
This issue consists of 2 parts. First, windows is missing
{{filesystem.__format__()}} method which is common place to handle URI
encoding. Second, methods in FileProxy for windows can't handle encoded URIs
was:
This can be reprod by file.spec.52
{{Entry.toURL on directory: entryFile.toURL() return URL with “” slashes
and non-encoded spaces in folder’s names}}
This issue consists of 2 parts. First, windows is missing
{{filesystem.__format__()}} method which is common place to handle URI
encoding. Second, methods in FileProxy for windows can't handle encoded URIs
> File plugin on windows doesn't encode URIs when using toUrl() method
>
>
> Key: CB-8092
> URL: https://issues.apache.org/jira/browse/CB-8092
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin File
>Reporter: Vladimir Kotikov
> Labels: plugin-file, windows
>
> This can be reprod by file.spec.52
> {{Entry.toURL on directory: entryFile.toURL() return URL with “\\\” slashes
> and non-encoded spaces in folder’s names}}
> This issue consists of 2 parts. First, windows is missing
> {{filesystem.__format__()}} method which is common place to handle URI
> encoding. Second, methods in FileProxy for windows can't handle encoded URIs
--
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
[jira] [Created] (CB-8093) File transfer plugin doesn't return response body in case of download failure
Vladimir Kotikov created CB-8093:
Summary: File transfer plugin doesn't return response body in case
of download failure
Key: CB-8093
URL: https://issues.apache.org/jira/browse/CB-8093
Project: Apache Cordova
Issue Type: Bug
Components: Plugin File Transfer
Reporter: Vladimir Kotikov
In case of download error plugin's {{download()}} method should return a
{{FileTransferError}} with responseText property, set to server's responce body
but current implementation always returns an empty field.
Can be reprod by filetransfer.spec.13
{{should get response body on failure}}
--
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
[jira] [Created] (CB-8095) upload method on windows doesn't support progress events correctly
Vladimir Kotikov created CB-8095:
Summary: upload method on windows doesn't support progress events
correctly
Key: CB-8095
URL: https://issues.apache.org/jira/browse/CB-8095
Project: Apache Cordova
Issue Type: Bug
Components: Plugin File Transfer
Reporter: Vladimir Kotikov
On windows FileTrasfer doesn't support {{progress}} events for upload operation
properly since internal implementation uses XHR which doesn't provide all
information, necessary to fire correct progress events.
Possible solution here is to replace XHR with {{BackgroundUploader}} class
which itself supports progress notification in more convenient way and can
provide all necessary data for progress events for FileTransfer.
--
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
[jira] [Commented] (CB-6763) Simultaneous local XHRs on WP8 returns incorrect result
[
https://issues.apache.org/jira/browse/CB-6763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14233984#comment-14233984
]
Vladimir Kotikov commented on CB-6763:
--
Hi, Koen. This was released in 3.7.0. See
https://github.com/apache/cordova-wp8/commit/efaf559ae846567e68e4d96446c8760c3ceed8fc
> Simultaneous local XHRs on WP8 returns incorrect result
> ---
>
> Key: CB-6763
> URL: https://issues.apache.org/jira/browse/CB-6763
> Project: Apache Cordova
> Issue Type: Bug
> Components: WP8
>Affects Versions: 3.4.0
>Reporter: Vladimir Kotikov
>Assignee: Jesse MacFadyen
> Labels: wp8, xhr, xhrhelper
>
> When try to get content of multiple local files via XHR, all requests return
> responses with same content. E.g. following code (using jQuery)
> {noformat}
> function loadTemplates (views) {
> var deferreds = [];
> $.each(views, function (index, view) {
> var vURL = 'tpl/' + view + '.html';
> deferreds.push($.get(vURL, function (data) {
> console.log(data)
> }, 'html'));
> })
> }
> loadTemplates(["HomeView", "ContactView", "ShellView", "EmployeeView",
> "EmployeeSummaryView", "EmployeeListItemView"]);
> {noformat}
> will print contents of {{tpl/EmployeeListItemView.html}} 6 times.
> The problem is when new local XHR is sent, it overrides
> {{__onXHRLocalCallback}} callback, already created by previous request.
--
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
[jira] [Created] (CB-8129) Add test coverage report generation to core cordova tools
Vladimir Kotikov created CB-8129: Summary: Add test coverage report generation to core cordova tools Key: CB-8129 URL: https://issues.apache.org/jira/browse/CB-8129 Project: Apache Cordova Issue Type: Improvement Components: CLI, CordovaJS, CordovaLib Reporter: Vladimir Kotikov It will be great to be able to generate reports easily just by running some npm commands or grunt tasks. E.g. 'npm run coverage' in repo could produce some coverage reports. -- 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
[jira] [Created] (CB-8190) Make plugman config and cache directories to be customizable via PLUGMAN_HOME
Vladimir Kotikov created CB-8190: Summary: Make plugman config and cache directories to be customizable via PLUGMAN_HOME Key: CB-8190 URL: https://issues.apache.org/jira/browse/CB-8190 Project: Apache Cordova Issue Type: Improvement Components: CordovaLib, Plugman Reporter: Vladimir Kotikov There is currently support of CORDOVA_HOME (https://github.com/apache/cordova-lib/blob/master/cordova-lib/src/cordova/util.js#L30) environment variable which could be used to set up user-independent directory for cordova platform cache and configs. I think to be consistent we should add the same support of PLUGMAN_HOME. -- 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
[jira] [Created] (CB-8197) Switch to nodejs for ios platform scripts
Vladimir Kotikov created CB-8197: Summary: Switch to nodejs for ios platform scripts Key: CB-8197 URL: https://issues.apache.org/jira/browse/CB-8197 Project: Apache Cordova Issue Type: Improvement Components: iOS Reporter: Vladimir Kotikov Currently platform tooling for ios is based on bash scripts and to improve maintainability of such scripts it would be useful to port them to NodeJS. Part of this work is already done for create/update scripts in https://issues.apache.org/jira/browse/CB-5706 but platform scripts placed in cordova folder of platform is still being unported. -- 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
[jira] [Commented] (CB-8197) Switch to nodejs for ios platform scripts
[ https://issues.apache.org/jira/browse/CB-8197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14255639#comment-14255639 ] Vladimir Kotikov commented on CB-8197: -- Similar task, already completed for windows > Switch to nodejs for ios platform scripts > - > > Key: CB-8197 > URL: https://issues.apache.org/jira/browse/CB-8197 > Project: Apache Cordova > Issue Type: Improvement > Components: iOS >Reporter: Vladimir Kotikov > > Currently platform tooling for ios is based on bash scripts and to improve > maintainability of such scripts it would be useful to port them to NodeJS. > Part of this work is already done for create/update scripts in > https://issues.apache.org/jira/browse/CB-5706 but platform scripts placed in > cordova folder of platform is still being unported. -- 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
[jira] [Issue Comment Deleted] (CB-8197) Switch to nodejs for ios platform scripts
[ https://issues.apache.org/jira/browse/CB-8197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Kotikov updated CB-8197: - Comment: was deleted (was: Similar task, already completed for windows) > Switch to nodejs for ios platform scripts > - > > Key: CB-8197 > URL: https://issues.apache.org/jira/browse/CB-8197 > Project: Apache Cordova > Issue Type: Improvement > Components: iOS >Reporter: Vladimir Kotikov > > Currently platform tooling for ios is based on bash scripts and to improve > maintainability of such scripts it would be useful to port them to NodeJS. > Part of this work is already done for create/update scripts in > https://issues.apache.org/jira/browse/CB-5706 but platform scripts placed in > cordova folder of platform is still being unported. -- 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
[jira] [Created] (CB-8198) Unified console output logic for core platforms
Vladimir Kotikov created CB-8198: Summary: Unified console output logic for core platforms Key: CB-8198 URL: https://issues.apache.org/jira/browse/CB-8198 Project: Apache Cordova Issue Type: New Feature Components: Android, iOS, Windows, WP8 Reporter: Vladimir Kotikov Assignee: Jesse MacFadyen Currently all major platform scripts doesn't recognize trace levels and always logging all their output to console. This could be unuseful, especially when a huge output from build tools is written (ant build/xcodebuild output is really huge and in most cases is unnecessary) I propose to unify the way we write messages to console output: 1. Pass verbosity arguments (-d, --debug ) downstream to platform scripts. 2. Introduce special Log class which is shared across platform scripts * automatically detects trace level according to command line arguments; * support of output redirection (file, other) in the future? 3. Add support for the following verbosity levels: Error, Normal, Debug by default: Error and Normal messages are traced -silent: only Error messages are traced -verbose: everything is traced -- 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
[jira] [Updated] (CB-8198) Unified console output logic for core platforms
[ https://issues.apache.org/jira/browse/CB-8198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Kotikov updated CB-8198: - Description: Currently all major platform scripts doesn't recognize trace levels and always logging all their output to console. This could be unuseful, especially when a huge output from build tools is put to console (ant build/xcodebuild output is really huge and in most cases is unnecessary) I propose to unify the way we write messages to console output: 1. Pass verbosity arguments (-d, --debug ) downstream to platform scripts. 2. Introduce special Log class which is shared across platform scripts * automatically detects trace level according to command line arguments; * support of output redirection (file, other) in the future? 3. Add support for the following verbosity levels: Error, Normal, Debug by default: Error and Normal messages are traced -silent: only Error messages are traced -verbose: everything is traced was: Currently all major platform scripts doesn't recognize trace levels and always logging all their output to console. This could be unuseful, especially when a huge output from build tools is written (ant build/xcodebuild output is really huge and in most cases is unnecessary) I propose to unify the way we write messages to console output: 1. Pass verbosity arguments (-d, --debug ) downstream to platform scripts. 2. Introduce special Log class which is shared across platform scripts * automatically detects trace level according to command line arguments; * support of output redirection (file, other) in the future? 3. Add support for the following verbosity levels: Error, Normal, Debug by default: Error and Normal messages are traced -silent: only Error messages are traced -verbose: everything is traced > Unified console output logic for core platforms > --- > > Key: CB-8198 > URL: https://issues.apache.org/jira/browse/CB-8198 > Project: Apache Cordova > Issue Type: New Feature > Components: Android, iOS, Windows, WP8 >Reporter: Vladimir Kotikov >Assignee: Jesse MacFadyen > > Currently all major platform scripts doesn't recognize trace levels and > always logging all their output to console. > This could be unuseful, especially when a huge output from build tools is put > to console (ant build/xcodebuild output is really huge and in most cases is > unnecessary) > I propose to unify the way we write messages to console output: > 1. Pass verbosity arguments (-d, --debug ) downstream to platform scripts. > 2. Introduce special Log class which is shared across platform scripts > * automatically detects trace level according to command line arguments; > * support of output redirection (file, other) in the future? > 3. Add support for the following verbosity levels: Error, Normal, Debug > by default: Error and Normal messages are traced > -silent: only Error messages are traced > -verbose: everything is traced -- 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
[jira] [Updated] (CB-8198) Unified console output logic for core platforms
[ https://issues.apache.org/jira/browse/CB-8198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Kotikov updated CB-8198: - Description: Currently all major platform scripts doesn't recognize trace levels and always logging all their output to console. This could be unuseful, especially when a huge output from build tools is put to console (ant build/xcodebuild output is really huge and in most cases is unnecessary) I propose to unify the way we write messages to console output: 1. Pass verbosity arguments (-d, --debug ) downstream to platform scripts. 2. Introduce special Log class which is shared across platform scripts * automatically detects trace level according to command line arguments; * support of output redirection (file, other) in the future? 3. Add support for the following verbosity levels: Error, Normal, Debug by default: Error and Normal messages are traced -silent: only Error messages are traced -verbose: everything is traced was: Currently all major platform scripts doesn't recognize trace levels and always logging all their output to console. This could be unuseful, especially when a huge output from build tools is put to console (ant build/xcodebuild output is really huge and in most cases is unnecessary) I propose to unify the way we write messages to console output: 1. Pass verbosity arguments (-d, --debug ) downstream to platform scripts. 2. Introduce special Log class which is shared across platform scripts * automatically detects trace level according to command line arguments; * support of output redirection (file, other) in the future? 3. Add support for the following verbosity levels: Error, Normal, Debug by default: Error and Normal messages are traced -silent: only Error messages are traced -verbose: everything is traced > Unified console output logic for core platforms > --- > > Key: CB-8198 > URL: https://issues.apache.org/jira/browse/CB-8198 > Project: Apache Cordova > Issue Type: New Feature > Components: Android, iOS, Windows, WP8 >Reporter: Vladimir Kotikov >Assignee: Jesse MacFadyen > > Currently all major platform scripts doesn't recognize trace levels and > always logging all their output to console. > This could be unuseful, especially when a huge output from build tools is put > to console (ant build/xcodebuild output is really huge and in most cases is > unnecessary) > I propose to unify the way we write messages to console output: > 1. Pass verbosity arguments (-d, --debug ) downstream to platform scripts. > 2. Introduce special Log class which is shared across platform scripts > * automatically detects trace level according to command line arguments; > * support of output redirection (file, other) in the future? > 3. Add support for the following verbosity levels: Error, Normal, Debug > by default: Error and Normal messages are traced > -silent: only Error messages are traced > -verbose: everything is traced -- 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
[jira] [Updated] (CB-8198) Unified console output logic for core platforms
[ https://issues.apache.org/jira/browse/CB-8198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Kotikov updated CB-8198: - Description: Currently all major platform scripts doesn't recognize trace levels and always logging all their output to console. This could be unuseful, especially when a huge output from build tools is put to console (ant build/xcodebuild output is really huge and in most cases is unnecessary) I propose to unify the way we write messages to console output: 1. Pass verbosity arguments (-d, --debug ) downstream to platform scripts. 2. Introduce special Log class which is shared across platform scripts * automatically detects trace level according to command line arguments; * support of output redirection (file, other) in the future? 3. Add support for the following verbosity levels: Error, Normal, Debug * by default: Error and Normal messages are traced * -silent: only Error messages are traced * -verbose: everything is traced was: Currently all major platform scripts doesn't recognize trace levels and always logging all their output to console. This could be unuseful, especially when a huge output from build tools is put to console (ant build/xcodebuild output is really huge and in most cases is unnecessary) I propose to unify the way we write messages to console output: 1. Pass verbosity arguments (-d, --debug ) downstream to platform scripts. 2. Introduce special Log class which is shared across platform scripts * automatically detects trace level according to command line arguments; * support of output redirection (file, other) in the future? 3. Add support for the following verbosity levels: Error, Normal, Debug by default: Error and Normal messages are traced -silent: only Error messages are traced -verbose: everything is traced > Unified console output logic for core platforms > --- > > Key: CB-8198 > URL: https://issues.apache.org/jira/browse/CB-8198 > Project: Apache Cordova > Issue Type: New Feature > Components: Android, iOS, Windows, WP8 >Reporter: Vladimir Kotikov >Assignee: Jesse MacFadyen > > Currently all major platform scripts doesn't recognize trace levels and > always logging all their output to console. > This could be unuseful, especially when a huge output from build tools is put > to console (ant build/xcodebuild output is really huge and in most cases is > unnecessary) > I propose to unify the way we write messages to console output: > 1. Pass verbosity arguments (-d, --debug ) downstream to platform scripts. > 2. Introduce special Log class which is shared across platform scripts > * automatically detects trace level according to command line arguments; > * support of output redirection (file, other) in the future? > 3. Add support for the following verbosity levels: Error, Normal, Debug > * by default: Error and Normal messages are traced > * -silent: only Error messages are traced > * -verbose: everything is traced -- 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
[jira] [Created] (CB-8199) Add support for verbosity levels for platform scripts
Vladimir Kotikov created CB-8199: Summary: Add support for verbosity levels for platform scripts Key: CB-8199 URL: https://issues.apache.org/jira/browse/CB-8199 Project: Apache Cordova Issue Type: Sub-task Components: Android, iOS, Windows, WP8 Reporter: Vladimir Kotikov Assignee: Jesse MacFadyen -- 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
[jira] [Created] (CB-8200) Pass verbosity arguments from cli downstream to platform scripts
Vladimir Kotikov created CB-8200: Summary: Pass verbosity arguments from cli downstream to platform scripts Key: CB-8200 URL: https://issues.apache.org/jira/browse/CB-8200 Project: Apache Cordova Issue Type: Sub-task Components: CLI Reporter: Vladimir Kotikov -- 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
[jira] [Closed] (CB-8129) Add test coverage report generation to core cordova tools
[ https://issues.apache.org/jira/browse/CB-8129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Kotikov closed CB-8129. Thanks, Andrew. > Add test coverage report generation to core cordova tools > - > > Key: CB-8129 > URL: https://issues.apache.org/jira/browse/CB-8129 > Project: Apache Cordova > Issue Type: Improvement > Components: CLI, CordovaJS, CordovaLib >Reporter: Vladimir Kotikov > Labels: coverage, tools > > It will be great to be able to generate reports easily just by running some > npm commands or grunt tasks. > E.g. 'npm run coverage' in repo could produce some coverage reports. -- 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
[jira] [Updated] (CB-8200) Pass verbosity arguments from cli downstream to platform scripts
[
https://issues.apache.org/jira/browse/CB-8200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Kotikov updated CB-8200:
-
Description:
Currently verbosity arguments for Cordova CLI commands ({{-d}} or
{{--verbose}}) isn't passed to platform scripts, so the only way to
icrease/decrease verbosity of updated platform scripts is to pass verbosity
argument behind double dash ({{--}}).
Moreover, this works only for build/run/emulate commands due to CLI arguments
parsing logic.
For better usability it will be better if we'll pass these arguments downstream
to platform scripts (create, build, run, etc.)
> Pass verbosity arguments from cli downstream to platform scripts
> -
>
> Key: CB-8200
> URL: https://issues.apache.org/jira/browse/CB-8200
> Project: Apache Cordova
> Issue Type: Sub-task
> Components: CLI
>Reporter: Vladimir Kotikov
>
> Currently verbosity arguments for Cordova CLI commands ({{-d}} or
> {{--verbose}}) isn't passed to platform scripts, so the only way to
> icrease/decrease verbosity of updated platform scripts is to pass verbosity
> argument behind double dash ({{--}}).
> Moreover, this works only for build/run/emulate commands due to CLI arguments
> parsing logic.
> For better usability it will be better if we'll pass these arguments
> downstream to platform scripts (create, build, run, etc.)
--
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
[jira] [Commented] (CB-8216) Adding plugins by relative path fails when CWD is not the project root
[ https://issues.apache.org/jira/browse/CB-8216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14276832#comment-14276832 ] Vladimir Kotikov commented on CB-8216: -- Looks like that this is medic specific and I’m doubt if we’ll experience this issue anywhere else. So since the fix to mobilespec already pushed to master, I propose to close original issue. More technical details below: Repro steps: 1. Cd to mobilespec’s parent folder 2. Set PWD to current directory 3. Run createmobilespec with following command: cordova-mobile-spec\createmobilespec\createmobilespec --android --skiplink --debug mobilespec Explanation: Initially on Windows PWD is not being set implicitly for each process (that’s why we were not able to catch this error while running createmobilespec from console) and in this case cli works fine. But buildbot ShellCommand explicitly sets PWD for spawned process (apparently for emulating NIX environment), and in case of Medic it will be set to project’s root parent directory. This coincidence causes plugman to fail resolve plugin location properly. > Adding plugins by relative path fails when CWD is not the project root > -- > > Key: CB-8216 > URL: https://issues.apache.org/jira/browse/CB-8216 > Project: Apache Cordova > Issue Type: Bug > Components: CordovaLib >Reporter: Andrew Grieve >Assignee: Sergey Grebnov >Priority: Minor > > e.g. cd into the platforms directory, then "cordova plugin add > ../../../cordova-plugin-file". It'll try to get it from the registry then > fail. The issue is that we chdir() into the project root before the call to > add the plugin. -- 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
[jira] [Comment Edited] (CB-8216) Adding plugins by relative path fails when CWD is not the project root
[ https://issues.apache.org/jira/browse/CB-8216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14276832#comment-14276832 ] Vladimir Kotikov edited comment on CB-8216 at 1/14/15 12:03 PM: Looks like that this is medic specific and I’m doubt if we’ll experience this issue anywhere else. More technical details below: Repro steps: 1. Cd to mobilespec’s parent folder 2. Set PWD to current directory 3. Run createmobilespec with following command: cordova-mobile-spec\createmobilespec\createmobilespec --android --skiplink --debug mobilespec Explanation: Initially on Windows PWD is not being set implicitly for each process (that’s why we were not able to catch this error while running createmobilespec from console) and in this case cli works fine. But buildbot ShellCommand explicitly sets PWD for spawned process (apparently for emulating NIX environment), and in case of Medic it will be set to project’s root parent directory. This coincidence causes plugman to fail resolve plugin location properly. was (Author: vladimir.kotikov): Looks like that this is medic specific and I’m doubt if we’ll experience this issue anywhere else. So since the fix to mobilespec already pushed to master, I propose to close original issue. More technical details below: Repro steps: 1. Cd to mobilespec’s parent folder 2. Set PWD to current directory 3. Run createmobilespec with following command: cordova-mobile-spec\createmobilespec\createmobilespec --android --skiplink --debug mobilespec Explanation: Initially on Windows PWD is not being set implicitly for each process (that’s why we were not able to catch this error while running createmobilespec from console) and in this case cli works fine. But buildbot ShellCommand explicitly sets PWD for spawned process (apparently for emulating NIX environment), and in case of Medic it will be set to project’s root parent directory. This coincidence causes plugman to fail resolve plugin location properly. > Adding plugins by relative path fails when CWD is not the project root > -- > > Key: CB-8216 > URL: https://issues.apache.org/jira/browse/CB-8216 > Project: Apache Cordova > Issue Type: Bug > Components: CordovaLib >Reporter: Andrew Grieve >Assignee: Sergey Grebnov >Priority: Minor > > e.g. cd into the platforms directory, then "cordova plugin add > ../../../cordova-plugin-file". It'll try to get it from the registry then > fail. The issue is that we chdir() into the project root before the call to > add the plugin. -- 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
[jira] [Closed] (CB-6615) Plugman fails when try to add plugin with specific version dependencies
[
https://issues.apache.org/jira/browse/CB-6615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Kotikov closed CB-6615.
> Plugman fails when try to add plugin with specific version dependencies
> ---
>
> Key: CB-6615
> URL: https://issues.apache.org/jira/browse/CB-6615
> Project: Apache Cordova
> Issue Type: Bug
> Components: CLI, Plugman
>Reporter: Vladimir Kotikov
>Assignee: Jesse MacFadyen
>
> Repro steps:
> # Create new Cordova project
> # Add any plugin
> # Add following tag to plugin.xml
> {noformat}
>
> {noformat}
> # Add any platform.
> Expected: The project should download and install dependent plugin with
> version 1.0.0
> Actual: The build generates the following output and error:
> {noformat}
> Error 47 Expected fetched plugin to have ID "org.apache.cordova.file@1.0.0"
> but got "org.apache.cordova.file".
> {noformat}
> Related: CB-4809
--
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
[jira] [Closed] (CB-7509) cordova fails to add wp8 platform with --usegit option
[
https://issues.apache.org/jira/browse/CB-7509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Kotikov closed CB-7509.
> cordova fails to add wp8 platform with --usegit option
> --
>
> Key: CB-7509
> URL: https://issues.apache.org/jira/browse/CB-7509
> Project: Apache Cordova
> Issue Type: Bug
> Components: CordovaLib
>Affects Versions: 3.6.0
>Reporter: Vladimir Kotikov
>Assignee: Jesse MacFadyen
>Priority: Critical
> Labels: usegit, wp8
> Fix For: 3.7.0
>
>
> *Repro steps*
> 1. Get cordova-cli and cordova-lib from
> [dist/dev|https://dist.apache.org/repos/dist/dev/cordova/CB-7383/]
> 1. Create empty cordova project
> 2. add WP8 platform with --usegit option: {{cdv platform add wp8 --usegit -d}}
> *Expected:* Platform successfully added
> *Actual:* command fails with following output:
> {noformat}
> Requesting
> {"url":"https://git-wip-us.apache.org/repos/asf?p=cordova-wp8.git;a=snapshot;h=3.6.1;sf=tgz","strictSSL":true}...
> Downloading cordova library for wp8...
> Downloaded, unzipped and extracted 313341 byte response.
> Download complete
> Creating wp8 project...
> Running command:
> C:\Users\vladimir.kotikov\.cordova\lib\wp\cordova\3.6.1\bin\create /s /c
> C:\Users\vladimir.kotikov\.cordova\lib\wp\cordova\3.6.1\bin\create
> d:\PROJECTS\Temp\test-usegit\platforms\wp8
> io.cordova.hellocordova HelloCordova
> Command finished with error code ENOENT:
> C:\Users\vladimir.kotikov\.cordova\lib\wp\cordova\3.6.1\bin\create
> /s,/c,C:\Users\vladimir.kotikov\.cordova\lib\wp\cordova\3.6.1\bin\create,d:\PROJECTS\Temp\test-usegit\platforms\wp8,io.cordova.hellocordova,HelloCordova
> Error: C:\Users\vladimir.kotikov\.cordova\lib\wp\cordova\3.6.1\bin\create:
> Command failed with exit code ENOENT
> at ChildProcess.whenDone
> (d:\cordova\cordova-lib\cordova-lib\src\cordova\superspawn.js:135:23)
> at ChildProcess.EventEmitter.emit (events.js:95:17)
> at Process.ChildProcess._handle.onexit (child_process.js:805:12)
> {noformat}
> Seems to be introduced by commit
> [60c42827|https://github.com/apache/cordova-lib/commit/60c42827a0e2c61729a65e904e798bf2e2830e7c].
> 'subdirectory' field, that specifies directory inside repo, where platform
> package contents is placed was removes, so cordova can't find create script
> due to invalid path.
> Commit already included in 3.6.1 release and corresponding cordova-lib
> already pushed to dist/dev
--
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
[jira] [Updated] (CB-8312) Multiply accelerometer values by -g on Windows
[ https://issues.apache.org/jira/browse/CB-8312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Kotikov updated CB-8312: - Description: Windows implementation of device-motion methods returns acceleration, measrued in g's (source: https://msdn.microsoft.com/en-us/library/windows/apps/windows.devices.sensors.accelerometerreading.accelerationx). To be consistent with current plugin's specs, it is necessary to multiply accelerometer result by G constant (9.81 according to https://github.com/apache/cordova-plugin-device-motion/blob/master/doc/index.md#acceleration) > Multiply accelerometer values by -g on Windows > -- > > Key: CB-8312 > URL: https://issues.apache.org/jira/browse/CB-8312 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Device Motion, Windows >Reporter: Sergey Shakhnazarov > > Windows implementation of device-motion methods returns acceleration, > measrued in g's (source: > https://msdn.microsoft.com/en-us/library/windows/apps/windows.devices.sensors.accelerometerreading.accelerationx). > To be consistent with current plugin's specs, it is necessary to multiply > accelerometer result by G constant (9.81 according to > https://github.com/apache/cordova-plugin-device-motion/blob/master/doc/index.md#acceleration) -- 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
[jira] [Assigned] (CB-7962) Add cordova-plugin-media support for browser platform
[ https://issues.apache.org/jira/browse/CB-7962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Kotikov reassigned CB-7962: Assignee: Vladimir Kotikov > Add cordova-plugin-media support for browser platform > - > > Key: CB-7962 > URL: https://issues.apache.org/jira/browse/CB-7962 > Project: Apache Cordova > Issue Type: Sub-task > Components: Browser >Reporter: Sergey Shakhnazarov >Assignee: Vladimir Kotikov > -- 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
[jira] [Assigned] (CB-7957) Add cordova-plugin-file-transfer support for browser platform
[ https://issues.apache.org/jira/browse/CB-7957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Kotikov reassigned CB-7957: Assignee: Vladimir Kotikov > Add cordova-plugin-file-transfer support for browser platform > -- > > Key: CB-7957 > URL: https://issues.apache.org/jira/browse/CB-7957 > Project: Apache Cordova > Issue Type: Sub-task > Components: Browser >Reporter: Sergey Shakhnazarov >Assignee: Vladimir Kotikov > -- 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
[jira] [Assigned] (CB-7956) Add cordova-plugin-file support for browser platform
[ https://issues.apache.org/jira/browse/CB-7956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Kotikov reassigned CB-7956: Assignee: Vladimir Kotikov > Add cordova-plugin-file support for browser platform > > > Key: CB-7956 > URL: https://issues.apache.org/jira/browse/CB-7956 > Project: Apache Cordova > Issue Type: Sub-task > Components: Browser >Reporter: Sergey Shakhnazarov >Assignee: Vladimir Kotikov > -- 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
[jira] [Assigned] (CB-7963) Add cordova-plugin-media-capture support for browser platform
[ https://issues.apache.org/jira/browse/CB-7963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Kotikov reassigned CB-7963: Assignee: Vladimir Kotikov > Add cordova-plugin-media-capture support for browser platform > - > > Key: CB-7963 > URL: https://issues.apache.org/jira/browse/CB-7963 > Project: Apache Cordova > Issue Type: Sub-task > Components: Browser >Reporter: Sergey Shakhnazarov >Assignee: Vladimir Kotikov > -- 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
[jira] [Created] (CB-8407) file-transfer plugin fails to download a file if to ms-appdata specified file on windows
Vladimir Kotikov created CB-8407: Summary: file-transfer plugin fails to download a file if to ms-appdata specified file on windows Key: CB-8407 URL: https://issues.apache.org/jira/browse/CB-8407 Project: Apache Cordova Issue Type: Bug Components: Plugin File Transfer Affects Versions: 0.4.8 Environment: Windows platform File-transfer plugin@0.4.9-dev file plugin@1.3.4-dev Reporter: Vladimir Kotikov Assignee: Vladimir Kotikov download() in file-transfer plugin expects path instead of internal URL on windows This bug seems to be introduced with these changes to cordova-plugin-file. All tests for download method of file-transfer plugin now fail on windows with following message: Exception calling native with command :: FileTransfer :: download ::exception=WinRTError: The parameter is incorrect. As per internal discussion, this line may be the cause: https://github.com/apache/cordova-plugin-file-transfer/blob/master/src/windows/FileTransferProxy.js#L166 Mobilespec output: org.apache.cordova.file-transfer.tests.tests >> FileTransfer methods download filetransfer.spec.4 should download a file Error: Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL. org.apache.cordova.file-transfer.tests.tests >> FileTransfer methods download filetransfer.spec.5 should download a file using http basic auth Error: Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL. org.apache.cordova.file-transfer.tests.tests >> FileTransfer methods download filetransfer.spec.6 should get 401 status on http basic auth failure Error: Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL. org.apache.cordova.file-transfer.tests.tests >> FileTransfer methods download filetransfer.spec.8 should download a file using https:// Error: Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL. org.apache.cordova.file-transfer.tests.tests >> FileTransfer methods download filetransfer.spec.11 should call the error callback on abort() Error: Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL. org.apache.cordova.file-transfer.tests.tests >> FileTransfer methods download filetransfer.spec.9 should not leave partial file due to abort Error: Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL. org.apache.cordova.file-transfer.tests.tests >> FileTransfer methods download filetransfer.spec.10 should be stopped by abort() right away Error: Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL. org.apache.cordova.file-transfer.tests.tests >> FileTransfer methods download filetransfer.spec.12 should get http status on failure Error: Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL. org.apache.cordova.file-transfer.tests.tests >> FileTransfer methods download filetransfer.spec.13 should get http body on failure Error: Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL. org.apache.cordova.file-transfer.tests.tests >> FileTransfer methods download filetransfer.spec.14 should handle malformed urls Error: Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL. org.apache.cordova.file-transfer.tests.tests >> FileTransfer methods download filetransfer.spec.15 filetransfer.spec.15 should handle unknown host Error: Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL. org.apache.cordova.file-transfer.tests.tests >> FileTransfer methods download filetransfer.spec.17 progress should work with gzip encoding Error: Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL. org.apache.cordova.file-transfer.tests.tests >> FileTransfer methods download filetransfer.spec.30 downloaded file entries should have a toNativeURL method Error: Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL. -- 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
[jira] [Updated] (CB-8407) file-transfer plugin fails to download a file if to ms-appdata specified file on windows
[ https://issues.apache.org/jira/browse/CB-8407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Kotikov updated CB-8407: - Description: download() in file-transfer plugin expects path instead of internal URL on windows This bug seems to be introduced with these changes to cordova-plugin-file: https://github.com/apache/cordova-plugin-file/commit/bcbeae24cd24583b790da95e0e076492eb16cd4f All tests for download method of file-transfer plugin now fail on windows with following message: Exception calling native with command :: FileTransfer :: download ::exception=WinRTError: The parameter is incorrect. As per internal discussion, this line may be the cause: https://github.com/apache/cordova-plugin-file-transfer/blob/master/src/windows/FileTransferProxy.js#L166 was: download() in file-transfer plugin expects path instead of internal URL on windows This bug seems to be introduced with these changes to cordova-plugin-file. All tests for download method of file-transfer plugin now fail on windows with following message: Exception calling native with command :: FileTransfer :: download ::exception=WinRTError: The parameter is incorrect. As per internal discussion, this line may be the cause: https://github.com/apache/cordova-plugin-file-transfer/blob/master/src/windows/FileTransferProxy.js#L166 Mobilespec output: org.apache.cordova.file-transfer.tests.tests >> FileTransfer methods download filetransfer.spec.4 should download a file Error: Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL. org.apache.cordova.file-transfer.tests.tests >> FileTransfer methods download filetransfer.spec.5 should download a file using http basic auth Error: Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL. org.apache.cordova.file-transfer.tests.tests >> FileTransfer methods download filetransfer.spec.6 should get 401 status on http basic auth failure Error: Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL. org.apache.cordova.file-transfer.tests.tests >> FileTransfer methods download filetransfer.spec.8 should download a file using https:// Error: Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL. org.apache.cordova.file-transfer.tests.tests >> FileTransfer methods download filetransfer.spec.11 should call the error callback on abort() Error: Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL. org.apache.cordova.file-transfer.tests.tests >> FileTransfer methods download filetransfer.spec.9 should not leave partial file due to abort Error: Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL. org.apache.cordova.file-transfer.tests.tests >> FileTransfer methods download filetransfer.spec.10 should be stopped by abort() right away Error: Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL. org.apache.cordova.file-transfer.tests.tests >> FileTransfer methods download filetransfer.spec.12 should get http status on failure Error: Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL. org.apache.cordova.file-transfer.tests.tests >> FileTransfer methods download filetransfer.spec.13 should get http body on failure Error: Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL. org.apache.cordova.file-transfer.tests.tests >> FileTransfer methods download filetransfer.spec.14 should handle malformed urls Error: Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL. org.apache.cordova.file-transfer.tests.tests >> FileTransfer methods download filetransfer.spec.15 filetransfer.spec.15 should handle unknown host Error: Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL. org.apache.cordova.file-transfer.tests.tests >> FileTransfer methods download filetransfer.spec.17 progress should work with gzip encoding Error: Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL. org.apache.cordova.file-transfer.tests.tests >> FileTransfer methods download filetransfer.spec.30 downloaded file entries should have a toNativeURL method Error: Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL. > file-transfer plugin fails to download a file if to ms-appdata specified file > on windows > > > Key: CB-8407 > URL: https://issues.apache.org/jira/browse/CB-8407 > Project:
[jira] [Assigned] (CB-8185) Add online and offiline plugin-network-information events support for the Browser platform
[ https://issues.apache.org/jira/browse/CB-8185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Kotikov reassigned CB-8185: Assignee: Vladimir Kotikov > Add online and offiline plugin-network-information events support for the > Browser platform > -- > > Key: CB-8185 > URL: https://issues.apache.org/jira/browse/CB-8185 > Project: Apache Cordova > Issue Type: Improvement > Components: Browser, Plugin Network Information >Reporter: Sergey Shakhnazarov >Assignee: Vladimir Kotikov > > http://caniuse.com/#feat=online-status -- 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
[jira] [Updated] (CB-8185) Add online and offiline plugin-network-information events support for the Browser platform
[
https://issues.apache.org/jira/browse/CB-8185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Kotikov updated CB-8185:
-
Description:
Initial implementation used XHR to check whether we connected to network or
not. Two main problems of this approach is that it used CORS and wasn't able to
detect local network access.
So for better compatibility with specs it is better to use browsers native
implementation of {{navigator.onLine}} property which properly handles all the
aspects of network accessibility.
{{navigator.onLine}} available for all modern browsers:
http://caniuse.com/#feat=online-status
was:http://caniuse.com/#feat=online-status
> Add online and offiline plugin-network-information events support for the
> Browser platform
> --
>
> Key: CB-8185
> URL: https://issues.apache.org/jira/browse/CB-8185
> Project: Apache Cordova
> Issue Type: Improvement
> Components: Browser, Plugin Network Information
>Reporter: Sergey Shakhnazarov
>Assignee: Vladimir Kotikov
>
> Initial implementation used XHR to check whether we connected to network or
> not. Two main problems of this approach is that it used CORS and wasn't able
> to detect local network access.
> So for better compatibility with specs it is better to use browsers native
> implementation of {{navigator.onLine}} property which properly handles all
> the aspects of network accessibility.
> {{navigator.onLine}} available for all modern browsers:
> http://caniuse.com/#feat=online-status
--
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
[jira] [Closed] (CB-8090) File plugin returns incorrect error when trying to resolve invalid URI with leading slash
[
https://issues.apache.org/jira/browse/CB-8090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Kotikov closed CB-8090.
Resolution: Cannot Reproduce
Assignee: Vladimir Kotikov
> File plugin returns incorrect error when trying to resolve invalid URI with
> leading slash
> -
>
> Key: CB-8090
> URL: https://issues.apache.org/jira/browse/CB-8090
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin File
>Reporter: Vladimir Kotikov
>Assignee: Vladimir Kotikov
> Labels: file, windows
>
> This is very formal but still...
> Bug can be reprod by file.spec.12
> {{should error (ENCODING_ERR) when resolving invalid URI with leading /”}}
--
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
[jira] [Created] (CB-8432) InAppBrowser window doesn't properly displayed when root page CSS differs from default.
Vladimir Kotikov created CB-8432: Summary: InAppBrowser window doesn't properly displayed when root page CSS differs from default. Key: CB-8432 URL: https://issues.apache.org/jira/browse/CB-8432 Project: Apache Cordova Issue Type: Bug Components: Plugin InAppBrowser Affects Versions: 0.6.1-dev Environment: Windows platform Reporter: Vladimir Kotikov Assignee: Vladimir Kotikov Fix For: 0.6.1 Wnen non-default CSS rules is applied to root page InappBrowser sometimes fails to display its view correctly. It could be placed under some elements or at the bottom of page, etc. The problem is that CSS, applied to InappBrowser view is relaxed, so we need to make it more strict or apply some CSS reset rules to it. -- 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
[jira] [Closed] (CB-8407) file-transfer plugin fails to download a file if to ms-appdata specified file on windows
[ https://issues.apache.org/jira/browse/CB-8407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Kotikov closed CB-8407. Resolution: Fixed > file-transfer plugin fails to download a file if to ms-appdata specified file > on windows > > > Key: CB-8407 > URL: https://issues.apache.org/jira/browse/CB-8407 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin File Transfer >Affects Versions: 0.4.8 > Environment: Windows platform > File-transfer plugin@0.4.9-dev > file plugin@1.3.4-dev >Reporter: Vladimir Kotikov >Assignee: Vladimir Kotikov > Labels: file, file-transfer, windows > > download() in file-transfer plugin expects path instead of internal URL on > windows > This bug seems to be introduced with these changes to cordova-plugin-file: > https://github.com/apache/cordova-plugin-file/commit/bcbeae24cd24583b790da95e0e076492eb16cd4f > All tests for download method of file-transfer plugin now fail on windows > with following message: > Exception calling native with command :: FileTransfer :: download > ::exception=WinRTError: The parameter is incorrect. > As per internal discussion, this line may be the cause: > https://github.com/apache/cordova-plugin-file-transfer/blob/master/src/windows/FileTransferProxy.js#L166 -- 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
[jira] [Updated] (CB-8458) Device-orientation tests fails on windows even compass device in not available
[
https://issues.apache.org/jira/browse/CB-8458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Kotikov updated CB-8458:
-
Summary: Device-orientation tests fails on windows even compass device in
not available (was: Device-orientation tests fails on windows even compass in
not available)
> Device-orientation tests fails on windows even compass device in not available
> --
>
> Key: CB-8458
> URL: https://issues.apache.org/jira/browse/CB-8458
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin Device Orientation
>Reporter: Vladimir Kotikov
>Assignee: Vladimir Kotikov
>
> Device orientation tests detects if compass hardware is available on device
> inside of dedicated {{it()}} block and if compass is not available this tests
> is marked as failed.
> Proposed approach - move corresponding logic to {{beforeEach}} block and
> remove false failure.
--
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
[jira] [Created] (CB-8458) Device-orientation tests fails on windows even compass in not available
Vladimir Kotikov created CB-8458:
Summary: Device-orientation tests fails on windows even compass in
not available
Key: CB-8458
URL: https://issues.apache.org/jira/browse/CB-8458
Project: Apache Cordova
Issue Type: Bug
Components: Plugin Device Orientation
Reporter: Vladimir Kotikov
Assignee: Vladimir Kotikov
Device orientation tests detects if compass hardware is available on device
inside of dedicated {{it()}} block and if compass is not available this tests
is marked as failed.
Proposed approach - move corresponding logic to {{beforeEach}} block and remove
false failure.
--
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
[jira] [Created] (CB-8459) File-plugin on Windows fails to get file above the root filesystem directory
Vladimir Kotikov created CB-8459:
Summary: File-plugin on Windows fails to get file above the root
filesystem directory
Key: CB-8459
URL: https://issues.apache.org/jira/browse/CB-8459
Project: Apache Cordova
Issue Type: Bug
Components: Plugin File
Reporter: Vladimir Kotikov
Assignee: Vladimir Kotikov
On Windows file plugin fails to get file by relative path when this path leads
to location above the root directory. ("file.spec.111 should not traverse above
above the root directory").
According to spec it should still resolve such paths, because correct behaviour
is to ignore the ../ at relative path start in this cases, not to fail out.
--
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
[jira] [Resolved] (CB-7957) Add cordova-plugin-file-transfer support for browser platform
[ https://issues.apache.org/jira/browse/CB-7957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Kotikov resolved CB-7957. -- Resolution: Fixed > Add cordova-plugin-file-transfer support for browser platform > -- > > Key: CB-7957 > URL: https://issues.apache.org/jira/browse/CB-7957 > Project: Apache Cordova > Issue Type: Sub-task > Components: Browser >Reporter: Sergey Shakhnazarov >Assignee: Vladimir Kotikov > -- 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
[jira] [Resolved] (CB-8185) Add online and offiline plugin-network-information events support for the Browser platform
[
https://issues.apache.org/jira/browse/CB-8185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Kotikov resolved CB-8185.
--
Resolution: Fixed
> Add online and offiline plugin-network-information events support for the
> Browser platform
> --
>
> Key: CB-8185
> URL: https://issues.apache.org/jira/browse/CB-8185
> Project: Apache Cordova
> Issue Type: Improvement
> Components: Browser, Plugin Network Information
>Reporter: Sergey Shakhnazarov
>Assignee: Vladimir Kotikov
>
> Initial implementation used XHR to check whether we connected to network or
> not. Two main problems of this approach is that it used CORS and wasn't able
> to detect local network access.
> So for better compatibility with specs it is better to use browsers native
> implementation of {{navigator.onLine}} property which properly handles all
> the aspects of network accessibility.
> {{navigator.onLine}} available for all modern browsers:
> http://caniuse.com/#feat=online-status
--
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
[jira] [Closed] (CB-7956) Add cordova-plugin-file support for browser platform
[ https://issues.apache.org/jira/browse/CB-7956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Kotikov closed CB-7956. Resolution: Fixed > Add cordova-plugin-file support for browser platform > > > Key: CB-7956 > URL: https://issues.apache.org/jira/browse/CB-7956 > Project: Apache Cordova > Issue Type: Sub-task > Components: Browser >Reporter: Sergey Shakhnazarov >Assignee: Vladimir Kotikov > -- 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
[jira] [Closed] (CB-8089) File plugin fails to resolve local filesystem root
[
https://issues.apache.org/jira/browse/CB-8089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Kotikov closed CB-8089.
Resolution: Cannot Reproduce
> File plugin fails to resolve local filesystem root
> --
>
> Key: CB-8089
> URL: https://issues.apache.org/jira/browse/CB-8089
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin File
> Environment: windows
>Reporter: Vladimir Kotikov
>
> This can be reproduced by running file spec 15
> {{file.spec.15 should have a root that is a DirectoryEntry: error in
> resolvingLocalSystemURL.}}
> Function try to resolve local URL like “C:\\Users\\...” but cannot find it
> because the following code searches index of incorrect root/prefix
> {noformat}
> if (uri.indexOf("file:///") === 0 ) {
> path = msappdataLocalPath + uri.substr(8).replace('/', '\\');
> } else if (uri.indexOf(msappdataLocalPrefix) === 0) {
> path = msappdataLocalPath + uri.replace(msappdataLocalPrefix,
> '').replace('/', '\\');
> } else if (uri.indexOf(msappdataTempPrefix) === 0) {
> path = msappdataTempPath + uri.replace(msappdataTempPrefix,
> '').replace('/', '\\');
> {noformat}
--
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
[jira] [Created] (CB-8654) File transfer plugin on WP8 caches web credentials?
Vladimir Kotikov created CB-8654: Summary: File transfer plugin on WP8 caches web credentials? Key: CB-8654 URL: https://issues.apache.org/jira/browse/CB-8654 Project: Apache Cordova Issue Type: Improvement Components: Plugin File Transfer Reporter: Vladimir Kotikov Assignee: Vladimir Kotikov Priority: Minor On WP8 File Transfer plugin caches download requests. The results of this can be confusing sometimes, for example downloading file from secured resource second time succeeds, even credentials for request does not specified, or already changed at server side (proof: http://stackoverflow.com/questions/20804452/httpwebrequest-credentials-stored-cached-automatically ) There is already workaround, available to end-user – just pass if-Modified-Since header with current time to download method. Probably this should be noted in plugin README as a platform-specific quirk. -- 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
[jira] [Resolved] (CB-7962) Add cordova-plugin-media support for browser platform
[ https://issues.apache.org/jira/browse/CB-7962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Kotikov resolved CB-7962. -- Resolution: Implemented > Add cordova-plugin-media support for browser platform > - > > Key: CB-7962 > URL: https://issues.apache.org/jira/browse/CB-7962 > Project: Apache Cordova > Issue Type: Sub-task > Components: Browser >Reporter: Sergey Shakhnazarov >Assignee: Vladimir Kotikov > -- 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
[jira] [Resolved] (CB-7963) Add cordova-plugin-media-capture support for browser platform
[ https://issues.apache.org/jira/browse/CB-7963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Kotikov resolved CB-7963. -- Resolution: Implemented > Add cordova-plugin-media-capture support for browser platform > - > > Key: CB-7963 > URL: https://issues.apache.org/jira/browse/CB-7963 > Project: Apache Cordova > Issue Type: Sub-task > Components: Browser >Reporter: Sergey Shakhnazarov >Assignee: Vladimir Kotikov > -- 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
[jira] [Closed] (CB-8521) 'cordova plugin save' should save all installed plugins and their version/git-url/folder-location into config.xml
[ https://issues.apache.org/jira/browse/CB-8521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Kotikov closed CB-8521. > 'cordova plugin save' should save all installed plugins and their > version/git-url/folder-location into config.xml > - > > Key: CB-8521 > URL: https://issues.apache.org/jira/browse/CB-8521 > Project: Apache Cordova > Issue Type: New Feature >Reporter: Omar Mefire >Assignee: Omar Mefire > > In addition to using 'cordova plugin add org.apache.cordova.device --save' to > both add and save a plugin to config.xml, It would be useful to have a way to > 'mass save' already installed plugins to config.xml. -- 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
[jira] [Resolved] (CB-8521) 'cordova plugin save' should save all installed plugins and their version/git-url/folder-location into config.xml
[ https://issues.apache.org/jira/browse/CB-8521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Kotikov resolved CB-8521. -- Resolution: Fixed > 'cordova plugin save' should save all installed plugins and their > version/git-url/folder-location into config.xml > - > > Key: CB-8521 > URL: https://issues.apache.org/jira/browse/CB-8521 > Project: Apache Cordova > Issue Type: New Feature >Reporter: Omar Mefire >Assignee: Omar Mefire > > In addition to using 'cordova plugin add org.apache.cordova.device --save' to > both add and save a plugin to config.xml, It would be useful to have a way to > 'mass save' already installed plugins to config.xml. -- 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
[jira] [Closed] (CB-8432) InAppBrowser window doesn't properly displayed when root page CSS differs from default.
[ https://issues.apache.org/jira/browse/CB-8432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Kotikov closed CB-8432. Resolution: Fixed > InAppBrowser window doesn't properly displayed when root page CSS differs > from default. > --- > > Key: CB-8432 > URL: https://issues.apache.org/jira/browse/CB-8432 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin InAppBrowser >Affects Versions: 0.6.1-dev > Environment: Windows platform >Reporter: Vladimir Kotikov >Assignee: Vladimir Kotikov > Fix For: 0.6.1 > > > Wnen non-default CSS rules is applied to root page InappBrowser sometimes > fails to display its view correctly. It could be placed under some elements > or at the bottom of page, etc. > The problem is that CSS, applied to InappBrowser view is relaxed, so we need > to make it more strict or apply some CSS reset rules to it. -- 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
[jira] [Closed] (CB-8185) Add online and offiline plugin-network-information events support for the Browser platform
[
https://issues.apache.org/jira/browse/CB-8185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Kotikov closed CB-8185.
> Add online and offiline plugin-network-information events support for the
> Browser platform
> --
>
> Key: CB-8185
> URL: https://issues.apache.org/jira/browse/CB-8185
> Project: Apache Cordova
> Issue Type: Improvement
> Components: Browser, Plugin Network Information
>Reporter: Sergey Shakhnazarov
>Assignee: Vladimir Kotikov
>
> Initial implementation used XHR to check whether we connected to network or
> not. Two main problems of this approach is that it used CORS and wasn't able
> to detect local network access.
> So for better compatibility with specs it is better to use browsers native
> implementation of {{navigator.onLine}} property which properly handles all
> the aspects of network accessibility.
> {{navigator.onLine}} available for all modern browsers:
> http://caniuse.com/#feat=online-status
--
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
[jira] [Resolved] (CB-8223) Expose config.xml in the Browser platform
[ https://issues.apache.org/jira/browse/CB-8223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Kotikov resolved CB-8223. -- Resolution: Implemented > Expose config.xml in the Browser platform > - > > Key: CB-8223 > URL: https://issues.apache.org/jira/browse/CB-8223 > Project: Apache Cordova > Issue Type: Improvement > Components: Browser >Reporter: Sergey Shakhnazarov > > Browser platform apps need to read parameter values from config.xml, e.g. > when [initializing SplashScreen > plugin|https://github.com/MSOpenTech/cordova-plugin-splashscreen/commits/CB-7964] -- 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
[jira] [Assigned] (CB-8583) WP8 FileTransfer.download does not overwrite existing file
[ https://issues.apache.org/jira/browse/CB-8583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Kotikov reassigned CB-8583: Assignee: Vladimir Kotikov > WP8 FileTransfer.download does not overwrite existing file > -- > > Key: CB-8583 > URL: https://issues.apache.org/jira/browse/CB-8583 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin File Transfer >Affects Versions: 0.4.8 > Environment: Windows Phone 8.1. Lumia 530 >Reporter: Don Becker >Assignee: Vladimir Kotikov > > FileTransfer.download() does not overwrite an existing file on Windows Phone > 8, as it does on Android and iOS. The function calls the successCallback, > but the target file is not updated with the new downloaded version. -- 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
[jira] [Commented] (CB-8583) WP8 FileTransfer.download does not overwrite existing file
[ https://issues.apache.org/jira/browse/CB-8583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14377737#comment-14377737 ] Vladimir Kotikov commented on CB-8583: -- I wasn't able to repro this using latest version of plugin from master branch on latest version of platform. [~psyon], if you are still experiencing this, could you please post a bit more details: plugin and platform versions, sample code or repro steps? > WP8 FileTransfer.download does not overwrite existing file > -- > > Key: CB-8583 > URL: https://issues.apache.org/jira/browse/CB-8583 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin File Transfer >Affects Versions: 0.4.8 > Environment: Windows Phone 8.1. Lumia 530 >Reporter: Don Becker >Assignee: Vladimir Kotikov > > FileTransfer.download() does not overwrite an existing file on Windows Phone > 8, as it does on Android and iOS. The function calls the successCallback, > but the target file is not updated with the new downloaded version. -- 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
[jira] [Assigned] (CB-7689) Add insertCSS support for Windows platform
[ https://issues.apache.org/jira/browse/CB-7689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Kotikov reassigned CB-7689: Assignee: Vladimir Kotikov > Add insertCSS support for Windows platform > -- > > Key: CB-7689 > URL: https://issues.apache.org/jira/browse/CB-7689 > Project: Apache Cordova > Issue Type: New Feature > Components: Plugin InAppBrowser > Environment: 'windows' platform >Reporter: Sergey Shakhnazarov >Assignee: Vladimir Kotikov > > insertCSS (injectStyleCode and injectStyleFile) are not implemented in > InAppBrowser Windows proxy -- 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
[jira] [Closed] (CB-7689) Add insertCSS support for Windows platform
[ https://issues.apache.org/jira/browse/CB-7689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Kotikov closed CB-7689. Resolution: Implemented > Add insertCSS support for Windows platform > -- > > Key: CB-7689 > URL: https://issues.apache.org/jira/browse/CB-7689 > Project: Apache Cordova > Issue Type: New Feature > Components: Plugin InAppBrowser > Environment: 'windows' platform >Reporter: Sergey Shakhnazarov >Assignee: Vladimir Kotikov > > insertCSS (injectStyleCode and injectStyleFile) are not implemented in > InAppBrowser Windows proxy -- 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
[jira] [Commented] (CB-8635) InAppBrowser on Windows adds 40px gray border, wrapper div without class or id
[
https://issues.apache.org/jira/browse/CB-8635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14377841#comment-14377841
]
Vladimir Kotikov commented on CB-8635:
--
[~BrandonLive], regarding your suggestions:
# The reason, why grey border exists around IAB window is that user needs the
way to close window. On android you cand do this with back button, but on
Windows there is no such concept.
# IAB designed as a container for displaying external content, so probably you
don't need to apply styles for browser container itself. If you want to apply
styles to displayed content, you have to use {{browser.insertCSS}} method:
https://github.com/apache/cordova-plugin-inappbrowser#insertcss
> InAppBrowser on Windows adds 40px gray border, wrapper div without class or id
> --
>
> Key: CB-8635
> URL: https://issues.apache.org/jira/browse/CB-8635
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin InAppBrowser
>Affects Versions: 3.6.0
> Environment: Windows 8.1, Windows Phone 8.1
>Reporter: Brandon Paddock
>
> The InAppBrowserProxy on Windows 8.1 does some weird things. One of them is
> that it adds a wrapper div with a bunch of inline styles on it, including a
> gray 40px border on all sides. This appears even if you set the "location=no"
> option to disable the default browser controls.
> Because this div is inserted directly under the body element with no id or
> class, you can't override its styling via CSS (and since it uses inline
> styles, you'd have to use !important to override them).
> Suggested fixes:
> 1) Assign a class name to the div so it can be styled.
> 2) Don't use an inline style for the default styling. Use CSS.
> 3) Don't put this weird gray border in the default styling (it isn't there on
> Android so why put it there on Windows?)
> 4) Or, remove the div entirely (at least in the location=no case).
--
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
[jira] [Comment Edited] (CB-8635) InAppBrowser on Windows adds 40px gray border, wrapper div without class or id
[
https://issues.apache.org/jira/browse/CB-8635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14377841#comment-14377841
]
Vladimir Kotikov edited comment on CB-8635 at 3/24/15 1:33 PM:
---
[~BrandonLive], regarding your suggestions:
# The reason, why grey border exists around IAB window is that user needs the
way to close window. On android you cand do this with back button, but on
Windows there is no such concept, to the only way to close windows is to
click/tap on this grey border.
# IAB designed as a container for displaying external content, so probably you
don't need to apply styles for browser container itself. If you want to apply
styles to displayed content, you have to use {{browser.insertCSS}} method:
https://github.com/apache/cordova-plugin-inappbrowser#insertcss
was (Author: vladimir.kotikov):
[~BrandonLive], regarding your suggestions:
# The reason, why grey border exists around IAB window is that user needs the
way to close window. On android you cand do this with back button, but on
Windows there is no such concept.
# IAB designed as a container for displaying external content, so probably you
don't need to apply styles for browser container itself. If you want to apply
styles to displayed content, you have to use {{browser.insertCSS}} method:
https://github.com/apache/cordova-plugin-inappbrowser#insertcss
> InAppBrowser on Windows adds 40px gray border, wrapper div without class or id
> --
>
> Key: CB-8635
> URL: https://issues.apache.org/jira/browse/CB-8635
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin InAppBrowser
>Affects Versions: 3.6.0
> Environment: Windows 8.1, Windows Phone 8.1
>Reporter: Brandon Paddock
>
> The InAppBrowserProxy on Windows 8.1 does some weird things. One of them is
> that it adds a wrapper div with a bunch of inline styles on it, including a
> gray 40px border on all sides. This appears even if you set the "location=no"
> option to disable the default browser controls.
> Because this div is inserted directly under the body element with no id or
> class, you can't override its styling via CSS (and since it uses inline
> styles, you'd have to use !important to override them).
> Suggested fixes:
> 1) Assign a class name to the div so it can be styled.
> 2) Don't use an inline style for the default styling. Use CSS.
> 3) Don't put this weird gray border in the default styling (it isn't there on
> Android so why put it there on Windows?)
> 4) Or, remove the div entirely (at least in the location=no case).
--
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
[jira] [Comment Edited] (CB-8635) InAppBrowser on Windows adds 40px gray border, wrapper div without class or id
[
https://issues.apache.org/jira/browse/CB-8635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14377841#comment-14377841
]
Vladimir Kotikov edited comment on CB-8635 at 3/24/15 1:34 PM:
---
[~BrandonLive], regarding your suggestions:
# The reason, why grey border exists around IAB window is that user needs the
way to close window. On android you cand do this with back button, but on
Windows there is no such concept, so the only way to close windows is to
click/tap on this grey border.
# IAB designed as a container for displaying external content, so probably you
don't need to apply styles for browser container itself. If you want to apply
styles to displayed content, you have to use {{browser.insertCSS}} method:
https://github.com/apache/cordova-plugin-inappbrowser#insertcss
was (Author: vladimir.kotikov):
[~BrandonLive], regarding your suggestions:
# The reason, why grey border exists around IAB window is that user needs the
way to close window. On android you cand do this with back button, but on
Windows there is no such concept, to the only way to close windows is to
click/tap on this grey border.
# IAB designed as a container for displaying external content, so probably you
don't need to apply styles for browser container itself. If you want to apply
styles to displayed content, you have to use {{browser.insertCSS}} method:
https://github.com/apache/cordova-plugin-inappbrowser#insertcss
> InAppBrowser on Windows adds 40px gray border, wrapper div without class or id
> --
>
> Key: CB-8635
> URL: https://issues.apache.org/jira/browse/CB-8635
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin InAppBrowser
>Affects Versions: 3.6.0
> Environment: Windows 8.1, Windows Phone 8.1
>Reporter: Brandon Paddock
>
> The InAppBrowserProxy on Windows 8.1 does some weird things. One of them is
> that it adds a wrapper div with a bunch of inline styles on it, including a
> gray 40px border on all sides. This appears even if you set the "location=no"
> option to disable the default browser controls.
> Because this div is inserted directly under the body element with no id or
> class, you can't override its styling via CSS (and since it uses inline
> styles, you'd have to use !important to override them).
> Suggested fixes:
> 1) Assign a class name to the div so it can be styled.
> 2) Don't use an inline style for the default styling. Use CSS.
> 3) Don't put this weird gray border in the default styling (it isn't there on
> Android so why put it there on Windows?)
> 4) Or, remove the div entirely (at least in the location=no case).
--
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
[jira] [Commented] (CB-8635) InAppBrowser on Windows adds 40px gray border, wrapper div without class or id
[
https://issues.apache.org/jira/browse/CB-8635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14377967#comment-14377967
]
Vladimir Kotikov commented on CB-8635:
--
[~jml] If you want just to have IAB window hidden, there is a {{"hidden=yes"}}
option available for InAppBrowser on windows. Here is sample usage:
{noformat}
var ref = cordova.InAppBrowser.open('http://apache.org', '_blank',
'hidden=yes');
{noformat}
> InAppBrowser on Windows adds 40px gray border, wrapper div without class or id
> --
>
> Key: CB-8635
> URL: https://issues.apache.org/jira/browse/CB-8635
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin InAppBrowser
>Affects Versions: 3.6.0
> Environment: Windows 8.1, Windows Phone 8.1
>Reporter: Brandon Paddock
>
> The InAppBrowserProxy on Windows 8.1 does some weird things. One of them is
> that it adds a wrapper div with a bunch of inline styles on it, including a
> gray 40px border on all sides. This appears even if you set the "location=no"
> option to disable the default browser controls.
> Because this div is inserted directly under the body element with no id or
> class, you can't override its styling via CSS (and since it uses inline
> styles, you'd have to use !important to override them).
> Suggested fixes:
> 1) Assign a class name to the div so it can be styled.
> 2) Don't use an inline style for the default styling. Use CSS.
> 3) Don't put this weird gray border in the default styling (it isn't there on
> Android so why put it there on Windows?)
> 4) Or, remove the div entirely (at least in the location=no case).
--
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
[jira] [Commented] (CB-8635) InAppBrowser on Windows adds 40px gray border, wrapper div without class or id
[ https://issues.apache.org/jira/browse/CB-8635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14380410#comment-14380410 ] Vladimir Kotikov commented on CB-8635: -- The bugfix for CB-8661 is on the way. > InAppBrowser on Windows adds 40px gray border, wrapper div without class or id > -- > > Key: CB-8635 > URL: https://issues.apache.org/jira/browse/CB-8635 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin InAppBrowser >Affects Versions: 3.6.0 > Environment: Windows 8.1, Windows Phone 8.1 >Reporter: Brandon Paddock > > The InAppBrowserProxy on Windows 8.1 does some weird things. One of them is > that it adds a wrapper div with a bunch of inline styles on it, including a > gray 40px border on all sides. This appears even if you set the "location=no" > option to disable the default browser controls. > Because this div is inserted directly under the body element with no id or > class, you can't override its styling via CSS (and since it uses inline > styles, you'd have to use !important to override them). > Suggested fixes: > 1) Assign a class name to the div so it can be styled. > 2) Don't use an inline style for the default styling. Use CSS. > 3) Don't put this weird gray border in the default styling (it isn't there on > Android so why put it there on Windows?) > 4) Or, remove the div entirely (at least in the location=no case). -- 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
[jira] [Closed] (CB-8654) File transfer plugin on WP8 caches web credentials?
[ https://issues.apache.org/jira/browse/CB-8654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Kotikov closed CB-8654. Resolution: Won't Fix Information regarding this behaviour has been added to plugin's README > File transfer plugin on WP8 caches web credentials? > --- > > Key: CB-8654 > URL: https://issues.apache.org/jira/browse/CB-8654 > Project: Apache Cordova > Issue Type: Improvement > Components: Plugin File Transfer >Reporter: Vladimir Kotikov >Assignee: Vladimir Kotikov >Priority: Minor > > On WP8 File Transfer plugin caches download requests. > The results of this can be confusing sometimes, for example downloading file > from secured resource second time succeeds, even credentials for request does > not specified, or already changed at server side (proof: > http://stackoverflow.com/questions/20804452/httpwebrequest-credentials-stored-cached-automatically > ) > > There is already workaround, available to end-user – just pass > if-Modified-Since header with current time to download method. > > Probably this should be noted in plugin README as a platform-specific quirk. -- 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
[jira] [Closed] (CB-8459) File-plugin on Windows fails to get file above the root filesystem directory
[
https://issues.apache.org/jira/browse/CB-8459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Kotikov closed CB-8459.
Resolution: Fixed
> File-plugin on Windows fails to get file above the root filesystem directory
>
>
> Key: CB-8459
> URL: https://issues.apache.org/jira/browse/CB-8459
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin File
>Reporter: Vladimir Kotikov
>Assignee: Vladimir Kotikov
>
> On Windows file plugin fails to get file by relative path when this path
> leads to location above the root directory. ("file.spec.111 should not
> traverse above above the root directory").
> According to spec it should still resolve such paths, because correct
> behaviour is to ignore the ../ at relative path start in this cases, not to
> fail out.
--
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
[jira] [Closed] (CB-8458) Device-orientation tests fails on windows even compass device in not available
[
https://issues.apache.org/jira/browse/CB-8458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Kotikov closed CB-8458.
Resolution: Fixed
> Device-orientation tests fails on windows even compass device in not available
> --
>
> Key: CB-8458
> URL: https://issues.apache.org/jira/browse/CB-8458
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin Device Orientation
>Reporter: Vladimir Kotikov
>Assignee: Vladimir Kotikov
>
> Device orientation tests detects if compass hardware is available on device
> inside of dedicated {{it()}} block and if compass is not available this tests
> is marked as failed.
> Proposed approach - move corresponding logic to {{beforeEach}} block and
> remove false failure.
--
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
[jira] [Closed] (CB-7491) Bridge manual tests page crashes mobilespec app on windows platform
[
https://issues.apache.org/jira/browse/CB-7491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Kotikov closed CB-7491.
Resolution: Fixed
> Bridge manual tests page crashes mobilespec app on windows platform
> ---
>
> Key: CB-7491
> URL: https://issues.apache.org/jira/browse/CB-7491
> Project: Apache Cordova
> Issue Type: Bug
> Components: mobile-spec
> Environment: Windows8/8.1/WP8.1 device
>Reporter: Vladimir Kotikov
> Labels: bridge, mobilespec, windows
>
> When user clicks on Non-plugin automatic tests -> Run bridge tests in
> mobilespec application on windows platform, app crashes.
> Origin is {{reportSuiteResults()}} method in HtmlReporter, which tries to
> call method of {{reporterView}} object which is undefined since Bridge tests
> suite contains no specs (on windows) and due to this instance of
> {{reporterView}} is not created.
> Possible fix - add check for {{reporterView === undefined}} in
> {{reportSuiteResults}} method
--
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
[jira] [Closed] (CB-8095) upload method on windows doesn't support progress events correctly
[
https://issues.apache.org/jira/browse/CB-8095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Kotikov closed CB-8095.
Resolution: Fixed
> upload method on windows doesn't support progress events correctly
> --
>
> Key: CB-8095
> URL: https://issues.apache.org/jira/browse/CB-8095
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin File Transfer
>Reporter: Vladimir Kotikov
> Labels: file-transfer, windows
>
> On windows FileTrasfer doesn't support {{progress}} events for upload
> operation properly since internal implementation uses XHR which doesn't
> provide all information, necessary to fire correct progress events.
> Possible solution here is to replace XHR with {{BackgroundUploader}} class
> which itself supports progress notification in more convenient way and can
> provide all necessary data for progress events for FileTransfer.
--
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
[jira] [Closed] (CB-6499) Add `multiple` option to pickContact method.
[
https://issues.apache.org/jira/browse/CB-6499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Kotikov closed CB-6499.
Resolution: Fixed
> Add `multiple` option to pickContact method.
>
>
> Key: CB-6499
> URL: https://issues.apache.org/jira/browse/CB-6499
> Project: Apache Cordova
> Issue Type: Improvement
> Components: Plugin Contacts
>Reporter: Vladimir Kotikov
>
> Sometimes user should have possibility to select multiple contacts from
> device's address book, e.g. select multiple message recipients.
> Sample usage is something like: {noformat}pickContact(success, error,
> {multiple: true}){noformat}
--
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
[jira] [Closed] (CB-6477) Adding media plugin doesn't add corresponding capabilities to Windows8 platform
[ https://issues.apache.org/jira/browse/CB-6477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Kotikov closed CB-6477. > Adding media plugin doesn't add corresponding capabilities to Windows8 > platform > --- > > Key: CB-6477 > URL: https://issues.apache.org/jira/browse/CB-6477 > Project: Apache Cordova > Issue Type: Bug > Components: CLI, Plugin Media, Windows 8 > Environment: Windows 8.1 cordova CLI 3.4.1 >Reporter: Vladimir Kotikov >Assignee: Jesse MacFadyen > > 1. create a new cordova app > 2. add the windows8 platform > 3. add the org.apache.cordova.media plugin > 4. call startRecord > 5. Debug the windows8 app > Result: > An exception is thrown when trying to record. > 0x80070005 - JavaScript runtime error: Access is denied. > WinRT information: Access to the specified location (MusicLibrary) requires a > capability to be declared in the manifest. > Expected: > Cordova should add the MusicLibrary and microphone capabilities to the > windows8 project. -- 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
[jira] [Closed] (CB-6485) Add pickContact functionality to cordova contacts plugin
[
https://issues.apache.org/jira/browse/CB-6485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Kotikov closed CB-6485.
> Add pickContact functionality to cordova contacts plugin
>
>
> Key: CB-6485
> URL: https://issues.apache.org/jira/browse/CB-6485
> Project: Apache Cordova
> Issue Type: Improvement
> Components: Plugin Contacts
>Reporter: Vladimir Kotikov
> Labels: contacts
>
> The PR listed below adds WP8, Windows 8, Android, FireOS and iOS support for
> this feature.
> It would be great to have a `pickContact` method that launches the Contact
> Picker, that allow user to choose single or multiple contacts from device's
> address book.
> Contact picker should have UI, native to each platform
> Sample usage:
> {noformat}
> navigator.contacts.pickContact(function(contact){
> console.log('The following contact has been selected:' +
> JSON.stringify(contact));
> },function(err){
> console.log('Error: ' + err);
> });
> {noformat}
--
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
[jira] [Closed] (CB-6613) "File not found" error when using targetWidth and targetHeight on Windows8 with Camera plugin
[ https://issues.apache.org/jira/browse/CB-6613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Kotikov closed CB-6613. > "File not found" error when using targetWidth and targetHeight on Windows8 > with Camera plugin > - > > Key: CB-6613 > URL: https://issues.apache.org/jira/browse/CB-6613 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Camera, Windows 8 >Affects Versions: 2.9.0 >Reporter: Vladimir Kotikov >Assignee: Jesse MacFadyen > > Reproduction steps: > 1. create a new cordova app > 2. add the camera plugin, version 0.2.9 (latest) > 3. add the window8 platform > 4. use getPicture with targetWidth and targetHeight set > Result: > No picture data is returned, the error callback is hit with the message "File > not found" > If you remove targetwidth and targetheight, the camera plugin works. > Expected: > camera plugin should work with targetWidth and targetHeight set -- 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
[jira] [Closed] (CB-6654) cordova run wp8 freezes after application starts and until app is closed.
[ https://issues.apache.org/jira/browse/CB-6654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Kotikov closed CB-6654. > cordova run wp8 freezes after application starts and until app is closed. > - > > Key: CB-6654 > URL: https://issues.apache.org/jira/browse/CB-6654 > Project: Apache Cordova > Issue Type: Bug > Components: CLI, WP8 >Reporter: Vladimir Kotikov >Assignee: Jesse MacFadyen > Fix For: 3.5.0 > > > Repro steps: > 1. create new cordova app > 2. add wp8 platform to app created > 3. start application from CLI (cordova emulate/run) > On all platforms except wp8 this causes application to start in > emulator/device and then then deploy script exits. > On wp8 deploy script freezes, until application is closed, and only then exit. > This is inconsistent across platforms and may be confusing to developers. > This is because of CB-802, which is still not resolved. > I propose to hide this behaviour behind '--wait' flag of Cordova Deploy, and > make this behaviour default when all (or most important) platform will > support it. -- 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
[jira] [Closed] (CB-6699) Cordova-cli / plugman add tag for each entry in www dir to windows8 / wp8 .jsproj files
[
https://issues.apache.org/jira/browse/CB-6699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Kotikov closed CB-6699.
> Cordova-cli / plugman add tag for each entry in www dir to windows8
> / wp8 .jsproj files
> -
>
> Key: CB-6699
> URL: https://issues.apache.org/jira/browse/CB-6699
> Project: Apache Cordova
> Issue Type: Improvement
> Components: CLI, Plugman, Windows 8, WP8
>Reporter: Vladimir Kotikov
>Assignee: Jesse MacFadyen
> Labels: cli, cordova-lib, windows8, wp8
> Attachments: VSProj.PNG
>
>
> Every time, when you trigger `cordova prepare/build` or `plugman
> install/uninstall/prepare` (this also `include cordova plugin add/rm`),
> cordova removes all references to www/* files from .jsproj file and then adds
> tags like {noformat}
>
>
>
> {noformat}
> to .jsproj file.
> *Proposal:* We can use one entry like {noformat}
>
>
>
> {noformat} for all files in www folder including static assets and plugins'
> .js modules (like described
> [here|http://msdn.microsoft.com/en-us/library/ms171454.aspx])
--
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
[jira] [Closed] (CB-6728) Support chip architecture as an option when building Windows and Windows Phone projects
[
https://issues.apache.org/jira/browse/CB-6728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Kotikov closed CB-6728.
> Support chip architecture as an option when building Windows and Windows
> Phone projects
> ---
>
> Key: CB-6728
> URL: https://issues.apache.org/jira/browse/CB-6728
> Project: Apache Cordova
> Issue Type: Improvement
> Components: Android, CLI, iOS, Windows 8, WP8
>Affects Versions: 3.4.0
>Reporter: Vladimir Kotikov
>Assignee: Jesse MacFadyen
> Labels: arm, cli, windows, wp8, x64, x86
>
> Currently apps for Windows 8 and Windows Phone 8 are targeted to AnyCPU
> architecture, which is universal, but sometimes it's critical to build
> application for specific processor architecture.
> As an example is WebSQL plugin which contains references to C++ libs so needs
> to be built for specific architecture (x84, x64, ARM) and which does not
> support AnyCPU target.
> So it looks important to add support for additional build flags `-x64`,
> `-x86`, `-arm`, '-any' to specify target chip architecture.
> {noformat}
> cordova build windows8 --release --x64
> cordova build wp8 --arm
> {noformat}
> If flag is not specified, `AnuCPU` target platform should be used by default.
--
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
[jira] [Closed] (CB-6909) shellCmd and shellRunParam in master.cfg use values for master, fails on Windows slaves if OS X master
[
https://issues.apache.org/jira/browse/CB-6909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Kotikov closed CB-6909.
Resolution: Not a Problem
> shellCmd and shellRunParam in master.cfg use values for master, fails on
> Windows slaves if OS X master
> --
>
> Key: CB-6909
> URL: https://issues.apache.org/jira/browse/CB-6909
> Project: Apache Cordova
> Issue Type: Bug
> Components: Medic, Windows 8, WP8
> Environment: OS X master, buildbot 0.8.8, Windows Server 2012R2
> slave, buildslave 0.8.8
>Reporter: Vladimir Kotikov
>Assignee: Max Woghiren
> Labels: medic, windows8, wp8
>
> shellCmd and shellRunCmd are defined in master.cfg and used for a lot of the
> build tasks. But the value depends on the OS of the master, so if you have a
> OS X master and Windows client (or vice versa) a lot of steps will fail.
> {noformat}
> shellCmd="/bin/sh"
> shellRunParam="-c"
> if is_Windows :
> shellCmd="cmd"
> shellRunParam="/c"
> {noformat}
> For some steps, like in wp8 and windows8 sections, we know they'll always run
> on Windows so we could always use 'cmd'. But in common sections or for a
> platform like android, it needs to work on both.
> -
> It seems that ShellCommand step already uses command interpreter according to
> slave platform (see
> http://docs.buildbot.net/current/manual/cfg-buildsteps.html#step-ShellCommand).
> So it's safe to remove this and specify commands for ShellCommand steps just
> with list of strings.
> Another possible issue is different path delimiter on windows and other
> platforms. But in most cases slash instead of backslash works fine on
> windows. So it is possible to replace '\\' to '/' in windows build steps.
--
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
[jira] [Closed] (CB-7378) Camera plugin is not working on WP8.1 since native API change
[
https://issues.apache.org/jira/browse/CB-7378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Kotikov closed CB-7378.
Resolution: Fixed
> Camera plugin is not working on WP8.1 since native API change
> -
>
> Key: CB-7378
> URL: https://issues.apache.org/jira/browse/CB-7378
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin Camera
> Environment: WP8.1 device/emulator
>Reporter: Vladimir Kotikov
>
> {{Camera.getPicture()}} won't work on WP8.1 since API change.
> Camre plugin use {{Windows.Media.Capture.CameraCaptureUI()}} class for
> acquiring camera picture, which is unavailable on WP8.1. Possible solution is
> to use MediaCapture class. Also it will require to implement custom camera
> interface.
--
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
[jira] [Closed] (CB-7373) Mobilespec manual contacts test provide no output for errors.
[ https://issues.apache.org/jira/browse/CB-7373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Kotikov closed CB-7373. Resolution: Fixed > Mobilespec manual contacts test provide no output for errors. > - > > Key: CB-7373 > URL: https://issues.apache.org/jira/browse/CB-7373 > Project: Apache Cordova > Issue Type: Bug > Components: mobile-spec >Reporter: Vladimir Kotikov >Priority: Minor > Labels: contacts, mobilespec, windows8, windows81 > > Mobilespec's manual test for contact->save method provdies no output if any > errors happens during test. > E.g. saving contacts is not supported on windows8/8.1, and save method always > resolves with NOT_SUPPORTED_ERR, but user can't see this in test results. -- 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
[jira] [Closed] (CB-7357) Contact plugin's find method fails on WP8.1 with PENDING_OPERATION_ERROR
[ https://issues.apache.org/jira/browse/CB-7357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Kotikov closed CB-7357. Resolution: Fixed > Contact plugin's find method fails on WP8.1 with PENDING_OPERATION_ERROR > > > Key: CB-7357 > URL: https://issues.apache.org/jira/browse/CB-7357 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Contacts > Environment: Windows 8.1, Windows Phone 8.1 device/emulator >Reporter: Vladimir Kotikov > Labels: contacts, windows-phone-81, wp8.1 > > Contact plugin's find method fails on WP8.1 with PENDING_OPERATION_ERROR > Repro steps: > 1. Create mobilespec app with latest contacts plugin included > 2. Run mobilespec app on wp8.1 device/emulator and navigate to New-style > tests -> Manual tests -> contact tests. > 3. Click on Get phone's contacts > Expected: > Contacts data shown in status box. or 'No contacts found' if no contacts > exists on device > Actual: > 'Error 3' message shown in status box. -- 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
[jira] [Closed] (CB-7440) Media-capture manual tests fails on Windows8/8.1/WP8.1 due to APi misalign
[
https://issues.apache.org/jira/browse/CB-7440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Kotikov closed CB-7440.
Resolution: Fixed
> Media-capture manual tests fails on Windows8/8.1/WP8.1 due to APi misalign
> --
>
> Key: CB-7440
> URL: https://issues.apache.org/jira/browse/CB-7440
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin Media Capture
>Reporter: Vladimir Kotikov
> Labels: media-capture, windows, wp8.1
>
> Capture manual tests fails on Windows 8/8.1/WP8.1 due to API misalign in
> CaptureProxy.
> Details:
> 1. Capture methods captures files to user's profile folders, instead of local
> app’s folders so these files can't be accessed via src="" attribute.
> 2. Capture methods returns MediaFile objects without fullPath property.
> 3. Capture methods returns MediaFile objects with localURL field set to
> file's full path.
> Proposed solution:
> 1. Return url with ms-appdata// for nativeURL/localURL property
> {noformat}
> @param nativeURL
> {DOMString} an alternate URL which can be used by native
> webview controls, for example media players.
> (optional, readonly)
> {noformat}
> 2. fullPath – same as above but w/o msappdata://prefix or native Windows full
> path.
> with these changes both of fullPath of localURL can be successfully resolved
> by File plugin after CB-7413 resolution
> (https://github.com/apache/cordova-plugin-file/pull/70)
--
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
[jira] [Closed] (CB-7494) cordova-windows fails to build app with unicode name using cordova/build.bat script
[
https://issues.apache.org/jira/browse/CB-7494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Kotikov closed CB-7494.
Resolution: Fixed
> cordova-windows fails to build app with unicode name using cordova/build.bat
> script
> ---
>
> Key: CB-7494
> URL: https://issues.apache.org/jira/browse/CB-7494
> Project: Apache Cordova
> Issue Type: Bug
> Components: Windows
>Reporter: Vladimir Kotikov
>
> Repro steps (in cordova-windows repo):
> {{windows\bin\create "testcreate 応用" com.test.app 応用}}
> {{".windows\testcreate 応用\cordova\build"}}
> Expected:
> App builds successfully.
> Actual:
> {noformat}
> package.windows80.appxmanifest(35,22): error APPX3032: App manifest
> validation failed.
> Value '応用' of attribute '/Package/Applications/Application/@Id' is n ot a
> valid ASCII Windows ID.
> It must contain one or more parts, separated with periods, where each part
> contains only characters a-z, A-Z, 0-9, and does no t start with a digit.
> [d:\cordova\cordova-windows\windows\testcreate 応用\CordovaApp.Windows80.jsproj]
> {noformat}
> This doesn't affects CLI
> The reason is that bin/create script write app name and app id in wrong
> places at *.manifest files
--
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
[jira] [Closed] (CB-7532) File transfer plugin for windows can't download file to non-existing dir
[
https://issues.apache.org/jira/browse/CB-7532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Kotikov closed CB-7532.
Resolution: Fixed
> File transfer plugin for windows can't download file to non-existing dir
>
>
> Key: CB-7532
> URL: https://issues.apache.org/jira/browse/CB-7532
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin File Transfer
>Reporter: Vladimir Kotikov
> Labels: filetransfer, windows
>
> Best way to repro:
> 1. Create mobilespec app with windows platform
> 2. Run plugin manual test -> org.apache.cordova.file-transfer.tests.tests
> 3. Push "Download to a non-existent dir (should work)" button
> Following contents is placed into log:
> {noformat}
> Requesting filesystem
> Checking for existing file
> Checking for existing directory.
> Starting download
> ERROR: ft.download 1
> {noformat}
--
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
[jira] [Closed] (CB-7529) File transfer plugin for windows platform can't resolve 'ms-appdata' URIs
[ https://issues.apache.org/jira/browse/CB-7529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Kotikov closed CB-7529. Resolution: Fixed > File transfer plugin for windows platform can't resolve 'ms-appdata' URIs > - > > Key: CB-7529 > URL: https://issues.apache.org/jira/browse/CB-7529 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin File Transfer >Reporter: Vladimir Kotikov > > Similar to https://issues.apache.org/jira/browse/CB-7413 File transfer plugin > is not able to resolve 'ms-appdata' uris for local files. Such URIs are > produced for example by camera plugin. > Due to this user can't upload a picture from camera to some remote server, > for example, and he needs to use File plugin functionality to get full path > to file and then upload it. -- 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
[jira] [Resolved] (CB-8092) File plugin on windows doesn't encode URIs when using toUrl() method
[
https://issues.apache.org/jira/browse/CB-8092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Kotikov resolved CB-8092.
--
Resolution: Fixed
> File plugin on windows doesn't encode URIs when using toUrl() method
>
>
> Key: CB-8092
> URL: https://issues.apache.org/jira/browse/CB-8092
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin File
>Reporter: Vladimir Kotikov
> Labels: plugin-file, windows
>
> This can be reprod by file.spec.52
> {{Entry.toURL on directory: entryFile.toURL() return URL with “\\\” slashes
> and non-encoded spaces in folder’s names}}
> This issue consists of 2 parts. First, windows is missing
> {{filesystem.__format__()}} method which is common place to handle URI
> encoding. Second, methods in FileProxy for windows can't handle encoded URIs
--
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
[jira] [Reopened] (CB-8092) File plugin on windows doesn't encode URIs when using toUrl() method
[
https://issues.apache.org/jira/browse/CB-8092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Kotikov reopened CB-8092:
--
> File plugin on windows doesn't encode URIs when using toUrl() method
>
>
> Key: CB-8092
> URL: https://issues.apache.org/jira/browse/CB-8092
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin File
>Reporter: Vladimir Kotikov
> Labels: plugin-file, windows
>
> This can be reprod by file.spec.52
> {{Entry.toURL on directory: entryFile.toURL() return URL with “\\\” slashes
> and non-encoded spaces in folder’s names}}
> This issue consists of 2 parts. First, windows is missing
> {{filesystem.__format__()}} method which is common place to handle URI
> encoding. Second, methods in FileProxy for windows can't handle encoded URIs
--
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
[jira] [Assigned] (CB-8721) (Windows Phone 8, File-transfer download method) When specifying header with comma in it, fail callback is called
[
https://issues.apache.org/jira/browse/CB-8721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Kotikov reassigned CB-8721:
Assignee: Vladimir Kotikov
> (Windows Phone 8, File-transfer download method) When specifying header with
> comma in it, fail callback is called
> -
>
> Key: CB-8721
> URL: https://issues.apache.org/jira/browse/CB-8721
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin File Transfer
>Reporter: Alexander Sorokin
>Assignee: Vladimir Kotikov
>
> This code fails because header with comma in it is not parsed properly:
> {code}
> transfer.download(fileURL, localFilePath, function win(){}, function
> fail(){}, true,
> {
> headers: {
> 'If-Modified-Since': 'Sun, 06 Nov 1994 08:49:37 GMT'
> }
> });
> {code}
--
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
[jira] [Assigned] (CB-8661) executeScript doesn't return the a result on Windows platform
[
https://issues.apache.org/jira/browse/CB-8661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Kotikov reassigned CB-8661:
Assignee: Vladimir Kotikov
> executeScript doesn't return the a result on Windows platform
> -
>
> Key: CB-8661
> URL: https://issues.apache.org/jira/browse/CB-8661
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin InAppBrowser, Windows
> Environment: Windows 8
> Latest version of Cordova 4.3.0
> Latest version of Plugin InAppBrowser 0.6.0
>Reporter: John Little
>Assignee: Vladimir Kotikov
>
> executeScript is supposed to provide a variable to the function called when
> the script is completed as per this clip from the documentation :-
> If the injected script is of type code, the callback executes with a single
> parameter, which is the return value of the script, wrapped in an Array. For
> multi-line scripts, this is the return value of the last statement, or the
> last expression evaluated.
> When running as a Windows app the array is empty.
> Looking in the Windows InAppBrowserProxy.js file, line 230 looks like this
>op.oncomplete = function () { hasCallback && win([]); };
> So clearly no data is being passed ([]) is an empty array.
> According to the documentation from Microsoft :-
> https://msdn.microsoft.com/en-us/library/windows.ui.xaml.controls.webview.invokescriptasync.aspx
> The invokeScriptAsync function can return a string.
> So if I modify line 230 to look like this
> op.oncomplete = function (e) { hasCallback && win([e.target.result]); };
> I get a string returned to my callback function.
> You could also modify the similar line in the injectScriptFile function, as
> it also calls invokeScriptAsync.
> I need the return value because the only way to comunicate between the page
> in the IAB and the app is to poll some sessionStorage and wait for the page
> to set some data.
--
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
[jira] [Assigned] (CB-8649) Media Plugin WP8.1 Media.getDuration returns -1 for audio (mp3) asset
[ https://issues.apache.org/jira/browse/CB-8649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Kotikov reassigned CB-8649: Assignee: Vladimir Kotikov > Media Plugin WP8.1 Media.getDuration returns -1 for audio (mp3) asset > - > > Key: CB-8649 > URL: https://issues.apache.org/jira/browse/CB-8649 > Project: Apache Cordova > Issue Type: Bug >Reporter: Kim Hansen >Assignee: Vladimir Kotikov >Priority: Minor > > It is understood that WP8.1 is not supported (hence minor priority) but when > support is added this is fixable. > Media plugin 0.2.13, Cordova 4.2.0, Tools for Apache Cordova > The duration can be found at Media.node.duration -- 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
[jira] [Commented] (CB-8649) Media Plugin WP8.1 Media.getDuration returns -1 for audio (mp3) asset
[ https://issues.apache.org/jira/browse/CB-8649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14381495#comment-14381495 ] Vladimir Kotikov commented on CB-8649: -- [~khansen] looks like this is a duplicate for CB-7638. This already fixed in https://github.com/apache/cordova-plugin-media/commit/2660e925ab3a4926999333751819fdac017698f7 and fix available since plugin version 0.2.14. Could you please update your plugin and check if still can be reproduced. > Media Plugin WP8.1 Media.getDuration returns -1 for audio (mp3) asset > - > > Key: CB-8649 > URL: https://issues.apache.org/jira/browse/CB-8649 > Project: Apache Cordova > Issue Type: Bug >Reporter: Kim Hansen >Assignee: Vladimir Kotikov >Priority: Minor > > It is understood that WP8.1 is not supported (hence minor priority) but when > support is added this is fixable. > Media plugin 0.2.13, Cordova 4.2.0, Tools for Apache Cordova > The duration can be found at Media.node.duration -- 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
[jira] [Reopened] (CB-7689) Add insertCSS support for Windows platform
[ https://issues.apache.org/jira/browse/CB-7689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Kotikov reopened CB-7689: -- > Add insertCSS support for Windows platform > -- > > Key: CB-7689 > URL: https://issues.apache.org/jira/browse/CB-7689 > Project: Apache Cordova > Issue Type: New Feature > Components: Plugin InAppBrowser > Environment: 'windows' platform >Reporter: Sergey Shakhnazarov >Assignee: Vladimir Kotikov > > insertCSS (injectStyleCode and injectStyleFile) are not implemented in > InAppBrowser Windows proxy -- 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
[jira] [Assigned] (CB-8589) Cordova no success callback on WP81
[ https://issues.apache.org/jira/browse/CB-8589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Kotikov reassigned CB-8589: Assignee: Vladimir Kotikov > Cordova no success callback on WP81 > > > Key: CB-8589 > URL: https://issues.apache.org/jira/browse/CB-8589 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin File Transfer > Environment: Windows Phone 8.1 >Reporter: Bodo Probst >Assignee: Vladimir Kotikov > > The success callback in fileTransfer.upload() is not call, when the server > does not respond with data, but only with a httpResonseStatus. > The call to (FileTransferProxy.js::167) > reader.loadAsync(result.progress.bytesReceived).then(function(size) > fails with exception, when bytesReceived == 0 > On Android, the callback is called correctly. -- 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
[jira] [Closed] (CB-8649) Media Plugin WP8.1 Media.getDuration returns -1 for audio (mp3) asset
[ https://issues.apache.org/jira/browse/CB-8649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Kotikov closed CB-8649. Resolution: Duplicate > Media Plugin WP8.1 Media.getDuration returns -1 for audio (mp3) asset > - > > Key: CB-8649 > URL: https://issues.apache.org/jira/browse/CB-8649 > Project: Apache Cordova > Issue Type: Bug >Reporter: Kim Hansen >Assignee: Vladimir Kotikov >Priority: Minor > > It is understood that WP8.1 is not supported (hence minor priority) but when > support is added this is fixable. > Media plugin 0.2.13, Cordova 4.2.0, Tools for Apache Cordova > The duration can be found at Media.node.duration -- 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
[jira] [Assigned] (CB-8541) [WP81] Cannot record: 'No suitable transform was found to encode or decode'
[ https://issues.apache.org/jira/browse/CB-8541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Kotikov reassigned CB-8541: Assignee: Vladimir Kotikov > [WP81] Cannot record: 'No suitable transform was found to encode or decode' > --- > > Key: CB-8541 > URL: https://issues.apache.org/jira/browse/CB-8541 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Media > Environment: Windows Phone 8.1 >Reporter: Corné Meerkerk >Assignee: Vladimir Kotikov > > The example from the documentation does not work on Windows (Phone) 8.1 with > any file extension (*.mp3, *.m4a, *.wma). The same code does work on Windows > Phone 8. > When media.startRecord() is called, the error callback returns this error > message twice: > 'No suitable transform was found to encode or decode the content.' -- 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
[jira] [Commented] (CB-8541) [WP81] Cannot record: 'No suitable transform was found to encode or decode'
[ https://issues.apache.org/jira/browse/CB-8541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388205#comment-14388205 ] Vladimir Kotikov commented on CB-8541: -- [~CornéM] Unfortunately tou can't use mp3 for audio recording on Windows phone 8.1 devices until you provide custom MP3 transcoder in your app. This is because an MP3 encoder is not shipped with Windows Phone. Here is corresponding link to MSDN documentation: https://msdn.microsoft.com/en-us/library/windows/apps/windows.media.mediaproperties.mediaencodingprofile.createmp3.aspx I'll add this information to Windows quirks section in plugin README. > [WP81] Cannot record: 'No suitable transform was found to encode or decode' > --- > > Key: CB-8541 > URL: https://issues.apache.org/jira/browse/CB-8541 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Media > Environment: Windows Phone 8.1 >Reporter: Corné Meerkerk >Assignee: Vladimir Kotikov > > The example from the documentation does not work on Windows (Phone) 8.1 with > any file extension (*.mp3, *.m4a, *.wma). The same code does work on Windows > Phone 8. > When media.startRecord() is called, the error callback returns this error > message twice: > 'No suitable transform was found to encode or decode the content.' -- 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
[jira] [Comment Edited] (CB-8541) [WP81] Cannot record: 'No suitable transform was found to encode or decode'
[ https://issues.apache.org/jira/browse/CB-8541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388205#comment-14388205 ] Vladimir Kotikov edited comment on CB-8541 at 3/31/15 7:57 AM: --- [~CornéM] Unfortunately tou can't use mp3 for audio recording on Windows phone 8.1 devices until you provide custom MP3 transcoder in your app. This is because an MP3 encoder is not shipped with Windows Phone. Here is corresponding link to MSDN documentation: https://msdn.microsoft.com/en-us/library/windows/apps/windows.media.mediaproperties.mediaencodingprofile.createmp3.aspx Note that this is works only for Windows Phone devices. On Windows desktop devices MP3 recording works well. As a solution on WP8.1 you could use other available formats for recording, such as M4A and WMA I'll add this information to Windows quirks section in plugin README. was (Author: vladimir.kotikov): [~CornéM] Unfortunately tou can't use mp3 for audio recording on Windows phone 8.1 devices until you provide custom MP3 transcoder in your app. This is because an MP3 encoder is not shipped with Windows Phone. Here is corresponding link to MSDN documentation: https://msdn.microsoft.com/en-us/library/windows/apps/windows.media.mediaproperties.mediaencodingprofile.createmp3.aspx I'll add this information to Windows quirks section in plugin README. > [WP81] Cannot record: 'No suitable transform was found to encode or decode' > --- > > Key: CB-8541 > URL: https://issues.apache.org/jira/browse/CB-8541 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Media > Environment: Windows Phone 8.1 >Reporter: Corné Meerkerk >Assignee: Vladimir Kotikov > > The example from the documentation does not work on Windows (Phone) 8.1 with > any file extension (*.mp3, *.m4a, *.wma). The same code does work on Windows > Phone 8. > When media.startRecord() is called, the error callback returns this error > message twice: > 'No suitable transform was found to encode or decode the content.' -- 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
[jira] [Closed] (CB-8541) [WP81] Cannot record: 'No suitable transform was found to encode or decode'
[ https://issues.apache.org/jira/browse/CB-8541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Kotikov closed CB-8541. > [WP81] Cannot record: 'No suitable transform was found to encode or decode' > --- > > Key: CB-8541 > URL: https://issues.apache.org/jira/browse/CB-8541 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Media > Environment: Windows Phone 8.1 >Reporter: Corné Meerkerk >Assignee: Vladimir Kotikov > > The example from the documentation does not work on Windows (Phone) 8.1 with > any file extension (*.mp3, *.m4a, *.wma). The same code does work on Windows > Phone 8. > When media.startRecord() is called, the error callback returns this error > message twice: > 'No suitable transform was found to encode or decode the content.' -- 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
[jira] [Resolved] (CB-8541) [WP81] Cannot record: 'No suitable transform was found to encode or decode'
[ https://issues.apache.org/jira/browse/CB-8541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Kotikov resolved CB-8541. -- Resolution: Fixed > [WP81] Cannot record: 'No suitable transform was found to encode or decode' > --- > > Key: CB-8541 > URL: https://issues.apache.org/jira/browse/CB-8541 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Media > Environment: Windows Phone 8.1 >Reporter: Corné Meerkerk >Assignee: Vladimir Kotikov > > The example from the documentation does not work on Windows (Phone) 8.1 with > any file extension (*.mp3, *.m4a, *.wma). The same code does work on Windows > Phone 8. > When media.startRecord() is called, the error callback returns this error > message twice: > 'No suitable transform was found to encode or decode the content.' -- 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
[jira] [Closed] (CB-7689) Add insertCSS support for Windows platform
[ https://issues.apache.org/jira/browse/CB-7689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Kotikov closed CB-7689. Resolution: Implemented > Add insertCSS support for Windows platform > -- > > Key: CB-7689 > URL: https://issues.apache.org/jira/browse/CB-7689 > Project: Apache Cordova > Issue Type: New Feature > Components: Plugin InAppBrowser > Environment: 'windows' platform >Reporter: Sergey Shakhnazarov >Assignee: Vladimir Kotikov > > insertCSS (injectStyleCode and injectStyleFile) are not implemented in > InAppBrowser Windows proxy -- 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
[jira] [Closed] (CB-8779) [WP8] Media is always in MEDIA_STARTING state
[ https://issues.apache.org/jira/browse/CB-8779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Kotikov closed CB-8779. Resolution: Fixed > [WP8] Media is always in MEDIA_STARTING state > - > > Key: CB-8779 > URL: https://issues.apache.org/jira/browse/CB-8779 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Media, WP8 >Reporter: Alexander Sorokin >Assignee: Jesse MacFadyen > > Steps to repro: > Run mobilespec manual tests. > Even when audio is actually playing, its status is always = 1. -- 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
[jira] [Created] (CB-8831) Battery plugin is not getting correctly registered on Windows platform
Vladimir Kotikov created CB-8831:
Summary: Battery plugin is not getting correctly registered on
Windows platform
Key: CB-8831
URL: https://issues.apache.org/jira/browse/CB-8831
Project: Apache Cordova
Issue Type: Bug
Components: Plugin Battery Status
Environment: Windows 8.1 (desktop)
Reporter: Vladimir Kotikov
Assignee: Vladimir Kotikov
Priority: Minor
Repro steps:
-Latest cordova
-createmobilespec testapp --windows
-run auto tests
Battery plugin will fail to register correcty:
{noformat}
Exception calling native with command :: Battery :: stop
::exception=WinRTError: The text associated with this error code could not be
found
{noformat}
--
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
