[jira] [Commented] (CB-10364) Make Plugin Specification (plugin.xml) page a reference

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-10364:
-

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

https://github.com/apache/cordova-docs/pull/474#discussion_r51471937
  
--- Diff: www/docs/en/dev/plugin_ref/spec.md ---
@@ -17,700 +17,489 @@ license: >
 specific language governing permissions and limitations
 under the License.
 
-title: Plugin Specification
+title: Plugin.xml
 ---
 
-# Plugin Specification
-
-The `plugin.xml` file is an XML document in the `plugins` namespace:
-`http://apache.org/cordova/ns/plugins/1.0`. It contains a top-level
-`plugin` element that defines the plugin, and children that define the
-structure of the plugin.
-
-A sample plugin element:
+# Plugin.xml
 
-
-http://apache.org/cordova/ns/plugins/1.0;
-xmlns:android="http://schemas.android.com/apk/res/android;
-id="com.alunny.foo"
-version="1.0.2">
+Plugin.xml file defines the structure and settings required for your 
plugin. It has several elements to provide details about your plugin.
 
-## _plugin_ Element
+## plugin
 
-The `plugin` element is the plugin manifest's top-level element. It
-features the following attributes:
+  The `plugin` element is the plugin manifest's top-level element.
 
-* `xmlns` (required):
-  The plugin namespace, `http://apache.org/cordova/ns/plugins/1.0`. If
-  the document contains XML from other namespaces, such as tags to be
-  added to the `AndroidManifest.xml` file, those namespaces should
-  also be included in the top-level element.
+  Attributes(type) | Description
+   | 
+  xmlns(string) | *Required*  The plugin namespace, 
`http://apache.org/cordova/ns/plugins/1.0`. If the document contains XML from 
other namespaces, such as tags to be added to the `AndroidManifest.xml` file, 
those namespaces should also be included in the  element.
+  id(string) | *Required*  A reverse-domain style identifier for the 
plugin.
+  version(string) | *Required*  A version number for the plugin, that 
matches the following major-minor-patch style regular expression: 
`^\d+[.]\d+[.]\d+$`
 
-* `id` (required):
-  A reverse-domain style identifier for the plugin, such as
-  `com.alunny.foo`
+  Example:
+  ```
+  
+  http://apache.org/cordova/ns/plugins/1.0;
+  xmlns:android="http://schemas.android.com/apk/res/android;
+  id="com.alunny.foo"
+  version="1.0.2">
+  ```
 
-* `version` (required):
-  A version number for the plugin, that matches the following
-  major-minor-patch style regular expression:
+### engines and engine
 
-^\d+[.]\d+[.]\d+$
+  The child elements of the `` element specify versions of Apache 
Cordova-based frameworks that this plugin supports. Plugman aborts with a 
non-zero code for any plugin whose target project does not meet the engine's 
constraints. If no  tags are specified, plugman attempts to install 
into the specified cordova project directory blindly.
 
-## _engines_ and _engine_ Elements
+  Attributes(type) | Description
+   | 
+  name(string) | *Required*  Name of the engine. Here are the default 
engines that are supported :  `cordova`   `cordova-plugman` 
  `cordova-android`   `cordova-ios`   
`cordova-blackberry10`   `cordova-wp8`   `cordova-windows` 
  `android-sdk` // returns the highest Android api level installed 
  `apple-xcode` // returns the xcode version   `apple-ios` // 
returns the highest iOS version installed   `apple-osx` // returns the 
OSX version   `blackberry-ndk` // returns the native blackberry SDK 
version  You can also specify a custom framework apart from the default 
ones.
+  version(string) | *Required*  The version that your framework must 
have in order to install. It should match a major-minor-patch string conforming 
to the regular expression: `^\d+[.]\d+[.]\d+$`
+  scriptSrc(string) | **For custom frameworks only**  *Required* 
  The script file that tells plugman the version of the custom framework. 
Ideally, this file should be within the top level directory of your plugin 
directory.
+  platform(string) | **For custom frameworks only**  *Required*  
The platforms your framework supports. You may use the wildcard `*` to say 
supported for all platforms, specify multiple with a pipe character like 
`android|ios|blackberry10` or just a single platform like `android`.
 
-The child elements of the `` element specify versions of
-Apache Cordova-based frameworks that this plugin supports. An example:
+  Examples:
+  ```
+  
+

[jira] [Commented] (CB-10364) Make Plugin Specification (plugin.xml) page a reference

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-10364:
-

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

https://github.com/apache/cordova-docs/pull/474#discussion_r51471311
  
--- Diff: www/docs/en/dev/plugin_ref/spec.md ---
@@ -17,700 +17,489 @@ license: >
 specific language governing permissions and limitations
 under the License.
 
-title: Plugin Specification
+title: Plugin.xml
 ---
 
-# Plugin Specification
-
-The `plugin.xml` file is an XML document in the `plugins` namespace:
-`http://apache.org/cordova/ns/plugins/1.0`. It contains a top-level
-`plugin` element that defines the plugin, and children that define the
-structure of the plugin.
-
-A sample plugin element:
+# Plugin.xml
 
-
-http://apache.org/cordova/ns/plugins/1.0;
-xmlns:android="http://schemas.android.com/apk/res/android;
-id="com.alunny.foo"
-version="1.0.2">
+Plugin.xml file defines the structure and settings required for your 
plugin. It has several elements to provide details about your plugin.
 
-## _plugin_ Element
+## plugin
 
-The `plugin` element is the plugin manifest's top-level element. It
-features the following attributes:
+  The `plugin` element is the plugin manifest's top-level element.
 
-* `xmlns` (required):
-  The plugin namespace, `http://apache.org/cordova/ns/plugins/1.0`. If
-  the document contains XML from other namespaces, such as tags to be
-  added to the `AndroidManifest.xml` file, those namespaces should
-  also be included in the top-level element.
+  Attributes(type) | Description
+   | 
+  xmlns(string) | *Required*  The plugin namespace, 
`http://apache.org/cordova/ns/plugins/1.0`. If the document contains XML from 
other namespaces, such as tags to be added to the `AndroidManifest.xml` file, 
those namespaces should also be included in the  element.
+  id(string) | *Required*  A reverse-domain style identifier for the 
plugin.
+  version(string) | *Required*  A version number for the plugin, that 
matches the following major-minor-patch style regular expression: 
`^\d+[.]\d+[.]\d+$`
 
-* `id` (required):
-  A reverse-domain style identifier for the plugin, such as
-  `com.alunny.foo`
+  Example:
+  ```
+  
+  http://apache.org/cordova/ns/plugins/1.0;
+  xmlns:android="http://schemas.android.com/apk/res/android;
+  id="com.alunny.foo"
+  version="1.0.2">
+  ```
 
-* `version` (required):
-  A version number for the plugin, that matches the following
-  major-minor-patch style regular expression:
+### engines and engine
 
-^\d+[.]\d+[.]\d+$
+  The child elements of the `` element specify versions of Apache 
Cordova-based frameworks that this plugin supports. Plugman aborts with a 
non-zero code for any plugin whose target project does not meet the engine's 
constraints. If no  tags are specified, plugman attempts to install 
into the specified cordova project directory blindly.
 
-## _engines_ and _engine_ Elements
+  Attributes(type) | Description
+   | 
+  name(string) | *Required*  Name of the engine. Here are the default 
engines that are supported :  `cordova`   `cordova-plugman` 
  `cordova-android`   `cordova-ios`   
`cordova-blackberry10`   `cordova-wp8`   `cordova-windows` 
  `android-sdk` // returns the highest Android api level installed 
  `apple-xcode` // returns the xcode version   `apple-ios` // 
returns the highest iOS version installed   `apple-osx` // returns the 
OSX version   `blackberry-ndk` // returns the native blackberry SDK 
version  You can also specify a custom framework apart from the default 
ones.
+  version(string) | *Required*  The version that your framework must 
have in order to install. It should match a major-minor-patch string conforming 
to the regular expression: `^\d+[.]\d+[.]\d+$`
+  scriptSrc(string) | **For custom frameworks only**  *Required* 
  The script file that tells plugman the version of the custom framework. 
Ideally, this file should be within the top level directory of your plugin 
directory.
+  platform(string) | **For custom frameworks only**  *Required*  
The platforms your framework supports. You may use the wildcard `*` to say 
supported for all platforms, specify multiple with a pipe character like 
`android|ios|blackberry10` or just a single platform like `android`.
 
-The child elements of the `` element specify versions of
-Apache Cordova-based frameworks that this plugin supports. An example:
+  Examples:
+  ```
+  
+

[jira] [Resolved] (CB-10485) Cordova-iOS still creates projects with the whitelist plugin at version 1

[Shazron Abdullah (JIRA)]

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

Shazron Abdullah resolved CB-10485.
---
Resolution: Not A Problem

The plugin itself does not have any iOS platform, it does not install anything 
for ios. It is added to config.xml because it is part of the template and is 
needed for other platforms (in this case, Android only)

> Cordova-iOS still creates projects with the whitelist plugin at version 1
> -
>
> Key: CB-10485
> URL: https://issues.apache.org/jira/browse/CB-10485
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: iOS
>Affects Versions: 6.0.0
> Environment: Cordova 6.0.0
> Cordova iOS 4.0.1
>Reporter: Jon Akhtar
>Priority: Minor
>  Labels: triaged, wfc
>
> When creating a new project, and then adding the iOS platform the config.xml 
> adds the following line:
> 
> This plugin is not needed for iOS 4.0.1



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

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

[jira] [Created] (CB-10500) cordova restore/prepare CPR plugin fails silently

[Steve Gill (JIRA)]

Steve Gill created CB-10500:
---

 Summary: cordova restore/prepare CPR plugin fails silently
 Key: CB-10500
 URL: https://issues.apache.org/jira/browse/CB-10500
 Project: Apache Cordova
  Issue Type: Bug
  Components: CordovaLib
Affects Versions: 6.0.0
Reporter: Steve Gill
Assignee: Steve Gill
 Fix For: 6.0.1


add the following line to your config.xml

{code:xml}

{code}

do cordova prepare and you will notice get these two lines

{code}
Discovered plugin "com.pushwoosh.plugins.pushwoosh" in config.xml. Installing 
to the project
Fetching plugin "com.pushwoosh.plugins.pushwoosh@~4.1.0" via npm
{code}

Problem is, that plugin doesn't get installed and doesn't actually get fetched 
because it doesn't exist on npm. It is failing silently.

If I add the plugin via `cordova plugin add 
com.pushwoosh.plugins.pushwoosh@~4.1.0`, I get the error message:

Error: Failed to fetch plugin com.pushwoosh.plugins.pushwoosh@~4.1.0 via 
registry.
Probably this is either a connection problem, or plugin spec is incorrect.
Check your connection and plugin name/version/URL.
Error: Registry returned 404 for GET on 
https://registry.npmjs.org/com.pushwoosh.plugins.pushwoosh

Seems to me it is a problem with save restore work not catching the error 
message. 



--
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-10499) --template should pull the latest template from NPM when version isn't specified

[ASF subversion and git services (JIRA)]

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

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

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

CB-10499 - --template should pull the latest template from NPM when
version isn't specified

- Pull the latest template if no version is specified
- Rename NPM to npm
- Rename Git to git

rename github to git

This close #372 #373


> --template should pull the latest template from NPM when version isn't 
> specified
> 
>
> Key: CB-10499
> URL: https://issues.apache.org/jira/browse/CB-10499
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: CordovaLib
>Affects Versions: Master
>Reporter: James Dubee
>Priority: Minor
>
> The latest template isn't always downloaded when @latest isn't specified when 
> using --template to create an app.



--
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-10499) --template should pull the latest template from NPM when version isn't specified

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-10499:
-

Github user asfgit closed the pull request at:

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


> --template should pull the latest template from NPM when version isn't 
> specified
> 
>
> Key: CB-10499
> URL: https://issues.apache.org/jira/browse/CB-10499
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: CordovaLib
>Affects Versions: Master
>Reporter: James Dubee
>Priority: Minor
>
> The latest template isn't always downloaded when @latest isn't specified when 
> using --template to create an app.



--
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-10270) camera.getPicture() returns an empty string

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-10270:
-

GitHub user riknoll opened a pull request:

https://github.com/apache/cordova-plugin-camera/pull/160

CB-10270 android: Added back support for file:// URIs to getRealPath

Our `getRealPath()` function is unable to handle `file: //` URIs, which can 
occasionally lead it to return an empty string for the result URI. These camera 
options reproduce when you select an image from the Gallery app:
```
{
destinationType: Camera.DestinationType.FILE_URI,
sourceType: Camera.PictureSourceType.PHOTOLIBRARY,
allowEdit: true,
correctOrientation: true
}
```
I believe that we used to do something similar to this, but it was removed 
at some point in the past. @infil00p do you have any idea why that was?

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

$ git pull https://github.com/MSOpenTech/cordova-plugin-camera CB-10270

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

https://github.com/apache/cordova-plugin-camera/pull/160.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 #160


commit ee06d3efb233d5404d0aeda2abe08e6fd765c7fe
Author: riknoll 
Date:   2016-01-29T23:47:00Z

CB-10270 android: Added back support for file:// URIs to getRealPath




> camera.getPicture() returns an empty string
> ---
>
> Key: CB-10270
> URL: https://issues.apache.org/jira/browse/CB-10270
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Plugin Camera
>Affects Versions: 2.1.0
> Environment: Android 4.4.2 (api 19)
>Reporter: Alexander Sorokin
>Assignee: Richard B Knoll
>Priority: Critical
>  Labels: android, reproduced, triaged
> Attachments: mobilespec-camera.7z
>
>
> Code sample to reproduce:
> {code}
> navigator.camera.getPicture(onSuccess, onFail, { 
> destinationType: Camera.DestinationType.FILE_URI,
> sourceType: Camera.PictureSourceType.PHOTOLIBRARY,
> correctOrientation: true
> });
> {code}
> {{onSuccess}} is called with an empty string as an argument.
> if {{correctOrientation}} is {{false}}, everything works as expected.



--
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-10484) Upgrade to iOS 4.0.1 should warn on allow-intents

[Shazron Abdullah (JIRA)]

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

Shazron Abdullah commented on CB-10484:
---

Not sure what you are getting at here. allow-intents are for opening links in 
the system browser, as documented. Explain what you mean here?

> Upgrade to iOS 4.0.1 should warn on allow-intents
> -
>
> Key: CB-10484
> URL: https://issues.apache.org/jira/browse/CB-10484
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: iOS
>Affects Versions: 6.0.0
>Reporter: Jon Akhtar
>Priority: Minor
>  Labels: triaged
>
> Prior versions of Cordova inserted global elements into config.xml
> `http://*/*; />`
> ``
> These function on android 5.x.x, but no longer on iOS 4.x.x. On 4.x.x this 
> will cause links to open in the system browser.
> A warning should probably be emitted to help people find 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-10473) iOS webview ignoring width 100%

[Shazron Abdullah (JIRA)]

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

Shazron Abdullah commented on CB-10473:
---

Check out the meta tag settings for your app index.html. See the default 
template app created, it does span device-width 100%.
This is not a Cordova problem, probably just a problem with your configuration.

> iOS webview ignoring width 100%
> ---
>
> Key: CB-10473
> URL: https://issues.apache.org/jira/browse/CB-10473
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: iOS
>Affects Versions: 6.0.0
> Environment: iOS 9.2 Cordova 6.0.0
>Reporter: Maverick Baumer
>
> Hi,
> I'm experiencing an issue on iOS with the newest version of Cordova 6.0.0.  
> It's ignoring width 100% on my website.  I've test on Android, Chrome, and 
> Safari and it works perfectly but soon as I load it within the native Safari 
> webview it doesn't display properly.
> Here are 2 screenshots displaying the issue:
> https://www.dropbox.com/s/3j7qklpbgcr7xs3/Screenshot%202016-01-28%2016.17.01.png?dl=0
> https://www.dropbox.com/s/p6cidcghxpbrhou/Screenshot%202016-01-28%2016.17.08.png?dl=0
> Thanks!
> Maverick



--
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-10493) [iOS] Missing icon.png

[Shazron Abdullah (JIRA)]

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

Shazron Abdullah updated CB-10493:
--
Labels: cordova-ios-4.1.0 triaged  (was: triaged)

> [iOS] Missing icon.png
> --
>
> Key: CB-10493
> URL: https://issues.apache.org/jira/browse/CB-10493
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: iOS
>Affects Versions: 4.0.1
> Environment: cordova@6.0.0
> cordova-ios@4.0.1
> ios@9.2
> xcode@7.2
>Reporter: Mark van Beek
>  Labels: cordova-ios-4.1.0, triaged
>
> When trying to upload the ipa created with the latest release of cordova 
> (6.0.0) and cordova-ios (4.0.1) the application loader complains about 
> missing "icon.png". This is probably caused by the use of xcassets to 
> generate the app icons whilst still mentioning
> {code:xml}
> CFBundleIconFile
> icon.png
> {code}
> in the *-Info.plist.
> This file is never copied or generated when using the xcassets function 
> (since all icons are named AppIcon*.png.
> A temporary workaround seems to be removing this key from the *Info.plist and 
> rebuilding.
> STR:
> 1) Create a blank cordova 6.0.0 project
> 2) cordova add platform ios
> 3) cordova build ios --device --release
> 4) Upload the app



--
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-10270) camera.getPicture() returns an empty string

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-10270:
-

Github user riknoll commented on the pull request:


https://github.com/apache/cordova-plugin-camera/pull/160#issuecomment-178228435
  
For reference, 
[this](https://github.com/apache/cordova-plugin-camera/commit/929733b8913311f2cfd504937268a8a1d22f4f9a)
 is the commit I mentioned.


> camera.getPicture() returns an empty string
> ---
>
> Key: CB-10270
> URL: https://issues.apache.org/jira/browse/CB-10270
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Plugin Camera
>Affects Versions: 2.1.0
> Environment: Android 4.4.2 (api 19)
>Reporter: Alexander Sorokin
>Assignee: Richard B Knoll
>Priority: Critical
>  Labels: android, reproduced, triaged
> Attachments: mobilespec-camera.7z
>
>
> Code sample to reproduce:
> {code}
> navigator.camera.getPicture(onSuccess, onFail, { 
> destinationType: Camera.DestinationType.FILE_URI,
> sourceType: Camera.PictureSourceType.PHOTOLIBRARY,
> correctOrientation: true
> });
> {code}
> {{onSuccess}} is called with an empty string as an argument.
> if {{correctOrientation}} is {{false}}, everything works as expected.



--
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-10472) NullPointerException: Attempt to invoke virtual method 'android.os.Bundle org.apache.cordova.PluginManager.onSaveInstanceState

[Richard B Knoll (JIRA)]

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

Richard B Knoll commented on CB-10472:
--

I figured the repro steps were going to look something like that. I wonder how 
possible it is for us to really test all of the native scenarios that can come 
up in a meaningful way. Still, we might be able to work up some unit tests for 
this. [~csantana] is this a very common use case? Do you happen to know how 
often people write their own Activities?

> NullPointerException: Attempt to invoke virtual method 'android.os.Bundle 
> org.apache.cordova.PluginManager.onSaveInstanceState
> --
>
> Key: CB-10472
> URL: https://issues.apache.org/jira/browse/CB-10472
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Android
>Affects Versions: 5.1.0
> Environment: cordova-android 5.1.0
>Reporter: Carlos Santana
>Assignee: Carlos Santana
>  Labels: android, regression, triaged
>
> pluginManager not being check for null before using it in CordovaInterfaceImpl
> 01-28 14:24:10.396  27684-27684/io.cordova.hellocordova E/AndroidRuntime﹕ 
> FATAL EXCEPTION: main
> Process: io.cordova.hellocordova, PID: 27684
> java.lang.NullPointerException: Attempt to invoke virtual method 
> 'android.os.Bundle org.apache.cordova.PluginManager.onSaveInstanceState()' on 
> a null object reference
> at 
> org.apache.cordova.CordovaInterfaceImpl.onSaveInstanceState(CordovaInterfaceImpl.java:173)
> at 
> org.apache.cordova.CordovaActivity.onSaveInstanceState(CordovaActivity.java:465)
> at 
> android.app.Activity.performSaveInstanceState(Activity.java:1298)
> at 
> android.app.Instrumentation.callActivityOnSaveInstanceState(Instrumentation.java:1288)
> at 
> android.app.ActivityThread.callCallActivityOnSaveInstanceState(ActivityThread.java:3958)
> at 
> android.app.ActivityThread.performStopActivityInner(ActivityThread.java:3369)
> at 
> android.app.ActivityThread.handleStopActivity(ActivityThread.java:3425)
> at android.app.ActivityThread.access$1100(ActivityThread.java:151)
> at 
> android.app.ActivityThread$H.handleMessage(ActivityThread.java:1332)
> at android.os.Handler.dispatchMessage(Handler.java:102)
> at android.os.Looper.loop(Looper.java:135)
> at android.app.ActivityThread.main(ActivityThread.java:5254)
> at java.lang.reflect.Method.invoke(Native Method)
> at java.lang.reflect.Method.invoke(Method.java:372)
> at 
> com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:903)
> at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:698)
> Recreate
> cordova create testapp
> cd testapp
> cordova platform add android@5.1.0
> Modify MainActivity to launch a second Cordova Activity like this:
> change MainActivity.java
> Notice no init or loadUrl called, this is on purpose in our App for this use 
> case we want to avoid this, and let the second Activity to call loadUrl
> public class MainActivity extends CordovaActivity
> {
> @Override
> public void onCreate(Bundle savedInstanceState)
> {
> super.onCreate(savedInstanceState);
> }
> @Override
> protected void onStart(){
> super.onStart();
> Intent newActivity = new Intent(this, MainActivity2.class);
> startActivity(newActivity);
> }
> }
> Add class io.cordova.hellocordova.MainActivity2.java
> public class MainActivity2 extends CordovaActivity
> {
> @Override
> public void onCreate(Bundle savedInstanceState)
> {
> super.onCreate(savedInstanceState);
> // Set by  in config.xml
> loadUrl(launchUrl);
> }
> }
> Add activity to AndroidManifest.xml
> 
> Since init() or loadUrl was never called in MainActivity, pluginManager never 
> got created, this let pluginManager be null



--
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=15127186#comment-15127186
 ] 

Richard B Knoll commented on CB-10498:
--

Other people are seeing this as well. Relevant discussion at the end of [this 
PR 
thread|https://github.com/apache/cordova-medic/blob/master/buildbot-conf/cordova.conf#L338]

> 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
>  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] [Comment Edited] (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=15127186#comment-15127186
 ] 

Richard B Knoll edited comment on CB-10498 at 2/1/16 10:47 PM:
---

Other people are seeing this as well. Relevant discussion at the end of [this 
PR 
thread|https://github.com/apache/cordova-plugin-camera/pull/97#issuecomment-177920211]


was (Author: riknoll):
Other people are seeing this as well. Relevant discussion at the end of [this 
PR 
thread|https://github.com/apache/cordova-medic/blob/master/buildbot-conf/cordova.conf#L338]

> 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
>  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] [Commented] (CB-10499) --template should pull the latest template from NPM when version isn't specified

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-10499:
-

GitHub user csantanapr opened a pull request:

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

CB-10499 - --template should pull the latest template from NPM when

version isn't specified

- Pull the latest template if no version is specified
- Rename NPM to npm

rename github to git

This close #372

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

$ git pull https://github.com/csantanapr/cordova-lib pr-372

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

https://github.com/apache/cordova-lib/pull/373.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 #373


commit a65333cfe490288dc5bc0ce992c88d4764872a94
Author: dubeejw 
Date:   2016-02-01T20:31:26Z

CB-10499 - --template should pull the latest template from NPM when
version isn't specified

- Pull the latest template if no version is specified
- Rename NPM to npm

rename github to git

This close #372




> --template should pull the latest template from NPM when version isn't 
> specified
> 
>
> Key: CB-10499
> URL: https://issues.apache.org/jira/browse/CB-10499
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: CordovaLib
>Affects Versions: Master
>Reporter: James Dubee
>Priority: Minor
>
> The latest template isn't always downloaded when @latest isn't specified when 
> using --template to create an app.



--
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-10499) --template should pull the latest template from NPM when version isn't specified

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-10499:
-

Github user asfgit closed the pull request at:

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


> --template should pull the latest template from NPM when version isn't 
> specified
> 
>
> Key: CB-10499
> URL: https://issues.apache.org/jira/browse/CB-10499
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: CordovaLib
>Affects Versions: Master
>Reporter: James Dubee
>Priority: Minor
>
> The latest template isn't always downloaded when @latest isn't specified when 
> using --template to create an app.



--
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-10484) Upgrade to iOS 4.0.1 should warn on allow-intents

[Jon Akhtar (JIRA)]

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

Jon Akhtar commented on CB-10484:
-

The behavior on iOS prior to 4.0.0 was to open http and https inside the 
webview. I guess it was just a surprise when it started behaving differently. 
Though I see that the new behavior is the intended one now. 

The default application template defines all http and https links as intended 
to be opened in an external web browser, I guess I never noticed that behavior 
before for whatever reason.

You can close this

> Upgrade to iOS 4.0.1 should warn on allow-intents
> -
>
> Key: CB-10484
> URL: https://issues.apache.org/jira/browse/CB-10484
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: iOS
>Affects Versions: 6.0.0
>Reporter: Jon Akhtar
>Priority: Minor
>  Labels: triaged
>
> Prior versions of Cordova inserted global elements into config.xml
> `http://*/*; />`
> ``
> These function on android 5.x.x, but no longer on iOS 4.x.x. On 4.x.x this 
> will cause links to open in the system browser.
> A warning should probably be emitted to help people find 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-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=15127388#comment-15127388
 ] 

ASF GitHub Bot commented on CB-10474:
-

Github user riknoll commented on the pull request:

https://github.com/apache/cordova-medic/pull/73#issuecomment-178293314
  
@dblotsky no problem; we need to be in a cordova project for that command 
(`cordova run --list`) to work anyway, so I'll just call `pushd` here as well. 
Thanks for investigating!


> 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=15127468#comment-15127468
 ] 

ASF GitHub Bot commented on CB-10474:
-

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

https://github.com/apache/cordova-medic/pull/73#discussion_r51514684
  
--- Diff: medic/medic-log.js ---
@@ -69,18 +70,72 @@ function logBlackberry() {
 return;
 }
 
-function logIOS() {
-var logScriptpath = path.join("mobilespec", "platforms", "ios", 
"cordova", "console.log");
-var command = "cat " + logScriptpath;
+function logIOS(appPath) {
+// We need to print out the system log for the simulator app. In order 
to figure
+// out the path to that file, we need to find the ID of the simulator 
running
+// mobilespec
+
+// First, figure out the simulator that ran mobilespec. "cordova run"" 
just chooses
+// the last simulator in this list that starts with the word "iPhone"
+shelljs.pushd(appPath);
+
+var findSimCommand = getLocalCLI() + " run --list --emulator | grep 
^iPhone | tail -n1";
--- End diff --

The `grep` and `tail` calls won't work on the Windows build machines. Is it 
a long task to do this in JS? If it's much more difficult, we can just add some 
steps to install Unix tools on Windows for our build machine docs.


> 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=15127461#comment-15127461
 ] 

ASF GitHub Bot commented on CB-10474:
-

Github user dblotsky commented on the pull request:

https://github.com/apache/cordova-medic/pull/73#issuecomment-178318882
  
I tried this on my machine and I ran into an issue where it couldn't find 
the deployed simulator because there were other non-deployed simulators 
installed. Is there a way to filter by running emulators? If now, we can still 
work around this by ensuring that there are no more than one simulators 
installed on the build machine.


> 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=15127296#comment-15127296
 ] 

ASF GitHub Bot commented on CB-10474:
-

Github user dblotsky commented on the pull request:

https://github.com/apache/cordova-medic/pull/73#issuecomment-178267393
  
@riknoll: The value returned by `getLocalCLI()` is used after 
`shell.pushd()` is called [here][pushd] to get into the `mobilespec` app 
directory in `medic-run`, and in `medic-log` this does not happen. Sorry, this 
is was a result of my unclear coding.

[pushd]: 
https://github.com/apache/cordova-medic/blob/master/medic/medic-run.js#L389


> 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-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=15127299#comment-15127299
 ] 

ASF GitHub Bot commented on CB-10405:
-

Github user dblotsky commented on the pull request:

https://github.com/apache/cordova-medic/pull/74#issuecomment-178267638
  
Does this need to be fixed? It's an intermittent connectivity issue and 
already gets polled, so if some polls fail it's not a problem.


> 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
>  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-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=15127431#comment-15127431
 ] 

ASF GitHub Bot commented on CB-10052:
-

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

https://github.com/apache/cordova-lib/pull/369#discussion_r51511432
  
--- Diff: cordova-common/src/superspawn.js ---
@@ -113,11 +139,15 @@ exports.spawn = function(cmd, args, opts) {
 child.stdout.setEncoding('utf8');
 child.stdout.on('data', function(data) {
 capturedOut += data;
+d.notify({'stdout': data});
--- End diff --

What is `d`?


> 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-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=15127477#comment-15127477
 ] 

ASF GitHub Bot commented on CB-10474:
-

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

https://github.com/apache/cordova-medic/pull/73#discussion_r51514920
  
--- Diff: medic/medic-log.js ---
@@ -69,18 +70,72 @@ function logBlackberry() {
 return;
 }
 
-function logIOS() {
-var logScriptpath = path.join("mobilespec", "platforms", "ios", 
"cordova", "console.log");
-var command = "cat " + logScriptpath;
+function logIOS(appPath) {
+// We need to print out the system log for the simulator app. In order 
to figure
+// out the path to that file, we need to find the ID of the simulator 
running
+// mobilespec
+
+// First, figure out the simulator that ran mobilespec. "cordova run"" 
just chooses
+// the last simulator in this list that starts with the word "iPhone"
+shelljs.pushd(appPath);
+
+var findSimCommand = getLocalCLI() + " run --list --emulator | grep 
^iPhone | tail -n1";
--- End diff --

I don't think any part of this will work on Windows. Every command is 
either Unix or OSX specific.


> 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=15127478#comment-15127478
 ] 

ASF GitHub Bot commented on CB-10474:
-

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

https://github.com/apache/cordova-medic/pull/73#discussion_r51514960
  
--- Diff: medic/medic-log.js ---
@@ -69,18 +70,72 @@ function logBlackberry() {
 return;
 }
 
-function logIOS() {
-var logScriptpath = path.join("mobilespec", "platforms", "ios", 
"cordova", "console.log");
-var command = "cat " + logScriptpath;
+function logIOS(appPath) {
+// We need to print out the system log for the simulator app. In order 
to figure
+// out the path to that file, we need to find the ID of the simulator 
running
+// mobilespec
+
+// First, figure out the simulator that ran mobilespec. "cordova run"" 
just chooses
+// the last simulator in this list that starts with the word "iPhone"
+shelljs.pushd(appPath);
+
+var findSimCommand = getLocalCLI() + " run --list --emulator | grep 
^iPhone | tail -n1";
--- End diff --

Why would the Windows build machines run this? It's iOS


> 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=15127544#comment-15127544
 ] 

ASF GitHub Bot commented on CB-10474:
-

Github user riknoll commented on the pull request:

https://github.com/apache/cordova-medic/pull/73#issuecomment-178333571
  
@dblotsky I'm not sure; I copied `cordova run's logic for choosing the 
emulator. This does not support choosing a specific simulator, just the 
default. I'll look into ios-sim to see if it has any sort of API to get the 
running one. Otherwise, we can configure medic to always launch to a 
preconfigured simulator (say iPhone 6s) and pass that into `run` and `log` as 
flags.


> 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=15127494#comment-15127494
 ] 

ASF GitHub Bot commented on CB-10474:
-

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

https://github.com/apache/cordova-medic/pull/73#discussion_r51515589
  
--- Diff: medic/medic-log.js ---
@@ -69,18 +70,72 @@ function logBlackberry() {
 return;
 }
 
-function logIOS() {
-var logScriptpath = path.join("mobilespec", "platforms", "ios", 
"cordova", "console.log");
-var command = "cat " + logScriptpath;
+function logIOS(appPath) {
+// We need to print out the system log for the simulator app. In order 
to figure
+// out the path to that file, we need to find the ID of the simulator 
running
+// mobilespec
+
+// First, figure out the simulator that ran mobilespec. "cordova run"" 
just chooses
+// the last simulator in this list that starts with the word "iPhone"
+shelljs.pushd(appPath);
+
+var findSimCommand = getLocalCLI() + " run --list --emulator | grep 
^iPhone | tail -n1";
--- End diff --

I only just realised this. Please disregard my comment. :P


> 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=15127434#comment-15127434
 ] 

ASF GitHub Bot commented on CB-10474:
-

Github user riknoll commented on the pull request:

https://github.com/apache/cordova-medic/pull/73#issuecomment-178308453
  
@dblotsky updated


> 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-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=15127436#comment-15127436
 ] 

ASF GitHub Bot commented on CB-10052:
-

Github user dblotsky commented on the pull request:

https://github.com/apache/cordova-lib/pull/369#issuecomment-178308498
  
Why not return the stdout and stderr objects on which calling code can 
subscribe to the `"data"` events directly?


> 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-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=15125939#comment-15125939
 ] 

ASF GitHub Bot commented on CB-10332:
-

Github user vladimir-kotikov commented on the pull request:

https://github.com/apache/cordova-docs/pull/471#issuecomment-177849723
  
@riknoll, +1, makes sense


> 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, e-mail: issues-h...@cordova.apache.org

[jira] [Commented] (CB-10394) config-file changes are not written to package.windows.appxmanifest

[ASF subversion and git services (JIRA)]

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

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

Commit 188ac247a8882352f4265f2f0c8e08e8d1f2 in cordova-windows's branch 
refs/heads/4.3.x from [~vladimir.kotikov]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-windows.git;h=188ac24 ]

CB-10394 Do not cache manifest file while getting package name


> config-file changes are not written to package.windows.appxmanifest
> ---
>
> Key: CB-10394
> URL: https://issues.apache.org/jira/browse/CB-10394
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Windows
>Affects Versions: 4.3.0
>Reporter: Marco Biasini
>Assignee: Vladimir Kotikov
>  Labels: regression, triaged
>
> I've noticed that config-file changes defined in a plugin are not correctly 
> written to package.windows.appxmanifest file. After a plugin import, the file 
> does not contain these changes. The changes are correctly applied to the 
> other appxmanifest files (phone, windows10, windows80). 
> I've bested both with windows platform 4.3.0 as well as master and the 
> problem exists in both branches.
> The problem is related to the appxmanifest caching mechanism. The 
> package.windows.appxmanifest file is loaded early on to determine the package 
> name (through jsprojManager.getPackageName()). The appxmanifest content is 
> then cached in memory. Then, the config-file changes defined in the 
> plugin.xml file are applied to the manifests and written to disk. They do not 
> use the cached manifests from the earlier step,but rather load the files 
> through a different code path. After that all previously cached appxmanifest 
> instances are then written to disk, which effectively overwrites the content 
> of package.windows.appxmanifest. Since this is the only manifest that gets 
> loaded early on, this does not affect the other appxmanifest files.



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

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

[jira] [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=15126228#comment-15126228
 ] 

ASF GitHub Bot commented on CB-10052:
-

GitHub user vladimir-kotikov opened a pull request:

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

CB-10052 Expose child process' io streams via promise progress notification

This implements [CB-10052](https://issues.apache.org/jira/browse/CB-10052).

The `superspawn.spawn` promise now emits notifications, which caller can 
subscribe to using `progress` method:

```
superspawn.spawn('adb', ['devices'])
.progress(function(data){
if (data.stderr) console.error('"adb devices" raised an error: ' + 
data.stderr);
})
.then(function(devices){
// Do something...
})
```

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

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

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

https://github.com/apache/cordova-lib/pull/369.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 #369


commit 5a37978e9aeeeda4f71e876299fce4358f4ed2fd
Author: Vladimir Kotikov 
Date:   2016-01-22T13:39:13Z

CB-10052 Expose child process' io streams via promise progress notification




> 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-10113) Browser - Camera plugin image z-index is too low

[ASF subversion and git services (JIRA)]

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

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

Commit 5b3845326216343bf25abbca90585a595dad3b6e in cordova-plugin-camera's 
branch refs/heads/master from [~ali_o_kan]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-camera.git;h=5b38453 
]

CB-10113 Browser - Layer camera UI on top of all!

Adds CSS style {position: 'relative', z-index: 2147483647} (2147483647 is the 
highest possible z-index) on DOM appended elements.

This closes #134


> Browser - Camera plugin image z-index is too low
> 
>
> Key: CB-10113
> URL: https://issues.apache.org/jira/browse/CB-10113
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Plugin Camera
>Reporter: Laurent Deketelaere
>
> In Browser platform, sometimes input appears below content. 
> z-index need to be increase. 



--
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-10113) Browser - Camera plugin image z-index is too low

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-10113:
-

Github user asfgit closed the pull request at:

https://github.com/apache/cordova-plugin-camera/pull/134


> Browser - Camera plugin image z-index is too low
> 
>
> Key: CB-10113
> URL: https://issues.apache.org/jira/browse/CB-10113
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Plugin Camera
>Reporter: Laurent Deketelaere
>
> In Browser platform, sometimes input appears below content. 
> z-index need to be increase. 



--
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=15127807#comment-15127807
 ] 

ASF GitHub Bot commented on CB-10052:
-

Github user vladimir-kotikov commented on a diff in the pull request:

https://github.com/apache/cordova-lib/pull/369#discussion_r51532148
  
--- Diff: cordova-common/src/superspawn.js ---
@@ -113,11 +139,15 @@ exports.spawn = function(cmd, args, opts) {
 child.stdout.setEncoding('utf8');
 child.stdout.on('data', function(data) {
 capturedOut += data;
+d.notify({'stdout': data});
--- End diff --

`d` is a `Deferred` object. See 
https://github.com/apache/cordova-lib/blob/master/cordova-common/src/superspawn.js#L68


> 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-10499) --template should pull the latest template from NPM when version isn't specified

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-10499:
-

GitHub user dubeejw opened a pull request:

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

CB-10499 - --template should pull the latest template from NPM when

version isn't specified

- Pull the latest template if no version is specified

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

$ git pull https://github.com/dubeejw/cordova-lib master

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

https://github.com/apache/cordova-lib/pull/372.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 #372


commit c181d428c22983b8641e61f62bc2444924ec2c58
Author: dubeejw 
Date:   2016-02-01T20:31:26Z

CB-10499 - --template should pull the latest template from NPM when
version isn't specified

- Pull the latest template if no version is specified




> --template should pull the latest template from NPM when version isn't 
> specified
> 
>
> Key: CB-10499
> URL: https://issues.apache.org/jira/browse/CB-10499
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: CordovaLib
>Affects Versions: Master
>Reporter: James Dubee
>Priority: Minor
>
> The latest template isn't always downloaded when @latest isn't specified when 
> using --template to create an app.



--
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=15127800#comment-15127800
 ] 

ASF GitHub Bot commented on CB-10430:
-

Github user purplecabbage commented on the pull request:

https://github.com/apache/cordova-lib/pull/370#issuecomment-178414449
  
Yeah, I too am not entirely behind this.
It seems like an anti-pattern here, and a consequence of 
require('../events') only being executed once per module.  This essentially 
makes it a global object that may change at runtime.



> 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-10502) Exception when click "Capture!" button for camera plugin in browser

[ASF subversion and git services (JIRA)]

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

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

Commit e48a7e5c5cffe8d9bab6eeff33feeb2747930ace in cordova-plugin-camera's 
branch refs/heads/master from [~TimBarham]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-camera.git;h=e48a7e5 
]

CB-10502 Fix camera plugin exception in Chrome when click capture.

The MediaStream.stop() method has been deprecated as of Chrome 47. We were 
using it, and it was generating an exception.

If stop() method is not found, instead stop each individual track (the new way 
of doing it).


> Exception when click "Capture!" button for camera plugin in browser
> ---
>
> Key: CB-10502
> URL: https://issues.apache.org/jira/browse/CB-10502
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Plugin Camera
>Reporter: Tim Barham
>Assignee: Tim Barham
>Priority: Critical
>
> When you click the "Capture!" button for the camera plugin on the browser 
> platform (in Chrome 47 or later), you get the following exception:
> {noformat}
> Uncaught TypeError: localMediaStream.stop is not a function
> button.onclick @ CameraProxy.js:69
> {noformat}
> This is because {{MediaStream.stop()}} is deprecated as of Chrome 47.



--
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-10502) Exception when click "Capture!" button for camera plugin in browser

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-10502:
-

Github user asfgit closed the pull request at:

https://github.com/apache/cordova-plugin-camera/pull/161


> Exception when click "Capture!" button for camera plugin in browser
> ---
>
> Key: CB-10502
> URL: https://issues.apache.org/jira/browse/CB-10502
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Plugin Camera
>Reporter: Tim Barham
>Assignee: Tim Barham
>Priority: Critical
>
> When you click the "Capture!" button for the camera plugin on the browser 
> platform (in Chrome 47 or later), you get the following exception:
> {noformat}
> Uncaught TypeError: localMediaStream.stop is not a function
> button.onclick @ CameraProxy.js:69
> {noformat}
> This is because {{MediaStream.stop()}} is deprecated as of Chrome 47.



--
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-10113) Browser - Camera plugin image z-index is too low

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-10113:
-

Github user TimBarham commented on the pull request:


https://github.com/apache/cordova-plugin-camera/pull/134#issuecomment-178412993
  
Thanks for this @aliokan. I've tweaked the commit a bit to store the magic 
number in a constant, and I'll merge it.


> Browser - Camera plugin image z-index is too low
> 
>
> Key: CB-10113
> URL: https://issues.apache.org/jira/browse/CB-10113
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Plugin Camera
>Reporter: Laurent Deketelaere
>
> In Browser platform, sometimes input appears below content. 
> z-index need to be increase. 



--
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=15127822#comment-15127822
 ] 

ASF GitHub Bot commented on CB-10052:
-

Github user vladimir-kotikov commented on the pull request:

https://github.com/apache/cordova-lib/pull/369#issuecomment-178421841
  
Returning data instead of raw eventEmitter is IMO just less complex for 
caller API, because you, as a caller, do not need to create handlers, 
subscribe, unsubscribe, etc.


> 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] [Created] (CB-10503) Documentation link points to 'latest' version even in latest build

[Sarangan Rajamanickam (JIRA)]

Sarangan Rajamanickam created CB-10503:
--

 Summary: Documentation link points to 'latest' version even in 
latest build
 Key: CB-10503
 URL: https://issues.apache.org/jira/browse/CB-10503
 Project: Apache Cordova
  Issue Type: Bug
  Components: Docs
Reporter: Sarangan Rajamanickam
Assignee: Sarangan Rajamanickam






--
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-10502) Exception when click "Capture!" button for camera plugin in browser

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-10502:
-

GitHub user TimBarham opened a pull request:

https://github.com/apache/cordova-plugin-camera/pull/161

CB-10502 Fix camera plugin exception in Chrome when click capture.

The `MediaStream.stop()` method has been deprecated as of Chrome 47. We 
were using it, and it was generating an exception.

If `stop()` method is not found, instead stop each individual track (the 
new way of doing it).

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

$ git pull https://github.com/TimBarham/cordova-plugin-camera CB-10502

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

https://github.com/apache/cordova-plugin-camera/pull/161.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 #161


commit e48a7e5c5cffe8d9bab6eeff33feeb2747930ace
Author: Tim Barham 
Date:   2016-02-02T06:25:00Z

CB-10502 Fix camera plugin exception in Chrome when click capture.

The MediaStream.stop() method has been deprecated as of Chrome 47. We were 
using it, and it was generating an exception.

If stop() method is not found, instead stop each individual track (the new 
way of doing it).




> Exception when click "Capture!" button for camera plugin in browser
> ---
>
> Key: CB-10502
> URL: https://issues.apache.org/jira/browse/CB-10502
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Plugin Camera
>Reporter: Tim Barham
>Assignee: Tim Barham
>Priority: Critical
>
> When you click the "Capture!" button for the camera plugin on the browser 
> platform (in Chrome 47 or later), you get the following exception:
> {noformat}
> Uncaught TypeError: localMediaStream.stop is not a function
> button.onclick @ CameraProxy.js:69
> {noformat}
> This is because {{MediaStream.stop()}} is deprecated as of Chrome 47.



--
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-10502) Exception when click "Capture!" button for camera plugin in browser

[Tim Barham (JIRA)]

Tim Barham created CB-10502:
---

 Summary: Exception when click "Capture!" button for camera plugin 
in browser
 Key: CB-10502
 URL: https://issues.apache.org/jira/browse/CB-10502
 Project: Apache Cordova
  Issue Type: Bug
  Components: Plugin Camera
Reporter: Tim Barham
Assignee: Tim Barham
Priority: Critical


When you click the "Capture!" button for the camera plugin on the browser 
platform (in Chrome 47 or later), you get the following exception:

{noformat}
Uncaught TypeError: localMediaStream.stop is not a function
button.onclick @ CameraProxy.js:69
{noformat}

This is because {{MediaStream.stop()}} is deprecated as of Chrome 47.



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

[Nikhil Khandelwal (JIRA)]

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

Nikhil Khandelwal updated CB-10498:
---
Assignee: Richard B Knoll

> 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] [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=15127589#comment-15127589
 ] 

ASF GitHub Bot commented on CB-10459:
-

Github user nikhilkh commented on the pull request:

https://github.com/apache/cordova-lib/pull/368#issuecomment-178344384
  
LGTM


> 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] [Created] (CB-10501) Splashscreen doesn not hide on command in IOS

[Core Elements (JIRA)]

Core Elements created CB-10501:
--

 Summary: Splashscreen doesn not hide on command in IOS
 Key: CB-10501
 URL: https://issues.apache.org/jira/browse/CB-10501
 Project: Apache Cordova
  Issue Type: Bug
  Components: iOS, Plugin SplashScreen
Affects Versions: 3.1.0
 Environment: ionic
ngcordova
Reporter: Core Elements


after updating from 3.0.0 to 3.1.0 I've noticed that

$cordovaSplashscreen.hide();
or
navigator.splashscreen.hide();

doesn't work any more. It doesn't hide the splashscreen anymore.

my config.xml

  
  
  
  
  
  

so it ignores the hide() command, but still it waits untill SplashScreenDelay 
is reached

all is fine on Android.



--
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-10483) Cordova platform Android@5.0.0 deletes app after rebuild

[Nikhil Khandelwal (JIRA)]

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

Nikhil Khandelwal resolved CB-10483.

   Resolution: Duplicate
Fix Version/s: CB-10157

> Cordova platform Android@5.0.0 deletes app after rebuild
> 
>
> Key: CB-10483
> URL: https://issues.apache.org/jira/browse/CB-10483
> Project: Apache Cordova
>  Issue Type: Wish
>  Components: Android
>Affects Versions: 5.0.0
>Reporter: Sumama Waheed
> Fix For: CB-10157
>
>
> I am using couchbase lite database in my cordova app. Alot of data is loaded 
> when the app is installed. On Android 4.1.1, whenever you rebuilt the app, 
> the app data was still intact. 
> However, after upgrading to Android 5.0.0 cordova platform, everytime you run 
> 'cordova run android' , the app is uninstalled and the app data is deleted 
> which is very inconvenient for debugging. 
> Can this be fixed?



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