[jira] [Commented] (CB-10459) cordova platform list should mark amazon-fireos and wp8 as deprecated

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on CB-10459:
--

Commit ffb779befc9ce8e39bf28096d7a5ff3eefeb1a46 in cordova-lib's branch 
refs/heads/master from [~sarangan12]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-lib.git;h=ffb779b ]

CB-10459: cordova platform list should mark amazon-fireos and wp8 as deprecated

Added depracted information to wp8 and amazon-fireos. This closes #368


> cordova platform list should mark amazon-fireos and wp8 as deprecated
> -
>
> Key: CB-10459
> URL: https://issues.apache.org/jira/browse/CB-10459
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: CordovaLib
>Affects Versions: 6.0.0
>Reporter: Nikhil Khandelwal
>Assignee: Sarangan Rajamanickam
>Priority: Minor
>
> {code}
> λ cordova platform ls
> Installed platforms: android 4.0.2, ios 3.8.0
> Available platforms: amazon-fireos, blackberry10, browser, firefoxos, webos, 
> windows, windows8, wp8
> {code}
> Consider printing:
> {code}
> Available platforms: amazon-fireos (deprecated), blackberry10, browser, 
> firefoxos, webos, windows, windows8, wp8 (deprecated)
> {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] [Commented] (CB-10459) cordova platform list should mark amazon-fireos and wp8 as deprecated

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-10459:
-

Github user asfgit closed the pull request at:

https://github.com/apache/cordova-lib/pull/368


> cordova platform list should mark amazon-fireos and wp8 as deprecated
> -
>
> Key: CB-10459
> URL: https://issues.apache.org/jira/browse/CB-10459
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: CordovaLib
>Affects Versions: 6.0.0
>Reporter: Nikhil Khandelwal
>Assignee: Sarangan Rajamanickam
>Priority: Minor
>
> {code}
> λ cordova platform ls
> Installed platforms: android 4.0.2, ios 3.8.0
> Available platforms: amazon-fireos, blackberry10, browser, firefoxos, webos, 
> windows, windows8, wp8
> {code}
> Consider printing:
> {code}
> Available platforms: amazon-fireos (deprecated), blackberry10, browser, 
> firefoxos, webos, windows, windows8, wp8 (deprecated)
> {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] [Commented] (CB-10515) LocalFileSystem.PERSISTENT does not detect file system storage

[Sam Deepak (JIRA)]

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

Sam Deepak commented on CB-10515:
-

And also my question, if cordova.file.externalRootDirectory is for Android and 
BB10, then according to MS documentation, why adding removableStorage to 
AppManifest.xml does not work.If it should not work, How do I access the public 
storage system in WP8.x platforms.

Is it to be implemented further?

> LocalFileSystem.PERSISTENT does not detect file system storage
> --
>
> Key: CB-10515
> URL: https://issues.apache.org/jira/browse/CB-10515
> Project: Apache Cordova
>  Issue Type: New Feature
>Reporter: Sam Deepak
>  Labels: triaged, windows
>
> The call to window.requestFileSystem(LocalFileSystem.PERSISTENT, 0, 
> function() {}); does not detect the root storage location in windows phone 
> 8.x. Rather it points to private data directory,even after adding   the 
> capability for accessing the local file system (removableStorage) in 
> AppManifest.xml.
> Basically window.requestFileSystem(LocalFileSystem.PERSISTENT, 
> 0,function(fileSystem) {}, function(error){}) gives me only "ms-appx://local" 
> path which is actually the private data directory for an app in windows 
> phone. I want to access the root directory of the file system because I am 
> letting the user to store app specific files anywhere in the phone. (It works 
> in Android without specifying anything)
> Basically the above LocalFileSystem.PERSISTENT should not point to private 
> data directory, rather it should be the root directory of the local file 
> system.



--
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-10482) Remove references to windows8 from cordova-lib/cli

[Sergey Shakhnazarov (JIRA)]

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

Sergey Shakhnazarov updated CB-10482:
-
Summary: Remove references to windows8 from cordova-lib/cli  (was: Remove 
references to windows8 from cordova-lib)

> Remove references to windows8 from cordova-lib/cli
> --
>
> Key: CB-10482
> URL: https://issues.apache.org/jira/browse/CB-10482
> Project: Apache Cordova
>  Issue Type: Sub-task
>  Components: CordovaLib
>Reporter: Sergey Shakhnazarov
>Assignee: Sergey Shakhnazarov
>




--
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-10480) Remove Windows 8 template from cordova-windows

[Sergey Shakhnazarov (JIRA)]

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

Sergey Shakhnazarov resolved CB-10480.
--
Resolution: Fixed

> Remove Windows 8 template from cordova-windows
> --
>
> Key: CB-10480
> URL: https://issues.apache.org/jira/browse/CB-10480
> Project: Apache Cordova
>  Issue Type: Sub-task
>  Components: Windows
>Reporter: Sergey Shakhnazarov
>Assignee: Sergey Shakhnazarov
>




--
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-10459) cordova platform list should mark amazon-fireos and wp8 as deprecated

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-10459:
-

Github user vladimir-kotikov commented on the pull request:

https://github.com/apache/cordova-lib/pull/368#issuecomment-179092390
  
@sarangan12, LGTM, merged.


> cordova platform list should mark amazon-fireos and wp8 as deprecated
> -
>
> Key: CB-10459
> URL: https://issues.apache.org/jira/browse/CB-10459
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: CordovaLib
>Affects Versions: 6.0.0
>Reporter: Nikhil Khandelwal
>Assignee: Sarangan Rajamanickam
>Priority: Minor
>
> {code}
> λ cordova platform ls
> Installed platforms: android 4.0.2, ios 3.8.0
> Available platforms: amazon-fireos, blackberry10, browser, firefoxos, webos, 
> windows, windows8, wp8
> {code}
> Consider printing:
> {code}
> Available platforms: amazon-fireos (deprecated), blackberry10, browser, 
> firefoxos, webos, windows, windows8, wp8 (deprecated)
> {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] [Commented] (CB-10052) Improve superspawn to allow to handle spawned process io streams

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on CB-10052:
--

Commit 540a623bb4d13bf13c8eab874d3ad2377eabe3fd in cordova-lib's branch 
refs/heads/master from [~vladimir.kotikov]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-lib.git;h=540a623 ]

CB-10052 Expose child process' io streams via promise progress notification. 
This closes #369


> Improve superspawn to allow to handle spawned process io streams
> 
>
> Key: CB-10052
> URL: https://issues.apache.org/jira/browse/CB-10052
> Project: Apache Cordova
>  Issue Type: Improvement
>  Components: CordovaCommon
>Affects Versions: 1.0.0
>Reporter: Vladimir Kotikov
>Assignee: Vladimir Kotikov
> Fix For: 1.1.0
>
>
> Sometimes it is useful to process spawned process stdout and stderr in some 
> way before out this to console. The current implementation of superspawn 
> doesn't give a way to do this. One of the cases when this could be helpful - 
> CB-9971 (see https://github.com/apache/cordova-android/pull/240 for some 
> discussion).
> The proposed approach is:
> 1. Add ability to accept any valid stdio configuration, just like the 
> original child_process.spawn does 
> (https://nodejs.org/api/child_process.html#child_process_options_stdio)
> 2. Give a way to caller to listen to stdout and stderr events. This might be 
> implemented as resultant promise progress notification:
> {code:JavaScript}
> spawn('mycommand', [], {stdio: 'pipe'})
> .progress(function (stdio){
> if (stdio.stderr) {
> console.error(stdio.stderr);
> }
> })
> .then(function(result){
> // do other stuff
> })
> {code}
> Another option is to return na object that implements both EventEmitter and 
> Promise interfaces, so anybody might subscribe to its events.



--
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-10052) Improve superspawn to allow to handle spawned process io streams

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-10052:
-

Github user asfgit closed the pull request at:

https://github.com/apache/cordova-lib/pull/369


> Improve superspawn to allow to handle spawned process io streams
> 
>
> Key: CB-10052
> URL: https://issues.apache.org/jira/browse/CB-10052
> Project: Apache Cordova
>  Issue Type: Improvement
>  Components: CordovaCommon
>Affects Versions: 1.0.0
>Reporter: Vladimir Kotikov
>Assignee: Vladimir Kotikov
> Fix For: 1.1.0
>
>
> Sometimes it is useful to process spawned process stdout and stderr in some 
> way before out this to console. The current implementation of superspawn 
> doesn't give a way to do this. One of the cases when this could be helpful - 
> CB-9971 (see https://github.com/apache/cordova-android/pull/240 for some 
> discussion).
> The proposed approach is:
> 1. Add ability to accept any valid stdio configuration, just like the 
> original child_process.spawn does 
> (https://nodejs.org/api/child_process.html#child_process_options_stdio)
> 2. Give a way to caller to listen to stdout and stderr events. This might be 
> implemented as resultant promise progress notification:
> {code:JavaScript}
> spawn('mycommand', [], {stdio: 'pipe'})
> .progress(function (stdio){
> if (stdio.stderr) {
> console.error(stdio.stderr);
> }
> })
> .then(function(result){
> // do other stuff
> })
> {code}
> Another option is to return na object that implements both EventEmitter and 
> Promise interfaces, so anybody might subscribe to its events.



--
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-10052) Improve superspawn to allow to handle spawned process io streams

[Vladimir Kotikov (JIRA)]

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

Vladimir Kotikov resolved CB-10052.
---
Resolution: Fixed

> Improve superspawn to allow to handle spawned process io streams
> 
>
> Key: CB-10052
> URL: https://issues.apache.org/jira/browse/CB-10052
> Project: Apache Cordova
>  Issue Type: Improvement
>  Components: CordovaCommon
>Affects Versions: 1.0.0
>Reporter: Vladimir Kotikov
>Assignee: Vladimir Kotikov
> Fix For: 1.1.0
>
>
> Sometimes it is useful to process spawned process stdout and stderr in some 
> way before out this to console. The current implementation of superspawn 
> doesn't give a way to do this. One of the cases when this could be helpful - 
> CB-9971 (see https://github.com/apache/cordova-android/pull/240 for some 
> discussion).
> The proposed approach is:
> 1. Add ability to accept any valid stdio configuration, just like the 
> original child_process.spawn does 
> (https://nodejs.org/api/child_process.html#child_process_options_stdio)
> 2. Give a way to caller to listen to stdout and stderr events. This might be 
> implemented as resultant promise progress notification:
> {code:JavaScript}
> spawn('mycommand', [], {stdio: 'pipe'})
> .progress(function (stdio){
> if (stdio.stderr) {
> console.error(stdio.stderr);
> }
> })
> .then(function(result){
> // do other stuff
> })
> {code}
> Another option is to return na object that implements both EventEmitter and 
> Promise interfaces, so anybody might subscribe to its events.



--
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-10480) Remove Windows 8 template from cordova-windows

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on CB-10480:
--

Commit 92a298a3189ce8ce9fe6973b49dbdc777835a62b in cordova-windows's branch 
refs/heads/master from [~daserge]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-windows.git;h=92a298a ]

CB-10480 Remove Windows 8 template from cordova-windows

Updated the tests


> Remove Windows 8 template from cordova-windows
> --
>
> Key: CB-10480
> URL: https://issues.apache.org/jira/browse/CB-10480
> Project: Apache Cordova
>  Issue Type: Sub-task
>  Components: Windows
>Reporter: Sergey Shakhnazarov
>Assignee: Sergey Shakhnazarov
>




--
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-10480) Remove Windows 8 template from cordova-windows

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-10480:
-

Github user asfgit closed the pull request at:

https://github.com/apache/cordova-windows/pull/147


> Remove Windows 8 template from cordova-windows
> --
>
> Key: CB-10480
> URL: https://issues.apache.org/jira/browse/CB-10480
> Project: Apache Cordova
>  Issue Type: Sub-task
>  Components: Windows
>Reporter: Sergey Shakhnazarov
>Assignee: Sergey Shakhnazarov
>




--
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-10480) Remove Windows 8 template from cordova-windows

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on CB-10480:
--

Commit 5f15c5eb0fc07cb3a37aaa2f436d03208b1cb80a in cordova-windows's branch 
refs/heads/master from [~daserge]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-windows.git;h=5f15c5e ]

CB-10480 Remove Windows 8 template from cordova-windows

Updated check_reqs
Updated the docs


> Remove Windows 8 template from cordova-windows
> --
>
> Key: CB-10480
> URL: https://issues.apache.org/jira/browse/CB-10480
> Project: Apache Cordova
>  Issue Type: Sub-task
>  Components: Windows
>Reporter: Sergey Shakhnazarov
>Assignee: Sergey Shakhnazarov
>




--
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-10480) Remove Windows 8 template from cordova-windows

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on CB-10480:
--

Commit d783f2073430492e59d99009b30411fb8e8e897a in cordova-windows's branch 
refs/heads/master from [~daserge]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-windows.git;h=d783f20 ]

CB-10480 Remove Windows 8 template from cordova-windows

Adds a friendly error message for windows-target-version = 8.0


> Remove Windows 8 template from cordova-windows
> --
>
> Key: CB-10480
> URL: https://issues.apache.org/jira/browse/CB-10480
> Project: Apache Cordova
>  Issue Type: Sub-task
>  Components: Windows
>Reporter: Sergey Shakhnazarov
>Assignee: Sergey Shakhnazarov
>




--
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-10515) LocalFileSystem.PERSISTENT does not detect file system storage

[Sam Deepak (JIRA)]

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

Sam Deepak commented on CB-10515:
-

Hi Sergey,

When I executed this statement 
window.requestFileSystem(LocalFileSystem.PERSISTENT, 0,function(fileSystem) {}, 
function(error){}) in windows phone 8.x, it gave me the access to 
ms-appx://local. I gave an alert to display the output of .toURL() method, it 
displays "ms-appx/://local" in sideloading and ms-appdata://local in WP8.1 
(private data directory), as mentioned here at 
:https://github.com/apache/cordova-plugin-file#windows-file-system-layout.

But When I read windows phone 8.x site at 
https://msdn.microsoft.com/en-us/library/windows/apps/hh464936.aspx, it is said 
that "removableStorage" capability has to be added to AppManifest.xml to get 
permission to storage system. But when I did it, it did not work.

By your answer, do you mean that right now once can not access the storage at 
the present moment in WP8.1 ? Please advice.

> LocalFileSystem.PERSISTENT does not detect file system storage
> --
>
> Key: CB-10515
> URL: https://issues.apache.org/jira/browse/CB-10515
> Project: Apache Cordova
>  Issue Type: New Feature
>Reporter: Sam Deepak
>  Labels: triaged, windows
>
> The call to window.requestFileSystem(LocalFileSystem.PERSISTENT, 0, 
> function() {}); does not detect the root storage location in windows phone 
> 8.x. Rather it points to private data directory,even after adding   the 
> capability for accessing the local file system (removableStorage) in 
> AppManifest.xml.
> Basically window.requestFileSystem(LocalFileSystem.PERSISTENT, 
> 0,function(fileSystem) {}, function(error){}) gives me only "ms-appx://local" 
> path which is actually the private data directory for an app in windows 
> phone. I want to access the root directory of the file system because I am 
> letting the user to store app specific files anywhere in the phone. (It works 
> in Android without specifying anything)
> Basically the above LocalFileSystem.PERSISTENT should not point to private 
> data directory, rather it should be the root directory of the local file 
> system.



--
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-10515) LocalFileSystem.PERSISTENT does not detect file system storage

[Sam Deepak (JIRA)]

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

Sam Deepak edited comment on CB-10515 at 2/3/16 10:26 AM:
--

Hi Sergey,

When I executed this statement 
window.requestFileSystem(LocalFileSystem.PERSISTENT, 0,function(fileSystem) {}, 
function(error){}) in windows phone 8.x, it gave me the access to 
ms-appx://local. I gave an alert to display the output of .toURL() method, it 
displays "ms-appx/://local" in sideloading and ms-appdata://local in WP8.1 
(private data directory), as mentioned here at 
:https://github.com/apache/cordova-plugin-file#windows-file-system-layout.

But When I read windows phone 8.x site at 
https://msdn.microsoft.com/en-us/library/windows/apps/hh464936.aspx, it is said 
that "removableStorage" capability has to be added to AppManifest.xml to get 
permission to storage system. But when I did it, it did not work.

By your answer, do you mean that right now one can not access the storage at 
the present moment in WP8.1 ? Please advice.


was (Author: theodarsamuel):
Hi Sergey,

When I executed this statement 
window.requestFileSystem(LocalFileSystem.PERSISTENT, 0,function(fileSystem) {}, 
function(error){}) in windows phone 8.x, it gave me the access to 
ms-appx://local. I gave an alert to display the output of .toURL() method, it 
displays "ms-appx/://local" in sideloading and ms-appdata://local in WP8.1 
(private data directory), as mentioned here at 
:https://github.com/apache/cordova-plugin-file#windows-file-system-layout.

But When I read windows phone 8.x site at 
https://msdn.microsoft.com/en-us/library/windows/apps/hh464936.aspx, it is said 
that "removableStorage" capability has to be added to AppManifest.xml to get 
permission to storage system. But when I did it, it did not work.

By your answer, do you mean that right now once can not access the storage at 
the present moment in WP8.1 ? Please advice.

> LocalFileSystem.PERSISTENT does not detect file system storage
> --
>
> Key: CB-10515
> URL: https://issues.apache.org/jira/browse/CB-10515
> Project: Apache Cordova
>  Issue Type: New Feature
>Reporter: Sam Deepak
>  Labels: triaged, windows
>
> The call to window.requestFileSystem(LocalFileSystem.PERSISTENT, 0, 
> function() {}); does not detect the root storage location in windows phone 
> 8.x. Rather it points to private data directory,even after adding   the 
> capability for accessing the local file system (removableStorage) in 
> AppManifest.xml.
> Basically window.requestFileSystem(LocalFileSystem.PERSISTENT, 
> 0,function(fileSystem) {}, function(error){}) gives me only "ms-appx://local" 
> path which is actually the private data directory for an app in windows 
> phone. I want to access the root directory of the file system because I am 
> letting the user to store app specific files anywhere in the phone. (It works 
> in Android without specifying anything)
> Basically the above LocalFileSystem.PERSISTENT should not point to private 
> data directory, rather it should be the root directory of the local file 
> system.



--
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-10477) Error in Android build CLI 5.1.1

[Antonio Zaaa (JIRA)]

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

Antonio Zaaa commented on CB-10477:
---

I use Intel XDK CLI 5.1.1. The plugin version is the latest one on the git: 
1.2.2.
Do you consider this is an Intel bug or a plugin bug? Consider IntelXDK build 
my app on theirs servers, in PaaS, so maybe they should manage something on 
theirs side. In this latter case, I have to open an issue on the XDK official 
forum.


> Error in Android build CLI 5.1.1
> 
>
> Key: CB-10477
> URL: https://issues.apache.org/jira/browse/CB-10477
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Android, CLI
>Reporter: Antonio Zaaa
>  Labels: triaged, wfc
>
> When build, I got this error:
> location: package org.apache.cordova
> [javac] 
> .../builds/build.5G6xNk.tmp/appanalyzer/platforms/android/src/org/apache/cordova/inappbrowser/InAppBrowser.java:917:
>  error: cannot find symbol
> [javac] if (pluginManager != null && 
> pluginManager.onReceivedHttpAuthRequest(webView, new 
> CordovaHttpAuthHandler(handler), host, realm)) {
> [javac]   
> ^
> [javac]   symbol:   class CordovaHttpAuthHandler
> [javac]   location: class InAppBrowser.InAppBrowserClient
> [javac] Note: Some input files use or override a deprecated API.
> [javac] Note: Recompile with -Xlint:deprecation for details.
> [javac] Note: Some input files use unchecked or unsafe operations.
> [javac] Note: Recompile with -Xlint:unchecked for details.
> [javac] 2 errors
> BUILD FAILED
> .../android-sdk-linux/tools/ant/build.xml:720: The following error occurred 
> while executing this line:
> .../android-sdk-linux/tools/ant/build.xml:734: Compile failed; see the 
> compiler error output for details.
> Total time: 11 seconds
> .../builds/build.5G6xNk.tmp/appanalyzer/platforms/android/cordova/node_modules/q/q.js:126
> throw e;
>   ^
> Error code 1 for command: ant with args: 
> release,-f,.../builds/build.5G6xNk.tmp/appanalyzer/platforms/android/build.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] [Commented] (CB-10515) LocalFileSystem.PERSISTENT does not detect file system storage

[Sergey Shakhnazarov (JIRA)]

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

Sergey Shakhnazarov commented on CB-10515:
--

[~theodarsamuel], just to clarify - do you use {{wp8}} or {{windows}} platform?
What do you mean by "sideloading"?

{{cordova.file.externalRootDirectory}} is supported for Android and BB10 for 
the moment according to the docs.

> LocalFileSystem.PERSISTENT does not detect file system storage
> --
>
> Key: CB-10515
> URL: https://issues.apache.org/jira/browse/CB-10515
> Project: Apache Cordova
>  Issue Type: New Feature
>Reporter: Sam Deepak
>  Labels: triaged, windows
>
> The call to window.requestFileSystem(LocalFileSystem.PERSISTENT, 0, 
> function() {}); does not detect the root storage location in windows phone 
> 8.x. Rather it points to private data directory,even after adding   the 
> capability for accessing the local file system (removableStorage) in 
> AppManifest.xml.
> Basically window.requestFileSystem(LocalFileSystem.PERSISTENT, 
> 0,function(fileSystem) {}, function(error){}) gives me only "ms-appx://local" 
> path which is actually the private data directory for an app in windows 
> phone. I want to access the root directory of the file system because I am 
> letting the user to store app specific files anywhere in the phone. (It works 
> in Android without specifying anything)
> Basically the above LocalFileSystem.PERSISTENT should not point to private 
> data directory, rather it should be the root directory of the local file 
> system.



--
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-10515) LocalFileSystem.PERSISTENT does not detect file system storage

[Sam Deepak (JIRA)]

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

Sam Deepak commented on CB-10515:
-

Hi Sergey, I use Intel XDK to create build packages. It creates both .appx and 
.appxupload files. You can use .appx files for testing in emulator or testing 
in actual device without publishing and .appxuload for publishing in app store. 
When you use .appx or xap files, it is called side loading.

And I use WP8.1 build to create these files, NOT Windows.

> LocalFileSystem.PERSISTENT does not detect file system storage
> --
>
> Key: CB-10515
> URL: https://issues.apache.org/jira/browse/CB-10515
> Project: Apache Cordova
>  Issue Type: New Feature
>Reporter: Sam Deepak
>  Labels: triaged, windows
>
> The call to window.requestFileSystem(LocalFileSystem.PERSISTENT, 0, 
> function() {}); does not detect the root storage location in windows phone 
> 8.x. Rather it points to private data directory,even after adding   the 
> capability for accessing the local file system (removableStorage) in 
> AppManifest.xml.
> Basically window.requestFileSystem(LocalFileSystem.PERSISTENT, 
> 0,function(fileSystem) {}, function(error){}) gives me only "ms-appx://local" 
> path which is actually the private data directory for an app in windows 
> phone. I want to access the root directory of the file system because I am 
> letting the user to store app specific files anywhere in the phone. (It works 
> in Android without specifying anything)
> Basically the above LocalFileSystem.PERSISTENT should not point to private 
> data directory, rather it should be the root directory of the local file 
> system.



--
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-10515) LocalFileSystem.PERSISTENT does not detect file system storage

[Sergey Shakhnazarov (JIRA)]

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

Sergey Shakhnazarov commented on CB-10515:
--

It does not work as it is not yet implemented - and a PR could be sent to the 
repository once someone has a solution for this.

> LocalFileSystem.PERSISTENT does not detect file system storage
> --
>
> Key: CB-10515
> URL: https://issues.apache.org/jira/browse/CB-10515
> Project: Apache Cordova
>  Issue Type: New Feature
>Reporter: Sam Deepak
>  Labels: triaged, windows
>
> The call to window.requestFileSystem(LocalFileSystem.PERSISTENT, 0, 
> function() {}); does not detect the root storage location in windows phone 
> 8.x. Rather it points to private data directory,even after adding   the 
> capability for accessing the local file system (removableStorage) in 
> AppManifest.xml.
> Basically window.requestFileSystem(LocalFileSystem.PERSISTENT, 
> 0,function(fileSystem) {}, function(error){}) gives me only "ms-appx://local" 
> path which is actually the private data directory for an app in windows 
> phone. I want to access the root directory of the file system because I am 
> letting the user to store app specific files anywhere in the phone. (It works 
> in Android without specifying anything)
> Basically the above LocalFileSystem.PERSISTENT should not point to private 
> data directory, rather it should be the root directory of the local file 
> system.



--
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-10515) LocalFileSystem.PERSISTENT does not detect file system storage

[Sam Deepak (JIRA)]

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

Sam Deepak commented on CB-10515:
-

Alright Sergey. Thanks. Please also update here as a comment and I will be 
notified.

> LocalFileSystem.PERSISTENT does not detect file system storage
> --
>
> Key: CB-10515
> URL: https://issues.apache.org/jira/browse/CB-10515
> Project: Apache Cordova
>  Issue Type: New Feature
>Reporter: Sam Deepak
>  Labels: triaged, windows
>
> The call to window.requestFileSystem(LocalFileSystem.PERSISTENT, 0, 
> function() {}); does not detect the root storage location in windows phone 
> 8.x. Rather it points to private data directory,even after adding   the 
> capability for accessing the local file system (removableStorage) in 
> AppManifest.xml.
> Basically window.requestFileSystem(LocalFileSystem.PERSISTENT, 
> 0,function(fileSystem) {}, function(error){}) gives me only "ms-appx://local" 
> path which is actually the private data directory for an app in windows 
> phone. I want to access the root directory of the file system because I am 
> letting the user to store app specific files anywhere in the phone. (It works 
> in Android without specifying anything)
> Basically the above LocalFileSystem.PERSISTENT should not point to private 
> data directory, rather it should be the root directory of the local file 
> system.



--
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-10476) cordova-plugin-media 2.1.0 dos not fire mediaSuccess

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-10476:
-

Github user hdsnet commented on the pull request:


https://github.com/apache/cordova-plugin-media/pull/78#issuecomment-179223182
  
Works like charm. Please merge asap.


> cordova-plugin-media 2.1.0 dos not fire mediaSuccess
> 
>
> Key: CB-10476
> URL: https://issues.apache.org/jira/browse/CB-10476
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Plugin Media
> Environment: cordova-plugin-file 4.1.0 "File"
> cordova-plugin-media 2.1.0 "Media"
> Installed platforms: android 5.1.0
>Reporter: jose nuno neto
>  Labels: android
>
> I am runnig a simple test from the code on github, the sound file plays okbut 
> the success function does not get fired.
> Code below:
> var my_media = new Media("file:///android_asset/www/hello2.wav",
> // success callback
> function () {
> console.log("playAudio():Audio Success");
> },
> // error callback
> function (err) {
> console.log("playAudio():Audio Error: " + err);
> },
> function () {
> console.log("playAudio():Audio Status");
> } 
>  
> );
> // Play audio
> my_media.play();



--
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-10512) Nothing happens when trying to move a file

[Eric dos Reis Santos (JIRA)]

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

Eric dos Reis Santos commented on CB-10512:
---

I gave an alert to display the fileSystem object in the callback function in 
ng-cordova.js, and this object don't contains the getFile() function:

$window.resolveLocalFileSystemURL(path, function (fileSystem) {
alert("fileSystem " + JSON.stringify(fileSystem));

> Nothing happens when trying to move a file
> --
>
> Key: CB-10512
> URL: https://issues.apache.org/jira/browse/CB-10512
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Android, CordovaJS
> Environment: Android
>Reporter: Eric dos Reis Santos
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
>
> I was to able to create a directory, and I'm trying to move a image stored in 
> "temp files" directory to my directory created in file system, but nothing 
> happens, the promise doesn't return error and success, absolutely nothing 
> happens.
> The cordova file plugin was added in my app.
> I debugged the app in my device with Android Studio, and I saw an error in 
> log cat: "Error in Success callbackId: File285873816 : TypeError: 
> fileSystem.getFile is not a function" in source: 
> file:///android_asset/www/cordova.js
> Someone can help me?



--
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-10517) Inappbrowser crashes browserified app on Android

[Alexander Sorokin (JIRA)]

Alexander Sorokin created CB-10517:
--

 Summary: Inappbrowser crashes browserified app on Android
 Key: CB-10517
 URL: https://issues.apache.org/jira/browse/CB-10517
 Project: Apache Cordova
  Issue Type: Bug
  Components: Plugin InAppBrowser
Affects Versions: Master
Reporter: Alexander Sorokin


* create mobilespec app with inappbrowser plugin
* run it with "cordova run android --browserify"
* go to manual inappbrowser tests
* click one of the buttons with "target=Random"
* inappbrowser loads the page successfully
* clik one of the buttons with "target=Random" again
* the app crashes



--
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-10476) cordova-plugin-media 2.1.0 dos not fire mediaSuccess

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-10476:
-

Github user hdsnet commented on the pull request:


https://github.com/apache/cordova-plugin-media/pull/78#issuecomment-179215307
  
Hi,
It still doesn't seem to work.


> cordova-plugin-media 2.1.0 dos not fire mediaSuccess
> 
>
> Key: CB-10476
> URL: https://issues.apache.org/jira/browse/CB-10476
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Plugin Media
> Environment: cordova-plugin-file 4.1.0 "File"
> cordova-plugin-media 2.1.0 "Media"
> Installed platforms: android 5.1.0
>Reporter: jose nuno neto
>  Labels: android
>
> I am runnig a simple test from the code on github, the sound file plays okbut 
> the success function does not get fired.
> Code below:
> var my_media = new Media("file:///android_asset/www/hello2.wav",
> // success callback
> function () {
> console.log("playAudio():Audio Success");
> },
> // error callback
> function (err) {
> console.log("playAudio():Audio Error: " + err);
> },
> function () {
> console.log("playAudio():Audio Status");
> } 
>  
> );
> // Play audio
> my_media.play();



--
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-8292) notification.prompt has invisible white text for user input

[Jackson Pauls (JIRA)]

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

Jackson Pauls commented on CB-8292:
---

I'm also getting white text on a white background with 
navigator.notification.prompt - but with the latest release: 
cordova-plugin-dialogs 1.2.0 on Cordova Android 5.1.0.

> notification.prompt has invisible white text for user input
> ---
>
> Key: CB-8292
> URL: https://issues.apache.org/jira/browse/CB-8292
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Plugin Dialogs
>Affects Versions: 3.5.0
> Environment: build.phonegap.com, with core plugins from source= 
> "plugins.cordova.io" .
> (Sorry I can't verify if this is just a build.phonegap.com problem or an 
> issue with the plugin, but from the code diffs, seems it is the plugin.)
>Reporter: Steve Bohrer
>Priority: Minor
>
> In 0.2.9 of the core dialogs plugin, the change note says: "When you don't 
> specify a theme the platform defaults back to gingerbread styling. By 
> applying the device default theme it will change it to the new (and much 
> nicer looking) styles on newer devices."
> However, the EditText item is not changed, so user-entered text is still in 
> the gingerbread styling, which results in white text on the new white dialog 
> background. This issue persists through dialogs plugin 0.2.11. (Note that the 
> default prompt string is drawn with the proper font, but when the user enters 
> text, it is white.)
> From the diffs at  
> https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-dialogs.git;a=commitdiff;h=90ad94c3309619b9e629ccf416d1a787df7c3d0e
> It is clear that AlertDialog.Builder is called with the new default style, 
> but the EditText item is unchanged.
> Here's the excerpt of the relevant diffs:
> @@ -270,7 +270,7 @@ public class Notification extends CordovaPlugin {
>  public void run() {
>  final EditText promptInput =  new 
> EditText(cordova.getActivity());
>  promptInput.setHint(defaultText);
> -AlertDialog.Builder dlg = new 
> AlertDialog.Builder(cordova.getActivity());
> +AlertDialog.Builder dlg = new 
> AlertDialog.Builder(cordova.getActivity(), 
> AlertDialog.THEME_DEVICE_DEFAULT_LIGHT);



--
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-10461) 'cordova platform ls' should list the versions of platforms pinned

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-10461:
-

Github user riknoll commented on the pull request:

https://github.com/apache/cordova-lib/pull/376#issuecomment-179500082
  
That's more like what we do for plugins (`cordova plugin ls`)


> 'cordova platform ls' should list the versions of platforms pinned
> --
>
> Key: CB-10461
> URL: https://issues.apache.org/jira/browse/CB-10461
> Project: Apache Cordova
>  Issue Type: Improvement
>  Components: CordovaLib
>Affects Versions: 6.0.0
>Reporter: Nikhil Khandelwal
>Assignee: Sarangan Rajamanickam
>Priority: Minor
>
> {Code}
> λ cordova platform ls
> Installed platforms: android 5.1.0
> Available platforms: amazon-fireos, blackberry10, browser, firefoxos, webos, 
> windows, windows8, wp8
> {Code}
> It would be great to list the pinned versions for all available platforms 
> here.



--
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-10461) 'cordova platform ls' should list the versions of platforms pinned

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-10461:
-

Github user sarangan12 commented on the pull request:

https://github.com/apache/cordova-lib/pull/376#issuecomment-179505519
  
@TimBarham @nikhilkh Agreed. Added formatting changes. Now the display will 
be like:
Installed platforms:
android 5.0.0
blackberry10 3.8.0-dev
browser 4.0.0
firefoxos 3.6.3
windows 4.2.0
wp8 (deprecated)
Available platforms:
amazon-fireos ~3.6.3 (deprecated)
webos ~3.7.0
windows8 ~4.2.0


> 'cordova platform ls' should list the versions of platforms pinned
> --
>
> Key: CB-10461
> URL: https://issues.apache.org/jira/browse/CB-10461
> Project: Apache Cordova
>  Issue Type: Improvement
>  Components: CordovaLib
>Affects Versions: 6.0.0
>Reporter: Nikhil Khandelwal
>Assignee: Sarangan Rajamanickam
>Priority: Minor
>
> {Code}
> λ cordova platform ls
> Installed platforms: android 5.1.0
> Available platforms: amazon-fireos, blackberry10, browser, firefoxos, webos, 
> windows, windows8, wp8
> {Code}
> It would be great to list the pinned versions for all available platforms 
> here.



--
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-10498) Resume event not guaranteed to be received with plugin result

[Richard B Knoll (JIRA)]

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

Richard B Knoll commented on CB-10498:
--

[~dpolivy] PR is [here|https://github.com/apache/cordova-android/pull/257], let 
me know how it works for you!

> Resume event not guaranteed to be received with plugin result
> -
>
> Key: CB-10498
> URL: https://issues.apache.org/jira/browse/CB-10498
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Android
>Reporter: Richard B Knoll
>Assignee: Richard B Knoll
>  Labels: android, triaged
>
> The save/restore API delivers results in the resume event. The issue is, it 
> is possible to "miss" the resume event if you don't add an event handler in 
> time.



--
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-10526) Improve 'iOS Guide' documentation

[Omar Mefire (JIRA)]

Omar Mefire created CB-10526:


 Summary: Improve 'iOS Guide' documentation
 Key: CB-10526
 URL: https://issues.apache.org/jira/browse/CB-10526
 Project: Apache Cordova
  Issue Type: Improvement
Reporter: Omar Mefire






--
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-10461) 'cordova platform ls' should list the versions of platforms pinned

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-10461:
-

Github user TimBarham commented on the pull request:

https://github.com/apache/cordova-lib/pull/376#issuecomment-179503770
  
Yeah, and in fact, for consistency maybe "installed platforms" should also 
be separated by line breaks rather than commas:

```
Installed platforms:
  android 5.1.0
  browser 4.1.0-dev
Available platforms:
  amazon-fireos ~3.6.3 (deprecated)
  blackberry10 ~3.8.0
  firefoxos ~3.6.3
  webos ~3.7.0
  windows ~4.3.0
  windows8 ~4.3.0
  wp8 ~3.8.2 (deprecated)
```



> 'cordova platform ls' should list the versions of platforms pinned
> --
>
> Key: CB-10461
> URL: https://issues.apache.org/jira/browse/CB-10461
> Project: Apache Cordova
>  Issue Type: Improvement
>  Components: CordovaLib
>Affects Versions: 6.0.0
>Reporter: Nikhil Khandelwal
>Assignee: Sarangan Rajamanickam
>Priority: Minor
>
> {Code}
> λ cordova platform ls
> Installed platforms: android 5.1.0
> Available platforms: amazon-fireos, blackberry10, browser, firefoxos, webos, 
> windows, windows8, wp8
> {Code}
> It would be great to list the pinned versions for all available platforms 
> here.



--
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-9366) Log error.stack when a call to a plugin throws an exception

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-9366:


Github user jimmont commented on the pull request:

https://github.com/apache/cordova-js/pull/118#issuecomment-179440047
  
[This 
try-catch](https://github.com/apache/cordova-js/blob/master/src/cordova.js#L228)
 for callbacks is a real pain. Having access to errors as they occur is highly 
desirable. And there appears to be [a logic error 
here](https://github.com/apache/cordova-js/blob/master/src/cordova.js#L223) 
where callbacks are never deleted if they throw an error. Isn't managing errors 
a responsibility outside of `self.cordova`? Just started looking at this 
javascript after a *lot* of problematic worker debugging.


> Log error.stack when a call to a plugin throws an exception
> ---
>
> Key: CB-9366
> URL: https://issues.apache.org/jira/browse/CB-9366
> Project: Apache Cordova
>  Issue Type: Improvement
>  Components: CordovaJS
>Affects Versions: Master
>Reporter: Nikhil Khandelwal
>Assignee: Nikhil Khandelwal
>Priority: Minor
>
> This can help in isolating the cause of the error.



--
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-10525) Review all config.xml preferences to their effect in OS X

[Tobias Bocanegra (JIRA)]

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

Tobias Bocanegra commented on CB-10525:
---

from https://cordova.apache.org/docs/en/latest/config_ref/index.html:

- Fullscreen (see impact on OSX Specific 'WindowSize')
- DisallowOverscroll (not supported on osx, docu ok)
- BackgroundColor (not supported on osx, docu ok)
- HideKeyboardFormAccessoryBar (not supported on osx. docu ok)
- Orientation (not supported on osx, docu ok)

todo:
- clarify {{Fullscreen}} in code and documenation
- replace hardcoded strings in code by constants and add docu
- update documentation
- clean up default config.xml 
https://github.com/apache/cordova-osx/blob/master/bin/templates/project/__PROJECT_NAME__/config.xml

> Review all config.xml preferences to their effect in OS X
> -
>
> Key: CB-10525
> URL: https://issues.apache.org/jira/browse/CB-10525
> Project: Apache Cordova
>  Issue Type: Improvement
>  Components: OSX
>Affects Versions: Master
>Reporter: Tobias Bocanegra
>Assignee: Tobias Bocanegra
>
> The default config.xml provides lot of preferences that are not supported or 
> recognized on OSX. This needs to be reviews and documented.



--
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-10498) Resume event not guaranteed to be received with plugin result

[Dan Polivy (JIRA)]

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

Dan Polivy commented on CB-10498:
-

Sounds like a good solution. If you have a PR/build, I'm happy to give it a try.

> Resume event not guaranteed to be received with plugin result
> -
>
> Key: CB-10498
> URL: https://issues.apache.org/jira/browse/CB-10498
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Android
>Reporter: Richard B Knoll
>Assignee: Richard B Knoll
>  Labels: android, triaged
>
> The save/restore API delivers results in the resume event. The issue is, it 
> is possible to "miss" the resume event if you don't add an event handler in 
> time.



--
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-10526) Improve 'iOS Guide' documentation

[Omar Mefire (JIRA)]

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

Omar Mefire reassigned CB-10526:


Assignee: Omar Mefire

> Improve 'iOS Guide' documentation
> -
>
> Key: CB-10526
> URL: https://issues.apache.org/jira/browse/CB-10526
> Project: Apache Cordova
>  Issue Type: Improvement
>  Components: Docs, iOS
>Reporter: Omar Mefire
>Assignee: Omar Mefire
>




--
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-10525) Review all config.xml preferences to their effect in OS X

[Tobias Bocanegra (JIRA)]

Tobias Bocanegra created CB-10525:
-

 Summary: Review all config.xml preferences to their effect in OS X
 Key: CB-10525
 URL: https://issues.apache.org/jira/browse/CB-10525
 Project: Apache Cordova
  Issue Type: Improvement
  Components: OSX
Affects Versions: Master
Reporter: Tobias Bocanegra
Assignee: Tobias Bocanegra


The default config.xml provides lot of preferences that are not supported or 
recognized on OSX. This needs to be reviews and documented.



--
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-10526) Improve 'iOS Guide' documentation

[Omar Mefire (JIRA)]

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

Omar Mefire updated CB-10526:
-
Component/s: iOS
 Docs

> Improve 'iOS Guide' documentation
> -
>
> Key: CB-10526
> URL: https://issues.apache.org/jira/browse/CB-10526
> Project: Apache Cordova
>  Issue Type: Improvement
>  Components: Docs, iOS
>Reporter: Omar Mefire
>




--
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-10461) 'cordova platform ls' should list the versions of platforms pinned

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-10461:
-

Github user TimBarham commented on the pull request:

https://github.com/apache/cordova-lib/pull/376#issuecomment-179498720
  
I like the idea, but find the list is starting to get a bit confusing (to 
see the actual platform names. We need to make sure the platform names a very 
easy to see. On option that might help would be to switch to using line breaks 
instead of commas, something like:

```
Installed platforms: browser 4.1.0-dev
Available platforms:
  amazon-fireos ~3.6.3 (deprecated)
  android ~5.1.0
  blackberry10 ~3.8.0
  firefoxos ~3.6.3
  webos ~3.7.0
  windows ~4.3.0
  windows8 ~4.3.0
  wp8 ~3.8.2 (deprecated)
```



> 'cordova platform ls' should list the versions of platforms pinned
> --
>
> Key: CB-10461
> URL: https://issues.apache.org/jira/browse/CB-10461
> Project: Apache Cordova
>  Issue Type: Improvement
>  Components: CordovaLib
>Affects Versions: 6.0.0
>Reporter: Nikhil Khandelwal
>Assignee: Sarangan Rajamanickam
>Priority: Minor
>
> {Code}
> λ cordova platform ls
> Installed platforms: android 5.1.0
> Available platforms: amazon-fireos, blackberry10, browser, firefoxos, webos, 
> windows, windows8, wp8
> {Code}
> It would be great to list the pinned versions for all available platforms 
> here.



--
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-10488) MediaFile.getFormatData does not work with localURL; changed with fullPath

[Tanase Butcaru (JIRA)]

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

Tanase Butcaru commented on CB-10488:
-

Fixed with this PR: 
https://github.com/apache/cordova-plugin-media-capture/pull/50

> MediaFile.getFormatData does not work with localURL; changed with fullPath
> --
>
> Key: CB-10488
> URL: https://issues.apache.org/jira/browse/CB-10488
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Plugin Media Capture
> Environment: Android, iOS
>Reporter: Tanase Butcaru
>  Labels: Android, iOS, media-capture, triaged
>
> _MediaFile.getFormatData_ result data was empty (filled with default "0" 
> values) for all types of capture: image, video & audio.
> Problem encountered on Android & iOS.
> I solved this by changing the url passed to native code from _localURL_ to 
> _fullPath_.
> Tested with two different Android phones (5.1 & 4.4) & one iPhone 5 (iOS 9).
> The fix works!



--
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-10489) MediaFile.getFormatData for audio recordings does not work for *.amr files

[Tanase Butcaru (JIRA)]

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

Tanase Butcaru commented on CB-10489:
-

Fixed with this PR: 
https://github.com/apache/cordova-plugin-media-capture/pull/50

> MediaFile.getFormatData for audio recordings does not work for *.amr files
> --
>
> Key: CB-10489
> URL: https://issues.apache.org/jira/browse/CB-10489
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Plugin Media Capture
> Environment: Android 4.4, Android 5.1
>Reporter: Tanase Butcaru
>  Labels: Android
>
> After resolving this bug (https://issues.apache.org/jira/browse/CB-10488) I 
> still could find a case where this feature does not work properly.
> iOS behaves as it should, only on Android the issue manifests.
> On my older device with Android 4.4, the sound recorder app has the option to 
> change the file type and if I set .wav instead of .amr, the recorded file is 
> read & its data is returned as it should (no "0" value for duration, for eg.).
> So the problem might be the .amr files.
> i tried to set the MIME type before launching the sound recorder app:
> {code}
> intent.putExtra(android.provider.MediaStore.Audio.Media.ENTRY_CONTENT_TYPE, 
> "audio/aac");
> {code}
> ... but with no success. Tried with _MIME_TYPE_ and _CONTENT_TYPE_ too.



--
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-10498) Resume event not guaranteed to be received with plugin result

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-10498:
-

GitHub user riknoll opened a pull request:

https://github.com/apache/cordova-android/pull/257

CB-10498: Resume event should be sticky if it has a plugin result

Changes the resume event behavior as follows:

1. When the app starts and there is no plugin result to be delivered, the 
**resume event will not fire** (same as current behavior)
2. When the app is left and then resumed (e.g. press the home button and 
then return to the app), the **resume event will fire but will not be sticky** 
(same as current behavior)
3. When the app is recreated after a plugin Activity finishes (i.e. the 
event payload contains a pending result), the **resume event will fire and will 
be sticky**

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/MSOpenTech/cordova-android CB-10498rebase

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cordova-android/pull/257.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #257


commit d7e111fb710c63c32ff21c15b6cb5c67ed6280cc
Author: riknoll 
Date:   2016-02-03T21:12:21Z

CB-10498: Resume event should be sticky if it has a plugin result




> Resume event not guaranteed to be received with plugin result
> -
>
> Key: CB-10498
> URL: https://issues.apache.org/jira/browse/CB-10498
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Android
>Reporter: Richard B Knoll
>Assignee: Richard B Knoll
>  Labels: android, triaged
>
> The save/restore API delivers results in the resume event. The issue is, it 
> is possible to "miss" the resume event if you don't add an event handler in 
> time.



--
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-10465) cordova.raw.emulate fires a cordova.raw.prepare with incorrect arguments

[Vladimir Kotikov (JIRA)]

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

Vladimir Kotikov updated CB-10465:
--
Labels: cordova-lib triaged  (was: cordova-lib regression triaged)

> cordova.raw.emulate fires a cordova.raw.prepare with incorrect arguments
> 
>
> Key: CB-10465
> URL: https://issues.apache.org/jira/browse/CB-10465
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: CordovaLib
>Affects Versions: 5.4.1
>Reporter: Manuel Martiarena
>Assignee: Vladimir Kotikov
>  Labels: cordova-lib, triaged
>
> All cordova.raw command now need to be called with arguments like this ticket 
> expains: https://issues.apache.org/jira/browse/CB-9987.
> Unfortunately the raw emulate command executes the raw prepare with the wrong 
> structure of arguments, with the side effect that if you want to emulate only 
> iOS, the other configured projects will also be add/checked/prepared.
> emulate.js calls it like this: 
> return require('./cordova').raw.prepare(options.platforms);
> https://github.com/apache/cordova-lib/blob/master/cordova-lib/src/cordova/emulate.js
>  line 36
> But the argument should be an object with a key named platforms. like so:
> return require('./cordova').raw.prepare({platforms: options.platforms}); 



--
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-10465) cordova.raw.emulate fires a cordova.raw.prepare with incorrect arguments

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-10465:
-

Github user vladimir-kotikov commented on the pull request:

https://github.com/apache/cordova-lib/pull/374#issuecomment-179262628
  
@sgrebnov, PTAL


> cordova.raw.emulate fires a cordova.raw.prepare with incorrect arguments
> 
>
> Key: CB-10465
> URL: https://issues.apache.org/jira/browse/CB-10465
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: CordovaLib
>Affects Versions: 5.4.1
>Reporter: Manuel Martiarena
>Assignee: Vladimir Kotikov
>  Labels: cordova-lib, triaged
>
> All cordova.raw command now need to be called with arguments like this ticket 
> expains: https://issues.apache.org/jira/browse/CB-9987.
> Unfortunately the raw emulate command executes the raw prepare with the wrong 
> structure of arguments, with the side effect that if you want to emulate only 
> iOS, the other configured projects will also be add/checked/prepared.
> emulate.js calls it like this: 
> return require('./cordova').raw.prepare(options.platforms);
> https://github.com/apache/cordova-lib/blob/master/cordova-lib/src/cordova/emulate.js
>  line 36
> But the argument should be an object with a key named platforms. like so:
> return require('./cordova').raw.prepare({platforms: options.platforms}); 



--
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-10465) cordova.raw.emulate fires a cordova.raw.prepare with incorrect arguments

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on CB-10465:
--

Commit b1bdd55690165ea75e0217c9ebf78b6e41257aad in cordova-lib's branch 
refs/heads/master from [~vladimir.kotikov]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-lib.git;h=b1bdd55 ]

CB-10465 Pass correct options to prepare from compile


> cordova.raw.emulate fires a cordova.raw.prepare with incorrect arguments
> 
>
> Key: CB-10465
> URL: https://issues.apache.org/jira/browse/CB-10465
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: CordovaLib
>Affects Versions: 5.4.1
>Reporter: Manuel Martiarena
>Assignee: Vladimir Kotikov
>  Labels: cordova-lib, reproduced, triaged
>
> All cordova.raw command now need to be called with arguments like this ticket 
> expains: https://issues.apache.org/jira/browse/CB-9987.
> Unfortunately the raw emulate command executes the raw prepare with the wrong 
> structure of arguments, with the side effect that if you want to emulate only 
> iOS, the other configured projects will also be add/checked/prepared.
> emulate.js calls it like this: 
> return require('./cordova').raw.prepare(options.platforms);
> https://github.com/apache/cordova-lib/blob/master/cordova-lib/src/cordova/emulate.js
>  line 36
> But the argument should be an object with a key named platforms. like so:
> return require('./cordova').raw.prepare({platforms: options.platforms}); 



--
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-10176) Cordova-common should contain a default logger implementation.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-10176:
-

GitHub user vladimir-kotikov opened a pull request:

https://github.com/apache/cordova-lib/pull/375

CB-10176 Adds CordovaLogger class, based on logger module from cordova-cli

This is an implementation for 
[CB-10176](https://issues.apache.org/jira/browse/CB-10176)
This PR adds a standard logger implementation, that could be reused by cli 
and platforms.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/MSOpenTech/cordova-lib CB-10176

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cordova-lib/pull/375.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #375


commit 1fd2dd857dca026483d869660e79784f392921d0
Author: Vladimir Kotikov 
Date:   2016-02-03T14:47:24Z

CB-10176 Adds CordovaLogger class, based on logger module from cordova-cli




> Cordova-common should contain a default logger implementation.
> --
>
> Key: CB-10176
> URL: https://issues.apache.org/jira/browse/CB-10176
> Project: Apache Cordova
>  Issue Type: Improvement
>  Components: CordovaCommon
>Affects Versions: 1.0.0
>Reporter: Vladimir Kotikov
>Assignee: Vladimir Kotikov
>  Labels: triaged
> Fix For: 1.1.0
>
>
> Currently ConsoleLogger, which is used for logging, when platform is not 
> supplied with EventEmitter, is duplicated across each platform.
> The same logic is already lives in CLI.
> To reduce code duplication it should be moved to 'common'.



--
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-10519) Using cordova.raw API outside of cordova project results in uncaught exception instead or promise rejection

[Vladimir Kotikov (JIRA)]

Vladimir Kotikov created CB-10519:
-

 Summary: Using cordova.raw API outside of cordova project results 
in uncaught exception instead or promise rejection
 Key: CB-10519
 URL: https://issues.apache.org/jira/browse/CB-10519
 Project: Apache Cordova
  Issue Type: Bug
  Components: CordovaLib
Affects Versions: 6.0.0
Reporter: Vladimir Kotikov


When trying to {{cordova.raw.platfom('add', ...)}} outside of cordova project 
the following error message logged to console:

> Error: Current working directory is not a Cordova-based project.

However, the error callback for {{cordova.raw.platfom('add', ...)}} isn't 
called at all.



--
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-10430) cordova-common events don't reach platform's code

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-10430:
-

Github user vladimir-kotikov commented on the pull request:

https://github.com/apache/cordova-lib/pull/370#issuecomment-179297923
  
No, this is not a part of API. However, this might be critical for some 
external tools to get this information.

@nikhilkh, what do you think about this?


> cordova-common events don't reach platform's code
> -
>
> Key: CB-10430
> URL: https://issues.apache.org/jira/browse/CB-10430
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: CordovaCommon
>Affects Versions: 1.0.0
>Reporter: Vladimir Kotikov
>Assignee: Vladimir Kotikov
>  Labels: common, logging, triaged
> Fix For: 1.1.0
>
>
> I was looking to get verbose output of cordova-windows to see what external 
> commands it is running on my behalf. I was hoping the APIfication with use of 
> superspawn will help here. However, that does not seem to be the case – even 
> though the code seems to suggest that.
> {code}
> exports.spawn = function(cmd, args, opts) {
> ..
> events.emit(opts.printCommand ? 'log' : 'verbose', 'Running command: ' + 
> maybeQuote(cmd) + ' ' + args.map(maybeQuote).join(' '));
> ..
> }
> {code}
> {noformat}
> λ cordova build windows --verbose -- --appx=uap --verbose
> Executing "before_build"  hook for all plugins.
> Executing "before_prepare"  hook for all plugins.
> Searching PlatformJson files for differences between project vs. platform 
> installed plugins
> No differences found between project and windows platform. Continuing...
> Generating config.xml from defaults for platform "windows"
> Updated project successfully
> Executing "after_prepare"  hook for all plugins.
> Executing "before_compile"  hook for all plugins.
> Searching for available MSBuild versions...
> Found MSBuild v14.0 at C:\Program Files (x86)\MSBuild\14.0\bin
> Found MSBuild v12.0 at C:\Program Files (x86)\MSBuild\12.0\bin\amd64\
> Found MSBuild v4.0 at C:\Windows\Microsoft.NET\Framework64\v4.0.30319\
> Building project: d:\apps\app\platforms\windows\CordovaApp.Windows10.jsproj
> Configuration : debug
> Platform  : anycpu
> C:\Program Files 
> (x86)\MSBuild\Microsoft\NuGet\Microsoft.NuGet.targets(181,5): error : 
> Couldn't find the required  information in the lock file. Make sure you have 
> .NETCore,Version=v5.0/win10-anycpu mentioned in your targets. [ 
> d:\apps\app\platforms\windows\CordovaApp.Windows10.jsproj]
> ERROR building one of the platforms: Error: C:\Program Files 
> (x86)\MSBuild\14.0\bin\msbuild.exe: Command failed with exit code 1
> You may not have the required environment or OS to build this project
> Error: C:\Program Files (x86)\MSBuild\14.0\bin\msbuild.exe: Command failed 
> with exit code 1
> at ChildProcess.whenDone 
> (d:\apps\app\platforms\windows\cordova\node_modules\cordova-common\src\superspawn.js:139:23)
> at emitTwo (events.js:87:13)
> at ChildProcess.emit (events.js:172:7)
> at maybeClose (internal/child_process.js:817:16)
> at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
> {noformat} 
> As you can see there is no “Running command …”



--
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-10465) cordova.raw.emulate fires a cordova.raw.prepare with incorrect arguments

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-10465:
-

GitHub user vladimir-kotikov opened a pull request:

https://github.com/apache/cordova-lib/pull/374

CB-10465 Pass correct options to prepare from compile

This fixes incorrect behaviour of `cordova emulate` command, which results 
in restoring all saved platforms even when only particular platform specified.

See [CB-10465](https://issues.apache.org/jira/browse/CB-10465) for details

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/MSOpenTech/cordova-lib CB-10465

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cordova-lib/pull/374.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #374


commit ff89da1de181f870c2461b1502d207a668c9b648
Author: Vladimir Kotikov 
Date:   2016-02-03T13:55:31Z

CB-10465 Pass correct options to prepare from compile




> cordova.raw.emulate fires a cordova.raw.prepare with incorrect arguments
> 
>
> Key: CB-10465
> URL: https://issues.apache.org/jira/browse/CB-10465
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: CordovaLib
>Affects Versions: 5.4.1
>Reporter: Manuel Martiarena
>Assignee: Vladimir Kotikov
>  Labels: cordova-lib, regression, triaged
>
> All cordova.raw command now need to be called with arguments like this ticket 
> expains: https://issues.apache.org/jira/browse/CB-9987.
> Unfortunately the raw emulate command executes the raw prepare with the wrong 
> structure of arguments, with the side effect that if you want to emulate only 
> iOS, the other configured projects will also be add/checked/prepared.
> emulate.js calls it like this: 
> return require('./cordova').raw.prepare(options.platforms);
> https://github.com/apache/cordova-lib/blob/master/cordova-lib/src/cordova/emulate.js
>  line 36
> But the argument should be an object with a key named platforms. like so:
> return require('./cordova').raw.prepare({platforms: options.platforms}); 



--
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-10512) Nothing happens when trying to move a file

[Eric dos Reis Santos (JIRA)]

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

Eric dos Reis Santos commented on CB-10512:
---

It was my mistake, in the function moveFile, I was sending the directory with 
the file name, in the moveFrom parameter in my service. The correct way is set 
only the directory:

$cordovaFile.moveFile(moveFrom, currentFileName, cordova.file.dataDirectory + 
moveTo, newFileName)
  .then(function (success) {
  alert("Yeah Success " + JSON.stringify(success));
  }, function (error) {
  alert("Fucking error " + JSON.stringify(error));
  });

Cordova file could return an invalid directory error.

> Nothing happens when trying to move a file
> --
>
> Key: CB-10512
> URL: https://issues.apache.org/jira/browse/CB-10512
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Android, CordovaJS
> Environment: Android
>Reporter: Eric dos Reis Santos
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
>
> I was to able to create a directory, and I'm trying to move a image stored in 
> "temp files" directory to my directory created in file system, but nothing 
> happens, the promise doesn't return error and success, absolutely nothing 
> happens.
> The cordova file plugin was added in my app.
> I debugged the app in my device with Android Studio, and I saw an error in 
> log cat: "Error in Success callbackId: File285873816 : TypeError: 
> fileSystem.getFile is not a function" in source: 
> file:///android_asset/www/cordova.js
> Someone can help me?



--
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-10465) cordova.raw.emulate fires a cordova.raw.prepare with incorrect arguments

[Vladimir Kotikov (JIRA)]

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

Vladimir Kotikov updated CB-10465:
--
Labels: cordova-lib reproduced triaged  (was: cordova-lib triaged)

> cordova.raw.emulate fires a cordova.raw.prepare with incorrect arguments
> 
>
> Key: CB-10465
> URL: https://issues.apache.org/jira/browse/CB-10465
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: CordovaLib
>Affects Versions: 5.4.1
>Reporter: Manuel Martiarena
>Assignee: Vladimir Kotikov
>  Labels: cordova-lib, reproduced, triaged
>
> All cordova.raw command now need to be called with arguments like this ticket 
> expains: https://issues.apache.org/jira/browse/CB-9987.
> Unfortunately the raw emulate command executes the raw prepare with the wrong 
> structure of arguments, with the side effect that if you want to emulate only 
> iOS, the other configured projects will also be add/checked/prepared.
> emulate.js calls it like this: 
> return require('./cordova').raw.prepare(options.platforms);
> https://github.com/apache/cordova-lib/blob/master/cordova-lib/src/cordova/emulate.js
>  line 36
> But the argument should be an object with a key named platforms. like so:
> return require('./cordova').raw.prepare({platforms: options.platforms}); 



--
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-10463) Windows Appxmanifest caching should use the same mechanism as ConfigChanged uses

[Vladimir Kotikov (JIRA)]

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

Vladimir Kotikov updated CB-10463:
--
Fix Version/s: (was: 1.1.0)

> Windows Appxmanifest caching should use the same mechanism as ConfigChanged 
> uses
> 
>
> Key: CB-10463
> URL: https://issues.apache.org/jira/browse/CB-10463
> Project: Apache Cordova
>  Issue Type: Improvement
>  Components: Windows
>Affects Versions: 4.3.0
>Reporter: Vladimir Kotikov
>Priority: Minor
> Fix For: 4.4.0
>
>
> CB-10394 revealed a problem with Appxmanifest class and its file caching. The 
> problem is that at some moment the same file might be cached twice by 
> different facilities and hence changes, made in one of these places might be 
> ignored.
> There is a temporary solution - [cordova-windows PR 
> #143|https://github.com/apache/cordova-windows/pull/143], which fixes the 
> regression, but we need for more general solution.
> A more general way to resolve this is to reuse the same caching mechanism for 
> Appxmanifests as used by {{ConfigChanges}} module. This should resolve the 
> stale cache issue automatically because the one cache will be used for all.



--
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-10463) Windows Appxmanifest caching should use the same mechanism as ConfigChanged uses

[Vladimir Kotikov (JIRA)]

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

Vladimir Kotikov updated CB-10463:
--
Component/s: (was: CordovaCommon)

> Windows Appxmanifest caching should use the same mechanism as ConfigChanged 
> uses
> 
>
> Key: CB-10463
> URL: https://issues.apache.org/jira/browse/CB-10463
> Project: Apache Cordova
>  Issue Type: Improvement
>  Components: Windows
>Affects Versions: 4.3.0
>Reporter: Vladimir Kotikov
>Priority: Minor
> Fix For: 4.4.0
>
>
> CB-10394 revealed a problem with Appxmanifest class and its file caching. The 
> problem is that at some moment the same file might be cached twice by 
> different facilities and hence changes, made in one of these places might be 
> ignored.
> There is a temporary solution - [cordova-windows PR 
> #143|https://github.com/apache/cordova-windows/pull/143], which fixes the 
> regression, but we need for more general solution.
> A more general way to resolve this is to reuse the same caching mechanism for 
> Appxmanifests as used by {{ConfigChanges}} module. This should resolve the 
> stale cache issue automatically because the one cache will be used for all.



--
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-10465) cordova.raw.emulate fires a cordova.raw.prepare with incorrect arguments

[Vladimir Kotikov (JIRA)]

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

Vladimir Kotikov commented on CB-10465:
---

I can see this issue even with cordova@5.3.3, so this is not related to 
CB-9987. It seems for me that this behaviour has been there from the beginning 
of 'restore' feature (see 
[8a313a0|https://github.com/apache/cordova-lib/commit/8a313a083bb2c4e39d3230ecbe090d7852bf5454],
 notice that {{cordova_util.preProcessOptions}} is now called after platforms 
restore).

> cordova.raw.emulate fires a cordova.raw.prepare with incorrect arguments
> 
>
> Key: CB-10465
> URL: https://issues.apache.org/jira/browse/CB-10465
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: CordovaLib
>Affects Versions: 5.4.1
>Reporter: Manuel Martiarena
>Assignee: Vladimir Kotikov
>  Labels: cordova-lib, regression, triaged
>
> All cordova.raw command now need to be called with arguments like this ticket 
> expains: https://issues.apache.org/jira/browse/CB-9987.
> Unfortunately the raw emulate command executes the raw prepare with the wrong 
> structure of arguments, with the side effect that if you want to emulate only 
> iOS, the other configured projects will also be add/checked/prepared.
> emulate.js calls it like this: 
> return require('./cordova').raw.prepare(options.platforms);
> https://github.com/apache/cordova-lib/blob/master/cordova-lib/src/cordova/emulate.js
>  line 36
> But the argument should be an object with a key named platforms. like so:
> return require('./cordova').raw.prepare({platforms: options.platforms}); 



--
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-10465) cordova.raw.emulate fires a cordova.raw.prepare with incorrect arguments

[Vladimir Kotikov (JIRA)]

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

Vladimir Kotikov edited comment on CB-10465 at 2/3/16 2:07 PM:
---

I can see this issue even with cordova@5.3.3, so this is not related to 
CB-9987. It seems for me that this behaviour was there from the beginning of 
'restore' feature (see 
[8a313a0|https://github.com/apache/cordova-lib/commit/8a313a083bb2c4e39d3230ecbe090d7852bf5454],
 notice that {{cordova_util.preProcessOptions}} is now called after platforms 
restore).


was (Author: vladimir.kotikov):
I can see this issue even with cordova@5.3.3, so this is not related to 
CB-9987. It seems for me that this behaviour has been there from the beginning 
of 'restore' feature (see 
[8a313a0|https://github.com/apache/cordova-lib/commit/8a313a083bb2c4e39d3230ecbe090d7852bf5454],
 notice that {{cordova_util.preProcessOptions}} is now called after platforms 
restore).

> cordova.raw.emulate fires a cordova.raw.prepare with incorrect arguments
> 
>
> Key: CB-10465
> URL: https://issues.apache.org/jira/browse/CB-10465
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: CordovaLib
>Affects Versions: 5.4.1
>Reporter: Manuel Martiarena
>Assignee: Vladimir Kotikov
>  Labels: cordova-lib, regression, triaged
>
> All cordova.raw command now need to be called with arguments like this ticket 
> expains: https://issues.apache.org/jira/browse/CB-9987.
> Unfortunately the raw emulate command executes the raw prepare with the wrong 
> structure of arguments, with the side effect that if you want to emulate only 
> iOS, the other configured projects will also be add/checked/prepared.
> emulate.js calls it like this: 
> return require('./cordova').raw.prepare(options.platforms);
> https://github.com/apache/cordova-lib/blob/master/cordova-lib/src/cordova/emulate.js
>  line 36
> But the argument should be an object with a key named platforms. like so:
> return require('./cordova').raw.prepare({platforms: options.platforms}); 



--
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-10477) Error in Android build CLI 5.1.1

[Tony Homer (JIRA)]

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

Tony Homer reassigned CB-10477:
---

Assignee: Tony Homer

> Error in Android build CLI 5.1.1
> 
>
> Key: CB-10477
> URL: https://issues.apache.org/jira/browse/CB-10477
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Android, CLI
>Reporter: Antonio Zaaa
>Assignee: Tony Homer
>  Labels: triaged, wfc
>
> When build, I got this error:
> location: package org.apache.cordova
> [javac] 
> .../builds/build.5G6xNk.tmp/appanalyzer/platforms/android/src/org/apache/cordova/inappbrowser/InAppBrowser.java:917:
>  error: cannot find symbol
> [javac] if (pluginManager != null && 
> pluginManager.onReceivedHttpAuthRequest(webView, new 
> CordovaHttpAuthHandler(handler), host, realm)) {
> [javac]   
> ^
> [javac]   symbol:   class CordovaHttpAuthHandler
> [javac]   location: class InAppBrowser.InAppBrowserClient
> [javac] Note: Some input files use or override a deprecated API.
> [javac] Note: Recompile with -Xlint:deprecation for details.
> [javac] Note: Some input files use unchecked or unsafe operations.
> [javac] Note: Recompile with -Xlint:unchecked for details.
> [javac] 2 errors
> BUILD FAILED
> .../android-sdk-linux/tools/ant/build.xml:720: The following error occurred 
> while executing this line:
> .../android-sdk-linux/tools/ant/build.xml:734: Compile failed; see the 
> compiler error output for details.
> Total time: 11 seconds
> .../builds/build.5G6xNk.tmp/appanalyzer/platforms/android/cordova/node_modules/q/q.js:126
> throw e;
>   ^
> Error code 1 for command: ant with args: 
> release,-f,.../builds/build.5G6xNk.tmp/appanalyzer/platforms/android/build.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-10512) Nothing happens when trying to move a file

[Eric dos Reis Santos (JIRA)]

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

Eric dos Reis Santos closed CB-10512.
-
Resolution: Resolved

It was my mistake, in the function moveFile, I was sending the directory with 
the file name, in the moveFrom parameter in my service. The correct way is set 
only the directory:

$cordovaFile.moveFile(moveFrom, currentFileName, cordova.file.dataDirectory + 
moveTo, newFileName)
.then(function (success)
{ alert("Yeah Success " + JSON.stringify(success)); }
, function (error)
{ alert("Fucking error " + JSON.stringify(error)); }
);

Cordova file could return an invalid directory error.

> Nothing happens when trying to move a file
> --
>
> Key: CB-10512
> URL: https://issues.apache.org/jira/browse/CB-10512
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Android, CordovaJS
> Environment: Android
>Reporter: Eric dos Reis Santos
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
>
> I was to able to create a directory, and I'm trying to move a image stored in 
> "temp files" directory to my directory created in file system, but nothing 
> happens, the promise doesn't return error and success, absolutely nothing 
> happens.
> The cordova file plugin was added in my app.
> I debugged the app in my device with Android Studio, and I saw an error in 
> log cat: "Error in Success callbackId: File285873816 : TypeError: 
> fileSystem.getFile is not a function" in source: 
> file:///android_asset/www/cordova.js
> Someone can help me?



--
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-10465) cordova.raw.emulate fires a cordova.raw.prepare with incorrect arguments

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-10465:
-

Github user asfgit closed the pull request at:

https://github.com/apache/cordova-lib/pull/374


> cordova.raw.emulate fires a cordova.raw.prepare with incorrect arguments
> 
>
> Key: CB-10465
> URL: https://issues.apache.org/jira/browse/CB-10465
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: CordovaLib
>Affects Versions: 5.4.1
>Reporter: Manuel Martiarena
>Assignee: Vladimir Kotikov
>  Labels: cordova-lib, reproduced, triaged
>
> All cordova.raw command now need to be called with arguments like this ticket 
> expains: https://issues.apache.org/jira/browse/CB-9987.
> Unfortunately the raw emulate command executes the raw prepare with the wrong 
> structure of arguments, with the side effect that if you want to emulate only 
> iOS, the other configured projects will also be add/checked/prepared.
> emulate.js calls it like this: 
> return require('./cordova').raw.prepare(options.platforms);
> https://github.com/apache/cordova-lib/blob/master/cordova-lib/src/cordova/emulate.js
>  line 36
> But the argument should be an object with a key named platforms. like so:
> return require('./cordova').raw.prepare({platforms: options.platforms}); 



--
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-10477) Error in Android build CLI 5.1.1

[Tony Homer (JIRA)]

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

Tony Homer commented on CB-10477:
-

[~Zappescu] - I work on Intel XDK team and will look into this why this error 
is occurring.  I wonder if it is possible for you to use version 1.0.1 of this 
plugin instead of latest (this is the version that was current when 
cordova-android 4.1.1 was released, which is what pin for CLI 5.1.1)?

> Error in Android build CLI 5.1.1
> 
>
> Key: CB-10477
> URL: https://issues.apache.org/jira/browse/CB-10477
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Android, CLI
>Reporter: Antonio Zaaa
>Assignee: Tony Homer
>  Labels: triaged, wfc
>
> When build, I got this error:
> location: package org.apache.cordova
> [javac] 
> .../builds/build.5G6xNk.tmp/appanalyzer/platforms/android/src/org/apache/cordova/inappbrowser/InAppBrowser.java:917:
>  error: cannot find symbol
> [javac] if (pluginManager != null && 
> pluginManager.onReceivedHttpAuthRequest(webView, new 
> CordovaHttpAuthHandler(handler), host, realm)) {
> [javac]   
> ^
> [javac]   symbol:   class CordovaHttpAuthHandler
> [javac]   location: class InAppBrowser.InAppBrowserClient
> [javac] Note: Some input files use or override a deprecated API.
> [javac] Note: Recompile with -Xlint:deprecation for details.
> [javac] Note: Some input files use unchecked or unsafe operations.
> [javac] Note: Recompile with -Xlint:unchecked for details.
> [javac] 2 errors
> BUILD FAILED
> .../android-sdk-linux/tools/ant/build.xml:720: The following error occurred 
> while executing this line:
> .../android-sdk-linux/tools/ant/build.xml:734: Compile failed; see the 
> compiler error output for details.
> Total time: 11 seconds
> .../builds/build.5G6xNk.tmp/appanalyzer/platforms/android/cordova/node_modules/q/q.js:126
> throw e;
>   ^
> Error code 1 for command: ant with args: 
> release,-f,.../builds/build.5G6xNk.tmp/appanalyzer/platforms/android/build.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] [Created] (CB-10518) Cordova reports error events with incorrect log level

[Vladimir Kotikov (JIRA)]

Vladimir Kotikov created CB-10518:
-

 Summary: Cordova reports error events with incorrect log level
 Key: CB-10518
 URL: https://issues.apache.org/jira/browse/CB-10518
 Project: Apache Cordova
  Issue Type: Bug
  Components: CordovaLib
Affects Versions: 6.0.0
Reporter: Vladimir Kotikov
Priority: Minor


In case of fatal errors {{cordova run}} and {{cordova emulate}} methods emit 
error messages using {{log}} event. This code probably should be changed to use 
'warn' level. (We can't use 'error' here due to its special meaning in Node: 
https://nodejs.org/api/events.html#events_error_events)

There is also other places, where 'log' events is used incorrectly:

cordova-lib\src\cordova\targets.js:events.emit('log', 'An unexpected 
error has occured');
cordova-lib\src\plugman\browserify.js:events.emit('log', 'error while 
generating cordova.js');
cordova-lib\src\plugman\browserify.js:events.emit('log', 'Error 
running platform version script');




--
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-10519) Using cordova.raw API outside of cordova project results in uncaught exception instead or promise rejection

[Vladimir Kotikov (JIRA)]

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

Vladimir Kotikov commented on CB-10519:
---

The same problem with other {{cordova.raw}} methods (build, compile, etc...)

> Using cordova.raw API outside of cordova project results in uncaught 
> exception instead or promise rejection
> ---
>
> Key: CB-10519
> URL: https://issues.apache.org/jira/browse/CB-10519
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: CordovaLib
>Affects Versions: 6.0.0
>Reporter: Vladimir Kotikov
>
> When trying to {{cordova.raw.platfom('add', ...)}} outside of cordova project 
> the following error message logged to console:
> > Error: Current working directory is not a Cordova-based project.
> However, the error callback for {{cordova.raw.platfom('add', ...)}} isn't 
> called at all.



--
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-10465) cordova.raw.emulate fires a cordova.raw.prepare with incorrect arguments

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-10465:
-

Github user sgrebnov commented on the pull request:

https://github.com/apache/cordova-lib/pull/374#issuecomment-179263903
  
LGTM


> cordova.raw.emulate fires a cordova.raw.prepare with incorrect arguments
> 
>
> Key: CB-10465
> URL: https://issues.apache.org/jira/browse/CB-10465
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: CordovaLib
>Affects Versions: 5.4.1
>Reporter: Manuel Martiarena
>Assignee: Vladimir Kotikov
>  Labels: cordova-lib, reproduced, triaged
>
> All cordova.raw command now need to be called with arguments like this ticket 
> expains: https://issues.apache.org/jira/browse/CB-9987.
> Unfortunately the raw emulate command executes the raw prepare with the wrong 
> structure of arguments, with the side effect that if you want to emulate only 
> iOS, the other configured projects will also be add/checked/prepared.
> emulate.js calls it like this: 
> return require('./cordova').raw.prepare(options.platforms);
> https://github.com/apache/cordova-lib/blob/master/cordova-lib/src/cordova/emulate.js
>  line 36
> But the argument should be an object with a key named platforms. like so:
> return require('./cordova').raw.prepare({platforms: options.platforms}); 



--
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-10465) cordova.raw.emulate fires a cordova.raw.prepare with incorrect arguments

[Vladimir Kotikov (JIRA)]

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

Vladimir Kotikov resolved CB-10465.
---
Resolution: Fixed

> cordova.raw.emulate fires a cordova.raw.prepare with incorrect arguments
> 
>
> Key: CB-10465
> URL: https://issues.apache.org/jira/browse/CB-10465
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: CordovaLib
>Affects Versions: 5.4.1
>Reporter: Manuel Martiarena
>Assignee: Vladimir Kotikov
>  Labels: cordova-lib, reproduced, triaged
>
> All cordova.raw command now need to be called with arguments like this ticket 
> expains: https://issues.apache.org/jira/browse/CB-9987.
> Unfortunately the raw emulate command executes the raw prepare with the wrong 
> structure of arguments, with the side effect that if you want to emulate only 
> iOS, the other configured projects will also be add/checked/prepared.
> emulate.js calls it like this: 
> return require('./cordova').raw.prepare(options.platforms);
> https://github.com/apache/cordova-lib/blob/master/cordova-lib/src/cordova/emulate.js
>  line 36
> But the argument should be an object with a key named platforms. like so:
> return require('./cordova').raw.prepare({platforms: options.platforms}); 



--
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-10477) Error in Android build CLI 5.1.1

[Tony Homer (JIRA)]

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

Tony Homer commented on CB-10477:
-

[~Zappescu] - After re-reading your error message, I see that you must be 
getting this error when you are building the debug module for your app.  This 
is an Intel XDK issue, not a Cordova issue.  Please contact me directly or post 
on the Intel XDK forums for support with this issue.

> Error in Android build CLI 5.1.1
> 
>
> Key: CB-10477
> URL: https://issues.apache.org/jira/browse/CB-10477
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Android, CLI
>Reporter: Antonio Zaaa
>Assignee: Tony Homer
>  Labels: triaged, wfc
>
> When build, I got this error:
> location: package org.apache.cordova
> [javac] 
> .../builds/build.5G6xNk.tmp/appanalyzer/platforms/android/src/org/apache/cordova/inappbrowser/InAppBrowser.java:917:
>  error: cannot find symbol
> [javac] if (pluginManager != null && 
> pluginManager.onReceivedHttpAuthRequest(webView, new 
> CordovaHttpAuthHandler(handler), host, realm)) {
> [javac]   
> ^
> [javac]   symbol:   class CordovaHttpAuthHandler
> [javac]   location: class InAppBrowser.InAppBrowserClient
> [javac] Note: Some input files use or override a deprecated API.
> [javac] Note: Recompile with -Xlint:deprecation for details.
> [javac] Note: Some input files use unchecked or unsafe operations.
> [javac] Note: Recompile with -Xlint:unchecked for details.
> [javac] 2 errors
> BUILD FAILED
> .../android-sdk-linux/tools/ant/build.xml:720: The following error occurred 
> while executing this line:
> .../android-sdk-linux/tools/ant/build.xml:734: Compile failed; see the 
> compiler error output for details.
> Total time: 11 seconds
> .../builds/build.5G6xNk.tmp/appanalyzer/platforms/android/cordova/node_modules/q/q.js:126
> throw e;
>   ^
> Error code 1 for command: ant with args: 
> release,-f,.../builds/build.5G6xNk.tmp/appanalyzer/platforms/android/build.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-10477) Error in Android build CLI 5.1.1

[Tony Homer (JIRA)]

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

Tony Homer closed CB-10477.
---
Resolution: Won't Fix

Not a Cordova issue.  Directed user to appropriate support resources.

> Error in Android build CLI 5.1.1
> 
>
> Key: CB-10477
> URL: https://issues.apache.org/jira/browse/CB-10477
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Android, CLI
>Reporter: Antonio Zaaa
>Assignee: Tony Homer
>  Labels: triaged, wfc
>
> When build, I got this error:
> location: package org.apache.cordova
> [javac] 
> .../builds/build.5G6xNk.tmp/appanalyzer/platforms/android/src/org/apache/cordova/inappbrowser/InAppBrowser.java:917:
>  error: cannot find symbol
> [javac] if (pluginManager != null && 
> pluginManager.onReceivedHttpAuthRequest(webView, new 
> CordovaHttpAuthHandler(handler), host, realm)) {
> [javac]   
> ^
> [javac]   symbol:   class CordovaHttpAuthHandler
> [javac]   location: class InAppBrowser.InAppBrowserClient
> [javac] Note: Some input files use or override a deprecated API.
> [javac] Note: Recompile with -Xlint:deprecation for details.
> [javac] Note: Some input files use unchecked or unsafe operations.
> [javac] Note: Recompile with -Xlint:unchecked for details.
> [javac] 2 errors
> BUILD FAILED
> .../android-sdk-linux/tools/ant/build.xml:720: The following error occurred 
> while executing this line:
> .../android-sdk-linux/tools/ant/build.xml:734: Compile failed; see the 
> compiler error output for details.
> Total time: 11 seconds
> .../builds/build.5G6xNk.tmp/appanalyzer/platforms/android/cordova/node_modules/q/q.js:126
> throw e;
>   ^
> Error code 1 for command: ant with args: 
> release,-f,.../builds/build.5G6xNk.tmp/appanalyzer/platforms/android/build.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] [Commented] (CB-10332) Improve Android Guide

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-10332:
-

Github user riknoll commented on a diff in the pull request:

https://github.com/apache/cordova-docs/pull/471#discussion_r51801334
  
--- Diff: www/docs/en/dev/guide/platforms/android/index.md ---
@@ -32,276 +32,152 @@ development. For a comparison of the two development 
paths, see the
 
 ## Requirements and Support
 
+### Java Development Kit (JDK)
+
+Install [Java Development Kit (JDK) 
7](http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html)
+or later.
+
+When installing on Windows you also need to set `JAVA_HOME` Environment 
Variable
+according to JDK installation path (for example, `C:\Program 
Files\Java\jdk1.7.0_75`).
+
+### Android SDK
+
 Cordova for Android requires the Android SDK which could be installed
 on OS X, Linux or Windows operation system. See the Android SDK's
 [System 
Requirements](http://developer.android.com/sdk/index.html#Requirements).
-
-Cordova supports Android 4.0.x (starting with Android API level 14)
-and higher.  As a general rule, Android versions become unsupported by 
Cordova as
+Cordova's latest Android package supports up to Android 
[API-Level](http://developer.android.com/guide/topics/manifest/uses-sdk-element.html#ApiLevels)
 23.
+The supported Android API-Levels for the past few cordova-android releases 
can
+be found in this table:
+
+cordova-android Version | Supported Android API-Levels
+|-
+5.X.X   | 14 - 23
+4.1.X   | 14 - 22
+4.0.X   | 10 - 22
+3.7.X   | 10 - 21
+
+Please note that the versions listed here are for Cordova's Android 
package,
+[cordova-android](https://github.com/apache/cordova-android), and not for 
the
+Cordova CLI. To determine what version of Cordova's Android package is 
installed
+in your Cordova project, run the command `cordova platform ls` in the 
directory
+that holds your project.
+
+As a general rule, Android versions become unsupported by Cordova as
 they dip below 5% on Google's
 [distribution 
dashboard](http://developer.android.com/about/dashboards/index.html).
-Android versions earlier than API level 10, and the 3.x versions 
(Honeycomb,
-API levels 11-13) fall significantly below that 5% threshold.
-
-## Install Cordova Shell Tools
-
-If you want to use Cordova's Android-centered shell tools in
-conjunction with the SDK, download Cordova from
-[cordova.apache.org](http://cordova.apache.org). Otherwise ignore this
-section if you plan to use the cross-platform CLI tool described in
-[The Command-Line Interface](../../cli/index.html).
 
-The Cordova download contains separate archives for each platform. Be
-sure to expand the appropriate archive, `android` in this case, within
-an empty directory.  The relevant executible utilities are available
-in the top-level `bin` directory. (Consult the __README__ file if
-necessary for more detailed directions.)
+ Installing the Android SDK
 
-These shell tools allow you to create, build, and run Android apps.
-For information on the additional command-line interface that enables
-plugin features across all platforms, see Using Plugman to Manage
-Plugins. See Application Plugins for details on how to develop
-plugins.
-
-## Install the Java Development Kit (JDK)
-
-Install [Java Development Kit (JDK) 
7](http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html)
-or later. 
-
-When installing on Windows you also need to set `JAVA_HOME` Environment 
Variable
-according to JDK installation path (for example, C:\Program 
Files\Java\jdk1.7.0_75).
-
-## Install the Android SDK
-
-Install the [Android Stand-alone SDK 
Tools](http://developer.android.com/sdk/installing/index.html?pkg=tools) or 
[Android 
Studio](http://developer.android.com/sdk/installing/index.html?pkg=studio). 
Procceed with `Android Studio` if you plan 
+Install the [Android Stand-alone SDK 
Tools](http://developer.android.com/sdk/installing/index.html?pkg=tools) or 
[Android 
Studio](http://developer.android.com/sdk/installing/index.html?pkg=studio).
+Proceed with Android Studio if you plan on
 developing new Cordova for Android plugins or using native tools to
--- End diff --

For some reason this article says "Cordova for Android" all over the place 
and so I kept that up. This sentence was referring to plugins. Android Studio 
can be used with apps, but  I think the better use case is with 

[jira] [Commented] (CB-10176) Cordova-common should contain a default logger implementation.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-10176:
-

Github user TimBarham commented on the pull request:

https://github.com/apache/cordova-lib/pull/375#issuecomment-179513568
  
:+1:  Thanks Vladimir.


> Cordova-common should contain a default logger implementation.
> --
>
> Key: CB-10176
> URL: https://issues.apache.org/jira/browse/CB-10176
> Project: Apache Cordova
>  Issue Type: Improvement
>  Components: CordovaCommon
>Affects Versions: 1.0.0
>Reporter: Vladimir Kotikov
>Assignee: Vladimir Kotikov
>  Labels: triaged
> Fix For: 1.1.0
>
>
> Currently ConsoleLogger, which is used for logging, when platform is not 
> supplied with EventEmitter, is duplicated across each platform.
> The same logic is already lives in CLI.
> To reduce code duplication it should be moved to 'common'.



--
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-10269) [iOS 8] cordova-plugin-wkwebview-engine breaks Cordova iOS 4.0.0 under iOS 8

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-10269:
-

Github user hassankhan commented on the pull request:


https://github.com/apache/cordova-plugin-wkwebview-engine/pull/3#issuecomment-179555817
  
Ah my mistake, I assumed the error I was getting was related to this.


> [iOS 8] cordova-plugin-wkwebview-engine breaks Cordova iOS 4.0.0 under iOS 8
> 
>
> Key: CB-10269
> URL: https://issues.apache.org/jira/browse/CB-10269
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Plugin WKWebViewEngine
>Affects Versions: 4.0.0
> Environment: Cordova tools 5.4.1
> Cordova iOS platform 4.0.1
> iOS Simulator 8.4
> cordova-plugin-wkwebview-engine plugin
>Reporter: Ivan Karpan
>Assignee: Shazron Abdullah
>Priority: Critical
>  Labels: cordova-ios-4.1.0, triaged
> Attachments: ios-wkwebview-exec.js
>
>
> When launching on iOS 8.4 simulator the following error breaks JS execution 
> early on:
> ios-wkwebview-exec.js:127 TypeError: undefined is not an object (evaluating 
> 'window.webkit.messageHandlers')
> So inclusion of 'cordova-plugin-wkwebview-engine' plugin breaks support of 
> iOS versions previous to 9.0. I assume ios-wkwebview-exec.js should have 
> environment checks before using WKWebView bridge...
> Exclusion of the same plugin breaks the project at all. Are there any 
> fallback mechanics in place?



--
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-9689) Select dropdowns are not working in ios 9 iPad split view and slide over

[Christian Hemker (JIRA)]

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

Christian Hemker commented on CB-9689:
--

This is an open issue since iOS 9 and exists still in iOS 9.2.1 and 9.3 beta 2.
https://forums.developer.apple.com/thread/23300

> Select dropdowns are not working in ios 9 iPad split view and slide over
> 
>
> Key: CB-9689
> URL: https://issues.apache.org/jira/browse/CB-9689
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: iOS
>Affects Versions: 3.8.0
>Reporter: Sravan
> Attachments: Screen Shot 2015-09-22 at 2.03.27 PM.png
>
>




--
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-10332) Improve Android Guide

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-10332:
-

Github user riknoll commented on a diff in the pull request:

https://github.com/apache/cordova-docs/pull/471#discussion_r51802704
  
--- Diff: www/docs/en/dev/guide/platforms/android/index.md ---
@@ -32,276 +32,152 @@ development. For a comparison of the two development 
paths, see the
 
 ## Requirements and Support
 
+### Java Development Kit (JDK)
+
+Install [Java Development Kit (JDK) 
7](http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html)
+or later.
+
+When installing on Windows you also need to set `JAVA_HOME` Environment 
Variable
+according to JDK installation path (for example, `C:\Program 
Files\Java\jdk1.7.0_75`).
+
+### Android SDK
+
 Cordova for Android requires the Android SDK which could be installed
 on OS X, Linux or Windows operation system. See the Android SDK's
 [System 
Requirements](http://developer.android.com/sdk/index.html#Requirements).
-
-Cordova supports Android 4.0.x (starting with Android API level 14)
-and higher.  As a general rule, Android versions become unsupported by 
Cordova as
+Cordova's latest Android package supports up to Android 
[API-Level](http://developer.android.com/guide/topics/manifest/uses-sdk-element.html#ApiLevels)
 23.
+The supported Android API-Levels for the past few cordova-android releases 
can
+be found in this table:
+
+cordova-android Version | Supported Android API-Levels
+|-
+5.X.X   | 14 - 23
+4.1.X   | 14 - 22
+4.0.X   | 10 - 22
+3.7.X   | 10 - 21
+
+Please note that the versions listed here are for Cordova's Android 
package,
+[cordova-android](https://github.com/apache/cordova-android), and not for 
the
+Cordova CLI. To determine what version of Cordova's Android package is 
installed
+in your Cordova project, run the command `cordova platform ls` in the 
directory
+that holds your project.
+
+As a general rule, Android versions become unsupported by Cordova as
 they dip below 5% on Google's
 [distribution 
dashboard](http://developer.android.com/about/dashboards/index.html).
-Android versions earlier than API level 10, and the 3.x versions 
(Honeycomb,
-API levels 11-13) fall significantly below that 5% threshold.
-
-## Install Cordova Shell Tools
-
-If you want to use Cordova's Android-centered shell tools in
-conjunction with the SDK, download Cordova from
-[cordova.apache.org](http://cordova.apache.org). Otherwise ignore this
-section if you plan to use the cross-platform CLI tool described in
-[The Command-Line Interface](../../cli/index.html).
 
-The Cordova download contains separate archives for each platform. Be
-sure to expand the appropriate archive, `android` in this case, within
-an empty directory.  The relevant executible utilities are available
-in the top-level `bin` directory. (Consult the __README__ file if
-necessary for more detailed directions.)
+ Installing the Android SDK
 
-These shell tools allow you to create, build, and run Android apps.
-For information on the additional command-line interface that enables
-plugin features across all platforms, see Using Plugman to Manage
-Plugins. See Application Plugins for details on how to develop
-plugins.
-
-## Install the Java Development Kit (JDK)
-
-Install [Java Development Kit (JDK) 
7](http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html)
-or later. 
-
-When installing on Windows you also need to set `JAVA_HOME` Environment 
Variable
-according to JDK installation path (for example, C:\Program 
Files\Java\jdk1.7.0_75).
-
-## Install the Android SDK
-
-Install the [Android Stand-alone SDK 
Tools](http://developer.android.com/sdk/installing/index.html?pkg=tools) or 
[Android 
Studio](http://developer.android.com/sdk/installing/index.html?pkg=studio). 
Procceed with `Android Studio` if you plan 
+Install the [Android Stand-alone SDK 
Tools](http://developer.android.com/sdk/installing/index.html?pkg=tools) or 
[Android 
Studio](http://developer.android.com/sdk/installing/index.html?pkg=studio).
+Proceed with Android Studio if you plan on
 developing new Cordova for Android plugins or using native tools to
-run and debug Android platform. Otherwise, `Android Stand-alone SDK Tools`
-are enough to build and deploy Android application.
+run and debug the Android platform. Otherwise, the Android Stand-alone SDK 
Tools
+are enough to build 

[jira] [Commented] (CB-10332) Improve Android Guide

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-10332:
-

Github user rakatyal commented on a diff in the pull request:

https://github.com/apache/cordova-docs/pull/471#discussion_r51802949
  
--- Diff: www/docs/en/dev/guide/platforms/android/plugin.md ---
@@ -31,12 +31,12 @@ platform and back.  For another sample, see also the 
comments in
 
[CordovaPlugin.java](https://github.com/apache/cordova-android/blob/master/framework/src/org/apache/cordova/CordovaPlugin.java).
 
 Android plugins are based on Cordova-Android, which consists of an
-Android WebView with hooks attached to it.  Plugins are represented as
-class mappings in the `config.xml` file.  A plugin consists of at
+Android WebView with hooks attached to it. Plugins are represented as
+class mappings in the `config.xml` file. A plugin consists of at
 least one Java class that extends the `CordovaPlugin` class,
-overriding one of its `execute` methods. As best practice, the plugin
-should also handle `[pause](../../../cordova/events/events.pause.html)` 
and `[resume](../../../cordova/events/events.resume.html)` events, along with 
any message
-passing between plugins.  Plugins with long-running requests,
+overriding one of its `execute` methods. As a best practice, the plugin
+should also handle [`pause`](../../../cordova/events/events.pause.html) 
and [`resume`](../../../cordova/events/events.resume.html) events, along with 
any message
--- End diff --

Link these to events reference?


> Improve Android Guide
> -
>
> Key: CB-10332
> URL: https://issues.apache.org/jira/browse/CB-10332
> Project: Apache Cordova
>  Issue Type: Task
>  Components: Docs
>Reporter: Raghav
>Assignee: Richard B Knoll
>  Labels: Docs-6.x
>
> We did a document scrub and found the following issues. Please feel free to 
> correct other things as well.
> - Android Platform Guide
> -- Install Cordova Shell tools is out of date
> -- Environment variable instructions for Windows are out of date
> -- Emulator section can just point to 
> http://developer.android.com/tools/devices/emulator.html
> -- Lots of duplicated content for create/build/deploy from CLI page
> -- Page keeps switching between CLI and platform-centric workflow
> - Android Shell Tool Guide
> -- Second paragraph is out of date
> -- Create/build/run/logging/clean should be clear that this is the 
> platform-centric workflow. Also duplicated in Android Platform guide
> -- Platform-centric workflow should probably just get its own explicit page
> -- Signing an app doesn't actually say how to sign an app. Gives arguments 
> for some mystery command
> --- Does this belong in our docs? We might just mention it and point to 
> Google's app signing instructions
> - Android WebViews
> -- Needs investigation if this is still supported.
> --- Step 1 is wrong (should be getting cordova-android by cloning or from npm)
> --- Step 3 needs to have instructions for adding jars to gradle
> --- Step 5 is out of date. CordovaActivity does not implement 
> CordovaInterface... Think they should be extending/modifying CordovaActivity. 
> Needs investigation
> --- Step 6 does not appear to be camera plugin specific
> --- Step 7 example is useless, it needs to be fleshed out
> - Android plugins
> -- Should be moved to plugin developer docs
> -- Need a reference for the classes that plugins have access to
> --- CordovaWebView, CallbackContext, CordovaPlugin, etc.
> --- Most already have javadoc
> -- Android Integration should be renamed and link to the Android classes it's 
> talking about
> -- Debugging Android plugins is out of date (mentions Eclipse and jars) and 
> should probably be fleshed out a bit
> - Android Configuration
> -- Should be a reference
> - Upgrading Android
> -- Ends at 4.0.0 (current is 4.1.1, soon to be 5.0.0)
> -- Needs to be reorganized in some way
> --- The instructions seem to be pretty much the same for versions 1.6.0 +
> -- Goes back to the phonegap days! Should probably only include Cordova 
> versions (1.5.0 +)
> -- Upgrade to 1.8.0 from 1.7.0 repeated twice
> -- Upgrade to 1.8.0 from 1.8.0 is a typo
> General guidelines:
> - While giving examples, keep them short. Do not repeat for all 
> plugins/platforms.
> - Remove all references to cordova plugin registry.
> - Remove Tizen references. The platform is deprecated 
> (http://markmail.org/message/hryg6sjswecpgndu)
> - Keep information up to date for the platforms, CLI and plugins



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, 

[jira] [Commented] (CB-10176) Cordova-common should contain a default logger implementation.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-10176:
-

Github user purplecabbage commented on the pull request:

https://github.com/apache/cordova-lib/pull/375#issuecomment-179518934
  
lgtm!
Seems we are slowly migrating from lowercase file names to CamelCase .. 


> Cordova-common should contain a default logger implementation.
> --
>
> Key: CB-10176
> URL: https://issues.apache.org/jira/browse/CB-10176
> Project: Apache Cordova
>  Issue Type: Improvement
>  Components: CordovaCommon
>Affects Versions: 1.0.0
>Reporter: Vladimir Kotikov
>Assignee: Vladimir Kotikov
>  Labels: triaged
> Fix For: 1.1.0
>
>
> Currently ConsoleLogger, which is used for logging, when platform is not 
> supplied with EventEmitter, is duplicated across each platform.
> The same logic is already lives in CLI.
> To reduce code duplication it should be moved to 'common'.



--
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-10269) [iOS 8] cordova-plugin-wkwebview-engine breaks Cordova iOS 4.0.0 under iOS 8

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-10269:
-

Github user hassankhan commented on the pull request:


https://github.com/apache/cordova-plugin-wkwebview-engine/pull/3#issuecomment-179554625
  
+1 can this be merged soon please? :+1: 


> [iOS 8] cordova-plugin-wkwebview-engine breaks Cordova iOS 4.0.0 under iOS 8
> 
>
> Key: CB-10269
> URL: https://issues.apache.org/jira/browse/CB-10269
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Plugin WKWebViewEngine
>Affects Versions: 4.0.0
> Environment: Cordova tools 5.4.1
> Cordova iOS platform 4.0.1
> iOS Simulator 8.4
> cordova-plugin-wkwebview-engine plugin
>Reporter: Ivan Karpan
>Assignee: Shazron Abdullah
>Priority: Critical
>  Labels: cordova-ios-4.1.0, triaged
> Attachments: ios-wkwebview-exec.js
>
>
> When launching on iOS 8.4 simulator the following error breaks JS execution 
> early on:
> ios-wkwebview-exec.js:127 TypeError: undefined is not an object (evaluating 
> 'window.webkit.messageHandlers')
> So inclusion of 'cordova-plugin-wkwebview-engine' plugin breaks support of 
> iOS versions previous to 9.0. I assume ios-wkwebview-exec.js should have 
> environment checks before using WKWebView bridge...
> Exclusion of the same plugin breaks the project at all. Are there any 
> fallback mechanics in place?



--
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-10269) [iOS 8] cordova-plugin-wkwebview-engine breaks Cordova iOS 4.0.0 under iOS 8

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-10269:
-

Github user dpogue commented on the pull request:


https://github.com/apache/cordova-plugin-wkwebview-engine/pull/3#issuecomment-179554784
  
It has already been merged in 
https://github.com/apache/cordova-plugin-wkwebview-engine/commit/faa9d877045d8baf8afdfd0d8689389ec240e2e4


> [iOS 8] cordova-plugin-wkwebview-engine breaks Cordova iOS 4.0.0 under iOS 8
> 
>
> Key: CB-10269
> URL: https://issues.apache.org/jira/browse/CB-10269
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Plugin WKWebViewEngine
>Affects Versions: 4.0.0
> Environment: Cordova tools 5.4.1
> Cordova iOS platform 4.0.1
> iOS Simulator 8.4
> cordova-plugin-wkwebview-engine plugin
>Reporter: Ivan Karpan
>Assignee: Shazron Abdullah
>Priority: Critical
>  Labels: cordova-ios-4.1.0, triaged
> Attachments: ios-wkwebview-exec.js
>
>
> When launching on iOS 8.4 simulator the following error breaks JS execution 
> early on:
> ios-wkwebview-exec.js:127 TypeError: undefined is not an object (evaluating 
> 'window.webkit.messageHandlers')
> So inclusion of 'cordova-plugin-wkwebview-engine' plugin breaks support of 
> iOS versions previous to 9.0. I assume ios-wkwebview-exec.js should have 
> environment checks before using WKWebView bridge...
> Exclusion of the same plugin breaks the project at all. Are there any 
> fallback mechanics in place?



--
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-10474) Gathering logs fails in cordova-ios CI

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-10474:
-

Github user dblotsky commented on the pull request:

https://github.com/apache/cordova-medic/pull/73#issuecomment-179507278
  
LGTM.


> Gathering logs fails in cordova-ios CI
> --
>
> Key: CB-10474
> URL: https://issues.apache.org/jira/browse/CB-10474
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Medic
> Environment: OSX
>Reporter: Richard B Knoll
>Assignee: Richard B Knoll
>  Labels: found-by-ci, ios, triaged
>
> In the cordova-ios Build Bot CI, the gathering logs step always fails. It 
> tries to {{cat}} a file for the log that does not exist. Here is an example 
> build: 
> https://ci.apache.org/builders/cordova-ios/builds/1607/steps/gathering-logs/logs/stdio



--
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-10332) Improve Android Guide

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-10332:
-

Github user rakatyal commented on a diff in the pull request:

https://github.com/apache/cordova-docs/pull/471#discussion_r51802258
  
--- Diff: www/docs/en/dev/guide/platforms/android/index.md ---
@@ -32,276 +32,152 @@ development. For a comparison of the two development 
paths, see the
 
 ## Requirements and Support
 
+### Java Development Kit (JDK)
+
+Install [Java Development Kit (JDK) 
7](http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html)
+or later.
+
+When installing on Windows you also need to set `JAVA_HOME` Environment 
Variable
+according to JDK installation path (for example, `C:\Program 
Files\Java\jdk1.7.0_75`).
+
+### Android SDK
+
 Cordova for Android requires the Android SDK which could be installed
 on OS X, Linux or Windows operation system. See the Android SDK's
 [System 
Requirements](http://developer.android.com/sdk/index.html#Requirements).
-
-Cordova supports Android 4.0.x (starting with Android API level 14)
-and higher.  As a general rule, Android versions become unsupported by 
Cordova as
+Cordova's latest Android package supports up to Android 
[API-Level](http://developer.android.com/guide/topics/manifest/uses-sdk-element.html#ApiLevels)
 23.
+The supported Android API-Levels for the past few cordova-android releases 
can
+be found in this table:
+
+cordova-android Version | Supported Android API-Levels
+|-
+5.X.X   | 14 - 23
+4.1.X   | 14 - 22
+4.0.X   | 10 - 22
+3.7.X   | 10 - 21
+
+Please note that the versions listed here are for Cordova's Android 
package,
+[cordova-android](https://github.com/apache/cordova-android), and not for 
the
+Cordova CLI. To determine what version of Cordova's Android package is 
installed
+in your Cordova project, run the command `cordova platform ls` in the 
directory
+that holds your project.
+
+As a general rule, Android versions become unsupported by Cordova as
 they dip below 5% on Google's
 [distribution 
dashboard](http://developer.android.com/about/dashboards/index.html).
-Android versions earlier than API level 10, and the 3.x versions 
(Honeycomb,
-API levels 11-13) fall significantly below that 5% threshold.
-
-## Install Cordova Shell Tools
-
-If you want to use Cordova's Android-centered shell tools in
-conjunction with the SDK, download Cordova from
-[cordova.apache.org](http://cordova.apache.org). Otherwise ignore this
-section if you plan to use the cross-platform CLI tool described in
-[The Command-Line Interface](../../cli/index.html).
 
-The Cordova download contains separate archives for each platform. Be
-sure to expand the appropriate archive, `android` in this case, within
-an empty directory.  The relevant executible utilities are available
-in the top-level `bin` directory. (Consult the __README__ file if
-necessary for more detailed directions.)
+ Installing the Android SDK
 
-These shell tools allow you to create, build, and run Android apps.
-For information on the additional command-line interface that enables
-plugin features across all platforms, see Using Plugman to Manage
-Plugins. See Application Plugins for details on how to develop
-plugins.
-
-## Install the Java Development Kit (JDK)
-
-Install [Java Development Kit (JDK) 
7](http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html)
-or later. 
-
-When installing on Windows you also need to set `JAVA_HOME` Environment 
Variable
-according to JDK installation path (for example, C:\Program 
Files\Java\jdk1.7.0_75).
-
-## Install the Android SDK
-
-Install the [Android Stand-alone SDK 
Tools](http://developer.android.com/sdk/installing/index.html?pkg=tools) or 
[Android 
Studio](http://developer.android.com/sdk/installing/index.html?pkg=studio). 
Procceed with `Android Studio` if you plan 
+Install the [Android Stand-alone SDK 
Tools](http://developer.android.com/sdk/installing/index.html?pkg=tools) or 
[Android 
Studio](http://developer.android.com/sdk/installing/index.html?pkg=studio).
+Proceed with Android Studio if you plan on
 developing new Cordova for Android plugins or using native tools to
-run and debug Android platform. Otherwise, `Android Stand-alone SDK Tools`
-are enough to build and deploy Android application.
+run and debug the Android platform. Otherwise, the Android Stand-alone SDK 
Tools
+are enough to 

[jira] [Commented] (CB-10405) Connectivity issue to Cordova VM

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on CB-10405:
--

Commit 50770495d86c46fcf3544ead6864657ef8b46213 in cordova-medic's branch 
refs/heads/master from [~sarangan12]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-medic.git;h=5077049 ]

CB-10405: Adding retry logic in check command


> Connectivity issue to Cordova VM 
> -
>
> Key: CB-10405
> URL: https://issues.apache.org/jira/browse/CB-10405
> Project: Apache Cordova
>  Issue Type: Test
>Reporter: Sarangan Rajamanickam
>Assignee: Sarangan Rajamanickam
>  Labels: found-by-ci, triaged
>
> During Apache Cordova CI, we get errors while checking the cordova VMs. They 
> are intermittent. So, we need to add retry logic to the 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] [Commented] (CB-10405) Connectivity issue to Cordova VM

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-10405:
-

Github user asfgit closed the pull request at:

https://github.com/apache/cordova-medic/pull/74


> Connectivity issue to Cordova VM 
> -
>
> Key: CB-10405
> URL: https://issues.apache.org/jira/browse/CB-10405
> Project: Apache Cordova
>  Issue Type: Test
>Reporter: Sarangan Rajamanickam
>Assignee: Sarangan Rajamanickam
>  Labels: found-by-ci, triaged
>
> During Apache Cordova CI, we get errors while checking the cordova VMs. They 
> are intermittent. So, we need to add retry logic to the 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] [Comment Edited] (CB-10283) Displays white bar at the bottom of the android app.

[Ray Shan (JIRA)]

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

Ray Shan edited comment on CB-10283 at 2/4/16 12:13 AM:


Hi [~bowserj], I'm reopening this issue with reproducible steps, hope that's ok.

Environment:
- Cordova 6.0, Cordova Android 5.1
- Samsung Galaxy Tab 10.1 or a Nexus 9, both on Android 5.1.1

1. Create a fresh Cordova sample app via cordova create cordova-hello-world
2. cordova platform add android
3. In config.xml, add:

4. In index.html, replace this meta tag and add:


console.log(window.innerHeight);

5. cordova run android --device
6. Launch app

Expected: app run and stays in full screen without status bar; upon initial 
launch console logs 1280 for window.innerHeight, which is the device screen 
height on the Samsung tablet
Actual: app runs with a black bar shown on the bottom, console logs 1255

Notes:
- Upon initial launch when the splash screen is shown, you can see the OS 
status bar shown for a brief moment then goes away.
- Black bar will go away and the light gray background will cover the entire 
viewport if screen orientation changes, if app is hidden then brought back to 
foreground, or if Chrome DevTools is used to debug the app
- When hiding the app via pressing home button, you can see the top of the 
screen showing a transparent bar matching the size of the bottom black bar and 
OS status bar


was (Author: rayshan):
Hi [~bowserj], I'm reopening this issue with reproducible steps, hope that's ok.

1. cordova create cordova-hello-world
2. cordova platform add android
3. In config.xml, add:

4. In index.html, replace this meta tag and add:


console.log(window.innerHeight);

5. cordova run android --device, on a Samsung Galaxy Tab 10.1 or a Nexus 9
6. Launch app

Expected: app run and stays in full screen without status bar; upon initial 
launch console logs 1280 for window.innerHeight, which is the device screen 
height on the Samsung tablet
Actual: app runs with a black bar shown on the bottom, console logs 1255

Notes:
- Upon initial launch when the splash screen is shown, you can see the OS 
status bar shown for a brief moment then goes away.
- Black bar will go away and the light gray background will cover the entire 
viewport if screen orientation changes, if app is hidden then brought back to 
foreground, or if Chrome DevTools is used to debug the app
- When hiding the app via pressing home button, you can see the top of the 
screen showing a transparent bar matching the size of the bottom black bar and 
OS status bar

> Displays white bar at the bottom of the android app.
> 
>
> Key: CB-10283
> URL: https://issues.apache.org/jira/browse/CB-10283
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Android, CordovaLib
>Affects Versions: 6.0.0, 5.3.3
> Environment: Cordova cli 5.3.9 and Cordova 4.1.1
> Android Sumsung s6 (v5.0)
> jquery.mobile-1.4.5.min.js
>Reporter: Devshi Patel
>  Labels: android, fullscreen, statusbar, test, viewport
>   Original Estimate: 504h
>  Remaining Estimate: 504h
>
> When the app starts it displays a white bar at the bottom of the screen like 
> a status bar. This happens frequently but not always.
> I have been using  Cordova cli 4.2 & Cordova 4.0 without any problems. the 
> app is on google play store. 
> I am using jquery mobile framework version 1.4.5 
> I think the issue is with webview display.
> The code for MainActivity.java file 
>public void onCreate(Bundle savedInstanceState) {
>   super.onCreate(savedInstanceState);
>   super.loadUrl("file:///android_asset/www/index.html");
>   new SimpleEula(this).show(); 
>   }
> index.html
> 
> 



--
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-10283) Displays white bar at the bottom of the android app.

[Ray Shan (JIRA)]

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

Ray Shan updated CB-10283:
--
Labels: android fullscreen statusbar test viewport  (was: test)

> Displays white bar at the bottom of the android app.
> 
>
> Key: CB-10283
> URL: https://issues.apache.org/jira/browse/CB-10283
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Android, CordovaLib
>Affects Versions: 6.0.0, 5.3.3
> Environment: Cordova cli 5.3.9 and Cordova 4.1.1
> Android Sumsung s6 (v5.0)
> jquery.mobile-1.4.5.min.js
>Reporter: Devshi Patel
>  Labels: android, fullscreen, statusbar, test, viewport
>   Original Estimate: 504h
>  Remaining Estimate: 504h
>
> When the app starts it displays a white bar at the bottom of the screen like 
> a status bar. This happens frequently but not always.
> I have been using  Cordova cli 4.2 & Cordova 4.0 without any problems. the 
> app is on google play store. 
> I am using jquery mobile framework version 1.4.5 
> I think the issue is with webview display.
> The code for MainActivity.java file 
>public void onCreate(Bundle savedInstanceState) {
>   super.onCreate(savedInstanceState);
>   super.loadUrl("file:///android_asset/www/index.html");
>   new SimpleEula(this).show(); 
>   }
> index.html
> 
> 



--
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-10405) Connectivity issue to Cordova VM

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-10405:
-

Github user dblotsky commented on the pull request:

https://github.com/apache/cordova-medic/pull/74#issuecomment-179512306
  
Alright, LGTM then.


> Connectivity issue to Cordova VM 
> -
>
> Key: CB-10405
> URL: https://issues.apache.org/jira/browse/CB-10405
> Project: Apache Cordova
>  Issue Type: Test
>Reporter: Sarangan Rajamanickam
>Assignee: Sarangan Rajamanickam
>  Labels: found-by-ci, triaged
>
> During Apache Cordova CI, we get errors while checking the cordova VMs. They 
> are intermittent. So, we need to add retry logic to the 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] [Commented] (CB-10332) Improve Android Guide

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-10332:
-

Github user rakatyal commented on a diff in the pull request:

https://github.com/apache/cordova-docs/pull/471#discussion_r51802634
  
--- Diff: www/docs/en/dev/guide/platforms/android/index.md ---
@@ -32,276 +32,152 @@ development. For a comparison of the two development 
paths, see the
 
 ## Requirements and Support
 
+### Java Development Kit (JDK)
+
+Install [Java Development Kit (JDK) 
7](http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html)
+or later.
+
+When installing on Windows you also need to set `JAVA_HOME` Environment 
Variable
+according to JDK installation path (for example, `C:\Program 
Files\Java\jdk1.7.0_75`).
+
+### Android SDK
+
 Cordova for Android requires the Android SDK which could be installed
 on OS X, Linux or Windows operation system. See the Android SDK's
 [System 
Requirements](http://developer.android.com/sdk/index.html#Requirements).
-
-Cordova supports Android 4.0.x (starting with Android API level 14)
-and higher.  As a general rule, Android versions become unsupported by 
Cordova as
+Cordova's latest Android package supports up to Android 
[API-Level](http://developer.android.com/guide/topics/manifest/uses-sdk-element.html#ApiLevels)
 23.
+The supported Android API-Levels for the past few cordova-android releases 
can
+be found in this table:
+
+cordova-android Version | Supported Android API-Levels
+|-
+5.X.X   | 14 - 23
+4.1.X   | 14 - 22
+4.0.X   | 10 - 22
+3.7.X   | 10 - 21
+
+Please note that the versions listed here are for Cordova's Android 
package,
+[cordova-android](https://github.com/apache/cordova-android), and not for 
the
+Cordova CLI. To determine what version of Cordova's Android package is 
installed
+in your Cordova project, run the command `cordova platform ls` in the 
directory
+that holds your project.
+
+As a general rule, Android versions become unsupported by Cordova as
 they dip below 5% on Google's
 [distribution 
dashboard](http://developer.android.com/about/dashboards/index.html).
-Android versions earlier than API level 10, and the 3.x versions 
(Honeycomb,
-API levels 11-13) fall significantly below that 5% threshold.
-
-## Install Cordova Shell Tools
-
-If you want to use Cordova's Android-centered shell tools in
-conjunction with the SDK, download Cordova from
-[cordova.apache.org](http://cordova.apache.org). Otherwise ignore this
-section if you plan to use the cross-platform CLI tool described in
-[The Command-Line Interface](../../cli/index.html).
 
-The Cordova download contains separate archives for each platform. Be
-sure to expand the appropriate archive, `android` in this case, within
-an empty directory.  The relevant executible utilities are available
-in the top-level `bin` directory. (Consult the __README__ file if
-necessary for more detailed directions.)
+ Installing the Android SDK
 
-These shell tools allow you to create, build, and run Android apps.
-For information on the additional command-line interface that enables
-plugin features across all platforms, see Using Plugman to Manage
-Plugins. See Application Plugins for details on how to develop
-plugins.
-
-## Install the Java Development Kit (JDK)
-
-Install [Java Development Kit (JDK) 
7](http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html)
-or later. 
-
-When installing on Windows you also need to set `JAVA_HOME` Environment 
Variable
-according to JDK installation path (for example, C:\Program 
Files\Java\jdk1.7.0_75).
-
-## Install the Android SDK
-
-Install the [Android Stand-alone SDK 
Tools](http://developer.android.com/sdk/installing/index.html?pkg=tools) or 
[Android 
Studio](http://developer.android.com/sdk/installing/index.html?pkg=studio). 
Procceed with `Android Studio` if you plan 
+Install the [Android Stand-alone SDK 
Tools](http://developer.android.com/sdk/installing/index.html?pkg=tools) or 
[Android 
Studio](http://developer.android.com/sdk/installing/index.html?pkg=studio).
+Proceed with Android Studio if you plan on
 developing new Cordova for Android plugins or using native tools to
--- End diff --

Yeah all right.


> Improve Android Guide
> -
>
> Key: CB-10332
> URL: https://issues.apache.org/jira/browse/CB-10332
> Project: Apache Cordova
>  

[jira] [Updated] (CB-10283) Displays white bar at the bottom of the android app.

[Ray Shan (JIRA)]

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

Ray Shan updated CB-10283:
--
Affects Version/s: 6.0.0

> Displays white bar at the bottom of the android app.
> 
>
> Key: CB-10283
> URL: https://issues.apache.org/jira/browse/CB-10283
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Android, CordovaLib
>Affects Versions: 6.0.0, 5.3.3
> Environment: Cordova cli 5.3.9 and Cordova 4.1.1
> Android Sumsung s6 (v5.0)
> jquery.mobile-1.4.5.min.js
>Reporter: Devshi Patel
>  Labels: test
>   Original Estimate: 504h
>  Remaining Estimate: 504h
>
> When the app starts it displays a white bar at the bottom of the screen like 
> a status bar. This happens frequently but not always.
> I have been using  Cordova cli 4.2 & Cordova 4.0 without any problems. the 
> app is on google play store. 
> I am using jquery mobile framework version 1.4.5 
> I think the issue is with webview display.
> The code for MainActivity.java file 
>public void onCreate(Bundle savedInstanceState) {
>   super.onCreate(savedInstanceState);
>   super.loadUrl("file:///android_asset/www/index.html");
>   new SimpleEula(this).show(); 
>   }
> index.html
> 
> 



--
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-8804) https://github.com/apache/cordova-plugin-camera#android-quirks

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-8804:


Github user riknoll commented on the pull request:


https://github.com/apache/cordova-plugin-camera/pull/97#issuecomment-179553260
  
@Titoine @adamduren I've got a PR open in cordova-android that should fix 
the `resume` event issues. It should let you subscribe to the `resume` event 
after `deviceready` fires with no issue. Check it out here: 

https://github.com/apache/cordova-android/pull/257

I would love some feedback if you have a chance to try it out. I hope to 
merge it in soon.


> https://github.com/apache/cordova-plugin-camera#android-quirks
> --
>
> Key: CB-8804
> URL: https://issues.apache.org/jira/browse/CB-8804
> Project: Apache Cordova
>  Issue Type: Improvement
>  Components: Plugin Camera
> Environment: Android
>Reporter: Serge Huijben
>  Labels: Android
>
> Android Quirks
> Android uses intents to launch the camera activity on the device to capture 
> images, and on phones with low memory, the Cordova activity may be killed. In 
> this scenario, the image may not appear when the Cordova activity is restored.
> It can be solved bij implementing this PR: 
> https://github.com/apache/cordova-plugin-camera/pull/97



--
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-10461) 'cordova platform ls' should list the versions of platforms pinned

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-10461:
-

Github user TimBarham commented on the pull request:

https://github.com/apache/cordova-lib/pull/376#issuecomment-179511413
  
Looks great! Just one comment: I think just a couple of spaces would look 
better than a tab.

Also, looks like there is a test that is sensitive to the output of this 
command.


> 'cordova platform ls' should list the versions of platforms pinned
> --
>
> Key: CB-10461
> URL: https://issues.apache.org/jira/browse/CB-10461
> Project: Apache Cordova
>  Issue Type: Improvement
>  Components: CordovaLib
>Affects Versions: 6.0.0
>Reporter: Nikhil Khandelwal
>Assignee: Sarangan Rajamanickam
>Priority: Minor
>
> {Code}
> λ cordova platform ls
> Installed platforms: android 5.1.0
> Available platforms: amazon-fireos, blackberry10, browser, firefoxos, webos, 
> windows, windows8, wp8
> {Code}
> It would be great to list the pinned versions for all available platforms 
> here.



--
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-10332) Improve Android Guide

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-10332:
-

Github user rakatyal commented on a diff in the pull request:

https://github.com/apache/cordova-docs/pull/471#discussion_r51801961
  
--- Diff: www/docs/en/dev/guide/platforms/android/index.md ---
@@ -32,276 +32,152 @@ development. For a comparison of the two development 
paths, see the
 
 ## Requirements and Support
 
+### Java Development Kit (JDK)
+
+Install [Java Development Kit (JDK) 
7](http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html)
+or later.
+
+When installing on Windows you also need to set `JAVA_HOME` Environment 
Variable
+according to JDK installation path (for example, `C:\Program 
Files\Java\jdk1.7.0_75`).
+
+### Android SDK
+
 Cordova for Android requires the Android SDK which could be installed
 on OS X, Linux or Windows operation system. See the Android SDK's
 [System 
Requirements](http://developer.android.com/sdk/index.html#Requirements).
-
-Cordova supports Android 4.0.x (starting with Android API level 14)
-and higher.  As a general rule, Android versions become unsupported by 
Cordova as
+Cordova's latest Android package supports up to Android 
[API-Level](http://developer.android.com/guide/topics/manifest/uses-sdk-element.html#ApiLevels)
 23.
+The supported Android API-Levels for the past few cordova-android releases 
can
+be found in this table:
+
+cordova-android Version | Supported Android API-Levels
+|-
+5.X.X   | 14 - 23
+4.1.X   | 14 - 22
+4.0.X   | 10 - 22
+3.7.X   | 10 - 21
+
+Please note that the versions listed here are for Cordova's Android 
package,
+[cordova-android](https://github.com/apache/cordova-android), and not for 
the
+Cordova CLI. To determine what version of Cordova's Android package is 
installed
+in your Cordova project, run the command `cordova platform ls` in the 
directory
+that holds your project.
+
+As a general rule, Android versions become unsupported by Cordova as
 they dip below 5% on Google's
 [distribution 
dashboard](http://developer.android.com/about/dashboards/index.html).
-Android versions earlier than API level 10, and the 3.x versions 
(Honeycomb,
-API levels 11-13) fall significantly below that 5% threshold.
-
-## Install Cordova Shell Tools
-
-If you want to use Cordova's Android-centered shell tools in
-conjunction with the SDK, download Cordova from
-[cordova.apache.org](http://cordova.apache.org). Otherwise ignore this
-section if you plan to use the cross-platform CLI tool described in
-[The Command-Line Interface](../../cli/index.html).
 
-The Cordova download contains separate archives for each platform. Be
-sure to expand the appropriate archive, `android` in this case, within
-an empty directory.  The relevant executible utilities are available
-in the top-level `bin` directory. (Consult the __README__ file if
-necessary for more detailed directions.)
+ Installing the Android SDK
 
-These shell tools allow you to create, build, and run Android apps.
-For information on the additional command-line interface that enables
-plugin features across all platforms, see Using Plugman to Manage
-Plugins. See Application Plugins for details on how to develop
-plugins.
-
-## Install the Java Development Kit (JDK)
-
-Install [Java Development Kit (JDK) 
7](http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html)
-or later. 
-
-When installing on Windows you also need to set `JAVA_HOME` Environment 
Variable
-according to JDK installation path (for example, C:\Program 
Files\Java\jdk1.7.0_75).
-
-## Install the Android SDK
-
-Install the [Android Stand-alone SDK 
Tools](http://developer.android.com/sdk/installing/index.html?pkg=tools) or 
[Android 
Studio](http://developer.android.com/sdk/installing/index.html?pkg=studio). 
Procceed with `Android Studio` if you plan 
+Install the [Android Stand-alone SDK 
Tools](http://developer.android.com/sdk/installing/index.html?pkg=tools) or 
[Android 
Studio](http://developer.android.com/sdk/installing/index.html?pkg=studio).
+Proceed with Android Studio if you plan on
 developing new Cordova for Android plugins or using native tools to
-run and debug Android platform. Otherwise, `Android Stand-alone SDK Tools`
-are enough to build and deploy Android application.
+run and debug the Android platform. Otherwise, the Android Stand-alone SDK 
Tools
+are enough to 

[jira] [Resolved] (CB-10405) Connectivity issue to Cordova VM

[Sarangan Rajamanickam (JIRA)]

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

Sarangan Rajamanickam resolved CB-10405.

Resolution: Fixed

> Connectivity issue to Cordova VM 
> -
>
> Key: CB-10405
> URL: https://issues.apache.org/jira/browse/CB-10405
> Project: Apache Cordova
>  Issue Type: Test
>Reporter: Sarangan Rajamanickam
>Assignee: Sarangan Rajamanickam
>  Labels: found-by-ci, triaged
>
> During Apache Cordova CI, we get errors while checking the cordova VMs. They 
> are intermittent. So, we need to add retry logic to the 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] [Commented] (CB-10332) Improve Android Guide

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-10332:
-

Github user rakatyal commented on a diff in the pull request:

https://github.com/apache/cordova-docs/pull/471#discussion_r51806333
  
--- Diff: www/docs/en/dev/guide/platforms/android/index.md ---
@@ -32,276 +32,152 @@ development. For a comparison of the two development 
paths, see the
 
 ## Requirements and Support
 
+### Java Development Kit (JDK)
+
+Install [Java Development Kit (JDK) 
7](http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html)
+or later.
+
+When installing on Windows you also need to set `JAVA_HOME` Environment 
Variable
+according to JDK installation path (for example, `C:\Program 
Files\Java\jdk1.7.0_75`).
+
+### Android SDK
+
 Cordova for Android requires the Android SDK which could be installed
 on OS X, Linux or Windows operation system. See the Android SDK's
 [System 
Requirements](http://developer.android.com/sdk/index.html#Requirements).
-
-Cordova supports Android 4.0.x (starting with Android API level 14)
-and higher.  As a general rule, Android versions become unsupported by 
Cordova as
+Cordova's latest Android package supports up to Android 
[API-Level](http://developer.android.com/guide/topics/manifest/uses-sdk-element.html#ApiLevels)
 23.
+The supported Android API-Levels for the past few cordova-android releases 
can
+be found in this table:
+
+cordova-android Version | Supported Android API-Levels
+|-
+5.X.X   | 14 - 23
+4.1.X   | 14 - 22
+4.0.X   | 10 - 22
+3.7.X   | 10 - 21
+
+Please note that the versions listed here are for Cordova's Android 
package,
+[cordova-android](https://github.com/apache/cordova-android), and not for 
the
+Cordova CLI. To determine what version of Cordova's Android package is 
installed
+in your Cordova project, run the command `cordova platform ls` in the 
directory
+that holds your project.
+
+As a general rule, Android versions become unsupported by Cordova as
 they dip below 5% on Google's
 [distribution 
dashboard](http://developer.android.com/about/dashboards/index.html).
-Android versions earlier than API level 10, and the 3.x versions 
(Honeycomb,
-API levels 11-13) fall significantly below that 5% threshold.
-
-## Install Cordova Shell Tools
-
-If you want to use Cordova's Android-centered shell tools in
-conjunction with the SDK, download Cordova from
-[cordova.apache.org](http://cordova.apache.org). Otherwise ignore this
-section if you plan to use the cross-platform CLI tool described in
-[The Command-Line Interface](../../cli/index.html).
 
-The Cordova download contains separate archives for each platform. Be
-sure to expand the appropriate archive, `android` in this case, within
-an empty directory.  The relevant executible utilities are available
-in the top-level `bin` directory. (Consult the __README__ file if
-necessary for more detailed directions.)
+ Installing the Android SDK
 
-These shell tools allow you to create, build, and run Android apps.
-For information on the additional command-line interface that enables
-plugin features across all platforms, see Using Plugman to Manage
-Plugins. See Application Plugins for details on how to develop
-plugins.
-
-## Install the Java Development Kit (JDK)
-
-Install [Java Development Kit (JDK) 
7](http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html)
-or later. 
-
-When installing on Windows you also need to set `JAVA_HOME` Environment 
Variable
-according to JDK installation path (for example, C:\Program 
Files\Java\jdk1.7.0_75).
-
-## Install the Android SDK
-
-Install the [Android Stand-alone SDK 
Tools](http://developer.android.com/sdk/installing/index.html?pkg=tools) or 
[Android 
Studio](http://developer.android.com/sdk/installing/index.html?pkg=studio). 
Procceed with `Android Studio` if you plan 
+Install the [Android Stand-alone SDK 
Tools](http://developer.android.com/sdk/installing/index.html?pkg=tools) or 
[Android 
Studio](http://developer.android.com/sdk/installing/index.html?pkg=studio).
+Proceed with Android Studio if you plan on
 developing new Cordova for Android plugins or using native tools to
-run and debug Android platform. Otherwise, `Android Stand-alone SDK Tools`
-are enough to build and deploy Android application.
+run and debug the Android platform. Otherwise, the Android Stand-alone SDK 
Tools
+are enough to 

[jira] [Commented] (CB-10269) [iOS 8] cordova-plugin-wkwebview-engine breaks Cordova iOS 4.0.0 under iOS 8

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-10269:
-

Github user hassankhan commented on the pull request:


https://github.com/apache/cordova-plugin-wkwebview-engine/pull/3#issuecomment-179556132
  
Is it possible for a new release to be tagged?


> [iOS 8] cordova-plugin-wkwebview-engine breaks Cordova iOS 4.0.0 under iOS 8
> 
>
> Key: CB-10269
> URL: https://issues.apache.org/jira/browse/CB-10269
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Plugin WKWebViewEngine
>Affects Versions: 4.0.0
> Environment: Cordova tools 5.4.1
> Cordova iOS platform 4.0.1
> iOS Simulator 8.4
> cordova-plugin-wkwebview-engine plugin
>Reporter: Ivan Karpan
>Assignee: Shazron Abdullah
>Priority: Critical
>  Labels: cordova-ios-4.1.0, triaged
> Attachments: ios-wkwebview-exec.js
>
>
> When launching on iOS 8.4 simulator the following error breaks JS execution 
> early on:
> ios-wkwebview-exec.js:127 TypeError: undefined is not an object (evaluating 
> 'window.webkit.messageHandlers')
> So inclusion of 'cordova-plugin-wkwebview-engine' plugin breaks support of 
> iOS versions previous to 9.0. I assume ios-wkwebview-exec.js should have 
> environment checks before using WKWebView bridge...
> Exclusion of the same plugin breaks the project at all. Are there any 
> fallback mechanics in place?



--
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-10269) [iOS 8] cordova-plugin-wkwebview-engine breaks Cordova iOS 4.0.0 under iOS 8

[Shazron Abdullah (JIRA)]

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

Shazron Abdullah commented on CB-10269:
---

Eventually.
For now you can just:
{code}
cordova plugin add 
https://github.com/apache/cordova-plugin-wkwebview-engine.git#master
{code}

Replace master in #master with a commit SHA etc, branch, but since its in 
master you're fine for now

> [iOS 8] cordova-plugin-wkwebview-engine breaks Cordova iOS 4.0.0 under iOS 8
> 
>
> Key: CB-10269
> URL: https://issues.apache.org/jira/browse/CB-10269
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Plugin WKWebViewEngine
>Affects Versions: 4.0.0
> Environment: Cordova tools 5.4.1
> Cordova iOS platform 4.0.1
> iOS Simulator 8.4
> cordova-plugin-wkwebview-engine plugin
>Reporter: Ivan Karpan
>Assignee: Shazron Abdullah
>Priority: Critical
>  Labels: cordova-ios-4.1.0, triaged
> Attachments: ios-wkwebview-exec.js
>
>
> When launching on iOS 8.4 simulator the following error breaks JS execution 
> early on:
> ios-wkwebview-exec.js:127 TypeError: undefined is not an object (evaluating 
> 'window.webkit.messageHandlers')
> So inclusion of 'cordova-plugin-wkwebview-engine' plugin breaks support of 
> iOS versions previous to 9.0. I assume ios-wkwebview-exec.js should have 
> environment checks before using WKWebView bridge...
> Exclusion of the same plugin breaks the project at all. Are there any 
> fallback mechanics in place?



--
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-10527) fileEntry.file function does not work with some files names

[Ibrahim Aboelsuod (JIRA)]

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

Ibrahim Aboelsuod updated CB-10527:
---
Description: 
The following code will always rise "not found" error if:
the file name contain the letter '#' and maybe some other letters
{quote}
fileEntry.file(function(file){
alert(file.name);
},error);
{quote}
I cant really think of any workaround, and this function is required to use the 
bolb in un-ziping for example.

  was:
The following code will always rise "not found" error if:
the file name contain the letter '#' -and maybe some other letters-
{quote}
fileEntry.file(function(file){
alert(file.name);
},error);
{quote}
I cant really think of any workaround, and this function is required to use the 
bolb in un-ziping for example.


> fileEntry.file function does not work with some files names
> ---
>
> Key: CB-10527
> URL: https://issues.apache.org/jira/browse/CB-10527
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Plugin File
> Environment: android
>Reporter: Ibrahim Aboelsuod
>
> The following code will always rise "not found" error if:
> the file name contain the letter '#' and maybe some other letters
> {quote}
> fileEntry.file(function(file){
>   alert(file.name);
> },error);
> {quote}
> I cant really think of any workaround, and this function is required to use 
> the bolb in un-ziping for example.



--
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-10474) Gathering logs fails in cordova-ios CI

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on CB-10474:
--

Commit 50d20dca3173fd658c09b104c086b81c4ef64163 in cordova-medic's branch 
refs/heads/master from Richard Knoll
[ https://git-wip-us.apache.org/repos/asf?p=cordova-medic.git;h=50d20dc ]

CB-10474: Fix medic-log behavior for cordova-ios. Adding --app flag to 
medic-log for iOS. This closes #73.


> Gathering logs fails in cordova-ios CI
> --
>
> Key: CB-10474
> URL: https://issues.apache.org/jira/browse/CB-10474
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Medic
> Environment: OSX
>Reporter: Richard B Knoll
>Assignee: Richard B Knoll
>  Labels: found-by-ci, ios, triaged
>
> In the cordova-ios Build Bot CI, the gathering logs step always fails. It 
> tries to {{cat}} a file for the log that does not exist. Here is an example 
> build: 
> https://ci.apache.org/builders/cordova-ios/builds/1607/steps/gathering-logs/logs/stdio



--
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-10474) Gathering logs fails in cordova-ios CI

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-10474:
-

Github user asfgit closed the pull request at:

https://github.com/apache/cordova-medic/pull/73


> Gathering logs fails in cordova-ios CI
> --
>
> Key: CB-10474
> URL: https://issues.apache.org/jira/browse/CB-10474
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Medic
> Environment: OSX
>Reporter: Richard B Knoll
>Assignee: Richard B Knoll
>  Labels: found-by-ci, ios, triaged
>
> In the cordova-ios Build Bot CI, the gathering logs step always fails. It 
> tries to {{cat}} a file for the log that does not exist. Here is an example 
> build: 
> https://ci.apache.org/builders/cordova-ios/builds/1607/steps/gathering-logs/logs/stdio



--
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-10527) fileEntry.file function does not work with some files names

[Ibrahim Aboelsuod (JIRA)]

Ibrahim Aboelsuod created CB-10527:
--

 Summary: fileEntry.file function does not work with some files 
names
 Key: CB-10527
 URL: https://issues.apache.org/jira/browse/CB-10527
 Project: Apache Cordova
  Issue Type: Bug
  Components: Plugin File
 Environment: android
Reporter: Ibrahim Aboelsuod


The following code will always rise "not found" error if:
the file name contain the letter '#' -and maybe some other letters-
{quote}
fileEntry.file(function(file){
alert(file.name);
},error);
{quote}
I cant really think of any workaround, and this function is required to use the 
bolb in un-ziping for example.



--
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-10517) Inappbrowser crashes browserified app on Android

[Sergey Grebnov (JIRA)]

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

Sergey Grebnov reassigned CB-10517:
---

Assignee: Sergey Grebnov

> Inappbrowser crashes browserified app on Android
> 
>
> Key: CB-10517
> URL: https://issues.apache.org/jira/browse/CB-10517
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Plugin InAppBrowser
>Affects Versions: Master
>Reporter: Alexander Sorokin
>Assignee: Sergey Grebnov
>
> * create mobilespec app with inappbrowser plugin
> * run it with "cordova run android --browserify"
> * go to manual inappbrowser tests
> * click one of the buttons with "target=Random"
> * inappbrowser loads the page successfully
> * clik one of the buttons with "target=Random" again
> * the app crashes



--
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-7500) executeScript with callback kills/blurs inAppBrowser window after callback exit

[Sergey Grebnov (JIRA)]

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

Sergey Grebnov reassigned CB-7500:
--

Assignee: Sergey Grebnov

> executeScript with callback kills/blurs inAppBrowser window after callback 
> exit
> ---
>
> Key: CB-7500
> URL: https://issues.apache.org/jira/browse/CB-7500
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Plugin InAppBrowser
>Affects Versions: 3.5.0
> Environment: Android 4.4.2 Samsung Galaxy Tab S
>Reporter: Andreas Imhof
>Assignee: Sergey Grebnov
>  Labels: Android, Triaged, patch
>   Original Estimate: 20m
>  Remaining Estimate: 20m
>
> Calling Javascript executeScript (inAppBrowser.js) WITH a callback into an 
> inAppBrowser window kills/blurs this IAB window after the callback exits. 
> Something like this also is mentioned in the author's comment in method 
> 'injectDeferredObject' in 'inAppBrowser.java' on line 254.
> After inverstigating, I accidentally found a work-around/solution which 
> helped on my Android 4.4.2 Samsung Galagy Tab S.
> SOLUTION:
> In 'inAppBrowser.java' on line 162:
> jsWrapper = String.format("prompt(JSON.stringify([eval(%%s)]), 
> 'gap-iab://%s')", callbackContext.getCallbackId());
> the 'prompt' statement should be assigned to a variable like:
> jsWrapper = String.format("var r=prompt(JSON.stringify([eval(%%s)]), 
> 'gap-iab://%s')", callbackContext.getCallbackId());
> Adding 'var r=' prevents from InAppBrowser window being killed. 
> Don't know why. Tell me...   :-)



--
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-10517) Inappbrowser crashes browserified app on Android

[Sergey Grebnov (JIRA)]

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

Sergey Grebnov updated CB-10517:

Labels: Android Triaged reproduced  (was: )

> Inappbrowser crashes browserified app on Android
> 
>
> Key: CB-10517
> URL: https://issues.apache.org/jira/browse/CB-10517
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Plugin InAppBrowser
>Affects Versions: Master
>Reporter: Alexander Sorokin
>Assignee: Sergey Grebnov
>  Labels: Android, Triaged, reproduced
>
> * create mobilespec app with inappbrowser plugin
> * run it with "cordova run android --browserify"
> * go to manual inappbrowser tests
> * click one of the buttons with "target=Random"
> * inappbrowser loads the page successfully
> * clik one of the buttons with "target=Random" again
> * the app crashes



--
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-10466) My payment link not working in cordova inappbrowser in windows phone

[Sergey Grebnov (JIRA)]

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

Sergey Grebnov reassigned CB-10466:
---

Assignee: Sergey Grebnov

> My payment link not working in cordova inappbrowser in windows phone
> 
>
> Key: CB-10466
> URL: https://issues.apache.org/jira/browse/CB-10466
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Plugin InAppBrowser
>Affects Versions: 1.2.0
> Environment: Windows phone 8.1
>Reporter: Sam Deepak
>Assignee: Sergey Grebnov
>  Labels: cordova, inappbrowser, triaged, windows
>
> I am using InAppBrowser to load the payment link and let the user pay for the 
> product. Now this link flawlessly works in Android. But in Windows phone, it 
> does not work i.e., certain scripts create error due to which the user could 
> not proceed with payment link. 
> The link works in IE or Edge browser from the same windows phone. It occurs 
> only in InAppBrowser.
> My Test payment Link: 
> https://www.instamojo.com/bytesevolution/how-much-app-for-civil-construction-estimati/.
> Please look at the android screen where it shows expanded view of details 
> (name, email, phone ) when clicked on "Get it now" button, whereas if you 
> look  at the windows phone screen, it does not expand the details view at 
> all. 
>  
> I am using Cordova inappbrowser latest version (1.2.0) to load this payment 
> link in both android and windows phone. Please help me why it does not work 
> in windows phones.



--
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-10395) InAppBrowser's WebView not storing cookies reliable to local device storage

[Sergey Grebnov (JIRA)]

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

Sergey Grebnov reassigned CB-10395:
---

Assignee: Sergey Grebnov

> InAppBrowser's WebView not storing cookies reliable to local device storage
> ---
>
> Key: CB-10395
> URL: https://issues.apache.org/jira/browse/CB-10395
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Plugin InAppBrowser
>Affects Versions: 1.1.0
> Environment: Android-22
>Reporter: Wolfram Kriesing
>Assignee: Sergey Grebnov
>  Labels: Android, Triaged
>
> we are simply embedding our website http://crewmeister.com/app using 
> `cordova.InAppBrowser.open()` looking at the sqlite storage on the device I 
> was able to reproduce that our server-side rails cookies are not stored 
> reliably in the cookie storage (the sqlite file under 
> /data/data/com.crewmeister.app/app_webview/Cookie on the device)
> I saw that the cookie was updated seemingly just sometimes by accident, I was 
> guessing that webkit's `CookieManager.flush()` might need to be called at 
> least upon closing the app (so cookies survive across sessions).
> I have read multiple complaints from other people online too but am not able 
> to fix it. Any hints or even fixes would be greatly appreciated.
> I guess somewhere in here the fix needs to take place 
> https://github.com/apache/cordova-plugin-inappbrowser/blob/master/src%2Fandroid%2FInAppBrowser.java
>  ...
> Thanks, Wolfram



--
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-10396) Implement test runner for Appium tests for core plugins

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-10396:
-

Github user sgrebnov commented on the pull request:

https://github.com/apache/cordova-medic/pull/70#issuecomment-179332769
  
lgtm


> Implement test runner for Appium tests for core plugins
> ---
>
> Key: CB-10396
> URL: https://issues.apache.org/jira/browse/CB-10396
> Project: Apache Cordova
>  Issue Type: Task
>  Components: Medic
>Reporter: Alexander Sorokin
>Assignee: Alexander Sorokin
>
> Implement test runner in form of medic command.
> Test runned should be able to start appium server and run appium tests 
> located in core plugins repos on both Android/iOS devices and emulators.



--
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-10332) Improve Android Guide

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-10332:
-

Github user rakatyal commented on a diff in the pull request:

https://github.com/apache/cordova-docs/pull/471#discussion_r51800700
  
--- Diff: www/docs/en/dev/guide/platforms/android/index.md ---
@@ -32,276 +32,152 @@ development. For a comparison of the two development 
paths, see the
 
 ## Requirements and Support
 
+### Java Development Kit (JDK)
+
+Install [Java Development Kit (JDK) 
7](http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html)
+or later.
+
+When installing on Windows you also need to set `JAVA_HOME` Environment 
Variable
+according to JDK installation path (for example, `C:\Program 
Files\Java\jdk1.7.0_75`).
+
+### Android SDK
+
 Cordova for Android requires the Android SDK which could be installed
 on OS X, Linux or Windows operation system. See the Android SDK's
 [System 
Requirements](http://developer.android.com/sdk/index.html#Requirements).
-
-Cordova supports Android 4.0.x (starting with Android API level 14)
-and higher.  As a general rule, Android versions become unsupported by 
Cordova as
+Cordova's latest Android package supports up to Android 
[API-Level](http://developer.android.com/guide/topics/manifest/uses-sdk-element.html#ApiLevels)
 23.
+The supported Android API-Levels for the past few cordova-android releases 
can
+be found in this table:
+
+cordova-android Version | Supported Android API-Levels
+|-
+5.X.X   | 14 - 23
+4.1.X   | 14 - 22
+4.0.X   | 10 - 22
+3.7.X   | 10 - 21
+
+Please note that the versions listed here are for Cordova's Android 
package,
+[cordova-android](https://github.com/apache/cordova-android), and not for 
the
+Cordova CLI. To determine what version of Cordova's Android package is 
installed
+in your Cordova project, run the command `cordova platform ls` in the 
directory
+that holds your project.
+
+As a general rule, Android versions become unsupported by Cordova as
 they dip below 5% on Google's
 [distribution 
dashboard](http://developer.android.com/about/dashboards/index.html).
-Android versions earlier than API level 10, and the 3.x versions 
(Honeycomb,
-API levels 11-13) fall significantly below that 5% threshold.
-
-## Install Cordova Shell Tools
-
-If you want to use Cordova's Android-centered shell tools in
-conjunction with the SDK, download Cordova from
-[cordova.apache.org](http://cordova.apache.org). Otherwise ignore this
-section if you plan to use the cross-platform CLI tool described in
-[The Command-Line Interface](../../cli/index.html).
 
-The Cordova download contains separate archives for each platform. Be
-sure to expand the appropriate archive, `android` in this case, within
-an empty directory.  The relevant executible utilities are available
-in the top-level `bin` directory. (Consult the __README__ file if
-necessary for more detailed directions.)
+ Installing the Android SDK
 
-These shell tools allow you to create, build, and run Android apps.
-For information on the additional command-line interface that enables
-plugin features across all platforms, see Using Plugman to Manage
-Plugins. See Application Plugins for details on how to develop
-plugins.
-
-## Install the Java Development Kit (JDK)
-
-Install [Java Development Kit (JDK) 
7](http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html)
-or later. 
-
-When installing on Windows you also need to set `JAVA_HOME` Environment 
Variable
-according to JDK installation path (for example, C:\Program 
Files\Java\jdk1.7.0_75).
-
-## Install the Android SDK
-
-Install the [Android Stand-alone SDK 
Tools](http://developer.android.com/sdk/installing/index.html?pkg=tools) or 
[Android 
Studio](http://developer.android.com/sdk/installing/index.html?pkg=studio). 
Procceed with `Android Studio` if you plan 
+Install the [Android Stand-alone SDK 
Tools](http://developer.android.com/sdk/installing/index.html?pkg=tools) or 
[Android 
Studio](http://developer.android.com/sdk/installing/index.html?pkg=studio).
+Proceed with Android Studio if you plan on
 developing new Cordova for Android plugins or using native tools to
--- End diff --

new Cordova apps or Android plugins?


> Improve Android Guide
> -
>
> Key: CB-10332
> URL: https://issues.apache.org/jira/browse/CB-10332
> Project: 

[jira] [Commented] (CB-10332) Improve Android Guide

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-10332:
-

Github user riknoll commented on a diff in the pull request:

https://github.com/apache/cordova-docs/pull/471#discussion_r51802869
  
--- Diff: www/docs/en/dev/guide/platforms/android/index.md ---
@@ -32,276 +32,152 @@ development. For a comparison of the two development 
paths, see the
 
 ## Requirements and Support
 
+### Java Development Kit (JDK)
+
+Install [Java Development Kit (JDK) 
7](http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html)
+or later.
+
+When installing on Windows you also need to set `JAVA_HOME` Environment 
Variable
+according to JDK installation path (for example, `C:\Program 
Files\Java\jdk1.7.0_75`).
+
+### Android SDK
+
 Cordova for Android requires the Android SDK which could be installed
 on OS X, Linux or Windows operation system. See the Android SDK's
 [System 
Requirements](http://developer.android.com/sdk/index.html#Requirements).
-
-Cordova supports Android 4.0.x (starting with Android API level 14)
-and higher.  As a general rule, Android versions become unsupported by 
Cordova as
+Cordova's latest Android package supports up to Android 
[API-Level](http://developer.android.com/guide/topics/manifest/uses-sdk-element.html#ApiLevels)
 23.
+The supported Android API-Levels for the past few cordova-android releases 
can
+be found in this table:
+
+cordova-android Version | Supported Android API-Levels
+|-
+5.X.X   | 14 - 23
+4.1.X   | 14 - 22
+4.0.X   | 10 - 22
+3.7.X   | 10 - 21
+
+Please note that the versions listed here are for Cordova's Android 
package,
+[cordova-android](https://github.com/apache/cordova-android), and not for 
the
+Cordova CLI. To determine what version of Cordova's Android package is 
installed
+in your Cordova project, run the command `cordova platform ls` in the 
directory
+that holds your project.
+
+As a general rule, Android versions become unsupported by Cordova as
 they dip below 5% on Google's
 [distribution 
dashboard](http://developer.android.com/about/dashboards/index.html).
-Android versions earlier than API level 10, and the 3.x versions 
(Honeycomb,
-API levels 11-13) fall significantly below that 5% threshold.
-
-## Install Cordova Shell Tools
-
-If you want to use Cordova's Android-centered shell tools in
-conjunction with the SDK, download Cordova from
-[cordova.apache.org](http://cordova.apache.org). Otherwise ignore this
-section if you plan to use the cross-platform CLI tool described in
-[The Command-Line Interface](../../cli/index.html).
 
-The Cordova download contains separate archives for each platform. Be
-sure to expand the appropriate archive, `android` in this case, within
-an empty directory.  The relevant executible utilities are available
-in the top-level `bin` directory. (Consult the __README__ file if
-necessary for more detailed directions.)
+ Installing the Android SDK
 
-These shell tools allow you to create, build, and run Android apps.
-For information on the additional command-line interface that enables
-plugin features across all platforms, see Using Plugman to Manage
-Plugins. See Application Plugins for details on how to develop
-plugins.
-
-## Install the Java Development Kit (JDK)
-
-Install [Java Development Kit (JDK) 
7](http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html)
-or later. 
-
-When installing on Windows you also need to set `JAVA_HOME` Environment 
Variable
-according to JDK installation path (for example, C:\Program 
Files\Java\jdk1.7.0_75).
-
-## Install the Android SDK
-
-Install the [Android Stand-alone SDK 
Tools](http://developer.android.com/sdk/installing/index.html?pkg=tools) or 
[Android 
Studio](http://developer.android.com/sdk/installing/index.html?pkg=studio). 
Procceed with `Android Studio` if you plan 
+Install the [Android Stand-alone SDK 
Tools](http://developer.android.com/sdk/installing/index.html?pkg=tools) or 
[Android 
Studio](http://developer.android.com/sdk/installing/index.html?pkg=studio).
+Proceed with Android Studio if you plan on
 developing new Cordova for Android plugins or using native tools to
-run and debug Android platform. Otherwise, `Android Stand-alone SDK Tools`
-are enough to build and deploy Android application.
+run and debug the Android platform. Otherwise, the Android Stand-alone SDK 
Tools
+are enough to build