[jira] [Updated] (CB-8444) Don't clobber `window.open`
[ https://issues.apache.org/jira/browse/CB-8444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Chase updated CB-8444: Assignee: (was: Jason Chase) Don't clobber `window.open` --- Key: CB-8444 URL: https://issues.apache.org/jira/browse/CB-8444 Project: Apache Cordova Issue Type: Wish Components: Plugin InAppBrowser Reporter: sandstrom Fix For: Master Where Cordova plugins map 1:1 to W3C API's it's great that they clobber the corresponding namespace. Geolocation is a good example. However, it doesn't really feel like this plugin is a 1:1, so perhaps it should be available at another name, e.g. `window.iabOpen` (the old API should be preserved until the next major though, since to keep backward compatibility). -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-8295) Enable CSP for mobilespec
[ https://issues.apache.org/jira/browse/CB-8295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Chase updated CB-8295: Assignee: (was: Jason Chase) Enable CSP for mobilespec - Key: CB-8295 URL: https://issues.apache.org/jira/browse/CB-8295 Project: Apache Cordova Issue Type: Improvement Components: mobile-spec Affects Versions: Master Reporter: Jason Chase Fix For: Master With the work done in CB-8210 and CB-8252, it is now possible to run at least the mobilespec plugin tests under CSP. Consequently, it makes sense to turn on CSP by default for mobilespec. This should help ensure there are no regressions in the platform/plugin support for running under CSP. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Assigned] (CB-8717) Write cordova-android@4.0.0 release notes
[ https://issues.apache.org/jira/browse/CB-8717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Chase reassigned CB-8717: --- Assignee: Jason Chase Write cordova-android@4.0.0 release notes - Key: CB-8717 URL: https://issues.apache.org/jira/browse/CB-8717 Project: Apache Cordova Issue Type: Task Components: Android Reporter: Andrew Grieve Assignee: Jason Chase Priority: Minor These will be hefty! Best to get them done before starting release process. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Assigned] (CB-8717) Write cordova-android@4.0.0 release notes
[ https://issues.apache.org/jira/browse/CB-8717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Chase reassigned CB-8717: --- Assignee: Andrew Grieve (was: Jason Chase) Please review the pull request with the release notes. Write cordova-android@4.0.0 release notes - Key: CB-8717 URL: https://issues.apache.org/jira/browse/CB-8717 Project: Apache Cordova Issue Type: Task Components: Android Reporter: Andrew Grieve Assignee: Andrew Grieve Priority: Minor These will be hefty! Best to get them done before starting release process. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-8444) Don't clobber `window.open`
[ https://issues.apache.org/jira/browse/CB-8444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Chase updated CB-8444: Assignee: (was: Jason Chase) Don't clobber `window.open` --- Key: CB-8444 URL: https://issues.apache.org/jira/browse/CB-8444 Project: Apache Cordova Issue Type: Wish Components: Plugin InAppBrowser Reporter: sandstrom Fix For: Master Where Cordova plugins map 1:1 to W3C API's it's great that they clobber the corresponding namespace. Geolocation is a good example. However, it doesn't really feel like this plugin is a 1:1, so perhaps it should be available at another name, e.g. `window.iabOpen` (the old API should be preserved until the next major though, since to keep backward compatibility). -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-8444) Don't clobber `window.open`
[ https://issues.apache.org/jira/browse/CB-8444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Chase resolved CB-8444. - Resolution: Fixed Fix Version/s: Master Don't clobber `window.open` --- Key: CB-8444 URL: https://issues.apache.org/jira/browse/CB-8444 Project: Apache Cordova Issue Type: Wish Components: Plugin InAppBrowser Reporter: sandstrom Assignee: Jason Chase Fix For: Master Where Cordova plugins map 1:1 to W3C API's it's great that they clobber the corresponding namespace. Geolocation is a good example. However, it doesn't really feel like this plugin is a 1:1, so perhaps it should be available at another name, e.g. `window.iabOpen` (the old API should be preserved until the next major though, since to keep backward compatibility). -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Reopened] (CB-8444) Don't clobber `window.open`
[ https://issues.apache.org/jira/browse/CB-8444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Chase reopened CB-8444: - After an appropriate deprecation period, the plugin needs to be changed to fully remove the clobber of `window.open`. As an API change, this would require a major release. Don't clobber `window.open` --- Key: CB-8444 URL: https://issues.apache.org/jira/browse/CB-8444 Project: Apache Cordova Issue Type: Wish Components: Plugin InAppBrowser Reporter: sandstrom Fix For: Master Where Cordova plugins map 1:1 to W3C API's it's great that they clobber the corresponding namespace. Geolocation is a good example. However, it doesn't really feel like this plugin is a 1:1, so perhaps it should be available at another name, e.g. `window.iabOpen` (the old API should be preserved until the next major though, since to keep backward compatibility). -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-8444) Don't clobber `window.open`
[ https://issues.apache.org/jira/browse/CB-8444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14329337#comment-14329337 ] Jason Chase commented on CB-8444: - A new symbol has been added to expose the InAppBrowser functionality, named `cordova.InAppBrowser.open`. The clobber of `window.open` has been deprecated (in the docs), but not removed. The plan is to wait to the next major release, to give apps a chance to update usage as appropriate. Don't clobber `window.open` --- Key: CB-8444 URL: https://issues.apache.org/jira/browse/CB-8444 Project: Apache Cordova Issue Type: Wish Components: Plugin InAppBrowser Reporter: sandstrom Fix For: Master Where Cordova plugins map 1:1 to W3C API's it's great that they clobber the corresponding namespace. Geolocation is a good example. However, it doesn't really feel like this plugin is a 1:1, so perhaps it should be available at another name, e.g. `window.iabOpen` (the old API should be preserved until the next major though, since to keep backward compatibility). -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Assigned] (CB-8444) Don't clobber `window.open`
[ https://issues.apache.org/jira/browse/CB-8444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Chase reassigned CB-8444: --- Assignee: Jason Chase Don't clobber `window.open` --- Key: CB-8444 URL: https://issues.apache.org/jira/browse/CB-8444 Project: Apache Cordova Issue Type: Wish Components: Plugin InAppBrowser Reporter: sandstrom Assignee: Jason Chase Fix For: Master Where Cordova plugins map 1:1 to W3C API's it's great that they clobber the corresponding namespace. Geolocation is a good example. However, it doesn't really feel like this plugin is a 1:1, so perhaps it should be available at another name, e.g. `window.iabOpen` (the old API should be preserved until the next major though, since to keep backward compatibility). -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Assigned] (CB-8444) Don't clobber `window.open`
[ https://issues.apache.org/jira/browse/CB-8444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Chase reassigned CB-8444: --- Assignee: Jason Chase Don't clobber `window.open` --- Key: CB-8444 URL: https://issues.apache.org/jira/browse/CB-8444 Project: Apache Cordova Issue Type: Wish Components: Plugin InAppBrowser Reporter: sandstrom Assignee: Jason Chase Where Cordova plugins map 1:1 to W3C API's it's great that they clobber the corresponding namespace. Geolocation is a good example. However, it doesn't really feel like this plugin is a 1:1, so perhaps it should be available at another name, e.g. `window.iabOpen` (the old API should be preserved until the next major though, since to keep backward compatibility). -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-5536) Use Unicode arrows instead of greater than / less than symbols to indicate back and forward buttons
[ https://issues.apache.org/jira/browse/CB-5536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Chase resolved CB-5536. - Resolution: Implemented Use Unicode arrows instead of greater than / less than symbols to indicate back and forward buttons --- Key: CB-5536 URL: https://issues.apache.org/jira/browse/CB-5536 Project: Apache Cordova Issue Type: Improvement Components: Plugin InAppBrowser Affects Versions: 3.1.0 Environment: Android (possibly others) Reporter: Oliver Moran Priority: Trivial The plugin currently represents navigate back and navigate forward buttons with less than or equal to signs ( and ). These actions could be represented more attractively (and more appropriately) using Unicode arrows symbols: https://en.wikipedia.org/wiki/Arrow_(symbol)#Arrows_in_Unicode Code sample in Android: back.setText(\u21e6); // ⇦ forward.setText(\u21e8); // ⇨ .. or ... back.setText(\u2190); // ← forward.setText(\u2192); // → -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-7459) Allow automatic tests to be run for specific plugin(s)
[ https://issues.apache.org/jira/browse/CB-7459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Chase resolved CB-7459. - Resolution: Fixed Fix Version/s: Master Allow automatic tests to be run for specific plugin(s) -- Key: CB-7459 URL: https://issues.apache.org/jira/browse/CB-7459 Project: Apache Cordova Issue Type: Improvement Components: mobile-spec Reporter: Jason Chase Assignee: Michal Mocny Priority: Minor Fix For: Master Currently, the mobile spec test runner will discover automatic tests for all plugins, and then run all discovered tests en masse. When working on a specific issue/plugin, it would be convenient to be able to run tests for a single plugin (or small subset of plugins). The test framework already supports the concept of enabling/disabling tests for plugins, but that is not exposed in the UI for the test runner. Proposed changes: * On the Auto Tests page for plugins, provide a UI to individually select which tests should be run. This UI should allow for multi-select of plugins. * The UI for test selection should indicate the existing enabled status of each plugin * When the page is initially loaded, keep the existing behaviour, where all enabled plugin tests are automatically run * Subsequent runs (i.e. using the existing Again button) will reflect any user changes to the selected tests -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-8295) Enable CSP for mobilespec
[ https://issues.apache.org/jira/browse/CB-8295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Chase resolved CB-8295. - Resolution: Fixed Fix Version/s: Master Enable CSP for mobilespec - Key: CB-8295 URL: https://issues.apache.org/jira/browse/CB-8295 Project: Apache Cordova Issue Type: Improvement Components: mobile-spec Affects Versions: Master Reporter: Jason Chase Assignee: Jason Chase Fix For: Master With the work done in CB-8210 and CB-8252, it is now possible to run at least the mobilespec plugin tests under CSP. Consequently, it makes sense to turn on CSP by default for mobilespec. This should help ensure there are no regressions in the platform/plugin support for running under CSP. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-8304) File transfer plugin - upload to invalid server can cause app to crash on iOS
[ https://issues.apache.org/jira/browse/CB-8304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Chase updated CB-8304: Assignee: (was: Jason Chase) File transfer plugin - upload to invalid server can cause app to crash on iOS - Key: CB-8304 URL: https://issues.apache.org/jira/browse/CB-8304 Project: Apache Cordova Issue Type: Bug Components: iOS, mobile-spec, Plugin File Transfer Affects Versions: Master Reporter: Jason Chase Labels: file-transfer, ios, plugin This was discovered when investigating that the file transfer plugin automatic tests would consistently cause mobile spec to crash on iOS. The specific offending test is filetransfer.spec.25 should handle unknown host. Investigation reveals that when an invalid host is specified as the upload target, on iOS, the upload will fail in the background. Part of the plugin's native iOS error handling is to delete the target file. When the upload target does not include a path (e.g. the test uses http://foobar.apache.org;), an error will occur trying to delete a nil path. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-8304) File transfer plugin - upload to invalid server can cause app to crash on iOS
[ https://issues.apache.org/jira/browse/CB-8304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Chase updated CB-8304: Description: This was discovered when investigating that the file transfer plugin automatic tests would consistently cause mobile spec to crash on iOS. The specific offending test is filetransfer.spec.25 should handle unknown host. Investigation reveals that when an invalid host is specified as the upload target, on iOS, the upload will fail in the background. Part of the plugin's native iOS error handling is to delete the target file. When the upload target does not include a path (e.g. the test uses http://foobar.apache.org;), an error will occur trying to delete a nil path. was: One of the file transfer plugin automatic tests will consistently cause mobile spec to crash on iOS. Specifically, the test filetransfer.spec.25 should handle unknown host. File transfer plugin - upload to invalid server can cause app to crash on iOS - Key: CB-8304 URL: https://issues.apache.org/jira/browse/CB-8304 Project: Apache Cordova Issue Type: Bug Components: iOS, mobile-spec, Plugin File Transfer Affects Versions: Master Reporter: Jason Chase Assignee: Jason Chase Labels: file-transfer, ios, plugin This was discovered when investigating that the file transfer plugin automatic tests would consistently cause mobile spec to crash on iOS. The specific offending test is filetransfer.spec.25 should handle unknown host. Investigation reveals that when an invalid host is specified as the upload target, on iOS, the upload will fail in the background. Part of the plugin's native iOS error handling is to delete the target file. When the upload target does not include a path (e.g. the test uses http://foobar.apache.org;), an error will occur trying to delete a nil path. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-8304) File transfer plugin - upload to invalid server can cause app to crash on iOS
[ https://issues.apache.org/jira/browse/CB-8304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14275973#comment-14275973 ] Jason Chase commented on CB-8304: - The crashing test seems to have been introduced in the refactoring of the tests in CB-8125 (commit fc8f4f0001b8f4620d58c8633b0b44cd8c4f7945). However, this appears to be a latent bug, introduced in the past. That is, there is logic to clean up target files for failed connections, which implicitly assumes the target contains a path. File transfer plugin - upload to invalid server can cause app to crash on iOS - Key: CB-8304 URL: https://issues.apache.org/jira/browse/CB-8304 Project: Apache Cordova Issue Type: Bug Components: iOS, mobile-spec, Plugin File Transfer Affects Versions: Master Reporter: Jason Chase Assignee: Jason Chase Labels: file-transfer, ios, plugin This was discovered when investigating that the file transfer plugin automatic tests would consistently cause mobile spec to crash on iOS. The specific offending test is filetransfer.spec.25 should handle unknown host. Investigation reveals that when an invalid host is specified as the upload target, on iOS, the upload will fail in the background. Part of the plugin's native iOS error handling is to delete the target file. When the upload target does not include a path (e.g. the test uses http://foobar.apache.org;), an error will occur trying to delete a nil path. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-8304) File transfer plugin test causes mobile spec to crash on iOS
Jason Chase created CB-8304: --- Summary: File transfer plugin test causes mobile spec to crash on iOS Key: CB-8304 URL: https://issues.apache.org/jira/browse/CB-8304 Project: Apache Cordova Issue Type: Bug Components: iOS, mobile-spec, Plugin File Transfer Affects Versions: Master Reporter: Jason Chase Assignee: Jason Chase One of the file transfer plugin automatic tests will consistently cause mobile spec to crash on iOS. Specifically, the test filetransfer.spec.25 should handle unknown host. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-8304) File transfer plugin - upload to invalid server can cause app to crash on iOS
[ https://issues.apache.org/jira/browse/CB-8304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Chase updated CB-8304: Summary: File transfer plugin - upload to invalid server can cause app to crash on iOS (was: File transfer plugin test causes mobile spec to crash on iOS) File transfer plugin - upload to invalid server can cause app to crash on iOS - Key: CB-8304 URL: https://issues.apache.org/jira/browse/CB-8304 Project: Apache Cordova Issue Type: Bug Components: iOS, mobile-spec, Plugin File Transfer Affects Versions: Master Reporter: Jason Chase Assignee: Jason Chase One of the file transfer plugin automatic tests will consistently cause mobile spec to crash on iOS. Specifically, the test filetransfer.spec.25 should handle unknown host. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-8304) File transfer plugin - upload to invalid server can cause app to crash on iOS
[ https://issues.apache.org/jira/browse/CB-8304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Chase updated CB-8304: Labels: file-transfer ios plugin (was: ) File transfer plugin - upload to invalid server can cause app to crash on iOS - Key: CB-8304 URL: https://issues.apache.org/jira/browse/CB-8304 Project: Apache Cordova Issue Type: Bug Components: iOS, mobile-spec, Plugin File Transfer Affects Versions: Master Reporter: Jason Chase Assignee: Jason Chase Labels: file-transfer, ios, plugin One of the file transfer plugin automatic tests will consistently cause mobile spec to crash on iOS. Specifically, the test filetransfer.spec.25 should handle unknown host. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-8252) Prep core plugins for CSP by removing eval()s (Android only)
[ https://issues.apache.org/jira/browse/CB-8252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Chase resolved CB-8252. - Resolution: Fixed Fix Version/s: Master Prep core plugins for CSP by removing eval()s (Android only) Key: CB-8252 URL: https://issues.apache.org/jira/browse/CB-8252 Project: Apache Cordova Issue Type: Improvement Components: Plugins Affects Versions: Master Reporter: Jason Chase Assignee: Andrew Grieve Fix For: Master In preparation for CSP, remove any native Android code in the core plugins that is using inline javascript/eval()s. Other platforms with native code (i.e. iOS) are out of scope for now. Found only the media plugin (org.apache.cordova.media) that was using inline javascript (to send status updates). -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-8252) Prep core plugins for CSP by removing eval()s (Android only)
[ https://issues.apache.org/jira/browse/CB-8252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Chase updated CB-8252: Summary: Prep core plugins for CSP by removing eval()s (Android only) (was: Prep core plugins for CSP by removing eval()s) Prep core plugins for CSP by removing eval()s (Android only) Key: CB-8252 URL: https://issues.apache.org/jira/browse/CB-8252 Project: Apache Cordova Issue Type: Improvement Components: Plugins Affects Versions: Master Reporter: Jason Chase Assignee: Jason Chase In preparation for CSP, remove any native code in the core plugins that is using inline javascript/eval()s. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-8252) Prep core plugins for CSP by removing eval()s (Android only)
[ https://issues.apache.org/jira/browse/CB-8252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Chase updated CB-8252: Description: In preparation for CSP, remove any native Android code in the core plugins that is using inline javascript/eval()s. Other platforms with native code (i.e. iOS) are out of scope for now. was:In preparation for CSP, remove any native code in the core plugins that is using inline javascript/eval()s. Prep core plugins for CSP by removing eval()s (Android only) Key: CB-8252 URL: https://issues.apache.org/jira/browse/CB-8252 Project: Apache Cordova Issue Type: Improvement Components: Plugins Affects Versions: Master Reporter: Jason Chase Assignee: Jason Chase In preparation for CSP, remove any native Android code in the core plugins that is using inline javascript/eval()s. Other platforms with native code (i.e. iOS) are out of scope for now. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Assigned] (CB-8252) Prep core plugins for CSP by removing eval()s (Android only)
[ https://issues.apache.org/jira/browse/CB-8252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Chase reassigned CB-8252: --- Assignee: Andrew Grieve (was: Jason Chase) For review of pull request. Prep core plugins for CSP by removing eval()s (Android only) Key: CB-8252 URL: https://issues.apache.org/jira/browse/CB-8252 Project: Apache Cordova Issue Type: Improvement Components: Plugins Affects Versions: Master Reporter: Jason Chase Assignee: Andrew Grieve In preparation for CSP, remove any native Android code in the core plugins that is using inline javascript/eval()s. Other platforms with native code (i.e. iOS) are out of scope for now. Found only the media plugin (org.apache.cordova.media) that was using inline javascript (to send status updates). -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-8252) Prep core plugins for CSP by removing eval()s (Android only)
[ https://issues.apache.org/jira/browse/CB-8252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Chase updated CB-8252: Description: In preparation for CSP, remove any native Android code in the core plugins that is using inline javascript/eval()s. Other platforms with native code (i.e. iOS) are out of scope for now. Found only the media plugin (org.apache.cordova.media) that was using inline javascript (to send status updates). was: In preparation for CSP, remove any native Android code in the core plugins that is using inline javascript/eval()s. Other platforms with native code (i.e. iOS) are out of scope for now. Prep core plugins for CSP by removing eval()s (Android only) Key: CB-8252 URL: https://issues.apache.org/jira/browse/CB-8252 Project: Apache Cordova Issue Type: Improvement Components: Plugins Affects Versions: Master Reporter: Jason Chase Assignee: Jason Chase In preparation for CSP, remove any native Android code in the core plugins that is using inline javascript/eval()s. Other platforms with native code (i.e. iOS) are out of scope for now. Found only the media plugin (org.apache.cordova.media) that was using inline javascript (to send status updates). -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-8252) Prep core plugins for CSP by removing eval()s
Jason Chase created CB-8252: --- Summary: Prep core plugins for CSP by removing eval()s Key: CB-8252 URL: https://issues.apache.org/jira/browse/CB-8252 Project: Apache Cordova Issue Type: Improvement Components: Plugins Affects Versions: Master Reporter: Jason Chase Assignee: Jason Chase In preparation for CSP, remove any native code in the core plugins that is using inline javascript/eval()s. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Assigned] (CB-8210) Prep cordova-android for CSP by removing eval()s
[ https://issues.apache.org/jira/browse/CB-8210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Chase reassigned CB-8210: --- Assignee: Andrew Grieve (was: Jason Chase) Please take a look at the two linked pull requests. My testing shows that the keyboard events are fired successfully, with CSP enabled via a META tag. Is the goal to also replace all usages of loadUrl(javascript:...)? Prep cordova-android for CSP by removing eval()s Key: CB-8210 URL: https://issues.apache.org/jira/browse/CB-8210 Project: Apache Cordova Issue Type: Improvement Components: Android Affects Versions: Master Reporter: Jason Chase Assignee: Andrew Grieve In preparation for CSP, remove any native code in cordova-android is that using inline javascript/eval()s. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-8210) Prep cordova-android for CSP by removing eval()s
Jason Chase created CB-8210: --- Summary: Prep cordova-android for CSP by removing eval()s Key: CB-8210 URL: https://issues.apache.org/jira/browse/CB-8210 Project: Apache Cordova Issue Type: Improvement Components: Android Affects Versions: Master Reporter: Jason Chase Assignee: Jason Chase In preparation for CSP, remove any native code in cordova-android is that using inline javascript/eval()s. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-8154) Unable to add new versions of platforms or plugins
[ https://issues.apache.org/jira/browse/CB-8154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Chase resolved CB-8154. - Resolution: Fixed Fix Version/s: Master Pull request #130 has been merged to master. Unable to add new versions of platforms or plugins -- Key: CB-8154 URL: https://issues.apache.org/jira/browse/CB-8154 Project: Apache Cordova Issue Type: Bug Components: CLI, CordovaLib Affects Versions: Master Reporter: Jason Chase Fix For: Master Adding a platform or plugin from the registry will fail if the package was not previously downloaded/cached on the machine. *Steps to recreate:* - Delete the contents of ~/.plugman - Add a new plugin to an existing cordova app, cordova plugin add plugin id OR - Delete the contents of ~/.cordova/lib/npm_cache - Create a new cordova app - Add a platform to the app, e.g. cordova platform add android *Examples of the errors:* 10387@ 11:15 AM:~/dev/myapps/web-notifications$ cordova platform add android Creating android project... Error: ENOENT, no such file or directory '/Users/chasej/.cordova/lib/npm_cache/cordova-android/3.6.4/package/VERSION' at Object.fs.openSync (fs.js:432:18) at Object.fs.readFileSync (fs.js:289:15) at call_into_create (/Users/chasej/git/cordova/cordova-lib/cordova-lib/src/cordova/platform.js:447:30) at /Users/chasej/git/cordova/cordova-lib/cordova-lib/src/cordova/platform.js:128:24 at _fulfilled (/Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:787:54) at self.promiseDispatch.done (/Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:816:30) at Promise.promise.promiseDispatch (/Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:749:13) at /Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:557:44 at flush (/Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:108:17) at process._tickCallback (node.js:419:13) 10397@ 01:31 PM:~/dev/myapps/web-notifications$ cordova plugin add org.apache.cordova.inappbrowser Fetching plugin org.apache.cordova.inappbrowser via plugin registry Error: Could not find plugin info in /Users/chasej/.plugman/cache/org.apache.cordova.inappbrowser/0.5.4/package at new PluginInfo (/Users/chasej/git/cordova/cordova-lib/cordova-lib/src/PluginInfo.js:229:15) at copyPlugin (/Users/chasej/git/cordova/cordova-lib/cordova-lib/src/plugman/fetch.js:249:17) at /Users/chasej/git/cordova/cordova-lib/cordova-lib/src/plugman/fetch.js:150:20 at _fulfilled (/Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:787:54) at self.promiseDispatch.done (/Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:816:30) at Promise.promise.promiseDispatch (/Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:749:13) at /Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:557:44 at flush (/Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:108:17) -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-8154) Unable to add new versions of platforms or plugins
Jason Chase created CB-8154: --- Summary: Unable to add new versions of platforms or plugins Key: CB-8154 URL: https://issues.apache.org/jira/browse/CB-8154 Project: Apache Cordova Issue Type: Bug Components: CLI Affects Versions: Master Reporter: Jason Chase Assignee: Jason Chase Adding a platform or plugin from the registry will fail if the package was not previously downloaded/cached on the machine. Examples of the errors: 10387@ 11:15 AM:~/dev/myapps/web-notifications$ cordova platform add android Creating android project... Error: ENOENT, no such file or directory '/Users/chasej/.cordova/lib/npm_cache/cordova-android/3.6.4/package/VERSION' at Object.fs.openSync (fs.js:432:18) at Object.fs.readFileSync (fs.js:289:15) at call_into_create (/Users/chasej/git/cordova/cordova-lib/cordova-lib/src/cordova/platform.js:447:30) at /Users/chasej/git/cordova/cordova-lib/cordova-lib/src/cordova/platform.js:128:24 at _fulfilled (/Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:787:54) at self.promiseDispatch.done (/Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:816:30) at Promise.promise.promiseDispatch (/Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:749:13) at /Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:557:44 at flush (/Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:108:17) at process._tickCallback (node.js:419:13) 10397@ 01:31 PM:~/dev/myapps/web-notifications$ cordova plugin add org.apache.cordova.inappbrowser Fetching plugin org.apache.cordova.inappbrowser via plugin registry Error: Could not find plugin info in /Users/chasej/.plugman/cache/org.apache.cordova.inappbrowser/0.5.4/package at new PluginInfo (/Users/chasej/git/cordova/cordova-lib/cordova-lib/src/PluginInfo.js:229:15) at copyPlugin (/Users/chasej/git/cordova/cordova-lib/cordova-lib/src/plugman/fetch.js:249:17) at /Users/chasej/git/cordova/cordova-lib/cordova-lib/src/plugman/fetch.js:150:20 at _fulfilled (/Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:787:54) at self.promiseDispatch.done (/Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:816:30) at Promise.promise.promiseDispatch (/Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:749:13) at /Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:557:44 at flush (/Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:108:17) -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-8154) Unable to add new versions of platforms or plugins
[ https://issues.apache.org/jira/browse/CB-8154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14244424#comment-14244424 ] Jason Chase commented on CB-8154: - The problem was uncovered by a recent commit to update the npm dependency to version 1.4.28 (issue CB-7736, commit f99de0d2c935c444cf982dfb2d3015bfaa09efe6). Root cause: - The cli is programmatically using npm cache add to download plugins/platforms from the registry - Prior to npm 1.4.10, adding to cache had the side effect of unpacking the package and leaving the contents on disk - The cli would then grab files out of the unpacked directory - With npm 1.4.10, there was an explicit change to stop the unpacking (see commit https://github.com/npm/npm/commit/d5fa4d01f7bf91027acc933411010bae5676e102) - As a result, the package.tgz is still downloaded, but the contents are not available in the location expected by the cli According to the npm docs (https://docs.npmjs.com/api/cache), the cli code should not have been relying on the specific folder structure in the cache. The only guarantees are that the package.tgz and package.json files will be cached (described by npm help cache). Unable to add new versions of platforms or plugins -- Key: CB-8154 URL: https://issues.apache.org/jira/browse/CB-8154 Project: Apache Cordova Issue Type: Bug Components: CLI Affects Versions: Master Reporter: Jason Chase Assignee: Jason Chase Adding a platform or plugin from the registry will fail if the package was not previously downloaded/cached on the machine. Examples of the errors: 10387@ 11:15 AM:~/dev/myapps/web-notifications$ cordova platform add android Creating android project... Error: ENOENT, no such file or directory '/Users/chasej/.cordova/lib/npm_cache/cordova-android/3.6.4/package/VERSION' at Object.fs.openSync (fs.js:432:18) at Object.fs.readFileSync (fs.js:289:15) at call_into_create (/Users/chasej/git/cordova/cordova-lib/cordova-lib/src/cordova/platform.js:447:30) at /Users/chasej/git/cordova/cordova-lib/cordova-lib/src/cordova/platform.js:128:24 at _fulfilled (/Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:787:54) at self.promiseDispatch.done (/Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:816:30) at Promise.promise.promiseDispatch (/Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:749:13) at /Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:557:44 at flush (/Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:108:17) at process._tickCallback (node.js:419:13) 10397@ 01:31 PM:~/dev/myapps/web-notifications$ cordova plugin add org.apache.cordova.inappbrowser Fetching plugin org.apache.cordova.inappbrowser via plugin registry Error: Could not find plugin info in /Users/chasej/.plugman/cache/org.apache.cordova.inappbrowser/0.5.4/package at new PluginInfo (/Users/chasej/git/cordova/cordova-lib/cordova-lib/src/PluginInfo.js:229:15) at copyPlugin (/Users/chasej/git/cordova/cordova-lib/cordova-lib/src/plugman/fetch.js:249:17) at /Users/chasej/git/cordova/cordova-lib/cordova-lib/src/plugman/fetch.js:150:20 at _fulfilled (/Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:787:54) at self.promiseDispatch.done (/Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:816:30) at Promise.promise.promiseDispatch (/Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:749:13) at /Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:557:44 at flush (/Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:108:17) -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-8154) Unable to add new versions of platforms or plugins
[ https://issues.apache.org/jira/browse/CB-8154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Chase updated CB-8154: Component/s: CordovaLib Unable to add new versions of platforms or plugins -- Key: CB-8154 URL: https://issues.apache.org/jira/browse/CB-8154 Project: Apache Cordova Issue Type: Bug Components: CLI, CordovaLib Affects Versions: Master Reporter: Jason Chase Assignee: Jason Chase Adding a platform or plugin from the registry will fail if the package was not previously downloaded/cached on the machine. *Steps to recreate:* - Delete the contents of ~/.plugman - Add a new plugin to an existing cordova app, cordova plugin add plugin id OR - Delete the contents of ~/.cordova/lib/npm_cache - Create a new cordova app - Add a platform to the app, e.g. cordova platform add android *Examples of the errors:* 10387@ 11:15 AM:~/dev/myapps/web-notifications$ cordova platform add android Creating android project... Error: ENOENT, no such file or directory '/Users/chasej/.cordova/lib/npm_cache/cordova-android/3.6.4/package/VERSION' at Object.fs.openSync (fs.js:432:18) at Object.fs.readFileSync (fs.js:289:15) at call_into_create (/Users/chasej/git/cordova/cordova-lib/cordova-lib/src/cordova/platform.js:447:30) at /Users/chasej/git/cordova/cordova-lib/cordova-lib/src/cordova/platform.js:128:24 at _fulfilled (/Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:787:54) at self.promiseDispatch.done (/Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:816:30) at Promise.promise.promiseDispatch (/Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:749:13) at /Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:557:44 at flush (/Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:108:17) at process._tickCallback (node.js:419:13) 10397@ 01:31 PM:~/dev/myapps/web-notifications$ cordova plugin add org.apache.cordova.inappbrowser Fetching plugin org.apache.cordova.inappbrowser via plugin registry Error: Could not find plugin info in /Users/chasej/.plugman/cache/org.apache.cordova.inappbrowser/0.5.4/package at new PluginInfo (/Users/chasej/git/cordova/cordova-lib/cordova-lib/src/PluginInfo.js:229:15) at copyPlugin (/Users/chasej/git/cordova/cordova-lib/cordova-lib/src/plugman/fetch.js:249:17) at /Users/chasej/git/cordova/cordova-lib/cordova-lib/src/plugman/fetch.js:150:20 at _fulfilled (/Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:787:54) at self.promiseDispatch.done (/Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:816:30) at Promise.promise.promiseDispatch (/Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:749:13) at /Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:557:44 at flush (/Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:108:17) -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-8154) Unable to add new versions of platforms or plugins
[ https://issues.apache.org/jira/browse/CB-8154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Chase updated CB-8154: Description: Adding a platform or plugin from the registry will fail if the package was not previously downloaded/cached on the machine. *Steps to recreate:* - Delete the contents of ~/.plugman - Add a new plugin to an existing cordova app, cordova plugin add plugin id OR - Delete the contents of ~/.cordova/lib/npm_cache - Create a new cordova app - Add a platform to the app, e.g. cordova platform add android *Examples of the errors:* 10387@ 11:15 AM:~/dev/myapps/web-notifications$ cordova platform add android Creating android project... Error: ENOENT, no such file or directory '/Users/chasej/.cordova/lib/npm_cache/cordova-android/3.6.4/package/VERSION' at Object.fs.openSync (fs.js:432:18) at Object.fs.readFileSync (fs.js:289:15) at call_into_create (/Users/chasej/git/cordova/cordova-lib/cordova-lib/src/cordova/platform.js:447:30) at /Users/chasej/git/cordova/cordova-lib/cordova-lib/src/cordova/platform.js:128:24 at _fulfilled (/Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:787:54) at self.promiseDispatch.done (/Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:816:30) at Promise.promise.promiseDispatch (/Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:749:13) at /Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:557:44 at flush (/Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:108:17) at process._tickCallback (node.js:419:13) 10397@ 01:31 PM:~/dev/myapps/web-notifications$ cordova plugin add org.apache.cordova.inappbrowser Fetching plugin org.apache.cordova.inappbrowser via plugin registry Error: Could not find plugin info in /Users/chasej/.plugman/cache/org.apache.cordova.inappbrowser/0.5.4/package at new PluginInfo (/Users/chasej/git/cordova/cordova-lib/cordova-lib/src/PluginInfo.js:229:15) at copyPlugin (/Users/chasej/git/cordova/cordova-lib/cordova-lib/src/plugman/fetch.js:249:17) at /Users/chasej/git/cordova/cordova-lib/cordova-lib/src/plugman/fetch.js:150:20 at _fulfilled (/Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:787:54) at self.promiseDispatch.done (/Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:816:30) at Promise.promise.promiseDispatch (/Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:749:13) at /Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:557:44 at flush (/Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:108:17) was: Adding a platform or plugin from the registry will fail if the package was not previously downloaded/cached on the machine. Examples of the errors: 10387@ 11:15 AM:~/dev/myapps/web-notifications$ cordova platform add android Creating android project... Error: ENOENT, no such file or directory '/Users/chasej/.cordova/lib/npm_cache/cordova-android/3.6.4/package/VERSION' at Object.fs.openSync (fs.js:432:18) at Object.fs.readFileSync (fs.js:289:15) at call_into_create (/Users/chasej/git/cordova/cordova-lib/cordova-lib/src/cordova/platform.js:447:30) at /Users/chasej/git/cordova/cordova-lib/cordova-lib/src/cordova/platform.js:128:24 at _fulfilled (/Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:787:54) at self.promiseDispatch.done (/Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:816:30) at Promise.promise.promiseDispatch (/Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:749:13) at /Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:557:44 at flush (/Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:108:17) at process._tickCallback (node.js:419:13) 10397@ 01:31 PM:~/dev/myapps/web-notifications$ cordova plugin add org.apache.cordova.inappbrowser Fetching plugin org.apache.cordova.inappbrowser via plugin registry Error: Could not find plugin info in /Users/chasej/.plugman/cache/org.apache.cordova.inappbrowser/0.5.4/package at new PluginInfo (/Users/chasej/git/cordova/cordova-lib/cordova-lib/src/PluginInfo.js:229:15) at copyPlugin (/Users/chasej/git/cordova/cordova-lib/cordova-lib/src/plugman/fetch.js:249:17) at /Users/chasej/git/cordova/cordova-lib/cordova-lib/src/plugman/fetch.js:150:20 at _fulfilled (/Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:787:54) at self.promiseDispatch.done (/Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:816:30) at Promise.promise.promiseDispatch (/Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:749:13) at /Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:557:44 at flush
[jira] [Updated] (CB-8154) Unable to add new versions of platforms or plugins
[ https://issues.apache.org/jira/browse/CB-8154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Chase updated CB-8154: Assignee: (was: Jason Chase) Unable to add new versions of platforms or plugins -- Key: CB-8154 URL: https://issues.apache.org/jira/browse/CB-8154 Project: Apache Cordova Issue Type: Bug Components: CLI, CordovaLib Affects Versions: Master Reporter: Jason Chase Adding a platform or plugin from the registry will fail if the package was not previously downloaded/cached on the machine. *Steps to recreate:* - Delete the contents of ~/.plugman - Add a new plugin to an existing cordova app, cordova plugin add plugin id OR - Delete the contents of ~/.cordova/lib/npm_cache - Create a new cordova app - Add a platform to the app, e.g. cordova platform add android *Examples of the errors:* 10387@ 11:15 AM:~/dev/myapps/web-notifications$ cordova platform add android Creating android project... Error: ENOENT, no such file or directory '/Users/chasej/.cordova/lib/npm_cache/cordova-android/3.6.4/package/VERSION' at Object.fs.openSync (fs.js:432:18) at Object.fs.readFileSync (fs.js:289:15) at call_into_create (/Users/chasej/git/cordova/cordova-lib/cordova-lib/src/cordova/platform.js:447:30) at /Users/chasej/git/cordova/cordova-lib/cordova-lib/src/cordova/platform.js:128:24 at _fulfilled (/Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:787:54) at self.promiseDispatch.done (/Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:816:30) at Promise.promise.promiseDispatch (/Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:749:13) at /Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:557:44 at flush (/Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:108:17) at process._tickCallback (node.js:419:13) 10397@ 01:31 PM:~/dev/myapps/web-notifications$ cordova plugin add org.apache.cordova.inappbrowser Fetching plugin org.apache.cordova.inappbrowser via plugin registry Error: Could not find plugin info in /Users/chasej/.plugman/cache/org.apache.cordova.inappbrowser/0.5.4/package at new PluginInfo (/Users/chasej/git/cordova/cordova-lib/cordova-lib/src/PluginInfo.js:229:15) at copyPlugin (/Users/chasej/git/cordova/cordova-lib/cordova-lib/src/plugman/fetch.js:249:17) at /Users/chasej/git/cordova/cordova-lib/cordova-lib/src/plugman/fetch.js:150:20 at _fulfilled (/Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:787:54) at self.promiseDispatch.done (/Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:816:30) at Promise.promise.promiseDispatch (/Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:749:13) at /Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:557:44 at flush (/Users/chasej/git/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:108:17) -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-7459) Allow automatic tests to be run for specific plugin(s)
[ https://issues.apache.org/jira/browse/CB-7459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14128482#comment-14128482 ] Jason Chase commented on CB-7459: - Pull request updated and rebased (hopefully correctly). Allow automatic tests to be run for specific plugin(s) -- Key: CB-7459 URL: https://issues.apache.org/jira/browse/CB-7459 Project: Apache Cordova Issue Type: Improvement Components: mobile-spec Reporter: Jason Chase Assignee: Michal Mocny Priority: Minor Currently, the mobile spec test runner will discover automatic tests for all plugins, and then run all discovered tests en masse. When working on a specific issue/plugin, it would be convenient to be able to run tests for a single plugin (or small subset of plugins). The test framework already supports the concept of enabling/disabling tests for plugins, but that is not exposed in the UI for the test runner. Proposed changes: * On the Auto Tests page for plugins, provide a UI to individually select which tests should be run. This UI should allow for multi-select of plugins. * The UI for test selection should indicate the existing enabled status of each plugin * When the page is initially loaded, keep the existing behaviour, where all enabled plugin tests are automatically run * Subsequent runs (i.e. using the existing Again button) will reflect any user changes to the selected tests -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7459) Allow automatic tests to be run for specific plugin(s)
[ https://issues.apache.org/jira/browse/CB-7459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14127478#comment-14127478 ] Jason Chase commented on CB-7459: - Pull request updated to address latest feedback Allow automatic tests to be run for specific plugin(s) -- Key: CB-7459 URL: https://issues.apache.org/jira/browse/CB-7459 Project: Apache Cordova Issue Type: Improvement Components: mobile-spec Reporter: Jason Chase Assignee: Michal Mocny Priority: Minor Currently, the mobile spec test runner will discover automatic tests for all plugins, and then run all discovered tests en masse. When working on a specific issue/plugin, it would be convenient to be able to run tests for a single plugin (or small subset of plugins). The test framework already supports the concept of enabling/disabling tests for plugins, but that is not exposed in the UI for the test runner. Proposed changes: * On the Auto Tests page for plugins, provide a UI to individually select which tests should be run. This UI should allow for multi-select of plugins. * The UI for test selection should indicate the existing enabled status of each plugin * When the page is initially loaded, keep the existing behaviour, where all enabled plugin tests are automatically run * Subsequent runs (i.e. using the existing Again button) will reflect any user changes to the selected tests -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7459) Allow automatic tests to be run for specific plugin(s)
[ https://issues.apache.org/jira/browse/CB-7459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14125526#comment-14125526 ] Jason Chase commented on CB-7459: - See pull request https://github.com/apache/cordova-plugin-test-framework/pull/4 Allow automatic tests to be run for specific plugin(s) -- Key: CB-7459 URL: https://issues.apache.org/jira/browse/CB-7459 Project: Apache Cordova Issue Type: Improvement Components: mobile-spec Reporter: Jason Chase Assignee: Jason Chase Priority: Minor Currently, the mobile spec test runner will discover automatic tests for all plugins, and then run all discovered tests en masse. When working on a specific issue/plugin, it would be convenient to be able to run tests for a single plugin (or small subset of plugins). The test framework already supports the concept of enabling/disabling tests for plugins, but that is not exposed in the UI for the test runner. Proposed changes: * On the Auto Tests page for plugins, provide a UI to individually select which tests should be run. This UI should allow for multi-select of plugins. * The UI for test selection should indicate the existing enabled status of each plugin * When the page is initially loaded, keep the existing behaviour, where all enabled plugin tests are automatically run * Subsequent runs (i.e. using the existing Again button) will reflect any user changes to the selected tests -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (CB-7459) Allow automatic tests to be run for specific plugin(s)
[ https://issues.apache.org/jira/browse/CB-7459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14125526#comment-14125526 ] Jason Chase edited comment on CB-7459 at 9/8/14 2:25 PM: - See pull request https://github.com/apache/cordova-plugin-test-framework/pull/4 Tested changes on multiple Android devices (v4.4.3 and v4.1), and IOS simulator. Not tested on other platforms. was (Author: chasej): See pull request https://github.com/apache/cordova-plugin-test-framework/pull/4 Allow automatic tests to be run for specific plugin(s) -- Key: CB-7459 URL: https://issues.apache.org/jira/browse/CB-7459 Project: Apache Cordova Issue Type: Improvement Components: mobile-spec Reporter: Jason Chase Assignee: Jason Chase Priority: Minor Currently, the mobile spec test runner will discover automatic tests for all plugins, and then run all discovered tests en masse. When working on a specific issue/plugin, it would be convenient to be able to run tests for a single plugin (or small subset of plugins). The test framework already supports the concept of enabling/disabling tests for plugins, but that is not exposed in the UI for the test runner. Proposed changes: * On the Auto Tests page for plugins, provide a UI to individually select which tests should be run. This UI should allow for multi-select of plugins. * The UI for test selection should indicate the existing enabled status of each plugin * When the page is initially loaded, keep the existing behaviour, where all enabled plugin tests are automatically run * Subsequent runs (i.e. using the existing Again button) will reflect any user changes to the selected tests -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CB-7459) Allow automatic tests to be run for specific plugin(s)
[ https://issues.apache.org/jira/browse/CB-7459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Chase reassigned CB-7459: --- Assignee: Michal Mocny (was: Jason Chase) For your review. Allow automatic tests to be run for specific plugin(s) -- Key: CB-7459 URL: https://issues.apache.org/jira/browse/CB-7459 Project: Apache Cordova Issue Type: Improvement Components: mobile-spec Reporter: Jason Chase Assignee: Michal Mocny Priority: Minor Currently, the mobile spec test runner will discover automatic tests for all plugins, and then run all discovered tests en masse. When working on a specific issue/plugin, it would be convenient to be able to run tests for a single plugin (or small subset of plugins). The test framework already supports the concept of enabling/disabling tests for plugins, but that is not exposed in the UI for the test runner. Proposed changes: * On the Auto Tests page for plugins, provide a UI to individually select which tests should be run. This UI should allow for multi-select of plugins. * The UI for test selection should indicate the existing enabled status of each plugin * When the page is initially loaded, keep the existing behaviour, where all enabled plugin tests are automatically run * Subsequent runs (i.e. using the existing Again button) will reflect any user changes to the selected tests -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CB-7459) Allow automatic tests to be run for specific plugin(s)
[ https://issues.apache.org/jira/browse/CB-7459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14126016#comment-14126016 ] Jason Chase commented on CB-7459: - I've added another commit to the pull request to address the review feedback. Allow automatic tests to be run for specific plugin(s) -- Key: CB-7459 URL: https://issues.apache.org/jira/browse/CB-7459 Project: Apache Cordova Issue Type: Improvement Components: mobile-spec Reporter: Jason Chase Assignee: Michal Mocny Priority: Minor Currently, the mobile spec test runner will discover automatic tests for all plugins, and then run all discovered tests en masse. When working on a specific issue/plugin, it would be convenient to be able to run tests for a single plugin (or small subset of plugins). The test framework already supports the concept of enabling/disabling tests for plugins, but that is not exposed in the UI for the test runner. Proposed changes: * On the Auto Tests page for plugins, provide a UI to individually select which tests should be run. This UI should allow for multi-select of plugins. * The UI for test selection should indicate the existing enabled status of each plugin * When the page is initially loaded, keep the existing behaviour, where all enabled plugin tests are automatically run * Subsequent runs (i.e. using the existing Again button) will reflect any user changes to the selected tests -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CB-7459) Allow automatic tests to be run for specific plugin(s)
Jason Chase created CB-7459: --- Summary: Allow automatic tests to be run for specific plugin(s) Key: CB-7459 URL: https://issues.apache.org/jira/browse/CB-7459 Project: Apache Cordova Issue Type: Improvement Components: mobile-spec Reporter: Jason Chase Assignee: Jason Chase Priority: Minor Currently, the mobile spec test runner will discover automatic tests for all plugins, and then run all discovered tests en masse. When working on a specific issue/plugin, it would be convenient to be able to run tests for a single plugin (or small subset of plugins). The test framework already supports the concept of enabling/disabling tests for plugins, but that is not exposed in the UI for the test runner. Proposed changes: * On the Auto Tests page for plugins, provide a UI to individually select which tests should be run. This UI should allow for multi-select of plugins. * The UI for test selection should indicate the existing enabled status of each plugin * When the page is initially loaded, keep the existing behaviour, where all enabled plugin tests are automatically run * Subsequent runs (i.e. using the existing Again button) will reflect any user changes to the selected tests -- This message was sent by Atlassian JIRA (v6.3.4#6332)
