[jira] [Commented] (CB-11534) Cordova file-transfer-plugin should support Android Marshmallow runtime permission

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-11534:
-

Github user stalniy commented on the issue:

https://github.com/apache/cordova-plugin-file-transfer/pull/150
  
@filmaj any news on this?


> Cordova file-transfer-plugin should support Android Marshmallow runtime 
> permission
> --
>
> Key: CB-11534
> URL: https://issues.apache.org/jira/browse/CB-11534
> Project: Apache Cordova
>  Issue Type: New Feature
>  Components: cordova-plugin-file-transfer
> Environment: Android Marshmallow,Android target platform 23.
>Reporter: Homen Borgohain
>Assignee: Filip Maj
>  Labels: Android, android6.0, permission
>   Original Estimate: 10m
>  Remaining Estimate: 10m
>
> In Android Marshmallow file-transfer-plugin should show a pop up if storage 
> permission is not granted.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CB-11144) Make Git fetches faster for plugin, platforms, and templates by using --depth 1

[Filip Maj (JIRA)]

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

Filip Maj commented on CB-11144:


Sounds like there are some different scenarios to consider (sha vs. branch vs. 
tag), but it may be worth investigating as per Carlos' comment there should be 
some good savings in the average case.

> Make Git fetches faster for plugin, platforms, and templates by using --depth 
> 1
> ---
>
> Key: CB-11144
> URL: https://issues.apache.org/jira/browse/CB-11144
> Project: Apache Cordova
>  Issue Type: Improvement
>  Components: cordova-fetch
>Reporter: Carlos Santana
>Assignee: Carlos Santana
>  Labels: backlog
>
> Some users are complaining that some plugin git repos are too big, and the 
> plugin is not available thru npm
> So people installing the plugin it can take up to 20 minutes to install a 
> plugin because Cordova CLI it's doing a full git clone of the repo.
> I was wondering if the flag --depth 1 would make it faster by fetching just 
> the last copy of the repo on the specified git hash, hash can be branch, or 
> tag, or commit hash
> Going to ask to the mailing list to see of using --depth 1 is a good and safe 
> change?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Updated] (CB-11144) Make Git fetches faster for plugin, platforms, and templates by using --depth 1

[Filip Maj (JIRA)]

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

Filip Maj updated CB-11144:
---
Component/s: (was: cordova-cli)
 cordova-fetch

> Make Git fetches faster for plugin, platforms, and templates by using --depth 
> 1
> ---
>
> Key: CB-11144
> URL: https://issues.apache.org/jira/browse/CB-11144
> Project: Apache Cordova
>  Issue Type: Improvement
>  Components: cordova-fetch
>Reporter: Carlos Santana
>Assignee: Carlos Santana
>  Labels: backlog
>
> Some users are complaining that some plugin git repos are too big, and the 
> plugin is not available thru npm
> So people installing the plugin it can take up to 20 minutes to install a 
> plugin because Cordova CLI it's doing a full git clone of the repo.
> I was wondering if the flag --depth 1 would make it faster by fetching just 
> the last copy of the repo on the specified git hash, hash can be branch, or 
> tag, or commit hash
> Going to ask to the mailing list to see of using --depth 1 is a good and safe 
> change?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Updated] (CB-11144) Make Git fetches faster for plugin, platforms, and templates by using --depth 1

[Filip Maj (JIRA)]

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

Filip Maj updated CB-11144:
---
Labels: backlog  (was: )

> Make Git fetches faster for plugin, platforms, and templates by using --depth 
> 1
> ---
>
> Key: CB-11144
> URL: https://issues.apache.org/jira/browse/CB-11144
> Project: Apache Cordova
>  Issue Type: Improvement
>  Components: cordova-fetch
>Reporter: Carlos Santana
>Assignee: Carlos Santana
>  Labels: backlog
>
> Some users are complaining that some plugin git repos are too big, and the 
> plugin is not available thru npm
> So people installing the plugin it can take up to 20 minutes to install a 
> plugin because Cordova CLI it's doing a full git clone of the repo.
> I was wondering if the flag --depth 1 would make it faster by fetching just 
> the last copy of the repo on the specified git hash, hash can be branch, or 
> tag, or commit hash
> Going to ask to the mailing list to see of using --depth 1 is a good and safe 
> change?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Resolved] (CB-11704) Separate configuration into multiple xml files

[Filip Maj (JIRA)]

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

Filip Maj resolved CB-11704.

Resolution: Won't Do

Closing due to inactivity.

> Separate configuration into multiple xml files
> --
>
> Key: CB-11704
> URL: https://issues.apache.org/jira/browse/CB-11704
> Project: Apache Cordova
>  Issue Type: New Feature
>  Components: cordova-cli
>Reporter: Julian Grinblat
>
> When building icons or splashscreens with third party modules, not only do 
> these tools output image files, they also output the required xml to be 
> included inside config.xml. It would be very useful to be have separate xml 
> files that are either explicitly included or implicitly. I'm not very sure 
> what the best way to accomplish this would be. For your consideration.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CB-11602) Splashscreen plugin receives onPause and hides

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-11602:
-

Github user alanhg commented on the issue:

https://github.com/apache/cordova-plugin-splashscreen/pull/109
  
if AutoHideSplashScreen works for android.
how to use if i want to hide splashscreen manually


> Splashscreen plugin receives onPause and hides
> --
>
> Key: CB-11602
> URL: https://issues.apache.org/jira/browse/CB-11602
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: cordova-plugin-splashscreen
>Affects Versions: 2.0.0, 2.1.0, 2.2.0, 2.3.0, 2.4.0, 2.5.0, 2.6.0, 2.7.0, 
> 2.8.0, 2.9.0, 2.9.1, 3.5.0
> Environment: Android
>Reporter: Nikolay Babanov
>Assignee: Sergey Shakhnazarov
>  Labels: easyfix, triaged
> Fix For: 4.0.0
>
>   Original Estimate: 0h
>  Remaining Estimate: 0h
>
> When you set the "AutoHideSplashScreen" to false in the config.xml, the 
> splash screen still automatically closes, before the crosswalk webview is 
> loaded.
> This is caused by the plugin receiving the onPause event and therefore 
> dismissing itself.
> My proposed solution is to use the onStop event in place of the onPause, as 
> this fixes the issue.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CB-11581) Add target configuration support and management

[Filip Maj (JIRA)]

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

Filip Maj commented on CB-11581:


I know there is some appetite for the different-environment use case you 
present.

Having multiple config.xml's opens up a whole new can of worms: when issuing 
cordova commands (platform/plugin ones, for example), you'd have to have the 
ability to specify against which config.xml (or both / all?). Lots of potential 
pitfalls here to think through.

I think first the idea needs to be more fleshed out and a vision for the 
workflow needs to be articulated.

> Add target configuration support and management
> ---
>
> Key: CB-11581
> URL: https://issues.apache.org/jira/browse/CB-11581
> Project: Apache Cordova
>  Issue Type: New Feature
>  Components: cordova-cli
> Environment: N/A
>Reporter: Ricardo Panaggio
>
> It would be awesome if it was possible to set target configuration. This 
> would interact with the build-related tools, which would expect (possibly) 
> different targets, instead of assuming a single target. This could be used by 
> some people to maintain within a single project several different 
> environments (i.e. development, qa, production, ...), several different build 
> types (i.e. demo, full, deluxe, ...), and I'm sure many other uses would come 
> up.
> This is a major change, and probably something that needs to be widely 
> discussed before it's implemented, but something like supporting several 
> config.xml (one per target) could be a good start, opening a great new avenue 
> to improve this side of the CLI and Cordova tools in a broader way.
> For instance, if we had two targets (say, dev and prod) and we would like to 
> build them on iOS, the CLI could be called like:
> ```
> $ cordova build ios # for the default target, say dev (and nothing different 
> from current syntax)
> $ cordova build ios:prod # for the production target, defined by 
> prod.config.xml or config.prod.xml, or some other convention/configuration
> ```



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Updated] (CB-11581) Add target configuration support and management

[Filip Maj (JIRA)]

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

Filip Maj updated CB-11581:
---
Issue Type: New Feature  (was: Improvement)

> Add target configuration support and management
> ---
>
> Key: CB-11581
> URL: https://issues.apache.org/jira/browse/CB-11581
> Project: Apache Cordova
>  Issue Type: New Feature
>  Components: cordova-cli
> Environment: N/A
>Reporter: Ricardo Panaggio
>
> It would be awesome if it was possible to set target configuration. This 
> would interact with the build-related tools, which would expect (possibly) 
> different targets, instead of assuming a single target. This could be used by 
> some people to maintain within a single project several different 
> environments (i.e. development, qa, production, ...), several different build 
> types (i.e. demo, full, deluxe, ...), and I'm sure many other uses would come 
> up.
> This is a major change, and probably something that needs to be widely 
> discussed before it's implemented, but something like supporting several 
> config.xml (one per target) could be a good start, opening a great new avenue 
> to improve this side of the CLI and Cordova tools in a broader way.
> For instance, if we had two targets (say, dev and prod) and we would like to 
> build them on iOS, the CLI could be called like:
> ```
> $ cordova build ios # for the default target, say dev (and nothing different 
> from current syntax)
> $ cordova build ios:prod # for the production target, defined by 
> prod.config.xml or config.prod.xml, or some other convention/configuration
> ```



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Resolved] (CB-11284) Telemetry: Log platform/plugin subcommands

[Filip Maj (JIRA)]

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

Filip Maj resolved CB-11284.

Resolution: Fixed

This was merged.

> Telemetry: Log platform/plugin subcommands
> --
>
> Key: CB-11284
> URL: https://issues.apache.org/jira/browse/CB-11284
> Project: Apache Cordova
>  Issue Type: Improvement
>  Components: cordova-cli
>Reporter: Omar Mefire
>Assignee: Omar Mefire
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Comment Edited] (CB-11309) Platform specific plugins install to all platforms

[Filip Maj (JIRA)]

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

Filip Maj edited comment on CB-11309 at 7/15/17 3:49 AM:
-

I'm not sure this is a problem. Both of these plugins have components that 
reside "outside" of the {{}} section of plugin.xml (like web and JS 
assets), so cordova-cli is still making _some_ changes here, to platforms other 
than iOS, that is in accordance with the plugin.xml spec.

What behaviour would you expect in this case?


was (Author: filmaj):
I'm not sure this is a problem. Both of these plugins have components that 
reside "outside" of the {{}} section of plugin.xml (like web and JS 
assets), so cordova-cli is still making _some_ changes here according to the 
plugin.xml spec.

What behaviour would you expect in this case?

> Platform specific plugins install to all platforms
> --
>
> Key: CB-11309
> URL: https://issues.apache.org/jira/browse/CB-11309
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: cordova-cli, cordova-plugman
>Affects Versions: 1.1.0, 6.1.1
>Reporter: Trevor Brindle
>Assignee: Shazron Abdullah
>
> CLI: 6.1.1
> Plugman: 1.2.1
> Node: 5.11.1
> npm: 3.9.2
> Steps to reproduce:
> 1. cordova create ~/Developer/plugmantest com.cordova.test plugmantest
> 2. cordova platform add ios android (4.1.1, 5.1.1)
> 3. cordova plugin add cordova-plugin-applepay-payeezy
> Resulted in: 
> Fetching plugin "cordova-plugin-applepay-payeezy" via npm
> Installing "cordova-plugin-applepay-payeezy" for android
> Installing "cordova-plugin-applepay-payeezy" for ios
> cordova-plugin-applepay-payeezy in android.json
> cordova-plugin-applepay-payeezy in platform_www
> Same result for 
> cordova plugin add https://github.com/shazron/KeychainPlugin



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CB-11309) Platform specific plugins install to all platforms

[Filip Maj (JIRA)]

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

Filip Maj commented on CB-11309:


I'm not sure this is a problem. Both of these plugins have components that 
reside "outside" of the {{}} section of plugin.xml (like web and JS 
assets), so cordova-cli is still making _some_ changes here according to the 
plugin.xml spec.

What behaviour would you expect in this case?

> Platform specific plugins install to all platforms
> --
>
> Key: CB-11309
> URL: https://issues.apache.org/jira/browse/CB-11309
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: cordova-cli, cordova-plugman
>Affects Versions: 1.1.0, 6.1.1
>Reporter: Trevor Brindle
>Assignee: Shazron Abdullah
>
> CLI: 6.1.1
> Plugman: 1.2.1
> Node: 5.11.1
> npm: 3.9.2
> Steps to reproduce:
> 1. cordova create ~/Developer/plugmantest com.cordova.test plugmantest
> 2. cordova platform add ios android (4.1.1, 5.1.1)
> 3. cordova plugin add cordova-plugin-applepay-payeezy
> Resulted in: 
> Fetching plugin "cordova-plugin-applepay-payeezy" via npm
> Installing "cordova-plugin-applepay-payeezy" for android
> Installing "cordova-plugin-applepay-payeezy" for ios
> cordova-plugin-applepay-payeezy in android.json
> cordova-plugin-applepay-payeezy in platform_www
> Same result for 
> cordova plugin add https://github.com/shazron/KeychainPlugin



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Updated] (CB-11803) Plugin features don't get written to iOS-specific config.xml

[Filip Maj (JIRA)]

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

Filip Maj updated CB-11803:
---
Component/s: (was: cordova-cli)
 (was: cordova-ios)
 cordova-lib

> Plugin features don't get written to iOS-specific config.xml
> 
>
> Key: CB-11803
> URL: https://issues.apache.org/jira/browse/CB-11803
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: cordova-lib
>Affects Versions: 6.3.1
>Reporter: Matus Koprda
>Priority: Critical
>  Labels: backlog, lib-refactor
> Fix For: cordova-ios@5.0.0
>
>
> When running `cordova prepare` or `cordova platform add ios` after adding 
> plugins, the platform-specific config.xml file for iOS 
> (`platforms/ios/NAME/config.xml`) doesn't have `` tags, which 
> effectively prevents any installed plugin from working.
> The tags *do* get added when installing plugins *after* the iOS platform was 
> created.
> How to reproduce - this creates a working config.xml:
> {code}
>   cordova create test
>   cd test
>   cordova platform add ios
>   cordova plugin add cordova-plugin-device --save
> {code}
> This creates a broken config.xml (resulting in `Plugin 'Device' not found, or 
> is not a CDVPlugin.` error when running on a an iPhone):
> {code}
>   cordova create test
>   cd test
>   cordova plugin add cordova-plugin-device --save
>   cordova platform add ios
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CB-11803) Plugin features don't get written to iOS-specific config.xml

[Filip Maj (JIRA)]

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

Filip Maj commented on CB-11803:


FYI [~stevegill] this may be one example of an issue arising out of a leaky 
restore/prepare design.

Adding a 'lib-refactor' label to it do that we can come back to this one when 
we start thinking of a cordova-lib refactor.

> Plugin features don't get written to iOS-specific config.xml
> 
>
> Key: CB-11803
> URL: https://issues.apache.org/jira/browse/CB-11803
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: cordova-cli, cordova-ios
>Affects Versions: 6.3.1
>Reporter: Matus Koprda
>Priority: Critical
>  Labels: backlog, lib-refactor
> Fix For: cordova-ios@5.0.0
>
>
> When running `cordova prepare` or `cordova platform add ios` after adding 
> plugins, the platform-specific config.xml file for iOS 
> (`platforms/ios/NAME/config.xml`) doesn't have `` tags, which 
> effectively prevents any installed plugin from working.
> The tags *do* get added when installing plugins *after* the iOS platform was 
> created.
> How to reproduce - this creates a working config.xml:
> {code}
>   cordova create test
>   cd test
>   cordova platform add ios
>   cordova plugin add cordova-plugin-device --save
> {code}
> This creates a broken config.xml (resulting in `Plugin 'Device' not found, or 
> is not a CDVPlugin.` error when running on a an iPhone):
> {code}
>   cordova create test
>   cd test
>   cordova plugin add cordova-plugin-device --save
>   cordova platform add ios
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Updated] (CB-11803) Plugin features don't get written to iOS-specific config.xml

[Filip Maj (JIRA)]

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

Filip Maj updated CB-11803:
---
Labels: backlog lib-refactor  (was: )

> Plugin features don't get written to iOS-specific config.xml
> 
>
> Key: CB-11803
> URL: https://issues.apache.org/jira/browse/CB-11803
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: cordova-cli, cordova-ios
>Affects Versions: 6.3.1
>Reporter: Matus Koprda
>Priority: Critical
>  Labels: backlog, lib-refactor
> Fix For: cordova-ios@5.0.0
>
>
> When running `cordova prepare` or `cordova platform add ios` after adding 
> plugins, the platform-specific config.xml file for iOS 
> (`platforms/ios/NAME/config.xml`) doesn't have `` tags, which 
> effectively prevents any installed plugin from working.
> The tags *do* get added when installing plugins *after* the iOS platform was 
> created.
> How to reproduce - this creates a working config.xml:
> {code}
>   cordova create test
>   cd test
>   cordova platform add ios
>   cordova plugin add cordova-plugin-device --save
> {code}
> This creates a broken config.xml (resulting in `Plugin 'Device' not found, or 
> is not a CDVPlugin.` error when running on a an iPhone):
> {code}
>   cordova create test
>   cd test
>   cordova plugin add cordova-plugin-device --save
>   cordova platform add ios
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CB-11378) Can't create project

[Filip Maj (JIRA)]

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

Filip Maj commented on CB-11378:


I'm going to guess it's because node or npm was installed into the admin user 
directory, but cordova is not being run with Administrator privileges. If 
that's the case, that error would be expected. 

[~jmail] can you confirm?

> Can't create project
> 
>
> Key: CB-11378
> URL: https://issues.apache.org/jira/browse/CB-11378
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: cordova-cli
>Affects Versions: 6.2.0
> Environment: Windows 10 Pro
>Reporter: Jarek Krzemienski
>Assignee: Sergey Shakhnazarov
>Priority: Critical
>  Labels: regression, triaged
>
> I am trying to create new project after cordova upgrade to 6.2.0 and I can't 
> do that with error:
> {code}
> c:\mobile_apps\projectFolder>cordova create dirName com.example.name 
> ProjectName
> C:\Users\admin\AppData\Roaming\npm\node_modules\cordova\node_modules\configstore\index.js:69
> throw err;
> ^
> Error: EPERM: operation not permitted, rename 
> 'C:\Users\admin\.config\configstore\insight-cordova.json.1159948568' -> 
> 'C:\Users\admin\.config\configstore\insight-cordova.json'
> at Error (native)
> at Object.fs.renameSync (fs.js:729:18)
> at Function.writeFileSync [as sync] 
> (C:\Users\admin\AppData\Roaming\npm\node_modules\cordova\node_modules\write-file-atomic\index.js:39:8)
> at Object.create.all.set 
> (C:\Users\admin\AppData\Roaming\npm\node_modules\cordova\node_modules\configstore\index.js:62:21)
> at Object.Configstore 
> (C:\Users\admin\AppData\Roaming\npm\node_modules\cordova\node_modules\configstore\index.js:27:11)
> at new Insight 
> (C:\Users\admin\AppData\Roaming\npm\node_modules\cordova\node_modules\insight\lib\index.js:38:34)
> at Object. 
> (C:\Users\admin\AppData\Roaming\npm\node_modules\cordova\src\telemetry.js:37:15)
> at Module._compile (module.js:413:34)
> at Object.Module._extensions..js (module.js:422:10)
> at Module.load (module.js:357:32)
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CB-12895) Replace jshint with eslint in our tools + platforms

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-12895:
-

Github user asfgit closed the pull request at:

https://github.com/apache/cordova-ios/pull/327


> Replace jshint with eslint in our tools + platforms
> ---
>
> Key: CB-12895
> URL: https://issues.apache.org/jira/browse/CB-12895
> Project: Apache Cordova
>  Issue Type: Improvement
>  Components: AllComponents
>Reporter: Steve Gill
>Assignee: Audrey So
>Priority: Minor
>  Labels: cordova-next
>
> Based on this proposal
> https://github.com/cordova/cordova-discuss/pull/70#issuecomment-306649308
> JSHint does minimal checks and JSCS has been deprecated in favor of ESLint.
>  +
>  +I suggest to replace the current style checkers with ESLint. This allows to 
> set much more strict styling rules than at at this moment.
>  +
>  +I recommend using a popular preset, such as 
> [airbnb-base](https://www.npmjs.com/package/eslint-config-airbnb-base). 
> Example configuration:
>  +
>  +```yaml
>  +root: true
>  +
>  +extends: airbnb-base
>  +```
>  +
>  +Many styling issues could be fixed by simply running:
>  +
>  +```
>  +./node_modules/.bin/eslint --fix .
>  +```
>  +
>  +
>  +
>  +Optionally the indent could be set to 4 instead of 2, because that's used 
> in the current code base.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CB-12895) Replace jshint with eslint in our tools + platforms

[ASF subversion and git services (JIRA)]

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

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

Commit 83435d56d0e7e71a5bbb744cf93684b7e42997f7 in cordova-ios's branch 
refs/heads/master from [~auso]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-ios.git;h=83435d5 ]

CB-12895 : removed jshint and added eslint


> Replace jshint with eslint in our tools + platforms
> ---
>
> Key: CB-12895
> URL: https://issues.apache.org/jira/browse/CB-12895
> Project: Apache Cordova
>  Issue Type: Improvement
>  Components: AllComponents
>Reporter: Steve Gill
>Assignee: Audrey So
>Priority: Minor
>  Labels: cordova-next
>
> Based on this proposal
> https://github.com/cordova/cordova-discuss/pull/70#issuecomment-306649308
> JSHint does minimal checks and JSCS has been deprecated in favor of ESLint.
>  +
>  +I suggest to replace the current style checkers with ESLint. This allows to 
> set much more strict styling rules than at at this moment.
>  +
>  +I recommend using a popular preset, such as 
> [airbnb-base](https://www.npmjs.com/package/eslint-config-airbnb-base). 
> Example configuration:
>  +
>  +```yaml
>  +root: true
>  +
>  +extends: airbnb-base
>  +```
>  +
>  +Many styling issues could be fixed by simply running:
>  +
>  +```
>  +./node_modules/.bin/eslint --fix .
>  +```
>  +
>  +
>  +
>  +Optionally the indent could be set to 4 instead of 2, because that's used 
> in the current code base.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CB-12895) Replace jshint with eslint in our tools + platforms

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-12895:
-

Github user asfgit closed the pull request at:

https://github.com/apache/cordova-osx/pull/38


> Replace jshint with eslint in our tools + platforms
> ---
>
> Key: CB-12895
> URL: https://issues.apache.org/jira/browse/CB-12895
> Project: Apache Cordova
>  Issue Type: Improvement
>  Components: AllComponents
>Reporter: Steve Gill
>Assignee: Audrey So
>Priority: Minor
>  Labels: cordova-next
>
> Based on this proposal
> https://github.com/cordova/cordova-discuss/pull/70#issuecomment-306649308
> JSHint does minimal checks and JSCS has been deprecated in favor of ESLint.
>  +
>  +I suggest to replace the current style checkers with ESLint. This allows to 
> set much more strict styling rules than at at this moment.
>  +
>  +I recommend using a popular preset, such as 
> [airbnb-base](https://www.npmjs.com/package/eslint-config-airbnb-base). 
> Example configuration:
>  +
>  +```yaml
>  +root: true
>  +
>  +extends: airbnb-base
>  +```
>  +
>  +Many styling issues could be fixed by simply running:
>  +
>  +```
>  +./node_modules/.bin/eslint --fix .
>  +```
>  +
>  +
>  +
>  +Optionally the indent could be set to 4 instead of 2, because that's used 
> in the current code base.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CB-12985) Change `InAppBrowser.open(url, target, options)` to get `options` as object, not string

[ASF subversion and git services (JIRA)]

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

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

Commit 34d879e0ca56e32b8224160bba49b20e1a969721 in cordova-osx's branch 
refs/heads/master from [~auso]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-osx.git;h=34d879e ]

CB-12985 : updated to use eslint format


> Change `InAppBrowser.open(url, target, options)` to get `options` as object, 
> not string
> ---
>
> Key: CB-12985
> URL: https://issues.apache.org/jira/browse/CB-12985
> Project: Apache Cordova
>  Issue Type: Improvement
>  Components: cordova-plugin-inappbrowser
>Reporter: Jan Piotrowski
>
> `InAppBrowser.open(url, target, options)` currently expects `options` to be a 
> string, formatted in a special way (no spaces).
> It would be much easier to maintain this if `options` would be a plain 
> Javascript object.
> The yes|no values could be changed to true|false of course.
> (During this change all options should probably also be unified to use 
> camelCase)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CB-12762) Point package.json repo items to github mirrors

[ASF subversion and git services (JIRA)]

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

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

Commit 6f09ffc01eebd62328be08aabc9d6fcfd6039d3c in cordova-osx's branch 
refs/heads/master from [~auso]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-osx.git;h=6f09ffc ]

CB-12762 : point package.json repo items to github mirrors instead of apache 
repos site

 This closes #37


> Point package.json repo items to github mirrors
> ---
>
> Key: CB-12762
> URL: https://issues.apache.org/jira/browse/CB-12762
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: AllComponents
>Reporter: Jesse MacFadyen
>Assignee: Audrey So
>
> Proposal is here:
> https://github.com/cordova/cordova-discuss/issues/67



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CB-3232) "cordova platform add blackberry" fails on 2.7.1-rc.1

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-3232:


Github user asfgit closed the pull request at:

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


> "cordova platform add blackberry" fails on 2.7.1-rc.1
> -
>
> Key: CB-3232
> URL: https://issues.apache.org/jira/browse/CB-3232
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: cordova-blackberry (DEPRECATED), cordova-cli
>Affects Versions: 2.7.0
>Reporter: Michael Brooks
>Assignee: Michael Brooks
> Fix For: 2.7.0
>
>
> The following error is thrown when running {{$ cordova platform add 
> blackberry}}:
> {code}
> [Error: An error occured during creation of blackberry sub-project. Creating 
> BlackBerry project...
> Updating config.xml ...
> sed: 
> /Users/mwbrooks/Dropbox/Development/sandbox/myapp/platforms/blackberry/www/config.xml:
>  No such file or directory
> Cleaning up ...
> Remember to update the project.properties file inside your application 
> directory!
> ]
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CB-12895) Replace jshint with eslint in our tools + platforms

[ASF subversion and git services (JIRA)]

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

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

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

CB-12895 : setup eslint and removed jshint


> Replace jshint with eslint in our tools + platforms
> ---
>
> Key: CB-12895
> URL: https://issues.apache.org/jira/browse/CB-12895
> Project: Apache Cordova
>  Issue Type: Improvement
>  Components: AllComponents
>Reporter: Steve Gill
>Assignee: Audrey So
>Priority: Minor
>  Labels: cordova-next
>
> Based on this proposal
> https://github.com/cordova/cordova-discuss/pull/70#issuecomment-306649308
> JSHint does minimal checks and JSCS has been deprecated in favor of ESLint.
>  +
>  +I suggest to replace the current style checkers with ESLint. This allows to 
> set much more strict styling rules than at at this moment.
>  +
>  +I recommend using a popular preset, such as 
> [airbnb-base](https://www.npmjs.com/package/eslint-config-airbnb-base). 
> Example configuration:
>  +
>  +```yaml
>  +root: true
>  +
>  +extends: airbnb-base
>  +```
>  +
>  +Many styling issues could be fixed by simply running:
>  +
>  +```
>  +./node_modules/.bin/eslint --fix .
>  +```
>  +
>  +
>  +
>  +Optionally the indent could be set to 4 instead of 2, because that's used 
> in the current code base.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CB-12895) Replace jshint with eslint in our tools + platforms

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-12895:
-

Github user asfgit closed the pull request at:

https://github.com/apache/cordova-plugman/pull/90


> Replace jshint with eslint in our tools + platforms
> ---
>
> Key: CB-12895
> URL: https://issues.apache.org/jira/browse/CB-12895
> Project: Apache Cordova
>  Issue Type: Improvement
>  Components: AllComponents
>Reporter: Steve Gill
>Assignee: Audrey So
>Priority: Minor
>  Labels: cordova-next
>
> Based on this proposal
> https://github.com/cordova/cordova-discuss/pull/70#issuecomment-306649308
> JSHint does minimal checks and JSCS has been deprecated in favor of ESLint.
>  +
>  +I suggest to replace the current style checkers with ESLint. This allows to 
> set much more strict styling rules than at at this moment.
>  +
>  +I recommend using a popular preset, such as 
> [airbnb-base](https://www.npmjs.com/package/eslint-config-airbnb-base). 
> Example configuration:
>  +
>  +```yaml
>  +root: true
>  +
>  +extends: airbnb-base
>  +```
>  +
>  +Many styling issues could be fixed by simply running:
>  +
>  +```
>  +./node_modules/.bin/eslint --fix .
>  +```
>  +
>  +
>  +
>  +Optionally the indent could be set to 4 instead of 2, because that's used 
> in the current code base.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CB-12895) Replace jshint with eslint in our tools + platforms

[ASF subversion and git services (JIRA)]

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

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

Commit 20c2f03ba55663dd3aebecb8558b8f2c36e1651f in cordova-plugman's branch 
refs/heads/master from [~auso]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-plugman.git;h=20c2f03 ]

CB-12895 : setup eslint and remove jshint


> Replace jshint with eslint in our tools + platforms
> ---
>
> Key: CB-12895
> URL: https://issues.apache.org/jira/browse/CB-12895
> Project: Apache Cordova
>  Issue Type: Improvement
>  Components: AllComponents
>Reporter: Steve Gill
>Assignee: Audrey So
>Priority: Minor
>  Labels: cordova-next
>
> Based on this proposal
> https://github.com/cordova/cordova-discuss/pull/70#issuecomment-306649308
> JSHint does minimal checks and JSCS has been deprecated in favor of ESLint.
>  +
>  +I suggest to replace the current style checkers with ESLint. This allows to 
> set much more strict styling rules than at at this moment.
>  +
>  +I recommend using a popular preset, such as 
> [airbnb-base](https://www.npmjs.com/package/eslint-config-airbnb-base). 
> Example configuration:
>  +
>  +```yaml
>  +root: true
>  +
>  +extends: airbnb-base
>  +```
>  +
>  +Many styling issues could be fixed by simply running:
>  +
>  +```
>  +./node_modules/.bin/eslint --fix .
>  +```
>  +
>  +
>  +
>  +Optionally the indent could be set to 4 instead of 2, because that's used 
> in the current code base.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CB-12895) Replace jshint with eslint in our tools + platforms

[ASF subversion and git services (JIRA)]

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

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

Commit b5877e51c160f5df5518151a806a6a0481137902 in cordova-create's branch 
refs/heads/master from [~auso]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-create.git;h=b5877e5 ]

CB-12895 : setup eslint and remove jshint


> Replace jshint with eslint in our tools + platforms
> ---
>
> Key: CB-12895
> URL: https://issues.apache.org/jira/browse/CB-12895
> Project: Apache Cordova
>  Issue Type: Improvement
>  Components: AllComponents
>Reporter: Steve Gill
>Assignee: Audrey So
>Priority: Minor
>  Labels: cordova-next
>
> Based on this proposal
> https://github.com/cordova/cordova-discuss/pull/70#issuecomment-306649308
> JSHint does minimal checks and JSCS has been deprecated in favor of ESLint.
>  +
>  +I suggest to replace the current style checkers with ESLint. This allows to 
> set much more strict styling rules than at at this moment.
>  +
>  +I recommend using a popular preset, such as 
> [airbnb-base](https://www.npmjs.com/package/eslint-config-airbnb-base). 
> Example configuration:
>  +
>  +```yaml
>  +root: true
>  +
>  +extends: airbnb-base
>  +```
>  +
>  +Many styling issues could be fixed by simply running:
>  +
>  +```
>  +./node_modules/.bin/eslint --fix .
>  +```
>  +
>  +
>  +
>  +Optionally the indent could be set to 4 instead of 2, because that's used 
> in the current code base.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CB-13014) cordova in-app-browser doesnt support vimeo videos

[Kerri Shotts (JIRA)]

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

Kerri Shotts commented on CB-13014:
---

Please provide a link to a minimal project that duplicates the issue you are 
seeing. Without that, we're just guessing as to what you're seeing, and 
wouldn't know for sure if any changes fixed your issue.

> cordova in-app-browser doesnt support vimeo videos
> --
>
> Key: CB-13014
> URL: https://issues.apache.org/jira/browse/CB-13014
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: cordova-android, cordova-plugin-inappbrowser, Ionic
> Environment: Android
>Reporter: nidhi trivedi
>Assignee: Joe Bowser
>
> Hi, 
> We are using* cordova-plugin in-app-browser version ^1.7.1*, as part of* 
> ionic -native* in our project. to open external links in the in-app-browser
> however, whenever the external link contains vimeo video, it doesnt work with 
> the in-app-browser. It behaves weird.
> 1. sometimes the audio for the video loads and plays but video doesnt play
> 2. sometimes the video plays but the play and pause button dissappears
> we raised an issue in *vimeo* and they said we should ask for support to you. 
> can you please help us with it. Its a little urgent.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CB-13018) cordova build failed for both android and ios

[Kerri Shotts (JIRA)]

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

Kerri Shotts commented on CB-13018:
---

Surely there's more to those error logs than what's been added here? It might 
be nice to link to a gist of the entire log (sans sensitive info).

> cordova build failed for both android and ios
> -
>
> Key: CB-13018
> URL: https://issues.apache.org/jira/browse/CB-13018
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: cordova-android, cordova-ios
>Affects Versions: cordova-ios@4.4.0, cordova-android@5.2.2, 7.0.1
> Environment: (1)MacOS: 10.12.5
> (2)node: v8.1.4
> (3)cordova: 7.0.1
> (4)*cordova platform ls*
>   android 6.2.3
>   ios 4.4.0
>Reporter: oscar peng
>Assignee: Joe Bowser
>  Labels: starter
>
> Following http://cordova.apache.org/docs/en/latest/guide/cli/index.html, 
> Create your first Cordova app.
> h1. cordova requirements
>  - Requirements check results for android:
> Java JDK: installed 1.8.0
> Android SDK: installed true
> Android target: installed 
> android-26,android-25,android-24,android-N,android-23,Google Inc.:Google 
> APIs:23,android-22,android-21,android-20,android-19,android-18,android-17,android-16,android-15,android-14
> Gradle: installed /Applications/Android Studio 3.0 
> Preview.app/Contents/gradle/gradle-4.1-milestone-1/bin/gradle
>   -  Requirements check results for ios:
> Apple OS X: installed darwin
> Xcode: installed 8.3.3
> ios-deploy: not installed
> ios-deploy was not found. Please download, build and install version 1.9.0 or 
> greater from https://github.com/phonegap/ios-deploy into your path, or do 
> 'npm install -g ios-deploy'
> CocoaPods: installed
> Error: Some of requirements check failed
> h1. sudo npm install -g ios-deploy --unsafe-perm=true
> h1. cordova requirements
> Requirements check results for android:
> Java JDK: installed 1.8.0
> Android SDK: installed true
> Android target: installed 
> android-26,android-25,android-24,android-N,android-23,Google Inc.:Google 
> APIs:23,android-22,android-21,android-20,android-19,android-18,android-17,android-16,android-15,android-14
> Gradle: installed /Applications/Android Studio 3.0 
> Preview.app/Contents/gradle/gradle-4.1-milestone-1/bin/gradle
> Requirements check results for ios:
> Apple OS X: installed darwin
> Xcode: installed 8.3.3
> ios-deploy: installed 1.9.1
> CocoaPods: installed
> h1. cordova build (or cordova build android)
> ANDROID_HOME=/Users/open/Library/Android/sdk
> JAVA_HOME=/Library/Java/JavaVirtualMachines/jdk1.8.0_102.jdk/Contents/Home
> Error: spawn EACCES
> h1. cordova build ios
> ** BUILD FAILED **
> The following build commands failed:
>   PhaseScriptExecution Copy\ www\ directory 
> /Users/open/Library/Developer/Xcode/DerivedData/HelloWorld-fqxzydxnjuyjjobwofitkplrpyef/Build/Intermediates/HelloWorld.build/Debug-iphonesimulator/HelloWorld.build/Script-304B58A110DAC018002A0835.sh
> (1 failure)
> Error: Error code 65 for command: xcodebuild with args: 
> -xcconfig,/Users/open/NodeProjects/cordova-projects/hello/platforms/ios/cordova/build-debug.xcconfig,-workspace,HelloWorld.xcworkspace,-scheme,HelloWorld,-configuration,Debug,-sdk,iphonesimulator,-destination,platform=iOS
>  Simulator,name=iPhone 
> SE,build,CONFIGURATION_BUILD_DIR=/Users/open/NodeProjects/cordova-projects/hello/platforms/ios/build/emulator,SHARED_PRECOMPS_DIR=/Users/open/NodeProjects/cordova-projects/hello/platforms/ios/build/sharedpch



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Resolved] (CB-12622) Added support for Android 6 and 7 to the cloudapp CI

[Filip Maj (JIRA)]

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

Filip Maj resolved CB-12622.

Resolution: Fixed

This is live! Thanks for your hard work [~alsorokin]!

> Added support for Android 6 and 7 to the cloudapp CI
> 
>
> Key: CB-12622
> URL: https://issues.apache.org/jira/browse/CB-12622
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Appium
>Reporter: Filip Maj
>Assignee: Alexander Sorokin
>
> Capabilities for Android 6 look like:
> {noformat}
> deviceName: 'Android Emulator',
> platformName: 'Android',
> platformVersion: '6.0',
> appiumVersion: '1.6.3'
> {noformat}
> While for 7 you need to specify a different {{deviceName}}:
> {noformat}
> deviceName: 'Android GoogleAPI Emulator',
> platformName: 'Android',
> platformVersion: '7.0',
> appiumVersion: '1.6.3'
> {noformat}
> [~alsorokin] is it possible to add these to the cloudapp android environment 
> matrix?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Updated] (CB-13021) Page loads in inAppBroswer, but content is clipped

[Kerri Shotts (JIRA)]

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

Kerri Shotts updated CB-13021:
--
Description: 

The link where the content is clipped:
http://flexsystem.lenovofiles.com/help/index.jsp?topic=%2Fcom.lenovo.lxca.doc%2Flxca_usemobileapp.html

Our code snippet is:
{{cordova.InAppBrowser.open('http://pic.dhe.ibm.com/infocenter/flexsys/information/topic/com.lenovo.lxca.doc/lxca_usemobileapp.html',
 '_blank', 'location=no,EnableViewPortScale=yes')}}

Our config.xml has this present:
{{}}

Launching the above link in the inAppBrowser shows the content but when the 
sidebar navigation on the page loads, the main content is clipped in the right 
hand side.




  was:
Launching the above link in the inAppBrowser shows the content but when the 
sidebar navigation on the page loads, the main content is clipped in the right 
hand side.





> Page loads in inAppBroswer, but content is clipped
> --
>
> Key: CB-13021
> URL: https://issues.apache.org/jira/browse/CB-13021
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: cordova-plugin-inappbrowser
>Affects Versions: cordova@7.0.0
> Environment: Ionic 1 app
> cordova-plugin-inappbrowser at 1.7.1
> cordova-ios at 4.4.0
>Reporter: MA
>Priority: Minor
>
> The link where the content is clipped:
> http://flexsystem.lenovofiles.com/help/index.jsp?topic=%2Fcom.lenovo.lxca.doc%2Flxca_usemobileapp.html
> Our code snippet is:
> {{cordova.InAppBrowser.open('http://pic.dhe.ibm.com/infocenter/flexsys/information/topic/com.lenovo.lxca.doc/lxca_usemobileapp.html',
>  '_blank', 'location=no,EnableViewPortScale=yes')}}
> Our config.xml has this present:
> {{}}
> Launching the above link in the inAppBrowser shows the content but when the 
> sidebar navigation on the page loads, the main content is clipped in the 
> right hand side.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CB-9661) Plugins should be notified after deviceready event has been fired

[Filip Maj (JIRA)]

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

Filip Maj commented on CB-9661:
---

As a workaround: what about having the plugin javascript wait for the 
deviceready event in JS land, and then send a message back to native using the 
regular {{cordova.exec}} channel?

> Plugins should be notified after deviceready event has been fired
> -
>
> Key: CB-9661
> URL: https://issues.apache.org/jira/browse/CB-9661
> Project: Apache Cordova
>  Issue Type: Improvement
>  Components: AllPlugins
>Affects Versions: 5.1.1
>Reporter: Sebastien Lorber
>
> I use the Intercom plugin.
> It is a plugin that shows a little button at the bottom (that we'll call 
> "widget") that permits to show a native chat panel when the user wants to 
> give a feedback for our app.
> On startup I run something akin to:
> {code}
> function deviceReady() {
> hideSplashScreen();
> if ( isUserConnected() ) {
> intercom.registerIdentifiedUser(userIntercomData);
> startApp();
> } 
> else {
> intercom.reset();
> showLoginForm();
> }
> }
> {code}
> The widget is only shawn after calling intercom.registerIdentifiedUser();
> The widget disappear when we call intercom.reset();
> The intercom plugin memoizes the fact that an user is registered over time.
> This means that if I kill the app with a registered user, and restart it, 
> Intercom will by default restore that regitered user on next startup.
> Unfortunatly, this means that the widget will be shawn at the very beginning 
> of the app initialization, even before the webview is initialized. In my 
> case, it means that the Intercom button will be shawn for a little amount of 
> time above the splash screen, which is a bit weird.
> This would make sense for the Intercom team to not show the widget until the 
> webview is initialized, particularly waiting for deviceready event to fire.
> After discussing with the Intercom team, it seems they can't implement this 
> because there's no possible way to wait for the deviceready event to fire 
> from the native plugin code.
> So I think it could be nice to be able, from the native plugin code, to wait 
> for the deviceready event to be handled, so that native code can be started 
> afterwards.
> The original plugin issue: 
> https://github.com/intercom/intercom-cordova/issues/18



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Updated] (CB-13021) Page loads in inAppBroswer, but content is clipped

[Kerri Shotts (JIRA)]

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

Kerri Shotts updated CB-13021:
--
Environment: 
Ionic 1 app
cordova-plugin-inappbrowser at 1.7.1
cordova-ios at 4.4.0



  was:
Ionic 1 app
cordova-plugin-inappbrowser at 1.7.1
cordova-ios at 4.4.0

The link where the content is clipped:
http://flexsystem.lenovofiles.com/help/index.jsp?topic=%2Fcom.lenovo.lxca.doc%2Flxca_usemobileapp.html

Our code snippet is:
cordova.InAppBrowser.open('http://pic.dhe.ibm.com/infocenter/flexsys/information/topic/com.lenovo.lxca.doc/lxca_usemobileapp.html',
 '_blank', 'location=no,EnableViewPortScale=yes')

Our config.xml has this present:




> Page loads in inAppBroswer, but content is clipped
> --
>
> Key: CB-13021
> URL: https://issues.apache.org/jira/browse/CB-13021
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: cordova-plugin-inappbrowser
>Affects Versions: cordova@7.0.0
> Environment: Ionic 1 app
> cordova-plugin-inappbrowser at 1.7.1
> cordova-ios at 4.4.0
>Reporter: MA
>Priority: Minor
>
> Launching the above link in the inAppBrowser shows the content but when the 
> sidebar navigation on the page loads, the main content is clipped in the 
> right hand side.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Assigned] (CB-13024) Default launch images still copied on iOS when using launch storyboard

[Kerri Shotts (JIRA)]

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

Kerri Shotts reassigned CB-13024:
-

Assignee: Kerri Shotts

> Default launch images still copied on iOS when using launch storyboard
> --
>
> Key: CB-13024
> URL: https://issues.apache.org/jira/browse/CB-13024
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: cordova-plugin-splashscreen
>Affects Versions: cordova-ios@4.4.0, cordova@7.0.0
> Environment: MacOS X 10.12.5
>Reporter: Yohan Lasorsa
>Assignee: Kerri Shotts
>Priority: Minor
>
> For defining the iOS splash screen, I use the new storyboard launch images 
> with this single line:
> {code:xml}
> 
> {code}
> Even though I do not use legacy launch images at all, the default cordova 
> launch images are still copied in the app resources and use a lot of disk 
> space for nothing, as shown on this screenshot:
> !https://img4.hostingpics.net/pics/643781Capturedecran20170714a213922.png!



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CB-13024) Default launch images still copied on iOS when using launch storyboard

[Kerri Shotts (JIRA)]

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

Kerri Shotts commented on CB-13024:
---

Can you paste a link to the output of {{cordova prepare ios --verbose}}? And I 
just want to verify that, for iOS, you have only one {{splash}} tag?

> Default launch images still copied on iOS when using launch storyboard
> --
>
> Key: CB-13024
> URL: https://issues.apache.org/jira/browse/CB-13024
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: cordova-plugin-splashscreen
>Affects Versions: cordova-ios@4.4.0, cordova@7.0.0
> Environment: MacOS X 10.12.5
>Reporter: Yohan Lasorsa
>Priority: Minor
>
> For defining the iOS splash screen, I use the new storyboard launch images 
> with this single line:
> {code:xml}
> 
> {code}
> Even though I do not use legacy launch images at all, the default cordova 
> launch images are still copied in the app resources and use a lot of disk 
> space for nothing, as shown on this screenshot:
> !https://img4.hostingpics.net/pics/643781Capturedecran20170714a213922.png!



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Resolved] (CB-9744) Plugin documentation should be generated from source code

[Filip Maj (JIRA)]

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

Filip Maj resolved CB-9744.
---
Resolution: Fixed

This is done.

> Plugin documentation should be generated from source code
> -
>
> Key: CB-9744
> URL: https://issues.apache.org/jira/browse/CB-9744
> Project: Apache Cordova
>  Issue Type: Task
>  Components: AllPlugins
>Reporter: Sergey Shakhnazarov
>
> [cordova-discuss PR|https://github.com/cordova/cordova-discuss/pull/16]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CB-11415) Can we merge all the cordova plugin objects in one single file

[Filip Maj (JIRA)]

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

Filip Maj commented on CB-11415:


Wait, what about the {{--browserify}} flag?

> Can we merge all the cordova plugin objects in one single file
> --
>
> Key: CB-11415
> URL: https://issues.apache.org/jira/browse/CB-11415
> Project: Apache Cordova
>  Issue Type: Improvement
>  Components: cordova-browser
> Environment: All the platforms
>Reporter: Arcoiris Labs
>Priority: Minor
>  Labels: build, performance
>
> Hi,
> Is it possible to merge all the plugin objects in one single file so that the 
> number of HTTP requests to pull the cordova plugin libraries shall be reduced 
> and the performance can be improved?? 
> The reason I am asking for this feature because when creating an app that 
> contains 20 plugins so then the browser has to request unminified files 20 
> times before the body is rendered. If we collab all the plugins in a single 
> file, all the plugins shall be accessed from a single file.
> Also we can use uglify/minify the plugin file during after_prepare hook which 
> can reduce the file size, which can be totally upto the developer's choice.
> It could also be a feature in the CLI itself that will minify and uglify the 
> plugins during release mode



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CB-11415) Can we merge all the cordova plugin objects in one single file

[Filip Maj (JIRA)]

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

Filip Maj commented on CB-11415:


I would say this issue is only relevant on the browser platform. For the other 
platforms, each plugin's JS is loaded from storage local on the device, so the 
number of requests has very negligible performance impact. In a browser 
environment, though, it makes sense.

I could see this feature existing as part of the tooling for the 
cordova-browser platform, like you mentioned, a pre-build/after-prepare 
concatenation/minification step.

> Can we merge all the cordova plugin objects in one single file
> --
>
> Key: CB-11415
> URL: https://issues.apache.org/jira/browse/CB-11415
> Project: Apache Cordova
>  Issue Type: Improvement
>  Components: cordova-browser
> Environment: All the platforms
>Reporter: Arcoiris Labs
>Priority: Minor
>  Labels: build, performance
>
> Hi,
> Is it possible to merge all the plugin objects in one single file so that the 
> number of HTTP requests to pull the cordova plugin libraries shall be reduced 
> and the performance can be improved?? 
> The reason I am asking for this feature because when creating an app that 
> contains 20 plugins so then the browser has to request unminified files 20 
> times before the body is rendered. If we collab all the plugins in a single 
> file, all the plugins shall be accessed from a single file.
> Also we can use uglify/minify the plugin file during after_prepare hook which 
> can reduce the file size, which can be totally upto the developer's choice.
> It could also be a feature in the CLI itself that will minify and uglify the 
> plugins during release mode



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Updated] (CB-11415) Can we merge all the cordova plugin objects in one single file

[Filip Maj (JIRA)]

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

Filip Maj updated CB-11415:
---
Component/s: (was: AllPlatforms)
 cordova-browser

> Can we merge all the cordova plugin objects in one single file
> --
>
> Key: CB-11415
> URL: https://issues.apache.org/jira/browse/CB-11415
> Project: Apache Cordova
>  Issue Type: Improvement
>  Components: cordova-browser
> Environment: All the platforms
>Reporter: Arcoiris Labs
>Priority: Minor
>  Labels: build, performance
>
> Hi,
> Is it possible to merge all the plugin objects in one single file so that the 
> number of HTTP requests to pull the cordova plugin libraries shall be reduced 
> and the performance can be improved?? 
> The reason I am asking for this feature because when creating an app that 
> contains 20 plugins so then the browser has to request unminified files 20 
> times before the body is rendered. If we collab all the plugins in a single 
> file, all the plugins shall be accessed from a single file.
> Also we can use uglify/minify the plugin file during after_prepare hook which 
> can reduce the file size, which can be totally upto the developer's choice.
> It could also be a feature in the CLI itself that will minify and uglify the 
> plugins during release mode



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Resolved] (CB-9550) Plugin for encrypting cordova projects

[Filip Maj (JIRA)]

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

Filip Maj resolved CB-9550.
---
Resolution: Won't Fix

The linked to repository actually stores its encryption key in the native code, 
which could be unobfuscated, no? Don't think this is a good approach for 
encryption. Closing.

> Plugin for encrypting cordova projects
> --
>
> Key: CB-9550
> URL: https://issues.apache.org/jira/browse/CB-9550
> Project: Apache Cordova
>  Issue Type: New Feature
>  Components: AllPlatforms
>Affects Versions: Master
> Environment: iOS, Android
>Reporter: Tammo Schimanski
>Priority: Minor
>  Labels: features, security
>
> Hey Guys,
> just a few weeks ago user tkyaji released an encryption plugin for iOS and 
> Android on GitHub. The plugin is going to encrypt your whole code (especially 
> .html, .htm, .css, and .js files). 
> One main reason for developers as far as i know is, that you're able to read 
> out the code someone wrote via a very easy way (just decompile the 
> application). 
> Adding the plugin from tkyaji will hide your code in a very great way. I 
> think this should be integrated into the docs or more!?
> More information can be found here -> 
> https://github.com/tkyaji/cordova-plugin-crypt-file



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Updated] (CB-12468) cordova-inappbrowser-plugin setDefaultOptions method

[Filip Maj (JIRA)]

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

Filip Maj updated CB-12468:
---
Issue Type: New Feature  (was: Improvement)

> cordova-inappbrowser-plugin setDefaultOptions method
> 
>
> Key: CB-12468
> URL: https://issues.apache.org/jira/browse/CB-12468
> Project: Apache Cordova
>  Issue Type: New Feature
>  Components: cordova-lib
>Affects Versions: 3.5.0
> Environment: IOS/Android
>Reporter: Ivan Prodaiko
>  Labels: features
> Fix For: Master
>
>
> While using cordova-inappbrowser-plugin I must set popup features only when 
> calling window.open method. But a lot of libraries (firebase, openFB) use 
> window.open inside their own code where I can't directly menage the features 
> of window to be opened, and on IOS, where we do not a have a 'back' button we 
> could have a problem. For example window, opened with 'toolbar=no' will make 
> app to stack with no ability to close the window. Another thing to be 
> mentioned is when on IOS you use  attribute, after opening a 
> new window without setting 'allowInlineMediaPlayback=yes' all inline 
> attributes will stop working properly and video will start to open in a 
> fullscreen mode.
> So, my proposal is to provide an ability to setDefaultOptions method that 
> will help to prevent external libraries to manage the options of of window to 
> be opened directly.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Updated] (CB-12468) cordova-inappbrowser-plugin setDefaultOptions method

[Filip Maj (JIRA)]

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

Filip Maj updated CB-12468:
---
Component/s: (was: AllPlatforms)

> cordova-inappbrowser-plugin setDefaultOptions method
> 
>
> Key: CB-12468
> URL: https://issues.apache.org/jira/browse/CB-12468
> Project: Apache Cordova
>  Issue Type: Improvement
>  Components: cordova-lib
>Affects Versions: 3.5.0
> Environment: IOS/Android
>Reporter: Ivan Prodaiko
>  Labels: features
> Fix For: Master
>
>
> While using cordova-inappbrowser-plugin I must set popup features only when 
> calling window.open method. But a lot of libraries (firebase, openFB) use 
> window.open inside their own code where I can't directly menage the features 
> of window to be opened, and on IOS, where we do not a have a 'back' button we 
> could have a problem. For example window, opened with 'toolbar=no' will make 
> app to stack with no ability to close the window. Another thing to be 
> mentioned is when on IOS you use  attribute, after opening a 
> new window without setting 'allowInlineMediaPlayback=yes' all inline 
> attributes will stop working properly and video will start to open in a 
> fullscreen mode.
> So, my proposal is to provide an ability to setDefaultOptions method that 
> will help to prevent external libraries to manage the options of of window to 
> be opened directly.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CB-12670) Clean up Apache Cordova JIRA

[Filip Maj (JIRA)]

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

Filip Maj commented on CB-12670:


I've tried to make some changes to the boards to make some of this stuff 
clearer.

In particular there are a series of '*-next' boards per component now. The idea 
is to use these leading up to a release for a particular component to allow you 
to see what's left to do, what's in progress and what's done. Issues labeled 
with e.g. "android-next" will show up under the "android-next" board.

Also added a wider-view 'backlog' board (similarly tagged via the backlog 
label) that shows _all_ components: 
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=195

Agree we should be more diligent with adding proper Releases per component. I 
will try to include that in my workflow.

> Clean up Apache Cordova JIRA
> 
>
> Key: CB-12670
> URL: https://issues.apache.org/jira/browse/CB-12670
> Project: Apache Cordova
>  Issue Type: Wish
>  Components: AllComponents
>Reporter: Jan Piotrowski
>Priority: Minor
>  Labels: jira
>
> or: Make Apache Cordova JIRA usable again!
> I was complaining about the Cordova JIRA on Slack today, wondering how great 
> the world would be if Cordova used GitHub issues. Then I noticed that this 
> was not very productive as it seems there is no way to achieve this.
> So I actually looked at the Cordova JIRA a bit and tried to find ways how it 
> could actually be improved:
> *Speed*
> - Why is everything so slow? Any way to speed it up?
> *Menu: Summary*
> https://issues.apache.org/jira/browse/CB/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel
> - Remove or update versions  if not used
> *Menu: Issues*
> https://issues.apache.org/jira/browse/CB/?selectedItem=com.atlassian.jirafisheyeplugin:fisheye-projectpanel=statistics=com.atlassian.jira.jira-projects-plugin:issues-panel
> - Declutter "Unresolved: By Assignee" by unassigning Issues with no updates 
> in last 6 months
> - "Unresolved: By Version" is pretty useless because of plugin versions 
> (1.4.0 of what?)
> *Menu: Roadmap*
> https://issues.apache.org/jira/browse/CB/?selectedTab=com.atlassian.jira.jira-projects-plugin:roadmap-panel
> https://issues.apache.org/jira/browse
> Menu: Changelogs
> /CB/?selectedTab=com.atlassian.jira.jira-projects-plugin:changelog-panel
> - Remove or update versions
> - If versions, roadmap or changelogs are not used, remove menu link 
> completely (Same for Component overview pages)
> *Menu: Versions*
> https://issues.apache.org/jira/browse/CB?selectedTab=com.atlassian.jira.jira-projects-plugin:versions-panel=-1
> - Sorting?
> - Missing descriptions
> - Missing release dates for so many versions
> - Unclear names
> *Menu: Components*
> https://issues.apache.org/jira/browse/CB/?selectedTab=com.atlassian.jira.jira-projects-plugin:components-panel=-1
> - Missing descriptions
> *Header*
> - Why all this unrelevant (to Cordova) stuff?
> - Getting from an issue to the Project summary is... "easy" but unexpected if 
> you don't know yet.
> Any way to help?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CB-12762) Point package.json repo items to github mirrors

[Filip Maj (JIRA)]

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

Filip Maj commented on CB-12762:


I think this one is almost complete, but still a few stragglers:

{noformat}
➔ find . -name package.json -maxdepth 2 | xargs grep url | grep git-wip
./cordova-amazon-fireos/package.json:"url": 
"https://git-wip-us.apache.org/repos/asf/cordova-amazon-fireos.git;
./cordova-app-hello-world/package.json:"url": 
"https://git-wip-us.apache.org/repos/asf/cordova-app-hello-world.git;
./cordova-blackberry/package.json:"url": 
"https://git-wip-us.apache.org/repos/asf/cordova-blackberry.git;
./cordova-coho/package.json:"url": 
"https://git-wip-us.apache.org/repos/asf/cordova-coho.git;
./cordova-firefoxos/package.json:"url": 
"https://git-wip-us.apache.org/repos/asf/cordova-firefoxos.git;
./cordova-js/package.json:"url": 
"http://git-wip-us.apache.org/repos/asf/cordova-js.git;
./cordova-osx/package.json:"url": 
"https://git-wip-us.apache.org/repos/asf/cordova-osx.git;
./cordova-plugin-wkwebview-engine/package.json:"url": 
"https://git-wip-us.apache.org/repos/asf/cordova-plugin-wkwebview-engine.git;
./cordova-plugman/package.json:"url": 
"git://git-wip-us.apache.org/repos/asf/cordova-plugman.git"
./cordova-registry/package.json:"url": 
"https://git-wip-us.apache.org/repos/asf/cordova-registry.git;
./cordova-tizen/package.json:"url": 
"https://git-wip-us.apache.org/repos/asf/cordova-tizen.git;
./cordova-ubuntu/package.json:"url": 
"https://git-wip-us.apache.org/repos/asf/cordova-ubuntu.git;
./cordova-webos/package.json:"url": 
"https://git-wip-us.apache.org/repos/asf/cordova-webos.git;
./cordova-wp8/package.json:"url": 
"https://git-wip-us.apache.org/repos/asf/cordova-wp8.git;
{noformat}

Lots of the above are deprecated repositories, so I don't care about them, but 
the ones that we should update to close this issue off are coho, js, osx, 
plugin-wkwebview, plugman and registry. [~auso] are you able to finish this one 
off?

> Point package.json repo items to github mirrors
> ---
>
> Key: CB-12762
> URL: https://issues.apache.org/jira/browse/CB-12762
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: AllComponents
>Reporter: Jesse MacFadyen
>Assignee: Audrey So
>
> Proposal is here:
> https://github.com/cordova/cordova-discuss/issues/67



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CB-12895) Replace jshint with eslint in our tools + platforms

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-12895:
-

GitHub user audreyso opened a pull request:

https://github.com/apache/cordova-osx/pull/38

CB-12895 : replaced jshint with eslint



### Platforms affected


### What does this PR do?

Replaced jshint with eslint

### What testing has been done on this change?


### Checklist
- [X] [Reported an issue](http://cordova.apache.org/contribute/issues.html) 
in the JIRA database
- [X] Commit message follows the format: "CB-3232: (android) Fix bug with 
resolving file paths", where CB- is the JIRA ID & "android" is the platform 
affected.
- [X] Added automated test coverage as appropriate for this change.


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

$ git pull https://github.com/audreyso/cordova-osx CB-12895

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

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


commit 031e2c2c99af24dd3d5de3c69a369814da6a6716
Author: Audrey So 
Date:   2017-06-01T18:41:28Z

CB-12762 : point package.json repo items to github mirrors instead of 
apache repos site

 This closes #37

commit e6ff572ccc752817f989a5e29840da134c320cba
Author: Audrey So 
Date:   2017-07-14T18:14:04Z

CB-12985 : updated to use eslint format




> Replace jshint with eslint in our tools + platforms
> ---
>
> Key: CB-12895
> URL: https://issues.apache.org/jira/browse/CB-12895
> Project: Apache Cordova
>  Issue Type: Improvement
>  Components: AllComponents
>Reporter: Steve Gill
>Assignee: Audrey So
>Priority: Minor
>  Labels: cordova-next
>
> Based on this proposal
> https://github.com/cordova/cordova-discuss/pull/70#issuecomment-306649308
> JSHint does minimal checks and JSCS has been deprecated in favor of ESLint.
>  +
>  +I suggest to replace the current style checkers with ESLint. This allows to 
> set much more strict styling rules than at at this moment.
>  +
>  +I recommend using a popular preset, such as 
> [airbnb-base](https://www.npmjs.com/package/eslint-config-airbnb-base). 
> Example configuration:
>  +
>  +```yaml
>  +root: true
>  +
>  +extends: airbnb-base
>  +```
>  +
>  +Many styling issues could be fixed by simply running:
>  +
>  +```
>  +./node_modules/.bin/eslint --fix .
>  +```
>  +
>  +
>  +
>  +Optionally the indent could be set to 4 instead of 2, because that's used 
> in the current code base.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CB-12895) Replace jshint with eslint in our tools + platforms

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-12895:
-

GitHub user audreyso opened a pull request:

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

CB-12895 : replaced jshint with eslint



### Platforms affected


### What does this PR do?
Replaced jshint with eslint

### What testing has been done on this change?


### Checklist
- [X] [Reported an issue](http://cordova.apache.org/contribute/issues.html) 
in the JIRA database
- [X] Commit message follows the format: "CB-3232: (android) Fix bug with 
resolving file paths", where CB- is the JIRA ID & "android" is the platform 
affected.
- [X] Added automated test coverage as appropriate for this change.


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

$ git pull https://github.com/audreyso/cordova-plugin-camera CB-12895

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

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


commit e2a27e6679585b0e4931b68dcf0b389014d877f2
Author: Audrey So 
Date:   2017-06-09T21:51:30Z

CB-12985 : setup eslint and removed jshint

commit f6a2fec1844b00ab6f1caf3e066c13817c9b4e70
Author: Audrey So 
Date:   2017-07-14T21:19:05Z

CB-12895 : updated src files to use eslint format




> Replace jshint with eslint in our tools + platforms
> ---
>
> Key: CB-12895
> URL: https://issues.apache.org/jira/browse/CB-12895
> Project: Apache Cordova
>  Issue Type: Improvement
>  Components: AllComponents
>Reporter: Steve Gill
>Assignee: Audrey So
>Priority: Minor
>  Labels: cordova-next
>
> Based on this proposal
> https://github.com/cordova/cordova-discuss/pull/70#issuecomment-306649308
> JSHint does minimal checks and JSCS has been deprecated in favor of ESLint.
>  +
>  +I suggest to replace the current style checkers with ESLint. This allows to 
> set much more strict styling rules than at at this moment.
>  +
>  +I recommend using a popular preset, such as 
> [airbnb-base](https://www.npmjs.com/package/eslint-config-airbnb-base). 
> Example configuration:
>  +
>  +```yaml
>  +root: true
>  +
>  +extends: airbnb-base
>  +```
>  +
>  +Many styling issues could be fixed by simply running:
>  +
>  +```
>  +./node_modules/.bin/eslint --fix .
>  +```
>  +
>  +
>  +
>  +Optionally the indent could be set to 4 instead of 2, because that's used 
> in the current code base.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Resolved] (CB-9958) Repo package.json files should point to github mirrors and not apache git

[Filip Maj (JIRA)]

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

Filip Maj resolved CB-9958.
---
Resolution: Duplicate

Closing as duplicate of CB-12762.

> Repo package.json files should point to github mirrors and not apache git
> -
>
> Key: CB-9958
> URL: https://issues.apache.org/jira/browse/CB-9958
> Project: Apache Cordova
>  Issue Type: Improvement
>  Components: AllComponents
>Reporter: Steve Gill
>Priority: Minor
>  Labels: triaged
>
> All our repos should update their package.json files to point to github 
> mirrors and not apache git repos. This repo field is displayed on npm and we 
> would rather have people go to the mirrors (better UI) than apache git.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Resolved] (CB-4204) add XSD schema for config.xml

[Filip Maj (JIRA)]

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

Filip Maj resolved CB-4204.
---
Resolution: Won't Fix

With config.xml not being a valid spec so much anymore, closing this as Won't 
Fix.

> add XSD schema for config.xml
> -
>
> Key: CB-4204
> URL: https://issues.apache.org/jira/browse/CB-4204
> Project: Apache Cordova
>  Issue Type: Improvement
>Reporter: Marcel Kinard
>Assignee: Marcel Kinard
>Priority: Minor
>
> Would be nice if there was an XML schema (xsd) for the config.xml file. This 
> would enable the xml to be validated programatically, and help serve as a 
> reference.
> Separate Jira items may look at automatically invoking the validation at app 
> build time.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Resolved] (CB-12744) Misspelling in Config.xml documentation

[Filip Maj (JIRA)]

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

Filip Maj resolved CB-12744.

Resolution: Fixed

Looks like this has been merged in / resolved.

> Misspelling in Config.xml documentation
> ---
>
> Key: CB-12744
> URL: https://issues.apache.org/jira/browse/CB-12744
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: cordova-docs
>Reporter: John C. Bland II
>Priority: Trivial
>  Labels: documentation
>
> Documentation reads:
> > This sets the IPHONEOSDEPLOYMENTTARGET in the build, which ultimately 
> > tranlsates to the MinimumOSVersion in the ipa. For more details please 
> > refer to Apple's documentation on Deployment Target Settings
> `tranlsates` is misspelled.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Updated] (CB-12744) Misspelling in Config.xml documentation

[Filip Maj (JIRA)]

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

Filip Maj updated CB-12744:
---
Component/s: cordova-docs

> Misspelling in Config.xml documentation
> ---
>
> Key: CB-12744
> URL: https://issues.apache.org/jira/browse/CB-12744
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: cordova-docs
>Reporter: John C. Bland II
>Priority: Trivial
>  Labels: documentation
>
> Documentation reads:
> > This sets the IPHONEOSDEPLOYMENTTARGET in the build, which ultimately 
> > tranlsates to the MinimumOSVersion in the ipa. For more details please 
> > refer to Apple's documentation on Deployment Target Settings
> `tranlsates` is misspelled.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Updated] (CB-12691) iOS icon sizes documentation

[Filip Maj (JIRA)]

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

Filip Maj updated CB-12691:
---
Component/s: (was: cordova-ios)

> iOS icon sizes documentation
> 
>
> Key: CB-12691
> URL: https://issues.apache.org/jira/browse/CB-12691
> Project: Apache Cordova
>  Issue Type: Improvement
>  Components: cordova-docs
>Reporter: Steve
>Priority: Minor
> Fix For: cordova-ios@4.4.1
>
> Attachments: icon.xml
>
>
> The documentation of icon sizes for iOS is confusing me.
> After long research I got a summary about the right sizes and a idea for a 
> better documentation.
> Following the rules on table 5 and 6 on 
> https://developer.apple.com/library/content/qa/qa1686/_index.html I got a 
> good overview.
> Please watch the attachment. This overview is much better and clearer than 
> the current and keeps the current minimum supported iOS version in mind.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Updated] (CB-4089) Undocumented API rule? Passing invalid option values uses default value instead.

[Filip Maj (JIRA)]

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

Filip Maj updated CB-4089:
--
Labels: backlog  (was: )

> Undocumented API rule? Passing invalid option values uses default value 
> instead.
> 
>
> Key: CB-4089
> URL: https://issues.apache.org/jira/browse/CB-4089
> Project: Apache Cordova
>  Issue Type: Improvement
>  Components: cordova-docs
>Affects Versions: 2.7.0
>Reporter: Peter
>Assignee: Michael Brooks
>Priority: Minor
>  Labels: backlog
>
> It looks like there is some undocumented rule such that if an _invalid_ 
> option value is passed via a Cordova API then the _default_ value will be 
> used instead.
> For example, the following calls are all equaivalent:
> {code}
> navigator.globalization.dateToString(new Date(), win, fail, {selector: 
> 'banana'}) 
> navigator.globalization.dateToString(new Date(), win, fail, {selector: 'date 
> and time'}) 
> navigator.globalization.dateToString(new Date(), win, fail, {}) 
> {code}
> I had (wrongly) expected 'banana' would result in some kind of API error 
> since it is not a supported value for the selector.
> This undocumented API rule should be documented.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CB-4089) Undocumented API rule? Passing invalid option values uses default value instead.

[Filip Maj (JIRA)]

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

Filip Maj commented on CB-4089:
---

Worth noting that while argument _types_ are validated in most core Cordova 
plugins (see 
https://github.com/apache/cordova-js/blob/master/src/common/argscheck.js#L39), 
properties on object parameters (such as used in your example) are not 
validated.

Agree that the docs for authoring plugins could probably cover this fact, and 
also point folks to the existing cordova-js utility methods such as 
{{argsCheck}} (and maybe worth showing examples using some code cordova plugin 
code).

> Undocumented API rule? Passing invalid option values uses default value 
> instead.
> 
>
> Key: CB-4089
> URL: https://issues.apache.org/jira/browse/CB-4089
> Project: Apache Cordova
>  Issue Type: Improvement
>  Components: cordova-docs
>Affects Versions: 2.7.0
>Reporter: Peter
>Assignee: Michael Brooks
>Priority: Minor
>
> It looks like there is some undocumented rule such that if an _invalid_ 
> option value is passed via a Cordova API then the _default_ value will be 
> used instead.
> For example, the following calls are all equaivalent:
> {code}
> navigator.globalization.dateToString(new Date(), win, fail, {selector: 
> 'banana'}) 
> navigator.globalization.dateToString(new Date(), win, fail, {selector: 'date 
> and time'}) 
> navigator.globalization.dateToString(new Date(), win, fail, {}) 
> {code}
> I had (wrongly) expected 'banana' would result in some kind of API error 
> since it is not a supported value for the selector.
> This undocumented API rule should be documented.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Updated] (CB-4089) Undocumented API rule? Passing invalid option values uses default value instead.

[Filip Maj (JIRA)]

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

Filip Maj updated CB-4089:
--
Component/s: (was: cordova-plugin-globalization)
 cordova-docs

> Undocumented API rule? Passing invalid option values uses default value 
> instead.
> 
>
> Key: CB-4089
> URL: https://issues.apache.org/jira/browse/CB-4089
> Project: Apache Cordova
>  Issue Type: Improvement
>  Components: cordova-docs
>Affects Versions: 2.7.0
>Reporter: Peter
>Assignee: Michael Brooks
>Priority: Minor
>
> It looks like there is some undocumented rule such that if an _invalid_ 
> option value is passed via a Cordova API then the _default_ value will be 
> used instead.
> For example, the following calls are all equaivalent:
> {code}
> navigator.globalization.dateToString(new Date(), win, fail, {selector: 
> 'banana'}) 
> navigator.globalization.dateToString(new Date(), win, fail, {selector: 'date 
> and time'}) 
> navigator.globalization.dateToString(new Date(), win, fail, {}) 
> {code}
> I had (wrongly) expected 'banana' would result in some kind of API error 
> since it is not a supported value for the selector.
> This undocumented API rule should be documented.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CB-12096) Apostrophe Escaping of names needs to be updated

[Filip Maj (JIRA)]

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

Filip Maj commented on CB-12096:


[~bowserj] can you elaborate on this issue? And is this a config.xml-parsing 
issue or a cordova-android issue?

> Apostrophe Escaping of names needs to be updated
> 
>
> Key: CB-12096
> URL: https://issues.apache.org/jira/browse/CB-12096
> Project: Apache Cordova
>  Issue Type: Bug
>Reporter: Joe Bowser
>Priority: Minor
>
> Android applications that escape apostrophes will run into compile errors.  
> Removing the escaping in config.xml fixes the issue.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Resolved] (CB-6176) HideKeyboardFormAccessoryBar no longer exists

[Filip Maj (JIRA)]

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

Filip Maj resolved CB-6176.
---
Resolution: Fixed

Seems to be fixed now.

> HideKeyboardFormAccessoryBar no longer exists
> -
>
> Key: CB-6176
> URL: https://issues.apache.org/jira/browse/CB-6176
> Project: Apache Cordova
>  Issue Type: Bug
>Affects Versions: 3.4.0
> Environment: iOS
>Reporter: Daniel Morrison
>Priority: Minor
>  Labels: easyfix, longtime
>
> On the documentation for 3.4.0 under "The config.xml File" -> "Multi-Platform 
> Preferences"  
> is said to still work with iOS.
> Link: 
> http://cordova.apache.org/docs/en/3.4.0/config_ref_index.md.html#The%20config.xml%20File
> When the preference is added to the config file it doesn't do anything. I 
> can't find a single string of code in the Xcode project that references it 
> either. Is it meant to be there and gone missing, should the documentation be 
> updated, am i doing something wrong or is this a bug.
> thanks



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Resolved] (CB-6273) Support config.xml BackgroundColor property

[Filip Maj (JIRA)]

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

Filip Maj resolved CB-6273.
---
Resolution: Fixed

> Support config.xml BackgroundColor property
> ---
>
> Key: CB-6273
> URL: https://issues.apache.org/jira/browse/CB-6273
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: cordova-ios
>Reporter: Jesse MacFadyen
>Priority: Minor
>
> Some platforms support it, some do not.  Let's be consistent.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Resolved] (CB-6311) Document developer-centeric CLI commands

[Filip Maj (JIRA)]

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

Filip Maj resolved CB-6311.
---
Resolution: Fixed

All of the specified options are documented now.

> Document developer-centeric CLI commands
> 
>
> Key: CB-6311
> URL: https://issues.apache.org/jira/browse/CB-6311
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: cordova-cli
>Affects Versions: 3.4.0
>Reporter: Mike Billau
>Assignee: Mike Billau
>Priority: Minor
>
> There are a few CLI commands and parameters that are only useful for cordova 
> developers and are thus not documented on our main docs site. It would be 
> nice to document this information in the Cordova wiki.
> Some topics:
> Platform-specific preferences: http://markmail.org/thread/7kalpsmw7rcvsbo7
> Creating myProject/.cordova/config.json to specify where the platforms should 
> be installed from: 
> https://github.com/apache/cordova-mobile-spec/blob/master/createmobilespec.sh#L57
> Parameters in create, like --link-to: 
> https://github.com/apache/cordova-mobile-spec/blob/master/createmobilespec.sh#L43
> I'm sure there are others out there...



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Resolved] (CB-4349) [BlackBerry10] Add platform guide section on debug tokens

[Filip Maj (JIRA)]

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

Filip Maj resolved CB-4349.
---
   Resolution: Won't Fix
Fix Version/s: (was: 3.6.0)

Blackberry is toast now. Closing.

> [BlackBerry10] Add platform guide section on debug tokens
> -
>
> Key: CB-4349
> URL: https://issues.apache.org/jira/browse/CB-4349
> Project: Apache Cordova
>  Issue Type: Improvement
>  Components: cordova-blackberry (DEPRECATED)
>Affects Versions: 3.0.0
>Reporter: Bryan Higgins
>Assignee: Bryan Higgins
>Priority: Minor
>
> These are automatically generated, but only if device PIN is specified (see 
> CB-4340) and signing key password provided. It is also possible to add a 
> pre-generated file to HOME/.cordova.
> The platform guide should have a section that explains how the process has 
> changed from prior versions of WebWorks / Cordova.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Updated] (CB-4349) [BlackBerry10] Add platform guide section on debug tokens

[Filip Maj (JIRA)]

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

Filip Maj updated CB-4349:
--
Component/s: cordova-blackberry (DEPRECATED)

> [BlackBerry10] Add platform guide section on debug tokens
> -
>
> Key: CB-4349
> URL: https://issues.apache.org/jira/browse/CB-4349
> Project: Apache Cordova
>  Issue Type: Improvement
>  Components: cordova-blackberry (DEPRECATED)
>Affects Versions: 3.0.0
>Reporter: Bryan Higgins
>Assignee: Bryan Higgins
>Priority: Minor
> Fix For: 3.6.0
>
>
> These are automatically generated, but only if device PIN is specified (see 
> CB-4340) and signing key password provided. It is also possible to add a 
> pre-generated file to HOME/.cordova.
> The platform guide should have a section that explains how the process has 
> changed from prior versions of WebWorks / Cordova.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Resolved] (CB-4329) Android config.xml file options should be updated to reflect what is in the code

[Filip Maj (JIRA)]

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

Filip Maj resolved CB-4329.
---
Resolution: Not A Problem

> Android config.xml file options should be updated to reflect what is in the 
> code
> 
>
> Key: CB-4329
> URL: https://issues.apache.org/jira/browse/CB-4329
> Project: Apache Cordova
>  Issue Type: Bug
>Affects Versions: 2.9.0
>Reporter: Dan Moore
>Assignee: Michael Brooks
>Priority: Minor
>
> The options in the docs:
> http://cordova.apache.org/docs/en/edge/guide_platforms_android_config.md.html#Android%20Configuration
> and the options in 2.9.x
> https://github.com/apache/cordova-android/blob/2.9.x/framework/src/org/apache/cordova/Config.java
> and in 3.0.x 
> https://github.com/apache/cordova-android/blob/3.0.x/framework/src/org/apache/cordova/Config.java
> have different cases.
> At the least, mention that these options are case insensitive.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Resolved] (CB-4512) Add links to any native documentation re: settings

[Filip Maj (JIRA)]

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

Filip Maj resolved CB-4512.
---
Resolution: Not A Problem

Not a problem!

> Add links to any native documentation re: settings
> --
>
> Key: CB-4512
> URL: https://issues.apache.org/jira/browse/CB-4512
> Project: Apache Cordova
>  Issue Type: Bug
>Affects Versions: Master
>Reporter: Filip Maj
>Assignee: Michael Brooks
>Priority: Minor
>
> Under platform guides, we currently have different sub-guides: CLI, plugins, 
> and one called Settings. Settings include different  elements you 
> can add to different platforms that tweak the behaviour of the webview.
> The combination of certain preferences for certain platforms together with 
> lack of consistent support across platforms for them can lead to confusion. 
> For example, you can lock screen orientation on cordova-ios with a 
> preference. You cannot do that on Android. Instead, on Android, you tweak 
> AndroidManifest.xml content to do the same thing.
> I think it would be prudent to, at a minimum, link to various native 
> configuration documentation to allow users to further explore.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Resolved] (CB-4529) Add to CLI documentation that android has to built after npm install.

[Filip Maj (JIRA)]

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

Filip Maj resolved CB-4529.
---
Resolution: Not A Problem

Years later, this is no longer relevant.

> Add to CLI documentation that android has to built after npm install.
> -
>
> Key: CB-4529
> URL: https://issues.apache.org/jira/browse/CB-4529
> Project: Apache Cordova
>  Issue Type: Improvement
>Affects Versions: 3.0.0
> Environment: Windows
>Reporter: Kris Erickson
>Assignee: Michael Brooks
>Priority: Minor
>
> Add to CLI documentation that android has to built after npm install.  See 
> https://groups.google.com/forum/#!searchin/phonegap/windows$20cli/phonegap/yqh0wFqHTss/52IXqyYy-SwJ
>  for more details.  Also it would be nice if the CLI recognized that android 
> platform was not built and produced a more insightful warning.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Updated] (CB-4704) ProgressEvent needs reference documentation

[Filip Maj (JIRA)]

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

Filip Maj updated CB-4704:
--
Labels: backlog  (was: )

> ProgressEvent needs reference documentation
> ---
>
> Key: CB-4704
> URL: https://issues.apache.org/jira/browse/CB-4704
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: cordova-plugin-file-transfer
>Affects Versions: 2.9.0
>Reporter: Shingo Toda
>Assignee: Michael Brooks
>Priority: Minor
>  Labels: backlog
>
> ProgressEvent object which is passed to FileTransfer.onprogress callback is 
> not explained in the document. Document explains this in sample code but 
> still a bit hard to understand how to use this (e.g. I don't understand what 
> is *lengthComputable* property). Please provide information about its 
> properties in detail.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Updated] (CB-4704) ProgressEvent needs reference documentation

[Filip Maj (JIRA)]

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

Filip Maj updated CB-4704:
--
Summary: ProgressEvent needs reference documentation  (was: (Doc) 
ProgressEvent is not explained well)

> ProgressEvent needs reference documentation
> ---
>
> Key: CB-4704
> URL: https://issues.apache.org/jira/browse/CB-4704
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: cordova-plugin-file-transfer
>Affects Versions: 2.9.0
>Reporter: Shingo Toda
>Assignee: Michael Brooks
>Priority: Minor
>
> ProgressEvent object which is passed to FileTransfer.onprogress callback is 
> not explained in the document. Document explains this in sample code but 
> still a bit hard to understand how to use this (e.g. I don't understand what 
> is *lengthComputable* property). Please provide information about its 
> properties in detail.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Updated] (CB-4737) cordova-plugin-file needs full function reference documentation

[Filip Maj (JIRA)]

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

Filip Maj updated CB-4737:
--
Description: 
write full documentation for the resolveLocalFileSytemURI and other functions 
and constants.


  was:write full documentation for the resolveLocalFileSytemURI function


> cordova-plugin-file needs full function reference documentation
> ---
>
> Key: CB-4737
> URL: https://issues.apache.org/jira/browse/CB-4737
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: cordova-plugin-file
>Affects Versions: 3.0.0
>Reporter: Lorin Beer
>Assignee: Michael Brooks
>Priority: Minor
>  Labels: backlog
> Fix For: 3.6.0
>
>
> write full documentation for the resolveLocalFileSytemURI and other functions 
> and constants.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Updated] (CB-4737) cordova-plugin-file needs full function reference documentation

[Filip Maj (JIRA)]

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

Filip Maj updated CB-4737:
--
Component/s: cordova-plugin-file

> cordova-plugin-file needs full function reference documentation
> ---
>
> Key: CB-4737
> URL: https://issues.apache.org/jira/browse/CB-4737
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: cordova-plugin-file
>Affects Versions: 3.0.0
>Reporter: Lorin Beer
>Assignee: Michael Brooks
>Priority: Minor
>  Labels: backlog
> Fix For: 3.6.0
>
>
> write full documentation for the resolveLocalFileSytemURI function



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Updated] (CB-4737) cordova-plugin-file needs full function reference documentation

[Filip Maj (JIRA)]

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

Filip Maj updated CB-4737:
--
Summary: cordova-plugin-file needs full function reference documentation  
(was: LocalFileSystem resolveLocalFileSystemURI function documentation)

> cordova-plugin-file needs full function reference documentation
> ---
>
> Key: CB-4737
> URL: https://issues.apache.org/jira/browse/CB-4737
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: cordova-plugin-file
>Affects Versions: 3.0.0
>Reporter: Lorin Beer
>Assignee: Michael Brooks
>Priority: Minor
>  Labels: backlog
> Fix For: 3.6.0
>
>
> write full documentation for the resolveLocalFileSytemURI function



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Updated] (CB-4737) cordova-plugin-file needs full function reference documentation

[Filip Maj (JIRA)]

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

Filip Maj updated CB-4737:
--
Labels: backlog  (was: easyfix longtime)

> cordova-plugin-file needs full function reference documentation
> ---
>
> Key: CB-4737
> URL: https://issues.apache.org/jira/browse/CB-4737
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: cordova-plugin-file
>Affects Versions: 3.0.0
>Reporter: Lorin Beer
>Assignee: Michael Brooks
>Priority: Minor
>  Labels: backlog
> Fix For: 3.6.0
>
>
> write full documentation for the resolveLocalFileSytemURI function



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Resolved] (CB-4615) Android quirks for notification.confirm not documented

[Filip Maj (JIRA)]

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

Filip Maj resolved CB-4615.
---
   Resolution: Fixed
 Assignee: Filip Maj
Fix Version/s: cordova-plugin-dialogs@1.3.4

Fixed up the docs in 59f148c

> Android quirks for notification.confirm not documented
> --
>
> Key: CB-4615
> URL: https://issues.apache.org/jira/browse/CB-4615
> Project: Apache Cordova
>  Issue Type: Improvement
>  Components: cordova-plugin-dialogs
>Affects Versions: 2.9.0
>Reporter: Peter
>Assignee: Filip Maj
>Priority: Minor
> Fix For: cordova-plugin-dialogs@1.3.4
>
>
> *notification.confirm* and notification.prompt for Android supports a maximum 
> of three buttons, and ignores any more than that. This quirk is documented 
> for notification.prompt but it is not documented for notification.confirm.
> Ref: 
> http://cordova.apache.org/docs/en/2.9.0/cordova_notification_notification.md.html#notification.confirm



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CB-4615) Android quirks for notification.confirm not documented

[ASF subversion and git services (JIRA)]

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

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

Commit 59f148ca448ea5361e9a1b88efbed39ff1ff9d8a in cordova-plugin-dialogs's 
branch refs/heads/master from filmaj
[ 
https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-dialogs.git;h=59f148c ]

CB-4615: document Android quirk around maximum number of button labels 
supported for the `confirm` method.


> Android quirks for notification.confirm not documented
> --
>
> Key: CB-4615
> URL: https://issues.apache.org/jira/browse/CB-4615
> Project: Apache Cordova
>  Issue Type: Improvement
>  Components: cordova-plugin-dialogs
>Affects Versions: 2.9.0
>Reporter: Peter
>Priority: Minor
>
> *notification.confirm* and notification.prompt for Android supports a maximum 
> of three buttons, and ignores any more than that. This quirk is documented 
> for notification.prompt but it is not documented for notification.confirm.
> Ref: 
> http://cordova.apache.org/docs/en/2.9.0/cordova_notification_notification.md.html#notification.confirm



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Updated] (CB-4615) Android quirks for notification.confirm not documented

[Filip Maj (JIRA)]

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

Filip Maj updated CB-4615:
--
Component/s: (was: cordova-android)
 cordova-plugin-dialogs

> Android quirks for notification.confirm not documented
> --
>
> Key: CB-4615
> URL: https://issues.apache.org/jira/browse/CB-4615
> Project: Apache Cordova
>  Issue Type: Improvement
>  Components: cordova-plugin-dialogs
>Affects Versions: 2.9.0
>Reporter: Peter
>Priority: Minor
>
> *notification.confirm* and notification.prompt for Android supports a maximum 
> of three buttons, and ignores any more than that. This quirk is documented 
> for notification.prompt but it is not documented for notification.confirm.
> Ref: 
> http://cordova.apache.org/docs/en/2.9.0/cordova_notification_notification.md.html#notification.confirm



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Updated] (CB-4673) MediaFile.lastModifiedDate - type does not match documentation on Android

[Filip Maj (JIRA)]

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

Filip Maj updated CB-4673:
--
Labels: backlog  (was: )

> MediaFile.lastModifiedDate - type does not match documentation on Android
> -
>
> Key: CB-4673
> URL: https://issues.apache.org/jira/browse/CB-4673
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: cordova-plugin-media-capture
>Affects Versions: 2.9.0
>Reporter: Peter
>Assignee: Joe Bowser
>Priority: Minor
>  Labels: backlog
>
> Capture API documentation for MediaFile says lastModifiedDate type is a 
> *Date*.
> Ref: 
> http://cordova.apache.org/docs/en/3.0.0/cordova_media_capture_capture.md.html#MediaFile
> but code in _Capture.java_ is returning a *long* timestamp
> {code}
> obj.put("lastModifiedDate", fp.lastModified());
> {code}
> Which is correct?
> This is a bit like CB-4596



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CB-4673) MediaFile.lastModifiedDate - type does not match documentation on Android

[Filip Maj (JIRA)]

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

Filip Maj commented on CB-4673:
---

This still looks like a legit bug four years later :)

> MediaFile.lastModifiedDate - type does not match documentation on Android
> -
>
> Key: CB-4673
> URL: https://issues.apache.org/jira/browse/CB-4673
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: cordova-plugin-media-capture
>Affects Versions: 2.9.0
>Reporter: Peter
>Assignee: Joe Bowser
>Priority: Minor
>  Labels: backlog
>
> Capture API documentation for MediaFile says lastModifiedDate type is a 
> *Date*.
> Ref: 
> http://cordova.apache.org/docs/en/3.0.0/cordova_media_capture_capture.md.html#MediaFile
> but code in _Capture.java_ is returning a *long* timestamp
> {code}
> obj.put("lastModifiedDate", fp.lastModified());
> {code}
> Which is correct?
> This is a bit like CB-4596



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Updated] (CB-4673) MediaFile.lastModifiedDate - type does not match documentation on Android

[Filip Maj (JIRA)]

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

Filip Maj updated CB-4673:
--
Summary: MediaFile.lastModifiedDate - type does not match documentation on 
Android  (was: MediaFile.lastModifiedDate - type does not match documentation)

> MediaFile.lastModifiedDate - type does not match documentation on Android
> -
>
> Key: CB-4673
> URL: https://issues.apache.org/jira/browse/CB-4673
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: cordova-plugin-media-capture
>Affects Versions: 2.9.0
>Reporter: Peter
>Assignee: Joe Bowser
>Priority: Minor
>  Labels: backlog
>
> Capture API documentation for MediaFile says lastModifiedDate type is a 
> *Date*.
> Ref: 
> http://cordova.apache.org/docs/en/3.0.0/cordova_media_capture_capture.md.html#MediaFile
> but code in _Capture.java_ is returning a *long* timestamp
> {code}
> obj.put("lastModifiedDate", fp.lastModified());
> {code}
> Which is correct?
> This is a bit like CB-4596



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Updated] (CB-4673) MediaFile.lastModifiedDate - type does not match documentation

[Filip Maj (JIRA)]

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

Filip Maj updated CB-4673:
--
Component/s: (was: cordova-android)

> MediaFile.lastModifiedDate - type does not match documentation
> --
>
> Key: CB-4673
> URL: https://issues.apache.org/jira/browse/CB-4673
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: cordova-plugin-media-capture
>Affects Versions: 2.9.0
>Reporter: Peter
>Assignee: Joe Bowser
>Priority: Minor
>
> Capture API documentation for MediaFile says lastModifiedDate type is a 
> *Date*.
> Ref: 
> http://cordova.apache.org/docs/en/3.0.0/cordova_media_capture_capture.md.html#MediaFile
> but code in _Capture.java_ is returning a *long* timestamp
> {code}
> obj.put("lastModifiedDate", fp.lastModified());
> {code}
> Which is correct?
> This is a bit like CB-4596



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Comment Edited] (CB-13013) Cordova iOS link (clang) failure caused by space in App name

[Gary N Griswold (JIRA)]

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

Gary N Griswold edited comment on CB-13013 at 7/14/17 8:50 PM:
---

I have downgraded this from Blocking to Major, because it is possible to 
mitigate the problem by removing the space in the AppName.


was (Author: g...@shortsands.com):
I have downgraded this from Blocking to Major, because it is possible to 
mitigate the problem removing the space in the AppName.

> Cordova iOS link (clang) failure caused by space in App name
> 
>
> Key: CB-13013
> URL: https://issues.apache.org/jira/browse/CB-13013
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: cordova-ios
>Affects Versions: cordova-ios@4.4.0, cordova@7.0.0
> Environment: Mac osx 10.12.5
> xCode 8.3.3
> cordova 7.0.1
> cordova iOS 4.4.0
>Reporter: Gary N Griswold
>Assignee: Shazron Abdullah
> Fix For: Master
>
>
> Where in iOS Cordova is the code that generates the clang command?  I would 
> be happy to investigate this problem myself, if I knew where in the Cordova 
> code that the clang (link) statement is generated.
> The clang statement that is being generated is not correctly handling a space 
> that is embedded in the App name:
>
> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang
>  
>  .
> -FYour
> -FBible/Plugins/com-shortsands-pkzip 
> -FBible/Plugins/com-shortsands-aws 
> -FBible/Plugins/com-shortsands-videoplayer 
> -FBible/Plugins/cordova-plugin-webserver 
> -FYour\ Bible/Plugins/com-shortsands-pkzip 
> -FYour\ Bible/Plugins/com-shortsands-aws 
> -FYour\ Bible/Plugins/com-shortsands-videoplayer
> . 
> The App is named "Your Bible". Noticed that it is not handling the space 
> properly when it generates the -F parameters, and those all fail with not 
> found errors. Then it generates -F parameters a second time, but this time 
> correctly handling the space.
> Custom, embedded frameworks are being used in these three plugins. This link 
> problem appeared after they were added to the project.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Updated] (CB-13013) Cordova iOS link (clang) failure caused by space in App name

[Gary N Griswold (JIRA)]

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

Gary N Griswold updated CB-13013:
-
Priority: Major  (was: Blocker)

I have downgraded this from Blocking to Major, because it is possible to 
mitigate the problem removing the space in the AppName.

> Cordova iOS link (clang) failure caused by space in App name
> 
>
> Key: CB-13013
> URL: https://issues.apache.org/jira/browse/CB-13013
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: cordova-ios
>Affects Versions: cordova-ios@4.4.0, cordova@7.0.0
> Environment: Mac osx 10.12.5
> xCode 8.3.3
> cordova 7.0.1
> cordova iOS 4.4.0
>Reporter: Gary N Griswold
>Assignee: Shazron Abdullah
> Fix For: Master
>
>
> Where in iOS Cordova is the code that generates the clang command?  I would 
> be happy to investigate this problem myself, if I knew where in the Cordova 
> code that the clang (link) statement is generated.
> The clang statement that is being generated is not correctly handling a space 
> that is embedded in the App name:
>
> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang
>  
>  .
> -FYour
> -FBible/Plugins/com-shortsands-pkzip 
> -FBible/Plugins/com-shortsands-aws 
> -FBible/Plugins/com-shortsands-videoplayer 
> -FBible/Plugins/cordova-plugin-webserver 
> -FYour\ Bible/Plugins/com-shortsands-pkzip 
> -FYour\ Bible/Plugins/com-shortsands-aws 
> -FYour\ Bible/Plugins/com-shortsands-videoplayer
> . 
> The App is named "Your Bible". Noticed that it is not handling the space 
> properly when it generates the -F parameters, and those all fail with not 
> found errors. Then it generates -F parameters a second time, but this time 
> correctly handling the space.
> Custom, embedded frameworks are being used in these three plugins. This link 
> problem appeared after they were added to the project.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Resolved] (CB-4738) MediaError.message is not supported?

[Filip Maj (JIRA)]

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

Filip Maj resolved CB-4738.
---
Resolution: Cannot Reproduce

This was from long ago.This is not longer an issue.

> MediaError.message is not supported?
> 
>
> Key: CB-4738
> URL: https://issues.apache.org/jira/browse/CB-4738
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: cordova-plugin-media
>Affects Versions: 2.9.0
>Reporter: Shingo Toda
>Assignee: Michael Brooks
>Priority: Minor
>
> I just tried to get an error message from MediaError.message but I failed. As 
> I see cordova.js, it seems that this property is not supported.
> {code:title=cordova.js|borderStyle=solid}
>  var _MediaError = window.MediaError;
> if(!_MediaError) {
> window.MediaError = _MediaError = function(code, msg) {
> this.code = (typeof code != 'undefined') ? code : null;
> this.message = msg || ""; // message is NON-standard! do not use!
> };
> }
> {code}
> This is just my assumption that it look like Cordova try to get browser's 
> MediaError at first. If it fails, Cordova will add original implementation. 
> But as commented, message property is not standard in W3C 
> [http://dev.w3.org/html5/spec-author-view/video.html#mediaerror] 
> If it is really not supported, please remove this property from document.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CB-12895) Replace jshint with eslint in our tools + platforms

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-12895:
-

GitHub user audreyso opened a pull request:

https://github.com/apache/cordova-plugman/pull/90

CB-12895 : setup eslint and removed jshint



### Platforms affected


### What does this PR do?

Setup eslint and removed jshint

### What testing has been done on this change?


### Checklist
- [X] [Reported an issue](http://cordova.apache.org/contribute/issues.html) 
in the JIRA database
- [X] Commit message follows the format: "CB-3232: (android) Fix bug with 
resolving file paths", where CB- is the JIRA ID & "android" is the platform 
affected.
- [X] Added automated test coverage as appropriate for this change.


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

$ git pull https://github.com/audreyso/cordova-plugman CB-12895

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

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


commit 20c2f03ba55663dd3aebecb8558b8f2c36e1651f
Author: Audrey So 
Date:   2017-06-09T21:01:44Z

CB-12895 : setup eslint and remove jshint




> Replace jshint with eslint in our tools + platforms
> ---
>
> Key: CB-12895
> URL: https://issues.apache.org/jira/browse/CB-12895
> Project: Apache Cordova
>  Issue Type: Improvement
>  Components: AllComponents
>Reporter: Steve Gill
>Assignee: Audrey So
>Priority: Minor
>  Labels: cordova-next
>
> Based on this proposal
> https://github.com/cordova/cordova-discuss/pull/70#issuecomment-306649308
> JSHint does minimal checks and JSCS has been deprecated in favor of ESLint.
>  +
>  +I suggest to replace the current style checkers with ESLint. This allows to 
> set much more strict styling rules than at at this moment.
>  +
>  +I recommend using a popular preset, such as 
> [airbnb-base](https://www.npmjs.com/package/eslint-config-airbnb-base). 
> Example configuration:
>  +
>  +```yaml
>  +root: true
>  +
>  +extends: airbnb-base
>  +```
>  +
>  +Many styling issues could be fixed by simply running:
>  +
>  +```
>  +./node_modules/.bin/eslint --fix .
>  +```
>  +
>  +
>  +
>  +Optionally the indent could be set to 4 instead of 2, because that's used 
> in the current code base.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Resolved] (CB-5022) Installing Core Plugins section unclear

[Filip Maj (JIRA)]

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

Filip Maj resolved CB-5022.
---
   Resolution: Fixed
 Assignee: Filip Maj  (was: Mike Billau)
Fix Version/s: (was: 3.6.0)

I've fixed any leftover incorrect example invocations of plugman in a recent 
push. Closing.

> Installing Core Plugins section unclear
> ---
>
> Key: CB-5022
> URL: https://issues.apache.org/jira/browse/CB-5022
> Project: Apache Cordova
>  Issue Type: Improvement
>  Components: cordova-docs
>Affects Versions: 3.1.0
> Environment: n/a
>Reporter: Angela Fowler
>Assignee: Filip Maj
>Priority: Minor
>  Labels: documentation
>
> http://cordova.apache.org/docs/en/edge/plugin_ref_plugman.md.html
> The "Installing Core Plugins" section appears as a bullet list of commands. 
> cordova-plugin-battery-status plugman --platform --project --plugin 
> org.apache.cordova.battery-status
> 1. Each command starts with the plugin name when it should start with 
> "plugman". Perhaps this was intended to be the first column of a table?
> 2. Each command is an example (according to the opening paragraph) but is 
> missing the platform e.g. "android" and the project
> 3. It is still unclear to us how to upgrade from 2.9 which has the plugins 
> included. If we don't use CLI as the introduction mentions, how is the 
> project created? Can plugins be built into the jar or is the plugin source 
> separate (as when added by CLI).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CB-5022) Installing Core Plugins section unclear

[ASF subversion and git services (JIRA)]

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

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

Commit 4c00574e967fb03b9a730d73c397b2c448920c90 in cordova-docs's branch 
refs/heads/master from filmaj
[ https://git-wip-us.apache.org/repos/asf?p=cordova-docs.git;h=4c00574 ]

CB-5022: clarify some invalid example `plugman install -d` syntax.


> Installing Core Plugins section unclear
> ---
>
> Key: CB-5022
> URL: https://issues.apache.org/jira/browse/CB-5022
> Project: Apache Cordova
>  Issue Type: Improvement
>  Components: cordova-docs
>Affects Versions: 3.1.0
> Environment: n/a
>Reporter: Angela Fowler
>Assignee: Mike Billau
>Priority: Minor
>  Labels: documentation
> Fix For: 3.6.0
>
>
> http://cordova.apache.org/docs/en/edge/plugin_ref_plugman.md.html
> The "Installing Core Plugins" section appears as a bullet list of commands. 
> cordova-plugin-battery-status plugman --platform --project --plugin 
> org.apache.cordova.battery-status
> 1. Each command starts with the plugin name when it should start with 
> "plugman". Perhaps this was intended to be the first column of a table?
> 2. Each command is an example (according to the opening paragraph) but is 
> missing the platform e.g. "android" and the project
> 3. It is still unclear to us how to upgrade from 2.9 which has the plugins 
> included. If we don't use CLI as the introduction mentions, how is the 
> project created? Can plugins be built into the jar or is the plugin source 
> separate (as when added by CLI).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Updated] (CB-5022) Installing Core Plugins section unclear

[Filip Maj (JIRA)]

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

Filip Maj updated CB-5022:
--
Component/s: cordova-docs

> Installing Core Plugins section unclear
> ---
>
> Key: CB-5022
> URL: https://issues.apache.org/jira/browse/CB-5022
> Project: Apache Cordova
>  Issue Type: Improvement
>  Components: cordova-docs
>Affects Versions: 3.1.0
> Environment: n/a
>Reporter: Angela Fowler
>Assignee: Mike Billau
>Priority: Minor
>  Labels: documentation
> Fix For: 3.6.0
>
>
> http://cordova.apache.org/docs/en/edge/plugin_ref_plugman.md.html
> The "Installing Core Plugins" section appears as a bullet list of commands. 
> cordova-plugin-battery-status plugman --platform --project --plugin 
> org.apache.cordova.battery-status
> 1. Each command starts with the plugin name when it should start with 
> "plugman". Perhaps this was intended to be the first column of a table?
> 2. Each command is an example (according to the opening paragraph) but is 
> missing the platform e.g. "android" and the project
> 3. It is still unclear to us how to upgrade from 2.9 which has the plugins 
> included. If we don't use CLI as the introduction mentions, how is the 
> project created? Can plugins be built into the jar or is the plugin source 
> separate (as when added by CLI).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Resolved] (CB-5260) iOS Platform Guide broken link to Tools Workflow Guide

[Filip Maj (JIRA)]

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

Filip Maj resolved CB-5260.
---
Resolution: Not A Problem

The latest ios guide has all the required info. Closing!

> iOS Platform Guide broken link to Tools Workflow Guide
> --
>
> Key: CB-5260
> URL: https://issues.apache.org/jira/browse/CB-5260
> Project: Apache Cordova
>  Issue Type: Bug
>Affects Versions: 3.1.0
> Environment: iOS
>Reporter: Angela Fowler
>Priority: Minor
>
> http://cordova.apache.org/docs/en/3.1.0/guide_platforms_ios_index.md.html#iOS%20Platform%20Guide
> Under "Deploy to Device"
> the “Tools Workflow Guide for iOS” link is broken :
> http://developer.apple.com/library/ios/#documentation/Xcode/Conceptual/ios_development_workflow/00-About_the_iOS_Application_Development_Workflow/introduction.html#//apple_ref/doc/uid/TP40007959



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Resolved] (CB-6424) UIBackgroundModes is not set as "audio" by default in order to use playAudioWhenScreenIsLocked in iOS

[Filip Maj (JIRA)]

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

Filip Maj resolved CB-6424.
---
Resolution: Won't Fix

It's been a while, cautiously closing this.

> UIBackgroundModes is not set as "audio" by default in order to use 
> playAudioWhenScreenIsLocked in iOS
> -
>
> Key: CB-6424
> URL: https://issues.apache.org/jira/browse/CB-6424
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: cordova-plugin-media
>Affects Versions: 3.4.0
> Environment: Mobile Spec 3.4.0 Application running on iPAD3 with iOS 
> 7.1
>Reporter: Pavankumar Joshi
>Priority: Minor
>  Labels: documentation
>
> Was writing a test case to test the functionality Media.play() command with 
> playAudioWhenScreenIsLocked option. The device used is iPAD 3  which has iOS 
> 7.1 version.
> while testing i noticed that, Whatever the value i set to the filed 
> playAudioWhenScreenIsLocked (true or false), the audio stopped playing in the 
> background when the devise got locked 
> I am writing the test case in MobileSpec3.4.0 test environment which is built 
> using Cordova 3.4.0 version. 
> Later i found that the MobileSpec340-info.plist does not contain the option 
> UIBackgroundModes set as  "audio". When i Manually set this option the 
> feature worked correctly. I think this point has to be mentioned in the 
> document or by default generated in info.plist.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Resolved] (CB-5451) document the project layout on the filesystem, and which config files do what

[Filip Maj (JIRA)]

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

Filip Maj resolved CB-5451.
---
Resolution: Fixed

There is a directory structure section in the docs now: 
https://cordova.apache.org/docs/en/latest/reference/cordova-cli/index.html#directory-structure

> document the project layout on the filesystem, and which config files do what
> -
>
> Key: CB-5451
> URL: https://issues.apache.org/jira/browse/CB-5451
> Project: Apache Cordova
>  Issue Type: Improvement
>Affects Versions: Master
>Reporter: Marcel Kinard
>Priority: Minor
>
> When using the CLI workflow, the docs don't have a clear description on the 
> layout of the files/dirs of the project. Also, the same is missing for all 
> the config files described in 
> http://wiki.apache.org/cordova/ConfigurationFiles - this needs to be in 
> cordova-docs. It is not clearly mentioned that there are hidden dirs 
> $HOME/.cordova and $HOME/.plugman. This information would be helpful so users 
> know how to navigate the filesystem layout and don't touch the wrong thing 
> and know what needs to be put into a source control system for their project.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Resolved] (CB-5459) Vibration - align with w3c spec

[Filip Maj (JIRA)]

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

Filip Maj resolved CB-5459.
---
Resolution: Won't Fix

The plugin audit at CB-12708 supersedes this now. The vibration API is no 
longer really applicable.

> Vibration - align with w3c spec
> ---
>
> Key: CB-5459
> URL: https://issues.apache.org/jira/browse/CB-5459
> Project: Apache Cordova
>  Issue Type: Improvement
>  Components: cordova-plugin-vibration
>Affects Versions: 3.3.0
>Reporter: Lisa Seacat DeLuca
>Assignee: Edna Morales
>Priority: Minor
>  Labels: vibration
>
> Align the vibration spec with the w3c spec. Specifically add the ability to 
> handle a vibration pattern:
> http://www.w3.org/TR/2013/CR-vibration-20130723/
> ex. navigator.vibrate([50, 100, 150]);
> the pattern will cause the device to vibrate for 50 ms, be still for 100 ms, 
> and then vibrate for 150 ms: 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Resolved] (CB-6913) migration path for old references of navigator.notification.vibrate

[Filip Maj (JIRA)]

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

Filip Maj resolved CB-6913.
---
Resolution: Won't Fix

The plugin audit at CB-12708 supersedes this now. The vibration API is no 
longer really applicable.

> migration path for old references of navigator.notification.vibrate
> ---
>
> Key: CB-6913
> URL: https://issues.apache.org/jira/browse/CB-6913
> Project: Apache Cordova
>  Issue Type: Sub-task
>  Components: cordova-plugin-vibration
>Reporter: Lisa Seacat DeLuca
>Assignee: Edna Morales
>  Labels: w3c
>
> migration path for old references of navigator.notification.vibrate
> see more details at: 
> https://docs.google.com/document/d/18b32aveubsr2g5Co_VeW4q3s3IXxuddUU2BO5eC3jVA/edit
> we need to support navigator.notification.vibrate once we align with w3c spec 
> and move to navigator.vibrate.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Resolved] (CB-5460) Vibration - align with w3c spec ANDROID

[Filip Maj (JIRA)]

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

Filip Maj resolved CB-5460.
---
Resolution: Won't Fix

The plugin audit at CB-12708 supersedes this now. The vibration API is no 
longer really applicable.

> Vibration - align with w3c spec ANDROID
> ---
>
> Key: CB-5460
> URL: https://issues.apache.org/jira/browse/CB-5460
> Project: Apache Cordova
>  Issue Type: Sub-task
>  Components: cordova-android, cordova-plugin-vibration
>Reporter: Lisa Seacat DeLuca
>Assignee: Edna Morales
>Priority: Minor
>
> Make the vibration changes for Android



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Resolved] (CB-5461) Vibration - align with w3c spec IOS

[Filip Maj (JIRA)]

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

Filip Maj resolved CB-5461.
---
Resolution: Won't Fix

The plugin audit at CB-12708 supersedes this now. The vibration API is no 
longer really applicable.

> Vibration - align with w3c spec IOS
> ---
>
> Key: CB-5461
> URL: https://issues.apache.org/jira/browse/CB-5461
> Project: Apache Cordova
>  Issue Type: Sub-task
>  Components: cordova-plugin-vibration
> Environment: iOS
>Reporter: Lisa Seacat DeLuca
>Assignee: Edna Morales
>Priority: Minor
>
> Make changes for IOS



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Resolved] (CB-6916) Multiple vibration pattern implementation

[Filip Maj (JIRA)]

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

Filip Maj resolved CB-6916.
---
Resolution: Won't Fix

The plugin audit at CB-12708 supersedes this now. The vibration API is no 
longer really applicable.

> Multiple vibration pattern implementation
> -
>
> Key: CB-6916
> URL: https://issues.apache.org/jira/browse/CB-6916
> Project: Apache Cordova
>  Issue Type: Sub-task
>  Components: cordova-plugin-vibration
>Reporter: Lisa Seacat DeLuca
>Assignee: Maxim Ermilov
>  Labels: w3c
>
> SEE 
> https://docs.google.com/document/d/18b32aveubsr2g5Co_VeW4q3s3IXxuddUU2BO5eC3jVA/edit
>  for more info
> Vibration patterns (section 5, example 2)
> In the following example the pattern will cause the device to vibrate for 50 
> ms, be still for 100 ms, and then vibrate for 150 ms:
> navigator.vibrate([50, 100, 150]);



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Resolved] (CB-5462) Vibration - align with w3c spec DOCS

[Filip Maj (JIRA)]

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

Filip Maj resolved CB-5462.
---
Resolution: Won't Fix

The plugin audit at CB-12708 supersedes this now. The vibration API is no 
longer really applicable.

> Vibration - align with w3c spec DOCS
> 
>
> Key: CB-5462
> URL: https://issues.apache.org/jira/browse/CB-5462
> Project: Apache Cordova
>  Issue Type: Sub-task
>  Components: cordova-plugin-vibration
>Reporter: Lisa Seacat DeLuca
>Assignee: Edna Morales
>Priority: Minor
>
> Update documentation to align vibration spec with w3c



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Resolved] (CB-5665) Document the need for xcopy on path

[Filip Maj (JIRA)]

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

Filip Maj resolved CB-5665.
---
   Resolution: Cannot Reproduce
Fix Version/s: (was: 3.6.0)

This isn't an issue. We use shelljs for OS I/O, and it does not require xcopy.

> Document the need for xcopy on path
> ---
>
> Key: CB-5665
> URL: https://issues.apache.org/jira/browse/CB-5665
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: cordova-cli
> Environment: Windows
>Reporter: Mike Billau
>Priority: Minor
>
> On Windows, you need to have xcopy on the path when trying to build Android, 
> otherwise it will fail. I think this maybe started when we switched to q.js
> See:
> https://issues.apache.org/jira/browse/CB-4074
> and
> http://stackoverflow.com/questions/20616893/an-error-occured-during-creation-of-android-sub-project/20640450
> If it is necessary only when you use the CLI, we can just add a note in the 
> CLI documentation.
> If it is necessary regardless of which workflow you use, then I think it 
> should be in check_reqs with a log message on the terminal to "Make sure 
> xcopy is on your path."
> It's probably a Windows-specific thing, no?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Resolved] (CB-7995) FileTransferError.exception property is always null on iOS

[Filip Maj (JIRA)]

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

Filip Maj resolved CB-7995.
---
   Resolution: Fixed
 Assignee: Filip Maj
Fix Version/s: cordova-plugin-file-transfer@1.6.4

> FileTransferError.exception property is always null on iOS
> --
>
> Key: CB-7995
> URL: https://issues.apache.org/jira/browse/CB-7995
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: cordova-plugin-file-transfer
>Affects Versions: 3.6.0
> Environment: iOS7, 8 iPhone/iPad
>Reporter: Shingo Toda
>Assignee: Filip Maj
>Priority: Minor
>  Labels: backlog
> Fix For: cordova-plugin-file-transfer@1.6.4
>
>
> {{exception}} property of FileTransferError is always null. When I looked 
> into source code for iOS and Android, probably this filed is used only on 
> Andrdoid. {{createFileTransferError}} method on iOS does not take exception 
> parameter while the one on Android does.
> This support information should be added in API reference.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CB-7995) FileTransferError.exception property is always null on iOS

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-7995:


Github user filmaj closed the pull request at:

https://github.com/apache/cordova-plugin-file-transfer/pull/185


> FileTransferError.exception property is always null on iOS
> --
>
> Key: CB-7995
> URL: https://issues.apache.org/jira/browse/CB-7995
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: cordova-plugin-file-transfer
>Affects Versions: 3.6.0
> Environment: iOS7, 8 iPhone/iPad
>Reporter: Shingo Toda
>Priority: Minor
>  Labels: backlog
>
> {{exception}} property of FileTransferError is always null. When I looked 
> into source code for iOS and Android, probably this filed is used only on 
> Andrdoid. {{createFileTransferError}} method on iOS does not take exception 
> parameter while the one on Android does.
> This support information should be added in API reference.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CB-7995) FileTransferError.exception property is always null on iOS

[ASF subversion and git services (JIRA)]

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

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

Commit 3e93c94d3bc49b37592cc2f20f66ce638cf377e9 in 
cordova-plugin-file-transfer's branch refs/heads/master from filmaj
[ 
https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-file-transfer.git;h=3e93c94
 ]

CB-7995: document that `FileTransferError.exception` on iOS is never defined.


> FileTransferError.exception property is always null on iOS
> --
>
> Key: CB-7995
> URL: https://issues.apache.org/jira/browse/CB-7995
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: cordova-plugin-file-transfer
>Affects Versions: 3.6.0
> Environment: iOS7, 8 iPhone/iPad
>Reporter: Shingo Toda
>Priority: Minor
>  Labels: backlog
>
> {{exception}} property of FileTransferError is always null. When I looked 
> into source code for iOS and Android, probably this filed is used only on 
> Andrdoid. {{createFileTransferError}} method on iOS does not take exception 
> parameter while the one on Android does.
> This support information should be added in API reference.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Resolved] (CB-5724) Splash screen sizes don't account for status bar

[Filip Maj (JIRA)]

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

Filip Maj resolved CB-5724.
---
Resolution: Won't Fix

Not sure what we can do to make this better for Android. There are already a 
plethora of densities and resolutions that one must target on Android - better 
to read the documentation under the Android section on how to configure your 
splash screen so it is "safe" in a variety of configurations.

> Splash screen sizes don't account for status bar
> 
>
> Key: CB-5724
> URL: https://issues.apache.org/jira/browse/CB-5724
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: cordova-plugin-splashscreen
>Affects Versions: 3.3.0
>Reporter: Jacob Weber
>Priority: Minor
>
> On the docs for [Splash Screens for the Android 
> Platform|http://cordova.apache.org/docs/en/3.3.0/config_ref_images.md.html#Icons%20and%20Splash%20Screens],
>  it lists the minimum screen sizes for each density. However, since an app 
> can show the status bar during startup, these images might be too big.
> For example, on a 720x1280 xhdpi device, if you start the app in landscape 
> mode, it will use drawable-land-xhdpi/splash.9.png, which would be at least 
> 720x960 based on this documentation. But with the status bar, there will be 
> less than 720 pixels vertically, so the image will be cut off.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Resolved] (CB-5894) Documentation makes no mention that platform's config.xml is generated from defaults.xml

[Filip Maj (JIRA)]

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

Filip Maj resolved CB-5894.
---
Resolution: Fixed

Not sure why that's necessary?

Closing.

> Documentation makes no mention that platform's config.xml is generated from 
> defaults.xml
> 
>
> Key: CB-5894
> URL: https://issues.apache.org/jira/browse/CB-5894
> Project: Apache Cordova
>  Issue Type: Task
>Affects Versions: 3.3.0
> Environment: Documentation
>Reporter: Jamie Perkins
>Priority: Minor
>  Labels: documentation
> Fix For: 3.3.0
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> In the documentation for the config.xml and the documentation for the command 
> line interface, there is no mention that a file called 'defaults.xml' in the 
> platform's 'cordova' directory is used to generate that platform's config.xml 
> file when you run 'cordova prepare ' or 'cordova build ' 
> from the CLI.
> Config.xml documentation:
> http://docs.phonegap.com/en/3.3.0/config_ref_index.md.html#The%20config.xml%20File
> CLI documentation:
> http://docs.phonegap.com/en/3.3.0/guide_cli_index.md.html#The%20Command-Line%20Interface



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CB-10916) Add ability to set different binary name and display name

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on CB-10916:
-

Github user asfgit closed the pull request at:

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


> Add ability to set different binary name and display name
> -
>
> Key: CB-10916
> URL: https://issues.apache.org/jira/browse/CB-10916
> Project: Apache Cordova
>  Issue Type: Wish
>  Components: cordova-android, cordova-ios
>Reporter: Jacob Weber
>Assignee: Darryl Pogue
>Priority: Minor
>  Labels: android-next
> Fix For: cordova-ios@4.4.1
>
>
> I would like to use a different value for the binary filenames (.ipa/.apk) 
> and the app display name. Currently  in config.xml is used for both.
> If I set  to the value I want for the binary name, I have to manually 
> edit app_name in res/values/strings.xml and CFBundleDisplayName in 
> *-Info.plist.
> On the other hand, if I set  to the value I want for the display name, 
> I can manually rename the binaries, but the iOS .ipa file still contains an 
> .app file with the display name, and CFBundleExecutable still has the display 
> name.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Resolved] (CB-10870) Inline code links (like `[link]`) are malformed

[Filip Maj (JIRA)]

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

Filip Maj resolved CB-10870.

Resolution: Fixed

I don't think this is an issue anymore. Closing.

> Inline code links (like `[link]`) are malformed
> ---
>
> Key: CB-10870
> URL: https://issues.apache.org/jira/browse/CB-10870
> Project: Apache Cordova
>  Issue Type: Bug
>Reporter: Dmitry Blotsky
>Priority: Minor
>  Labels: triaged
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> See "[pause](../../../cordova/events/events.pause.html)" on 
> http://cordova.apache.org/docs/en/5.4.0/guide/platforms/android/plugin.html.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CB-10916) Add ability to set different binary name and display name

[ASF subversion and git services (JIRA)]

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

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

Commit 22645d9158075b99d43cdcd9551c52a3bcf9ed29 in cordova-android's branch 
refs/heads/master from [~dpogue]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-android.git;h=22645d9 ]

[CB-10916] Support display name for Android


> Add ability to set different binary name and display name
> -
>
> Key: CB-10916
> URL: https://issues.apache.org/jira/browse/CB-10916
> Project: Apache Cordova
>  Issue Type: Wish
>  Components: cordova-android, cordova-ios
>Reporter: Jacob Weber
>Assignee: Darryl Pogue
>Priority: Minor
>  Labels: android-next
> Fix For: cordova-ios@4.4.1
>
>
> I would like to use a different value for the binary filenames (.ipa/.apk) 
> and the app display name. Currently  in config.xml is used for both.
> If I set  to the value I want for the binary name, I have to manually 
> edit app_name in res/values/strings.xml and CFBundleDisplayName in 
> *-Info.plist.
> On the other hand, if I set  to the value I want for the display name, 
> I can manually rename the binaries, but the iOS .ipa file still contains an 
> .app file with the display name, and CFBundleExecutable still has the display 
> name.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[jira] [Commented] (CB-10871) All docs versions should be of the form N.x

[Filip Maj (JIRA)]

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

Filip Maj commented on CB-10871:


ping [~dblotsky] on this one - need more details :)

> All docs versions should be of the form N.x
> ---
>
> Key: CB-10871
> URL: https://issues.apache.org/jira/browse/CB-10871
> Project: Apache Cordova
>  Issue Type: New Feature
>Reporter: Dmitry Blotsky
>Priority: Minor
>  Labels: triaged
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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