[jira] [Commented] (CB-13311) Statusbar does not overlay correctly on iPhone X
[ https://issues.apache.org/jira/browse/CB-13311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16254586#comment-16254586 ] ASF GitHub Bot commented on CB-13311: - jay-b commented on issue #87: CB-13311: (iOS) Statusbar does not overlay correctly on iPhone X URL: https://github.com/apache/cordova-plugin-statusbar/pull/87#issuecomment-344783469 Hi folks. In my Ionic v1 app, I've installed this PR, have `viewport-fit=cover` in my www/index.html, updated the Splash assets, and added these [SCSS Platform Tweaks](https://raw.githubusercontent.com/ionic-team/ionic-v1/fc404f98c346fa9b86609236568d575ce7c9f2f8/scss/_platform.scss) but I'm still getting incorrect padding in the header and footer on the iPhone X [Screenshot showing iPhone X / iPhone 8](http://cdn.4muladesign.com/clients/jb/assets/uploads/2017/iPhoneX-UI-Padding-Issue--2017-11-16.jpg) Anything else I could try? cli packages: (/usr/local/lib/node_modules) @ionic/cli-utils : 1.18.0 ionic (Ionic CLI) : 3.18.0 global packages: cordova (Cordova CLI) : 7.1.0 local packages: Cordova Platforms : android 6.2.3 ios 4.5.3 Ionic Framework : ionic1 1.3.2 System: ios-deploy : 1.9.2 Node : v6.11.0 npm: 5.5.1 OS : macOS Sierra Xcode : Xcode 9.1 Build version 9B55 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Statusbar does not overlay correctly on iPhone X > > > Key: CB-13311 > URL: https://issues.apache.org/jira/browse/CB-13311 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-plugin-statusbar >Reporter: jcesarmobile >Assignee: jcesarmobile > > As statusbar plugin has the statusbar height hardcoded to 20 points, it > doesn't overlay correctly on the iPhone X simulator as it's statusbar height > is 44 points. > This happens when the viewport has viewport-fit=cover -- 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-13311) Statusbar does not overlay correctly on iPhone X
[ https://issues.apache.org/jira/browse/CB-13311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16254584#comment-16254584 ] ASF GitHub Bot commented on CB-13311: - jay-b commented on issue #87: CB-13311: (iOS) Statusbar does not overlay correctly on iPhone X URL: https://github.com/apache/cordova-plugin-statusbar/pull/87#issuecomment-344783469 Hi folks. In my Ionic v1 app, I've installed this PR, have `viewport-fit=cover` in my www/index.html, updated the Splash assets, and added these [SCSS Platform Tweaks](https://raw.githubusercontent.com/ionic-team/ionic-v1/fc404f98c346fa9b86609236568d575ce7c9f2f8/scss/_platform.scss) but I'm still getting incorrect padding on the iPhone X [Screenshot showing iPhone X / iPhone 8](http://cdn.4muladesign.com/clients/jb/assets/uploads/2017/iPhoneX-UI-Padding-Issue--2017-11-16.jpg) Anything else I could try? cli packages: (/usr/local/lib/node_modules) @ionic/cli-utils : 1.18.0 ionic (Ionic CLI) : 3.18.0 global packages: cordova (Cordova CLI) : 7.1.0 local packages: Cordova Platforms : android 6.2.3 ios 4.5.3 Ionic Framework : ionic1 1.3.2 System: ios-deploy : 1.9.2 Node : v6.11.0 npm: 5.5.1 OS : macOS Sierra Xcode : Xcode 9.1 Build version 9B55 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Statusbar does not overlay correctly on iPhone X > > > Key: CB-13311 > URL: https://issues.apache.org/jira/browse/CB-13311 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-plugin-statusbar >Reporter: jcesarmobile >Assignee: jcesarmobile > > As statusbar plugin has the statusbar height hardcoded to 20 points, it > doesn't overlay correctly on the iPhone X simulator as it's statusbar height > is 44 points. > This happens when the viewport has viewport-fit=cover -- 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-13580) cordova-android 6.4.0 broke build if cdvBuildMultipleApks is set to true
[ https://issues.apache.org/jira/browse/CB-13580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16254579#comment-16254579 ] ASF GitHub Bot commented on CB-13580: - codecov-io commented on issue #417: CB-13580: (android) fix build for multiple apks (different product flavors) URL: https://github.com/apache/cordova-android/pull/417#issuecomment-344782111 # [Codecov](https://codecov.io/gh/apache/cordova-android/pull/417?src=pr&el=h1) Report > Merging [#417](https://codecov.io/gh/apache/cordova-android/pull/417?src=pr&el=desc) into [master](https://codecov.io/gh/apache/cordova-android/commit/3760616639eb8d264edc99c3b5c8794c4d378bc8?src=pr&el=desc) will **decrease** coverage by `0.23%`. > The diff coverage is `0%`. [](https://codecov.io/gh/apache/cordova-android/pull/417?src=pr&el=tree) ```diff @@Coverage Diff @@ ## master #417 +/- ## == - Coverage 44.01% 43.77% -0.24% == Files 17 17 Lines1679 1688 +9 Branches 304 306 +2 == Hits 739 739 - Misses940 949 +9 ``` | [Impacted Files](https://codecov.io/gh/apache/cordova-android/pull/417?src=pr&el=tree) | Coverage Δ | | |---|---|---| | [...n/templates/cordova/lib/builders/GenericBuilder.js](https://codecov.io/gh/apache/cordova-android/pull/417?src=pr&el=tree#diff-YmluL3RlbXBsYXRlcy9jb3Jkb3ZhL2xpYi9idWlsZGVycy9HZW5lcmljQnVpbGRlci5qcw==) | `27.5% <0%> (-3.49%)` | :arrow_down: | -- [Continue to review full report at Codecov](https://codecov.io/gh/apache/cordova-android/pull/417?src=pr&el=continue). > **Legend** - [Click here to learn more](https://docs.codecov.io/docs/codecov-delta) > `Δ = absolute (impact)`, `ø = not affected`, `? = missing data` > Powered by [Codecov](https://codecov.io/gh/apache/cordova-android/pull/417?src=pr&el=footer). Last update [3760616...5d99e50](https://codecov.io/gh/apache/cordova-android/pull/417?src=pr&el=lastupdated). Read the [comment docs](https://docs.codecov.io/docs/pull-request-comments). This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > cordova-android 6.4.0 broke build if cdvBuildMultipleApks is set to true > > > Key: CB-13580 > URL: https://issues.apache.org/jira/browse/CB-13580 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-android >Affects Versions: 6.4.0 >Reporter: David Strauß >Assignee: Joe Bowser > Labels: build > > With the latest cordova-android (6.4.0) builds for different product flavors > (arm, x86) do not work anymore (error e.g.: "No flavor is associated with > flavor dimension ...") because of the changes introduced with gradle 3.0.0. > With the new gradle plugin a flavorDimenson must be specified to build > different product flavors (mentioned > [here|https://developer.android.com/studio/build/gradle-plugin-3-0-0-migration.html?utm_source=android-studio#flavor_dimensions] > in the upgrade guide. This can be fixed by adding `flavorDimensions > "default"` to build.gradle if cdvBuildMultipleApks is set to true. > Another change that was introduced with the new gradle version is that builds > for different architectures are put into their own directory > (build/outputs/apk//) which results in APK files not > being found (mentioned in the upgrade guide under the point "Modifying > variant outputs at build time may not work"). > This can be fixed by adapting the findOutputApksHelper method in > GenericBuilder.js. > An unfortunate side effect of these issues is that projects leveraging > crosswalk do not work anymore. -- 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-13580) cordova-android 6.4.0 broke build if cdvBuildMultipleApks is set to true
[ https://issues.apache.org/jira/browse/CB-13580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16254576#comment-16254576 ] ASF GitHub Bot commented on CB-13580: - DavidStrausz commented on issue #417: CB-13580: (android) fix build for multiple apks (different product flavors) URL: https://github.com/apache/cordova-android/pull/417#issuecomment-344781050 @infil00p Done! 👍 Yeah it also took me some time to figure it out. But the migration guide was really useful if read carfully. I will definitely keep that in mind for future contributions, thanks for pointing that out! This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > cordova-android 6.4.0 broke build if cdvBuildMultipleApks is set to true > > > Key: CB-13580 > URL: https://issues.apache.org/jira/browse/CB-13580 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-android >Affects Versions: 6.4.0 >Reporter: David Strauß >Assignee: Joe Bowser > Labels: build > > With the latest cordova-android (6.4.0) builds for different product flavors > (arm, x86) do not work anymore (error e.g.: "No flavor is associated with > flavor dimension ...") because of the changes introduced with gradle 3.0.0. > With the new gradle plugin a flavorDimenson must be specified to build > different product flavors (mentioned > [here|https://developer.android.com/studio/build/gradle-plugin-3-0-0-migration.html?utm_source=android-studio#flavor_dimensions] > in the upgrade guide. This can be fixed by adding `flavorDimensions > "default"` to build.gradle if cdvBuildMultipleApks is set to true. > Another change that was introduced with the new gradle version is that builds > for different architectures are put into their own directory > (build/outputs/apk//) which results in APK files not > being found (mentioned in the upgrade guide under the point "Modifying > variant outputs at build time may not work"). > This can be fixed by adapting the findOutputApksHelper method in > GenericBuilder.js. > An unfortunate side effect of these issues is that projects leveraging > crosswalk do not work anymore. -- 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-13580) cordova-android 6.4.0 broke build if cdvBuildMultipleApks is set to true
[ https://issues.apache.org/jira/browse/CB-13580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16254559#comment-16254559 ] ASF GitHub Bot commented on CB-13580: - infil00p commented on issue #417: CB-13580: (android) fix build for multiple apks (different product flavors) URL: https://github.com/apache/cordova-android/pull/417#issuecomment-344778138 @DavidStrausz Fix the lint errors and I'll merge this in. I tried adding more flavours and it kept crapping the bed on me. I didn't realize that just adding default would get this to work properly again. If you're inclined, you can always send a PR to my Crosswalk repo. It's technically the "official" repo, and if you could get that working, that would win you some serious cred. (And yeah, I'll try to merge it in, because I can do that, even though I'm not technically supposed to). This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > cordova-android 6.4.0 broke build if cdvBuildMultipleApks is set to true > > > Key: CB-13580 > URL: https://issues.apache.org/jira/browse/CB-13580 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-android >Affects Versions: 6.4.0 >Reporter: David Strauß >Assignee: Joe Bowser > Labels: build > > With the latest cordova-android (6.4.0) builds for different product flavors > (arm, x86) do not work anymore (error e.g.: "No flavor is associated with > flavor dimension ...") because of the changes introduced with gradle 3.0.0. > With the new gradle plugin a flavorDimenson must be specified to build > different product flavors (mentioned > [here|https://developer.android.com/studio/build/gradle-plugin-3-0-0-migration.html?utm_source=android-studio#flavor_dimensions] > in the upgrade guide. This can be fixed by adding `flavorDimensions > "default"` to build.gradle if cdvBuildMultipleApks is set to true. > Another change that was introduced with the new gradle version is that builds > for different architectures are put into their own directory > (build/outputs/apk//) which results in APK files not > being found (mentioned in the upgrade guide under the point "Modifying > variant outputs at build time may not work"). > This can be fixed by adapting the findOutputApksHelper method in > GenericBuilder.js. > An unfortunate side effect of these issues is that projects leveraging > crosswalk do not work anymore. -- 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-13580) cordova-android 6.4.0 broke build if cdvBuildMultipleApks is set to true
[ https://issues.apache.org/jira/browse/CB-13580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16254556#comment-16254556 ] ASF GitHub Bot commented on CB-13580: - infil00p commented on issue #417: CB-13580: (android) fix build for multiple apks (different product flavors) URL: https://github.com/apache/cordova-android/pull/417#issuecomment-344778138 @DavidStrausz Fix the lint errors and I'll merge this in. I tried adding more flavours and it kept crapping the bed on me. I didn't realize that just adding default would get this to work properly again. If you're inclined, you can always send a PR to my Crosswalk repo. It's technically the "official" repo, and if you could get that working, that would win you some serious cred. (And yeah, I'll try merge it in, because I can do that, even though I'm not technically supposed to). This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > cordova-android 6.4.0 broke build if cdvBuildMultipleApks is set to true > > > Key: CB-13580 > URL: https://issues.apache.org/jira/browse/CB-13580 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-android >Affects Versions: 6.4.0 >Reporter: David Strauß >Assignee: Joe Bowser > Labels: build > > With the latest cordova-android (6.4.0) builds for different product flavors > (arm, x86) do not work anymore (error e.g.: "No flavor is associated with > flavor dimension ...") because of the changes introduced with gradle 3.0.0. > With the new gradle plugin a flavorDimenson must be specified to build > different product flavors (mentioned > [here|https://developer.android.com/studio/build/gradle-plugin-3-0-0-migration.html?utm_source=android-studio#flavor_dimensions] > in the upgrade guide. This can be fixed by adding `flavorDimensions > "default"` to build.gradle if cdvBuildMultipleApks is set to true. > Another change that was introduced with the new gradle version is that builds > for different architectures are put into their own directory > (build/outputs/apk//) which results in APK files not > being found (mentioned in the upgrade guide under the point "Modifying > variant outputs at build time may not work"). > This can be fixed by adapting the findOutputApksHelper method in > GenericBuilder.js. > An unfortunate side effect of these issues is that projects leveraging > crosswalk do not work anymore. -- 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-13580) cordova-android 6.4.0 broke build if cdvBuildMultipleApks is set to true
[ https://issues.apache.org/jira/browse/CB-13580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16254557#comment-16254557 ] ASF GitHub Bot commented on CB-13580: - infil00p commented on issue #417: CB-13580: (android) fix build for multiple apks (different product flavors) URL: https://github.com/apache/cordova-android/pull/417#issuecomment-344778138 @DavidStrausz Fix the lint errors and I'll merge this in. I tried adding more flavours and it kept crapping the bed on me. I didn't realize that just adding default would get this to work properly again. If you're inclined, you can always send a PR to my Crosswalk repo. It's technically the "official" repo, and if you could get that working, that would win you some serious cred. (And yeah, I'll merge it in, because I can do that, even though I'm not technically supposed to). This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > cordova-android 6.4.0 broke build if cdvBuildMultipleApks is set to true > > > Key: CB-13580 > URL: https://issues.apache.org/jira/browse/CB-13580 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-android >Affects Versions: 6.4.0 >Reporter: David Strauß >Assignee: Joe Bowser > Labels: build > > With the latest cordova-android (6.4.0) builds for different product flavors > (arm, x86) do not work anymore (error e.g.: "No flavor is associated with > flavor dimension ...") because of the changes introduced with gradle 3.0.0. > With the new gradle plugin a flavorDimenson must be specified to build > different product flavors (mentioned > [here|https://developer.android.com/studio/build/gradle-plugin-3-0-0-migration.html?utm_source=android-studio#flavor_dimensions] > in the upgrade guide. This can be fixed by adding `flavorDimensions > "default"` to build.gradle if cdvBuildMultipleApks is set to true. > Another change that was introduced with the new gradle version is that builds > for different architectures are put into their own directory > (build/outputs/apk//) which results in APK files not > being found (mentioned in the upgrade guide under the point "Modifying > variant outputs at build time may not work"). > This can be fixed by adapting the findOutputApksHelper method in > GenericBuilder.js. > An unfortunate side effect of these issues is that projects leveraging > crosswalk do not work anymore. -- 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-13580) cordova-android 6.4.0 broke build if cdvBuildMultipleApks is set to true
[ https://issues.apache.org/jira/browse/CB-13580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16254555#comment-16254555 ] Joe Bowser commented on CB-13580: - THANK YOU!!!1 This is a duplicate but it comes with a PR, so yeah! > cordova-android 6.4.0 broke build if cdvBuildMultipleApks is set to true > > > Key: CB-13580 > URL: https://issues.apache.org/jira/browse/CB-13580 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-android >Affects Versions: 6.4.0 >Reporter: David Strauß >Assignee: Joe Bowser > Labels: build > > With the latest cordova-android (6.4.0) builds for different product flavors > (arm, x86) do not work anymore (error e.g.: "No flavor is associated with > flavor dimension ...") because of the changes introduced with gradle 3.0.0. > With the new gradle plugin a flavorDimenson must be specified to build > different product flavors (mentioned > [here|https://developer.android.com/studio/build/gradle-plugin-3-0-0-migration.html?utm_source=android-studio#flavor_dimensions] > in the upgrade guide. This can be fixed by adding `flavorDimensions > "default"` to build.gradle if cdvBuildMultipleApks is set to true. > Another change that was introduced with the new gradle version is that builds > for different architectures are put into their own directory > (build/outputs/apk//) which results in APK files not > being found (mentioned in the upgrade guide under the point "Modifying > variant outputs at build time may not work"). > This can be fixed by adapting the findOutputApksHelper method in > GenericBuilder.js. > An unfortunate side effect of these issues is that projects leveraging > crosswalk do not work anymore. -- 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-13580) cordova-android 6.4.0 broke build if cdvBuildMultipleApks is set to true
[ https://issues.apache.org/jira/browse/CB-13580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16254555#comment-16254555 ] Joe Bowser edited comment on CB-13580 at 11/16/17 12:43 AM: THANK YOU!!! This is a duplicate but it comes with a PR, so yeah! was (Author: bowserj): THANK YOU!!!1 This is a duplicate but it comes with a PR, so yeah! > cordova-android 6.4.0 broke build if cdvBuildMultipleApks is set to true > > > Key: CB-13580 > URL: https://issues.apache.org/jira/browse/CB-13580 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-android >Affects Versions: 6.4.0 >Reporter: David Strauß >Assignee: Joe Bowser > Labels: build > > With the latest cordova-android (6.4.0) builds for different product flavors > (arm, x86) do not work anymore (error e.g.: "No flavor is associated with > flavor dimension ...") because of the changes introduced with gradle 3.0.0. > With the new gradle plugin a flavorDimenson must be specified to build > different product flavors (mentioned > [here|https://developer.android.com/studio/build/gradle-plugin-3-0-0-migration.html?utm_source=android-studio#flavor_dimensions] > in the upgrade guide. This can be fixed by adding `flavorDimensions > "default"` to build.gradle if cdvBuildMultipleApks is set to true. > Another change that was introduced with the new gradle version is that builds > for different architectures are put into their own directory > (build/outputs/apk//) which results in APK files not > being found (mentioned in the upgrade guide under the point "Modifying > variant outputs at build time may not work"). > This can be fixed by adapting the findOutputApksHelper method in > GenericBuilder.js. > An unfortunate side effect of these issues is that projects leveraging > crosswalk do not work anymore. -- 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-13580) cordova-android 6.4.0 broke build if cdvBuildMultipleApks is set to true
[ https://issues.apache.org/jira/browse/CB-13580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16254542#comment-16254542 ] ASF GitHub Bot commented on CB-13580: - DavidStrausz opened a new pull request #417: CB-13580: (android) fix build for multiple apks (different product flavors) URL: https://github.com/apache/cordova-android/pull/417 ### Platforms affected cordova-android ### What does this PR do? This PR fixes the build if cdvBuildMultipleApks is set to true by defining `flavorDimensions "default"` in `build.gradle` and by adapting the `findOutputApksHelper` method in `GenericBuilder.js` to recursively scan the `build/outputs/apk` directory for matching candidates. ### What testing has been done on this change? I ran the unit tests and the connectedAndroidTest tests and did manual tests of builds with crosswalk (multiple APKs) and builds without crosswalk (single APK). ### 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. - [ ] Added automated test coverage as appropriate for this change. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > cordova-android 6.4.0 broke build if cdvBuildMultipleApks is set to true > > > Key: CB-13580 > URL: https://issues.apache.org/jira/browse/CB-13580 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-android >Affects Versions: 6.4.0 >Reporter: David Strauß >Assignee: Joe Bowser > Labels: build > > With the latest cordova-android (6.4.0) builds for different product flavors > (arm, x86) do not work anymore (error e.g.: "No flavor is associated with > flavor dimension ...") because of the changes introduced with gradle 3.0.0. > With the new gradle plugin a flavorDimenson must be specified to build > different product flavors (mentioned > [here|https://developer.android.com/studio/build/gradle-plugin-3-0-0-migration.html?utm_source=android-studio#flavor_dimensions] > in the upgrade guide. This can be fixed by adding `flavorDimensions > "default"` to build.gradle if cdvBuildMultipleApks is set to true. > Another change that was introduced with the new gradle version is that builds > for different architectures are put into their own directory > (build/outputs/apk//) which results in APK files not > being found (mentioned in the upgrade guide under the point "Modifying > variant outputs at build time may not work"). > This can be fixed by adapting the findOutputApksHelper method in > GenericBuilder.js. > An unfortunate side effect of these issues is that projects leveraging > crosswalk do not work anymore. -- 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] [Created] (CB-13580) cordova-android 6.4.0 broke build if cdvBuildMultipleApks is set to true
David Strauß created CB-13580: - Summary: cordova-android 6.4.0 broke build if cdvBuildMultipleApks is set to true Key: CB-13580 URL: https://issues.apache.org/jira/browse/CB-13580 Project: Apache Cordova Issue Type: Bug Components: cordova-android Affects Versions: 6.4.0 Reporter: David Strauß Assignee: Joe Bowser With the latest cordova-android (6.4.0) builds for different product flavors (arm, x86) do not work anymore (error e.g.: "No flavor is associated with flavor dimension ...") because of the changes introduced with gradle 3.0.0. With the new gradle plugin a flavorDimenson must be specified to build different product flavors (mentioned [here|https://developer.android.com/studio/build/gradle-plugin-3-0-0-migration.html?utm_source=android-studio#flavor_dimensions] in the upgrade guide. This can be fixed by adding `flavorDimensions "default"` to build.gradle if cdvBuildMultipleApks is set to true. Another change that was introduced with the new gradle version is that builds for different architectures are put into their own directory (build/outputs/apk//) which results in APK files not being found (mentioned in the upgrade guide under the point "Modifying variant outputs at build time may not work"). This can be fixed by adapting the findOutputApksHelper method in GenericBuilder.js. An unfortunate side effect of these issues is that projects leveraging crosswalk do not work anymore. -- 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-12863) Can't install plugins from a branch (cordova@7)
[
https://issues.apache.org/jira/browse/CB-12863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16254427#comment-16254427
]
Alexander Regueiro commented on CB-12863:
-
My work-around is also to run a before_prepare hook script that adds the plugin
using --nofetch, if it doesn't already exist.
> Can't install plugins from a branch (cordova@7)
> ---
>
> Key: CB-12863
> URL: https://issues.apache.org/jira/browse/CB-12863
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-fetch
> Environment: cordova-cli@7.0.1
> node@4.6.0
>Reporter: Shazron Abdullah
>Assignee: Shazron Abdullah
> Labels: cordova-8.0.0, reproduced, triage
> Fix For: cordova-labs-wkwebview-engine-localhost@0.5.1
>
>
> 1st try:
> {code}
> $ cordova plugin add
> https://github.com/apache/cordova-plugins.git\#wkwebview-engine-localhost
> Installing "cordova-labs-wkwebview-engine-localhost" for ios
> Failed to install 'cordova-labs-wkwebview-engine-localhost': CordovaError:
> Failed to fetch plugin
> https://git-wip-us.apache.org/repos/asf/cordova-plugins.git#local-webserver
> via registry.
> Probably this is either a connection problem, or plugin spec is incorrect.
> Check your connection and plugin name/version/URL.
> Error: npm: Command failed with exit code 254 Error output:
> npm WARN package.json helloworld@1.0.0 No repository field.
> npm WARN package.json helloworld@1.0.0 No README data
> npm ERR! not a package
> /var/folders/40/pyxnqlcj6bn_43qrjp3p0xtwgp/T/npm-28533-ff14b1ee/git-wip-us.apache.org/repos/asf/cordova-plugins.git/local-webserver
> npm ERR! Darwin 16.7.0
> npm ERR! argv "/Users/shazron/.nvm/versions/node/v4.6.0/bin/node"
> "/Users/shazron/.nvm/versions/node/v4.6.0/bin/npm" "install"
> "https://git-wip-us.apache.org/repos/asf/cordova-plugins.git#local-webserver";
> "--save"
> npm ERR! node v4.6.0
> npm ERR! npm v2.15.9
> npm ERR! path
> /var/folders/40/pyxnqlcj6bn_43qrjp3p0xtwgp/T/npm-28533-ff14b1ee/unpack-968d75f9eab2/package.json
> npm ERR! code ENOENT
> npm ERR! errno -2
> npm ERR! syscall open
> npm ERR! enoent ENOENT: no such file or directory, open
> '/var/folders/40/pyxnqlcj6bn_43qrjp3p0xtwgp/T/npm-28533-ff14b1ee/unpack-968d75f9eab2/package.json'
> npm ERR! enoent This is most likely not a problem with npm itself
> npm ERR! enoent and is related to npm not being able to find a file.
> npm ERR! enoent
> npm ERR! Please include the following file with any support request:
> npm ERR! /Users/shazron/Desktop/gtm/node_modules/npm-debug.log
> at
> /Users/shazron/.nvm/versions/node/v4.6.0/lib/node_modules/cordova/node_modules/cordova-lib/src/plugman/fetch.js:205:33
> at _rejected
> (/Users/shazron/.nvm/versions/node/v4.6.0/lib/node_modules/cordova/node_modules/cordova-lib/node_modules/cordova-fetch/node_modules/q/q.js:864:24)
> at
> /Users/shazron/.nvm/versions/node/v4.6.0/lib/node_modules/cordova/node_modules/cordova-lib/node_modules/cordova-fetch/node_modules/q/q.js:890:30
> at Promise.when
> (/Users/shazron/.nvm/versions/node/v4.6.0/lib/node_modules/cordova/node_modules/cordova-lib/node_modules/cordova-fetch/node_modules/q/q.js:1142:31)
> at Promise.promise.promiseDispatch
> (/Users/shazron/.nvm/versions/node/v4.6.0/lib/node_modules/cordova/node_modules/cordova-lib/node_modules/cordova-fetch/node_modules/q/q.js:808:41)
> at
> /Users/shazron/.nvm/versions/node/v4.6.0/lib/node_modules/cordova/node_modules/cordova-lib/node_modules/cordova-fetch/node_modules/q/q.js:624:44
> at runSingle
> (/Users/shazron/.nvm/versions/node/v4.6.0/lib/node_modules/cordova/node_modules/cordova-lib/node_modules/cordova-fetch/node_modules/q/q.js:137:13)
> at flush
> (/Users/shazron/.nvm/versions/node/v4.6.0/lib/node_modules/cordova/node_modules/cordova-lib/node_modules/cordova-fetch/node_modules/q/q.js:125:13)
> at nextTickCallbackWith0Args (node.js:420:9)
> at process._tickCallback (node.js:349:13)
> Error: Failed to fetch plugin
> https://git-wip-us.apache.org/repos/asf/cordova-plugins.git#local-webserver
> via registry.
> Probably this is either a connection problem, or plugin spec is incorrect.
> Check your connection and plugin name/version/URL.
> Error: npm: Command failed with exit code 254 Error output:
> npm WARN package.json helloworld@1.0.0 No repository field.
> npm WARN package.json helloworld@1.0.0 No README data
> npm ERR! not a package
> /var/folders/40/pyxnqlcj6bn_43qrjp3p0xtwgp/T/npm-28533-ff14b1ee/git-wip-us.apache.org/repos/asf/cordova-plugins.git/local-webserver
> npm ERR! Darwin 16.7.0
> npm ERR! argv "/Users/shazron/.nvm/versions/node/v4.6.0/bin/node"
> "/Users/shazron/.nvm/versions/node/v4.6.0/bin/npm" "install"
> "https://git-wip-us.apache.org/repos/asf/cordova-plugins.git#local-w
[jira] [Commented] (CB-13555) (ios) Present notification view controller by inappbrowser view controller
[
https://issues.apache.org/jira/browse/CB-13555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16254330#comment-16254330
]
ASF GitHub Bot commented on CB-13555:
-
jcesarmobile commented on issue #98: CB-13555 (ios) Present notification view
controller by inappbrowser view controller
URL:
https://github.com/apache/cordova-plugin-dialogs/pull/98#issuecomment-344748040
Merged, thanks for the PR!
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> (ios) Present notification view controller by inappbrowser view controller
> --
>
> Key: CB-13555
> URL: https://issues.apache.org/jira/browse/CB-13555
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-plugin-dialogs
>Affects Versions: cordova-ios 4.5.0
> Environment: IOS 10 and 11
>Reporter: Jonathan Li
> Labels: dialog, inappbrowser
>
> When inappbrowser window is shown, if main uiwebview or wkwebview calls
> cordova Dialog plugin method to show the dialog view, the dialog should show
> to user on top of the inappbrowser view controller.
> However, currently the dialog view is shown behind the inappbrowser view, so
> user cannot see it or click button on the dialog
> An similar issue was reported for barcode scanner plugin at
> https://github.com/phonegap/phonegap-plugin-barcodescanner/issues/570
> The issue can be repeated with the below method
> function confirm(){
> var win = window.open( "https://www.google.com";, "_blank" );
> win.addEventListener( "loadstop", function() {
> setTimeout(function() {
> function onConfirm(buttonIndex) {
> console.log('You selected button ' + buttonIndex);
> }
>
> navigator.notification.confirm(
> 'You are the winner!', // message
> onConfirm,// callback to invoke with index of button
> pressed
> 'Game Over', // title
> ['Restart','Exit'] // buttonLabels
> );
> }, 1000 );
> });
> }
--
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-13505) Update LaunchScreen story board constrains
[ https://issues.apache.org/jira/browse/CB-13505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16254327#comment-16254327 ] ASF subversion and git services commented on CB-13505: -- Commit 9ddcd885be159f253f40b1bebc55652f8c68244f in cordova-ios's branch refs/heads/4.5.x from [~mhartington] [ https://gitbox.apache.org/repos/asf?p=cordova-ios.git;h=9ddcd88 ] CB-13505: adjust storyboard constraints > Update LaunchScreen story board constrains > -- > > Key: CB-13505 > URL: https://issues.apache.org/jira/browse/CB-13505 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-ios >Reporter: Mike Hartington >Assignee: Suraj Pindoria > Attachments: jump.gif > > > LaunchScreen storyboard constraints were never updated for ios11/iphoneX. > This can cause the splashscreen to jump during startup. Sending a patch for > this. -- 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-13579) Cordova-iOS Platform Release November 15, 2017
[ https://issues.apache.org/jira/browse/CB-13579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16254326#comment-16254326 ] ASF subversion and git services commented on CB-13579: -- Commit 6eaf06e7eb51736e502855d31c4c1cb31ae6c6b3 in cordova-ios's branch refs/heads/master from [~surajpindoria] [ https://gitbox.apache.org/repos/asf?p=cordova-ios.git;h=6eaf06e ] CB-13579 Updated checked in node_modules > Cordova-iOS Platform Release November 15, 2017 > -- > > Key: CB-13579 > URL: https://issues.apache.org/jira/browse/CB-13579 > Project: Apache Cordova > Issue Type: Task >Reporter: Suraj Pindoria >Assignee: Suraj Pindoria > > Following steps at > https://github.com/apache/cordova-coho/blob/master/docs/platforms-release-process.md -- 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-13505) Update LaunchScreen story board constrains
[ https://issues.apache.org/jira/browse/CB-13505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16254328#comment-16254328 ] ASF subversion and git services commented on CB-13505: -- Commit 1661d9f42c24d86ec6a0181f4783150a88659215 in cordova-ios's branch refs/heads/4.5.x from [~mhartington] [ https://gitbox.apache.org/repos/asf?p=cordova-ios.git;h=1661d9f ] CB-13505: (ios) adjust storyboard constraints > Update LaunchScreen story board constrains > -- > > Key: CB-13505 > URL: https://issues.apache.org/jira/browse/CB-13505 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-ios >Reporter: Mike Hartington >Assignee: Suraj Pindoria > Attachments: jump.gif > > > LaunchScreen storyboard constraints were never updated for ios11/iphoneX. > This can cause the splashscreen to jump during startup. Sending a patch for > this. -- 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-13523) Add build config option to enable Xcode automatic provisioning
[ https://issues.apache.org/jira/browse/CB-13523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16254329#comment-16254329 ] ASF subversion and git services commented on CB-13523: -- Commit 0e5e38c6bf144d99c85d5ad0cfb9180ff7ffca5b in cordova-ios's branch refs/heads/4.5.x from [~dpogue] [ https://gitbox.apache.org/repos/asf?p=cordova-ios.git;h=0e5e38c ] CB-13523: Add flag for Xcode-managed provisioning This adds a `automaticProvisioning` option to the build config which passes flags to xcodebuild during the exporting step that allow it to automatically create and update provisioning profiles for automatic code signing. > Add build config option to enable Xcode automatic provisioning > -- > > Key: CB-13523 > URL: https://issues.apache.org/jira/browse/CB-13523 > Project: Apache Cordova > Issue Type: Improvement > Components: cordova-ios > Environment: Xcode 9 > Cordova-iOS 4.5.3 >Reporter: Darryl Pogue >Assignee: Darryl Pogue > > Xcode 9 made more changes to how provisioning works for apps, particularly > around manual vs automatic signing. > The changes required to support manual signing of release builds was > implemented as part of CB-13315. > In order for automatic signing to work, we need to pass an additional flag to > xcodebuild to allow Xcode to manage automatically updating provisioning > profiles as needed. I want to keep this being a build config option because > many people may not want to grant Xcode such power by default. -- 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-13555) (ios) Present notification view controller by inappbrowser view controller
[
https://issues.apache.org/jira/browse/CB-13555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jcesarmobile resolved CB-13555.
---
Resolution: Fixed
Fix Version/s: (was: Master)
Fixed in 1.3.5-dev
> (ios) Present notification view controller by inappbrowser view controller
> --
>
> Key: CB-13555
> URL: https://issues.apache.org/jira/browse/CB-13555
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-plugin-dialogs
>Affects Versions: cordova-ios 4.5.0
> Environment: IOS 10 and 11
>Reporter: Jonathan Li
> Labels: dialog, inappbrowser
>
> When inappbrowser window is shown, if main uiwebview or wkwebview calls
> cordova Dialog plugin method to show the dialog view, the dialog should show
> to user on top of the inappbrowser view controller.
> However, currently the dialog view is shown behind the inappbrowser view, so
> user cannot see it or click button on the dialog
> An similar issue was reported for barcode scanner plugin at
> https://github.com/phonegap/phonegap-plugin-barcodescanner/issues/570
> The issue can be repeated with the below method
> function confirm(){
> var win = window.open( "https://www.google.com";, "_blank" );
> win.addEventListener( "loadstop", function() {
> setTimeout(function() {
> function onConfirm(buttonIndex) {
> console.log('You selected button ' + buttonIndex);
> }
>
> navigator.notification.confirm(
> 'You are the winner!', // message
> onConfirm,// callback to invoke with index of button
> pressed
> 'Game Over', // title
> ['Restart','Exit'] // buttonLabels
> );
> }, 1000 );
> });
> }
--
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-13555) (ios) Present notification view controller by inappbrowser view controller
[
https://issues.apache.org/jira/browse/CB-13555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16254319#comment-16254319
]
ASF GitHub Bot commented on CB-13555:
-
jcesarmobile closed pull request #98: CB-13555 (ios) Present notification view
controller by inappbrowser view controller
URL: https://github.com/apache/cordova-plugin-dialogs/pull/98
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git a/src/ios/CDVNotification.m b/src/ios/CDVNotification.m
index 0dd3d2c..89f3d5d 100644
--- a/src/ios/CDVNotification.m
+++ b/src/ios/CDVNotification.m
@@ -228,8 +228,11 @@ - (void)beep:(CDVInvokedUrlCommand*)command
-(UIViewController *)getTopPresentedViewController {
UIViewController *presentingViewController = self.viewController;
-while(presentingViewController.presentedViewController != nil &&
![presentingViewController.presentedViewController isBeingDismissed])
-{
+if (presentingViewController.view.window != [UIApplication
sharedApplication].keyWindow){
+presentingViewController = [UIApplication
sharedApplication].keyWindow.rootViewController;
+}
+
+while (presentingViewController.presentedViewController != nil &&
![presentingViewController.presentedViewController isBeingDismissed]){
presentingViewController =
presentingViewController.presentedViewController;
}
return presentingViewController;
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> (ios) Present notification view controller by inappbrowser view controller
> --
>
> Key: CB-13555
> URL: https://issues.apache.org/jira/browse/CB-13555
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-plugin-dialogs
>Affects Versions: cordova-ios 4.5.0
> Environment: IOS 10 and 11
>Reporter: Jonathan Li
> Labels: dialog, inappbrowser
> Fix For: Master
>
>
> When inappbrowser window is shown, if main uiwebview or wkwebview calls
> cordova Dialog plugin method to show the dialog view, the dialog should show
> to user on top of the inappbrowser view controller.
> However, currently the dialog view is shown behind the inappbrowser view, so
> user cannot see it or click button on the dialog
> An similar issue was reported for barcode scanner plugin at
> https://github.com/phonegap/phonegap-plugin-barcodescanner/issues/570
> The issue can be repeated with the below method
> function confirm(){
> var win = window.open( "https://www.google.com";, "_blank" );
> win.addEventListener( "loadstop", function() {
> setTimeout(function() {
> function onConfirm(buttonIndex) {
> console.log('You selected button ' + buttonIndex);
> }
>
> navigator.notification.confirm(
> 'You are the winner!', // message
> onConfirm,// callback to invoke with index of button
> pressed
> 'Game Over', // title
> ['Restart','Exit'] // buttonLabels
> );
> }, 1000 );
> });
> }
--
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-13555) (ios) Present notification view controller by inappbrowser view controller
[
https://issues.apache.org/jira/browse/CB-13555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16254320#comment-16254320
]
ASF subversion and git services commented on CB-13555:
--
Commit 5a03f7fb469912de10070eae144862efef825b02 in cordova-plugin-dialogs's
branch refs/heads/master from [~jonathanli]
[ https://gitbox.apache.org/repos/asf?p=cordova-plugin-dialogs.git;h=5a03f7f ]
CB-13555 (ios) Present notification view controller by inappbrowser view
controller (#98)
* (IOS) notification window does not show when inappbrowser window is presented
> (ios) Present notification view controller by inappbrowser view controller
> --
>
> Key: CB-13555
> URL: https://issues.apache.org/jira/browse/CB-13555
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-plugin-dialogs
>Affects Versions: cordova-ios 4.5.0
> Environment: IOS 10 and 11
>Reporter: Jonathan Li
> Labels: dialog, inappbrowser
> Fix For: Master
>
>
> When inappbrowser window is shown, if main uiwebview or wkwebview calls
> cordova Dialog plugin method to show the dialog view, the dialog should show
> to user on top of the inappbrowser view controller.
> However, currently the dialog view is shown behind the inappbrowser view, so
> user cannot see it or click button on the dialog
> An similar issue was reported for barcode scanner plugin at
> https://github.com/phonegap/phonegap-plugin-barcodescanner/issues/570
> The issue can be repeated with the below method
> function confirm(){
> var win = window.open( "https://www.google.com";, "_blank" );
> win.addEventListener( "loadstop", function() {
> setTimeout(function() {
> function onConfirm(buttonIndex) {
> console.log('You selected button ' + buttonIndex);
> }
>
> navigator.notification.confirm(
> 'You are the winner!', // message
> onConfirm,// callback to invoke with index of button
> pressed
> 'Game Over', // title
> ['Restart','Exit'] // buttonLabels
> );
> }, 1000 );
> });
> }
--
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-13541) Error: Path must be a string. Received undefined
[
https://issues.apache.org/jira/browse/CB-13541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16254310#comment-16254310
]
Joe Bowser commented on CB-13541:
-
I don't see anything out of the ordinary. However, 3D Touch isn't an official
Cordova Plugin, so I would try removing that plugin and seeing if you can build
the project without it first.
> Error: Path must be a string. Received undefined
>
>
> Key: CB-13541
> URL: https://issues.apache.org/jira/browse/CB-13541
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-android
> Environment: Kubuntu 17.04 64 bit, Gradle 3.2, Cordova Android 6.3.0,
> Cordova cli-6.3.0, Android Studio 3.0.0
>Reporter: Teguh Teknisi
>Assignee: Joe Bowser
>Priority: Trivial
> Labels: newbie
>
> When i try to cordiva build android, it will fail, with error:
> Error: Path must be a string. Received undefined
> I have to delete platforms/android/android.json
> to make the cordova android build to success.
> Here the error log:
> {code:java}
> sukanime@Asus-X201EV:~/AndroidStudioProjects/SaklarWiFi$ cordova build android
> Error: Path must be a string. Received undefined
> sukanime@Asus-X201EV:~/AndroidStudioProjects/SaklarWiFi$ rm
> platforms/android/android.json
> sukanime@Asus-X201EV:~/AndroidStudioProjects/SaklarWiFi$ cordova build android
> ANDROID_HOME=/home/sukanime/Android/Sdk
> JAVA_HOME=/usr/lib/jvm/java-8-oracle
> Subproject Path: CordovaLib
> The Task.leftShift(Closure) method has been deprecated and is scheduled to be
> removed in Gradle 5.0. Please use Task.doLast(Action) instead.
> at
> build_asz7izgfnstnapj05rr74ilff.run(/home/sukanime/AndroidStudioProjects/SaklarWiFi/platforms/android/build.gradle:141)
> The JavaCompile.setDependencyCacheDir() method has been deprecated and is
> scheduled to be removed in Gradle 4.0.
> Incremental java compilation is an incubating feature.
> The TaskInputs.source(Object) method has been deprecated and is scheduled to
> be removed in Gradle 4.0. Please use TaskInputs.file(Object).skipWhenEmpty()
> instead.
> :clean
> :CordovaLib:clean
> BUILD SUCCESSFUL
> Total time: 3.13 secs
> Subproject Path: CordovaLib
> Subproject Path: CordovaLib
> Running command:
> /home/sukanime/AndroidStudioProjects/SaklarWiFi/hooks/after_prepare/030_resource_files.js
> /home/sukanime/AndroidStudioProjects/SaklarWiFi
> ANDROID_HOME=/home/sukanime/Android/Sdk
> JAVA_HOME=/usr/lib/jvm/java-8-oracle
> Subproject Path: CordovaLib
> The Task.leftShift(Closure) method has been deprecated and is scheduled to be
> removed in Gradle 5.0. Please use Task.doLast(Action) instead.
> at
> build_asz7izgfnstnapj05rr74ilff.run(/home/sukanime/AndroidStudioProjects/SaklarWiFi/platforms/android/build.gradle:141)
> The JavaCompile.setDependencyCacheDir() method has been deprecated and is
> scheduled to be removed in Gradle 4.0.
> Incremental java compilation is an incubating feature.
> The TaskInputs.source(Object) method has been deprecated and is scheduled to
> be removed in Gradle 4.0. Please use TaskInputs.file(Object).skipWhenEmpty()
> instead.
> :preBuild UP-TO-DATE
> :preDebugBuild UP-TO-DATE
> :checkDebugManifest
> :preReleaseBuild UP-TO-DATE
> :CordovaLib:preBuild UP-TO-DATE
> :CordovaLib:preDebugBuild UP-TO-DATE
> :CordovaLib:checkDebugManifest
> :CordovaLib:prepareDebugDependencies
> :CordovaLib:compileDebugAidl
> :CordovaLib:compileDebugNdk UP-TO-DATE
> :CordovaLib:compileLint
> :CordovaLib:copyDebugLint UP-TO-DATE
> :CordovaLib:mergeDebugShaders
> :CordovaLib:compileDebugShaders
> :CordovaLib:generateDebugAssets
> :CordovaLib:mergeDebugAssets
> :CordovaLib:mergeDebugProguardFiles UP-TO-DATE
> :CordovaLib:packageDebugRenderscript UP-TO-DATE
> :CordovaLib:compileDebugRenderscript
> :CordovaLib:generateDebugResValues
> :CordovaLib:generateDebugResources
> :CordovaLib:packageDebugResources
> :CordovaLib:processDebugManifest
> :CordovaLib:generateDebugBuildConfig
> :CordovaLib:processDebugResources
> :CordovaLib:generateDebugSources
> :CordovaLib:incrementalDebugJavaCompilationSafeguard
> :CordovaLib:compileDebugJavaWithJavac
> :CordovaLib:compileDebugJavaWithJavac - is not incremental (e.g. outputs have
> changed, no previous execution, etc.).
> Note: Some input files use or override a deprecated API.
> Note: Recompile with -Xlint:deprecation for details.
> :CordovaLib:processDebugJavaRes UP-TO-DATE
> :CordovaLib:transformResourcesWithMergeJavaResForDebug
> :CordovaLib:transformClassesAndResourcesWithSyncLibJarsForDebug
> :CordovaLib:mergeDebugJniLibFolders
> :CordovaLib:transformNative_libsWithMergeJniLibsForDebug
> :CordovaLib:transformNative_libsWithSyncJniLibsForDebug
> :CordovaLib:bundleDebug
> :CordovaLib:preReleaseBuild UP-TO-DATE
> :CordovaLib:checkReleaseManifest
>
[jira] [Commented] (CB-13564) Multiple edit-config items for Info.plist causing error
[
https://issues.apache.org/jira/browse/CB-13564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16254226#comment-16254226
]
Jacob Weber commented on CB-13564:
--
Having the same issue with cordova-cli 7.1.0 and cordova-plugin-camera 3.0.0,
when I add two edit-config entries for NSCameraUsageDescription and
NSPhotoLibraryUsageDescription.
> Multiple edit-config items for Info.plist causing error
> ---
>
> Key: CB-13564
> URL: https://issues.apache.org/jira/browse/CB-13564
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-cli
>Reporter: Tom Bell
>
> I am on 7.1.0 of `cordova-cli`, there was no `7.1.0` in the "Affects
> Versions" dropdown.
> I've updated `cordova-ios` to 4.5.3 and `cordova-plugin-contacts` to 3..0.0,
> I've got the following
> working:
> {code:xml}
> target="NSContactsUsageDescription">
> We require permission to access your contacts so you can import
> contacts into [redacted]
>
> {code}
> However when I decided to move some stuff from an `after_prepare` hook
> script, to use edit-config, it fails with an error `doc.find is not a
> function`
> {code:xml}
> target="NSContactsUsageDescription">
> We require permission to access your contacts so you can import
> contacts into [redacted]
>
>
> UIStatusBarStyleLightContent
>
> {code}
> If I take out the additional `` everything works.
--
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-13323) Cordova-Android Platform Release September 24, 2017
[ https://issues.apache.org/jira/browse/CB-13323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16254110#comment-16254110 ] ASF GitHub Bot commented on CB-13323: - janpio closed pull request #739: CB-13323: Cordova-Android 6.3.0 Release Announcement URL: https://github.com/apache/cordova-docs/pull/739 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As this is a foreign pull request (from a fork), the diff is supplied below (as it won't show otherwise due to GitHub magic): diff --git a/www/_posts/2017-09-27-android-release.md b/www/_posts/2017-09-27-android-release.md new file mode 100644 index 0..abe7d980b --- /dev/null +++ b/www/_posts/2017-09-27-android-release.md @@ -0,0 +1,42 @@ +--- +layout: post +author: +name: Joe Bowser +url: https://twitter.com/infil00p +title: "Cordova Android 6.3.0 Released!" +categories: announcements +tags: news releases +--- + +We are happy to announce that `Cordova Android 6.3.0` has been released! + +This release now targets the latest Android API level of API 26 and has fixed issues related to the **Android SDK Tools 26.0.2** release. **Google** changed how the Android emulator was executed, causing errors when deploying to the emulator. + +This release contains the integration of `cordova-plugin-compat`, so please remove that plugin from projects once you update to this version of `cordova-android`. + +To upgrade: + +npm install -g cordova +cd my_project +cordova platform update android@6.3.0 + +To add it explicitly: + +cordova platform add android@6.3.0 + + +## What's new in Android +* [CB-6936](https://issues.apache.org/jira/browse/CB-6936) fix crash when calling methods on a destroyed webview +* [CB-12981](https://issues.apache.org/jira/browse/CB-12981) handle SDK 26.0.2 slightly different AVD list output for **Android** 8+ AVDs. Would cause "cannot read property replace of undefined" errors when trying to deploy an **Android** 8 emulator. +* Updated maven repo to include most recent lib versions +* [CB-13177](https://issues.apache.org/jira/browse/CB-13177) Updating to API Level 26 +* Revert [CB-12015](https://issues.apache.org/jira/browse/CB-12015) initial-scale values less than 1.0 are ignored on **Android** +* [CB-12730](https://issues.apache.org/jira/browse/CB-12730) The Cordova Compatibility Plugin is now integrated into `cordova-android` +* [CB-12453](https://issues.apache.org/jira/browse/CB-12453) Remove unnecessary double quotes from .bat files which are the causes of crash if project path contains spaces +* [CB-13031](https://issues.apache.org/jira/browse/CB-13031) Fix bug with case-sensitivity of **Android**-packageName +* [CB-10916](https://issues.apache.org/jira/browse/CB-10916) Support display name for **Android** +* [CB-12423](https://issues.apache.org/jira/browse/CB-12423) make explicit JDK 1.8 or greater is needed in the `README`, we require 1.8 for compilation, but do not have 1.8 Java features yet +* [CB-12605](https://issues.apache.org/jira/browse/CB-12605) In **Windows** get **Android** studio path from the registry +* [CB-12617](https://issues.apache.org/jira/browse/CB-12617) : removed node0.x support for platforms and added engineStrict + +# This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Cordova-Android Platform Release September 24, 2017 > --- > > Key: CB-13323 > URL: https://issues.apache.org/jira/browse/CB-13323 > Project: Apache Cordova > Issue Type: Task > Components: cordova-android >Reporter: Joe Bowser >Assignee: Joe Bowser > > Following steps at > https://github.com/apache/cordova-coho/blob/master/docs/platforms-release-process.md -- 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-13577) bug with ionic cordova emulate android
[
https://issues.apache.org/jira/browse/CB-13577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16254079#comment-16254079
]
Jan Piotrowski (Sujan) edited comment on CB-13577 at 11/15/17 8:16 PM:
---
Nothing to accept downstream - Ionic installs Cordova CLI and everything else
directly via npm, so no "downstream". The user just has to update to current
versions.
[~godefroid] best post this at https://forum.ionicframework.com/ where we can
debug this step by step. Start by posting the same stuff you did here and add
your `ionic info` output so we have some versions.
was (Author: sujan12):
Nothing to accept downstream - Ionic installs Cordova CLI and everything else
directly from Cordova, so no "downstream". The user just has to update to
current versions.
[~godefroid] best post this at https://forum.ionicframework.com/ where we can
debug this step by step. Start by posting the same stuff you did here and add
your `ionic info` output so we have some versions.
> bug with ionic cordova emulate android
> --
>
> Key: CB-13577
> URL: https://issues.apache.org/jira/browse/CB-13577
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-android
>Affects Versions: cordova@7.0.0
> Environment: ionic info :
> cli packages: (/usr/local/lib/node_modules)
> @ionic/cli-utils : 1.18.0
> ionic (Ionic CLI) : 3.18.0
> global packages:
> cordova (Cordova CLI) : 7.1.0
> local packages:
> @ionic/app-scripts : 3.1.2
> Cordova Platforms : android 6.3.0 ios 4.5.3
> Ionic Framework: ionic-angular 3.9.2
> System:
> ios-deploy : 1.9.2
> ios-sim: 6.1.2
> Node : v8.9.1
> npm: 5.5.1
> OS : macOS High Sierra
> Xcode : Xcode 9.1 Build version 9B55
> Environment Variables:
> ANDROID_HOME : not set
> Misc:
> backend : pro
>Reporter: gilles Godefroid
>Assignee: Joe Bowser
>
> ionic cordova emulate android --list
> > cordova run android --list --emulator
> Available android virtual devices:
> Nexus_5_API_26
> Nexus_6_API_23
> ionic cordova emulate android --verbose
> [DEBUG] Reason for not using local CLI: LOCAL_CLI_NOT_FOUND
> [DEBUG] CLI flags: { interactive: true, confirm: false }
> [DEBUG] { cwd: '/Users/gillesgodefroid/Documents/Ionic2Weather', local:
> false,
> binPath: '/usr/local/lib/node_modules/ionic/bin/ionic', libPath:
> '/usr/local/lib/node_modules/ionic/dist/index.js' }
> [DEBUG] Daemon found (pid: 2011)
> Running app-scripts build: --platform android --target cordova
> [16:48:26] build dev started ...
> [16:48:26] clean started ...
> [16:48:26] clean finished in 122 ms
> [16:48:26] copy started ...
> [16:48:27] deeplinks started ...
> [16:48:27] deeplinks finished in 27 ms
> [16:48:27] transpile started ...
> [16:48:42] transpile finished in 14.95 s
> [16:48:42] preprocess started ...
> [16:48:42] preprocess finished in 4 ms
> [16:48:42] webpack started ...
> [16:48:44] copy finished in 17.39 s
> [16:48:52] webpack finished in 10.10 s
> [16:48:52] sass started ...
> [16:48:59] sass finished in 7.02 s
> [16:48:59] postprocess started ...
> [16:48:59] postprocess finished in 11 ms
> [16:48:59] lint started ...
> [16:48:59] build dev finished in 33.20 s
> > cordova emulate android
> [16:49:02] lint finished in 2.72 s
> ANDROID_HOME=/Users/gillesgodefroid/Library/Android/sdk
> JAVA_HOME=/Library/Java/JavaVirtualMachines/jdk1.8.0_91.jdk/Contents/Home
> Error: spawn EACCES
> [ERROR] An error occurred while running cordova emulate android (exit code 1).
>
> [DEBUG] registerShutdownFunction process.exit/normal shutdown
--
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-13543) Automate build/deploy for cordova-docs
[ https://issues.apache.org/jira/browse/CB-13543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16254087#comment-16254087 ] ASF GitHub Bot commented on CB-13543: - janpio commented on a change in pull request #760: CB-13543 : updated instructions/documentation around travis build/dep… URL: https://github.com/apache/cordova-docs/pull/760#discussion_r151238364 ## File path: doc/building-and-deploying-the-website.md ## @@ -0,0 +1,20 @@ +## Building and Deploying (Automated) + +### Testing + +After you are finished developing and making your changes, make sure to test them. Run: + + npm test + +`npm test` runs both [eslint] and [mocha] tests. If your tests pass, commit and push your work to Github. + +### Travis + +[Travis] automatically builds and publishes the website on every change. In [travis.yml](../.travis.yml), Travis installs required dependencies and runs the build script. Travis will build the full website for you by running `gulp build --prod` under the hood. Travis also uses [SVN] to update, copy, add, and commit the new changes over to the website. Committing to svn can only occur once the commit has been merged to master. You can read more about is happening under the hood with SVN [here](deploying-the-website.md). Travis also runs `npm test` and will notify you if any of your `eslint` or `mocha` tests are failing. When Travis is done building and deploying, send a pull request and ask for a review. Review comment: @stevengill What about forks in the apache repo? I did create one of those by accident instead of forking on my user for #761 - there probably has to be a real check for `master`? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Automate build/deploy for cordova-docs > -- > > Key: CB-13543 > URL: https://issues.apache.org/jira/browse/CB-13543 > Project: Apache Cordova > Issue Type: Improvement > Components: cordova-docs >Reporter: Audrey So >Assignee: Audrey So > Labels: enhancement, feature, in-progress, optimization > > Automate build/deploy for cordova-docs > Cordova-docs should be built and published automatically on every change > Replace jsihnt with eslint > Update README.md & update instructions in docs to reflect changes > https://issues.apache.org/jira/browse/CB-13162 -- 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-13577) bug with ionic cordova emulate android
[
https://issues.apache.org/jira/browse/CB-13577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16254079#comment-16254079
]
Jan Piotrowski (Sujan) commented on CB-13577:
-
Nothing to accept downstream - Ionic installs Cordova CLI and everything else
directly from Cordova, so no "downstream". The user just has to update to
current versions.
[~godefroid] best post this at https://forum.ionicframework.com/ where we can
debug this step by step. Start by posting the same stuff you did here and add
your `ionic info` output so we have some versions.
> bug with ionic cordova emulate android
> --
>
> Key: CB-13577
> URL: https://issues.apache.org/jira/browse/CB-13577
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-android
>Affects Versions: cordova@7.0.0
> Environment: ionic info :
> cli packages: (/usr/local/lib/node_modules)
> @ionic/cli-utils : 1.18.0
> ionic (Ionic CLI) : 3.18.0
> global packages:
> cordova (Cordova CLI) : 7.1.0
> local packages:
> @ionic/app-scripts : 3.1.2
> Cordova Platforms : android 6.3.0 ios 4.5.3
> Ionic Framework: ionic-angular 3.9.2
> System:
> ios-deploy : 1.9.2
> ios-sim: 6.1.2
> Node : v8.9.1
> npm: 5.5.1
> OS : macOS High Sierra
> Xcode : Xcode 9.1 Build version 9B55
> Environment Variables:
> ANDROID_HOME : not set
> Misc:
> backend : pro
>Reporter: gilles Godefroid
>Assignee: Joe Bowser
>
> ionic cordova emulate android --list
> > cordova run android --list --emulator
> Available android virtual devices:
> Nexus_5_API_26
> Nexus_6_API_23
> ionic cordova emulate android --verbose
> [DEBUG] Reason for not using local CLI: LOCAL_CLI_NOT_FOUND
> [DEBUG] CLI flags: { interactive: true, confirm: false }
> [DEBUG] { cwd: '/Users/gillesgodefroid/Documents/Ionic2Weather', local:
> false,
> binPath: '/usr/local/lib/node_modules/ionic/bin/ionic', libPath:
> '/usr/local/lib/node_modules/ionic/dist/index.js' }
> [DEBUG] Daemon found (pid: 2011)
> Running app-scripts build: --platform android --target cordova
> [16:48:26] build dev started ...
> [16:48:26] clean started ...
> [16:48:26] clean finished in 122 ms
> [16:48:26] copy started ...
> [16:48:27] deeplinks started ...
> [16:48:27] deeplinks finished in 27 ms
> [16:48:27] transpile started ...
> [16:48:42] transpile finished in 14.95 s
> [16:48:42] preprocess started ...
> [16:48:42] preprocess finished in 4 ms
> [16:48:42] webpack started ...
> [16:48:44] copy finished in 17.39 s
> [16:48:52] webpack finished in 10.10 s
> [16:48:52] sass started ...
> [16:48:59] sass finished in 7.02 s
> [16:48:59] postprocess started ...
> [16:48:59] postprocess finished in 11 ms
> [16:48:59] lint started ...
> [16:48:59] build dev finished in 33.20 s
> > cordova emulate android
> [16:49:02] lint finished in 2.72 s
> ANDROID_HOME=/Users/gillesgodefroid/Library/Android/sdk
> JAVA_HOME=/Library/Java/JavaVirtualMachines/jdk1.8.0_91.jdk/Contents/Home
> Error: spawn EACCES
> [ERROR] An error occurred while running cordova emulate android (exit code 1).
>
> [DEBUG] registerShutdownFunction process.exit/normal shutdown
--
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-11244) Update Android Project Structure to be more compatible with Android Studio
[ https://issues.apache.org/jira/browse/CB-11244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16254075#comment-16254075 ] ASF GitHub Bot commented on CB-11244: - codecov-io commented on issue #389: CB-11244: Studio Project Compatibility: Now with merge commit URL: https://github.com/apache/cordova-android/pull/389#issuecomment-316205218 # [Codecov](https://codecov.io/gh/apache/cordova-android/pull/389?src=pr&el=h1) Report > Merging [#389](https://codecov.io/gh/apache/cordova-android/pull/389?src=pr&el=desc) into [master](https://codecov.io/gh/apache/cordova-android/commit/83601dca2fa468a76bcb2c687b5baebfcb69588b?src=pr&el=desc) will **decrease** coverage by `0.3%`. > The diff coverage is `38.46%`. [](https://codecov.io/gh/apache/cordova-android/pull/389?src=pr&el=tree) ```diff @@Coverage Diff @@ ## master #389 +/- ## == - Coverage 44.01% 43.71% -0.31% == Files 17 17 Lines1679 1718 +39 Branches 304 314 +10 == + Hits 739 751 +12 - Misses940 967 +27 ``` | [Impacted Files](https://codecov.io/gh/apache/cordova-android/pull/389?src=pr&el=tree) | Coverage Δ | | |---|---|---| | [...n/templates/cordova/lib/builders/GenericBuilder.js](https://codecov.io/gh/apache/cordova-android/pull/389?src=pr&el=tree#diff-YmluL3RlbXBsYXRlcy9jb3Jkb3ZhL2xpYi9idWlsZGVycy9HZW5lcmljQnVpbGRlci5qcw==) | `30.61% <ø> (-0.38%)` | :arrow_down: | | [bin/templates/cordova/lib/builders/builders.js](https://codecov.io/gh/apache/cordova-android/pull/389?src=pr&el=tree#diff-YmluL3RlbXBsYXRlcy9jb3Jkb3ZhL2xpYi9idWlsZGVycy9idWlsZGVycy5qcw==) | `37.5% <ø> (ø)` | :arrow_up: | | [bin/templates/cordova/lib/device.js](https://codecov.io/gh/apache/cordova-android/pull/389?src=pr&el=tree#diff-YmluL3RlbXBsYXRlcy9jb3Jkb3ZhL2xpYi9kZXZpY2UuanM=) | `22.44% <0%> (ø)` | :arrow_up: | | [bin/templates/cordova/lib/build.js](https://codecov.io/gh/apache/cordova-android/pull/389?src=pr&el=tree#diff-YmluL3RlbXBsYXRlcy9jb3Jkb3ZhL2xpYi9idWlsZC5qcw==) | `13.04% <0%> (-0.39%)` | :arrow_down: | | [bin/templates/cordova/lib/AndroidStudio.js](https://codecov.io/gh/apache/cordova-android/pull/389?src=pr&el=tree#diff-YmluL3RlbXBsYXRlcy9jb3Jkb3ZhL2xpYi9BbmRyb2lkU3R1ZGlvLmpz) | `94.73% <100%> (ø)` | :arrow_up: | | [bin/templates/cordova/lib/pluginHandlers.js](https://codecov.io/gh/apache/cordova-android/pull/389?src=pr&el=tree#diff-YmluL3RlbXBsYXRlcy9jb3Jkb3ZhL2xpYi9wbHVnaW5IYW5kbGVycy5qcw==) | `87.34% <100%> (+0.47%)` | :arrow_up: | | [...in/templates/cordova/lib/builders/GradleBuilder.js](https://codecov.io/gh/apache/cordova-android/pull/389?src=pr&el=tree#diff-YmluL3RlbXBsYXRlcy9jb3Jkb3ZhL2xpYi9idWlsZGVycy9HcmFkbGVCdWlsZGVyLmpz) | `20.25% <15.78%> (-0.47%)` | :arrow_down: | | [bin/templates/cordova/Api.js](https://codecov.io/gh/apache/cordova-android/pull/389?src=pr&el=tree#diff-YmluL3RlbXBsYXRlcy9jb3Jkb3ZhL0FwaS5qcw==) | `41.88% <16.66%> (-2.57%)` | :arrow_down: | | [bin/lib/create.js](https://codecov.io/gh/apache/cordova-android/pull/389?src=pr&el=tree#diff-YmluL2xpYi9jcmVhdGUuanM=) | `49.26% <45.45%> (-1.57%)` | :arrow_down: | -- [Continue to review full report at Codecov](https://codecov.io/gh/apache/cordova-android/pull/389?src=pr&el=continue). > **Legend** - [Click here to learn more](https://docs.codecov.io/docs/codecov-delta) > `Δ = absolute (impact)`, `ø = not affected`, `? = missing data` > Powered by [Codecov](https://codecov.io/gh/apache/cordova-android/pull/389?src=pr&el=footer). Last update [83601dc...3acba59](https://codecov.io/gh/apache/cordova-android/pull/389?src=pr&el=lastupdated). Read the [comment docs](https://docs.codecov.io/docs/pull-request-comments). This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Update Android Project Structure to be more compatible with Android Studio > -- > > Key: CB-11244 > URL: https://issues.apache.org/jira/browse/CB-11244 > Project: Apache Cordova > Issue Type: Improvement > Components: cordova-android >Reporter: Joe Bowser >
[jira] [Resolved] (CB-13568) Update from Cordova file transfer plugin crash Phonegap build for Android
[
https://issues.apache.org/jira/browse/CB-13568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bowser resolved CB-13568.
-
Resolution: Invalid
This is the Cordova issue tracker, and not the PhoneGap Build issue tracker. I
have no idea why your project stopped working on PGB, but it seems that the
class is just simply missing based on the information that you provided. I can
mention it to the PGB team, but other than that, there's not a lot that I can
do on this end. Apologies.
> Update from Cordova file transfer plugin crash Phonegap build for Android
> -
>
> Key: CB-13568
> URL: https://issues.apache.org/jira/browse/CB-13568
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-android, cordova-cli
>Affects Versions: 6.3.0, cordova-cli@6.4.0, cordova@7.0.0
> Environment: Android for all Phonegap build
>Reporter: clarklight
>Assignee: Joe Bowser
>Priority: Critical
>
> The recent update for the file-transfer plugin started crashing the phonegap
> build for android today. Last stable build was on Friday. It produce the
> error below.
> (More than 19 people had reported the same issue on the adobe forum with no
> one assigned,
> https://forums.adobe.com/thread/2410942?start=0&tstart=0
> https://forums.adobe.com/thread/2411286)
> {code}
> :generateDebugSources
> :incrementalDebugJavaCompilationSafeguard
> :compileDebugJavaWithJavac
> :compileDebugJavaWithJavac - is not incremental (e.g. outputs have changed,
> no previous execution, etc.).
> /project/src/org/apache/cordova/filetransfer/FileTransfer.java:49: error:
> package org.apache.cordova.file does not exist
> import org.apache.cordova.file.FileUtils;
> ^
> /project/src/org/apache/cordova/filetransfer/FileTransfer.java:851: error:
> cannot find symbol
> FileUtils filePlugin = (FileUtils) pm.getPlugin("File");
> ^
> symbol: class FileUtils
> /project/src/org/apache/cordova/filetransfer/FileTransfer.java:851: error:
> cannot find symbol
> FileUtils filePlugin = (FileUtils) pm.getPlugin("File");
> ^
> symbol: class FileUtils
> Note: Some input files use or override a deprecated API.
> Note: Recompile with -Xlint:deprecation for details.
> Note: Some input files use unchecked or unsafe operations.
> Note: Recompile with -Xlint:unchecked for details.
> 3 errors
> :compileDebugJavaWithJavac FAILED
>
> FAILURE: Build failed with an exception.
>
> * What went wrong:
> Execution failed for task ':compileDebugJavaWithJavac'.
> > Compilation failed; see the compiler error output for details.
>
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --info or
> --debug option to get more log output.
>
> BUILD FAILED
>
> Total time: 6.438 secs
> Error: /project/gradlew: Command failed with exit code 1 Error output:
> Note: Some input files use or override a deprecated API.
> Note: Recompile with -Xlint:deprecation for details.
> Note: Some input files use or override a deprecated API.
> Note: Recompile with -Xlint:deprecation for details.
> warning: string 'menu_settings' has no default translation.
> Warning: AndroidManifest.xml already defines debuggable (in
> http://schemas.android.com/apk/res/android); using existing value in manifest.
>
> /project/src/org/apache/cordova/filetransfer/FileTransfer.java:49: error:
> package org.apache.cordova.file does not exist
> import org.apache.cordova.file.FileUtils;
> ^
> /project/src/org/apache/cordova/filetransfer/FileTransfer.java:851: error:
> cannot find symbol
> FileUtils filePlugin = (FileUtils) pm.getPlugin("File");
> ^
> symbol: class FileUtils
> /project/src/org/apache/cordova/filetransfer/FileTransfer.java:851: error:
> cannot find symbol
> FileUtils filePlugin = (FileUtils) pm.getPlugin("File");
> ^
> symbol: class FileUtils
> Note: Some input files use or override a deprecated API.
> Note: Recompile with -Xlint:deprecation for details.
> Note: Some input files use unchecked or unsafe operations.
> Note: Recompile with -Xlint:unchecked for details.
> 3 errors
>
> FAILURE: Build failed with an exception.
>
> * What went wrong:
> Execution failed for task ':compileDebugJavaWithJavac'.
> > Compilation failed; see the compiler error output for details.
>
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --info or
> --debug option to get more log output.
> at ChildProcess.whenDone
> (/project/cordova/node_modules/cordova-common/src/superspawn.js:169:23)
> at emitTwo (events.js:106:13)
> at ChildProcess.emit (events.js:191:7)
> at maybeClose (internal/child_process.js:877:16)
> at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---
[jira] [Resolved] (CB-13578) IntelliJ won't run APK on device due to "test mode"
[ https://issues.apache.org/jira/browse/CB-13578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser resolved CB-13578. - Resolution: Cannot Reproduce It works fine on my Android Studio 3.0 Final installation locally, and Android Studio is based on IntelliJ. This may be an issue with how your IntelliJ is setup based on what [~Sujan12] mentioned. > IntelliJ won't run APK on device due to "test mode" > --- > > Key: CB-13578 > URL: https://issues.apache.org/jira/browse/CB-13578 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-android >Affects Versions: 6.4.0 >Reporter: Tom Bell >Assignee: Joe Bowser > > I've upgraded cordova-android to 6.4.0 (`cordova platform update > android@6.4.0`) however now when I try running the app on a device from > within IntelliJ it errors with > *Failure [INSTALL_FAILED_TEST_ONLY: installPackageLI]* -- 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-13289) Gradle/Android Plugin DSL change breaks including CordovaLib
[ https://issues.apache.org/jira/browse/CB-13289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser resolved CB-13289. - Resolution: Fixed This has been merged in for 6.4.0 released, and that has been merged into StudioProjectCompat for the next release, closing. > Gradle/Android Plugin DSL change breaks including CordovaLib > > > Key: CB-13289 > URL: https://issues.apache.org/jira/browse/CB-13289 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-android >Affects Versions: 6.2.1 >Reporter: Joe Bowser >Assignee: Joe Bowser >Priority: Blocker > Labels: android-next > Fix For: 7.0.0 > > > Android Studio 3.0.0 uses a new DSL, and this breaks the dependency list. > This directly affects Cordova plugins that work as a Library Module, as well > as adding and removing the Android platform. Basically, once Android Studio > 3.0 updates, Cordova projects will not work properly with the new version of > Android Studio once they're updated. > This depends on CB-11244 -- 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-13576) android cordova Could not open camera with
[ https://issues.apache.org/jira/browse/CB-13576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser resolved CB-13576. - Resolution: Won't Fix This functionality is currently unsupported in Cordova. If you wish to use the Camera, please install the camera plugin. > android cordova Could not open camera with accept="image/*" capture="camera"> > > > Key: CB-13576 > URL: https://issues.apache.org/jira/browse/CB-13576 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-android >Reporter: Bahgat Samy Mashaly >Assignee: Joe Bowser >Priority: Critical > > i can't use capture="camera" with cordova app in android device, although if > i open the application from browser it work fine, I am sure the cordova app > have all permissions to open camera > when use cordova app: > !https://i.stack.imgur.com/3nk2P.jpg! > . > .. > . > when use browser it work fine and ask to select an action: > when use browser it work fine and ask to select an action : > > !https://i.stack.imgur.com/wb1mC.jpg! > -- 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-13543) Automate build/deploy for cordova-docs
[ https://issues.apache.org/jira/browse/CB-13543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16254034#comment-16254034 ] ASF GitHub Bot commented on CB-13543: - stevengill commented on a change in pull request #760: CB-13543 : updated instructions/documentation around travis build/dep… URL: https://github.com/apache/cordova-docs/pull/760#discussion_r151231646 ## File path: doc/building-and-deploying-the-website.md ## @@ -0,0 +1,20 @@ +## Building and Deploying (Automated) + +### Testing + +After you are finished developing and making your changes, make sure to test them. Run: + + npm test + +`npm test` runs both [eslint] and [mocha] tests. If your tests pass, commit and push your work to Github. + +### Travis + +[Travis] automatically builds and publishes the website on every change. In [travis.yml](../.travis.yml), Travis installs required dependencies and runs the build script. Travis will build the full website for you by running `gulp build --prod` under the hood. Travis also uses [SVN] to update, copy, add, and commit the new changes over to the website. Committing to svn can only occur once the commit has been merged to master. You can read more about is happening under the hood with SVN [here](deploying-the-website.md). Travis also runs `npm test` and will notify you if any of your `eslint` or `mocha` tests are failing. When Travis is done building and deploying, send a pull request and ask for a review. Review comment: Travis checks for the variable `svn_pass`. If one exists, it uses that to try and commit to svn. `svn_pass` is set as an encrypted variable on travis for github.com/apache. Encrypted variables aren't available for PRs, only master. So the deploy can only happen on master. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Automate build/deploy for cordova-docs > -- > > Key: CB-13543 > URL: https://issues.apache.org/jira/browse/CB-13543 > Project: Apache Cordova > Issue Type: Improvement > Components: cordova-docs >Reporter: Audrey So >Assignee: Audrey So > Labels: enhancement, feature, in-progress, optimization > > Automate build/deploy for cordova-docs > Cordova-docs should be built and published automatically on every change > Replace jsihnt with eslint > Update README.md & update instructions in docs to reflect changes > https://issues.apache.org/jira/browse/CB-13162 -- 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-13577) bug with ionic cordova emulate android
[
https://issues.apache.org/jira/browse/CB-13577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bowser resolved CB-13577.
-
Resolution: Duplicate
This is why Cordova-Android 6.4.0 was released. Contact ionic to determine
when they will accept the fix downstream.
> bug with ionic cordova emulate android
> --
>
> Key: CB-13577
> URL: https://issues.apache.org/jira/browse/CB-13577
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-android
>Affects Versions: cordova@7.0.0
> Environment: ionic info :
> cli packages: (/usr/local/lib/node_modules)
> @ionic/cli-utils : 1.18.0
> ionic (Ionic CLI) : 3.18.0
> global packages:
> cordova (Cordova CLI) : 7.1.0
> local packages:
> @ionic/app-scripts : 3.1.2
> Cordova Platforms : android 6.3.0 ios 4.5.3
> Ionic Framework: ionic-angular 3.9.2
> System:
> ios-deploy : 1.9.2
> ios-sim: 6.1.2
> Node : v8.9.1
> npm: 5.5.1
> OS : macOS High Sierra
> Xcode : Xcode 9.1 Build version 9B55
> Environment Variables:
> ANDROID_HOME : not set
> Misc:
> backend : pro
>Reporter: gilles Godefroid
>Assignee: Joe Bowser
>
> ionic cordova emulate android --list
> > cordova run android --list --emulator
> Available android virtual devices:
> Nexus_5_API_26
> Nexus_6_API_23
> ionic cordova emulate android --verbose
> [DEBUG] Reason for not using local CLI: LOCAL_CLI_NOT_FOUND
> [DEBUG] CLI flags: { interactive: true, confirm: false }
> [DEBUG] { cwd: '/Users/gillesgodefroid/Documents/Ionic2Weather', local:
> false,
> binPath: '/usr/local/lib/node_modules/ionic/bin/ionic', libPath:
> '/usr/local/lib/node_modules/ionic/dist/index.js' }
> [DEBUG] Daemon found (pid: 2011)
> Running app-scripts build: --platform android --target cordova
> [16:48:26] build dev started ...
> [16:48:26] clean started ...
> [16:48:26] clean finished in 122 ms
> [16:48:26] copy started ...
> [16:48:27] deeplinks started ...
> [16:48:27] deeplinks finished in 27 ms
> [16:48:27] transpile started ...
> [16:48:42] transpile finished in 14.95 s
> [16:48:42] preprocess started ...
> [16:48:42] preprocess finished in 4 ms
> [16:48:42] webpack started ...
> [16:48:44] copy finished in 17.39 s
> [16:48:52] webpack finished in 10.10 s
> [16:48:52] sass started ...
> [16:48:59] sass finished in 7.02 s
> [16:48:59] postprocess started ...
> [16:48:59] postprocess finished in 11 ms
> [16:48:59] lint started ...
> [16:48:59] build dev finished in 33.20 s
> > cordova emulate android
> [16:49:02] lint finished in 2.72 s
> ANDROID_HOME=/Users/gillesgodefroid/Library/Android/sdk
> JAVA_HOME=/Library/Java/JavaVirtualMachines/jdk1.8.0_91.jdk/Contents/Home
> Error: spawn EACCES
> [ERROR] An error occurred while running cordova emulate android (exit code 1).
>
> [DEBUG] registerShutdownFunction process.exit/normal shutdown
--
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-13297) Bump Java Compatibility in the Android Code to 1.8
[ https://issues.apache.org/jira/browse/CB-13297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser updated CB-13297: Issue Type: Sub-task (was: Bug) Parent: CB-11244 > Bump Java Compatibility in the Android Code to 1.8 > -- > > Key: CB-13297 > URL: https://issues.apache.org/jira/browse/CB-13297 > Project: Apache Cordova > Issue Type: Sub-task > Components: cordova-android >Reporter: Joe Bowser >Assignee: Joe Bowser > Labels: android-next > Fix For: 7.0.0 > > > This depends on CB-11244 -- 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-13297) Bump Java Compatibility in the Android Code to 1.8
[ https://issues.apache.org/jira/browse/CB-13297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser updated CB-13297: Description: This depends on CB-11244 > Bump Java Compatibility in the Android Code to 1.8 > -- > > Key: CB-13297 > URL: https://issues.apache.org/jira/browse/CB-13297 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-android >Reporter: Joe Bowser >Assignee: Joe Bowser > Labels: android-next > Fix For: 7.0.0 > > > This depends on CB-11244 -- 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-13543) Automate build/deploy for cordova-docs
[ https://issues.apache.org/jira/browse/CB-13543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16254016#comment-16254016 ] ASF GitHub Bot commented on CB-13543: - dblotsky commented on a change in pull request #760: CB-13543 : updated instructions/documentation around travis build/dep… URL: https://github.com/apache/cordova-docs/pull/760#discussion_r151229142 ## File path: doc/building-and-deploying-the-website.md ## @@ -0,0 +1,20 @@ +## Building and Deploying (Automated) + +### Testing + +After you are finished developing and making your changes, make sure to test them. Run: + + npm test + +`npm test` runs both [eslint] and [mocha] tests. If your tests pass, commit and push your work to Github. + +### Travis + +[Travis] automatically builds and publishes the website on every change. In [travis.yml](../.travis.yml), Travis installs required dependencies and runs the build script. Travis will build the full website for you by running `gulp build --prod` under the hood. Travis also uses [SVN] to update, copy, add, and commit the new changes over to the website. Committing to svn can only occur once the commit has been merged to master. You can read more about is happening under the hood with SVN [here](deploying-the-website.md). Travis also runs `npm test` and will notify you if any of your `eslint` or `mocha` tests are failing. When Travis is done building and deploying, send a pull request and ask for a review. Review comment: @stevengill what ensures that deploy happens only on master? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Automate build/deploy for cordova-docs > -- > > Key: CB-13543 > URL: https://issues.apache.org/jira/browse/CB-13543 > Project: Apache Cordova > Issue Type: Improvement > Components: cordova-docs >Reporter: Audrey So >Assignee: Audrey So > Labels: enhancement, feature, in-progress, optimization > > Automate build/deploy for cordova-docs > Cordova-docs should be built and published automatically on every change > Replace jsihnt with eslint > Update README.md & update instructions in docs to reflect changes > https://issues.apache.org/jira/browse/CB-13162 -- 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-13543) Automate build/deploy for cordova-docs
[ https://issues.apache.org/jira/browse/CB-13543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16254014#comment-16254014 ] ASF GitHub Bot commented on CB-13543: - janpio commented on a change in pull request #760: CB-13543 : updated instructions/documentation around travis build/dep… URL: https://github.com/apache/cordova-docs/pull/760#discussion_r151228684 ## File path: doc/building-and-deploying-the-website.md ## @@ -0,0 +1,20 @@ +## Building and Deploying (Automated) + +### Testing + +After you are finished developing and making your changes, make sure to test them. Run: + + npm test + +`npm test` runs both [eslint] and [mocha] tests. If your tests pass, commit and push your work to Github. + +### Travis + +[Travis] automatically builds and publishes the website on every change. In [travis.yml](../.travis.yml), Travis installs required dependencies and runs the build script. Travis will build the full website for you by running `gulp build --prod` under the hood. Travis also uses [SVN] to update, copy, add, and commit the new changes over to the website. Committing to svn can only occur once the commit has been merged to master. You can read more about is happening under the hood with SVN [here](deploying-the-website.md). Travis also runs `npm test` and will notify you if any of your `eslint` or `mocha` tests are failing. When Travis is done building and deploying, send a pull request and ask for a review. Review comment: Ok, maybe this should be explain a bit here and the workflow clarified? You fork, commit your changes to your fork, wait for the test result via Travis. If green, you can send the PR which will trigger Travis again. If (green and) merged, it will trigger a deploy. Correct? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Automate build/deploy for cordova-docs > -- > > Key: CB-13543 > URL: https://issues.apache.org/jira/browse/CB-13543 > Project: Apache Cordova > Issue Type: Improvement > Components: cordova-docs >Reporter: Audrey So >Assignee: Audrey So > Labels: enhancement, feature, in-progress, optimization > > Automate build/deploy for cordova-docs > Cordova-docs should be built and published automatically on every change > Replace jsihnt with eslint > Update README.md & update instructions in docs to reflect changes > https://issues.apache.org/jira/browse/CB-13162 -- 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-13543) Automate build/deploy for cordova-docs
[ https://issues.apache.org/jira/browse/CB-13543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16254012#comment-16254012 ] ASF GitHub Bot commented on CB-13543: - dblotsky commented on issue #760: CB-13543 : updated instructions/documentation around travis build/dep… URL: https://github.com/apache/cordova-docs/pull/760#issuecomment-344702130 @audreyso yep, the question about infra still remains open. Are Apache Infra OK with us having SVN credentials in Travis? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Automate build/deploy for cordova-docs > -- > > Key: CB-13543 > URL: https://issues.apache.org/jira/browse/CB-13543 > Project: Apache Cordova > Issue Type: Improvement > Components: cordova-docs >Reporter: Audrey So >Assignee: Audrey So > Labels: enhancement, feature, in-progress, optimization > > Automate build/deploy for cordova-docs > Cordova-docs should be built and published automatically on every change > Replace jsihnt with eslint > Update README.md & update instructions in docs to reflect changes > https://issues.apache.org/jira/browse/CB-13162 -- 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-13543) Automate build/deploy for cordova-docs
[ https://issues.apache.org/jira/browse/CB-13543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253993#comment-16253993 ] ASF GitHub Bot commented on CB-13543: - stevengill commented on a change in pull request #760: CB-13543 : updated instructions/documentation around travis build/dep… URL: https://github.com/apache/cordova-docs/pull/760#discussion_r151225869 ## File path: doc/building-and-deploying-the-website.md ## @@ -0,0 +1,20 @@ +## Building and Deploying (Automated) + +### Testing + +After you are finished developing and making your changes, make sure to test them. Run: + + npm test + +`npm test` runs both [eslint] and [mocha] tests. If your tests pass, commit and push your work to Github. + +### Travis + +[Travis] automatically builds and publishes the website on every change. In [travis.yml](../.travis.yml), Travis installs required dependencies and runs the build script. Travis will build the full website for you by running `gulp build --prod` under the hood. Travis also uses [SVN] to update, copy, add, and commit the new changes over to the website. Committing to svn can only occur once the commit has been merged to master. You can read more about is happening under the hood with SVN [here](deploying-the-website.md). Travis also runs `npm test` and will notify you if any of your `eslint` or `mocha` tests are failing. When Travis is done building and deploying, send a pull request and ask for a review. Review comment: yes. Tests will run on branches/prs. Deploy only happens on master This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Automate build/deploy for cordova-docs > -- > > Key: CB-13543 > URL: https://issues.apache.org/jira/browse/CB-13543 > Project: Apache Cordova > Issue Type: Improvement > Components: cordova-docs >Reporter: Audrey So >Assignee: Audrey So > Labels: enhancement, feature, in-progress, optimization > > Automate build/deploy for cordova-docs > Cordova-docs should be built and published automatically on every change > Replace jsihnt with eslint > Update README.md & update instructions in docs to reflect changes > https://issues.apache.org/jira/browse/CB-13162 -- 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-13573) Clarify Cordova Android 6.4.0 blog post
[ https://issues.apache.org/jira/browse/CB-13573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253986#comment-16253986 ] ASF subversion and git services commented on CB-13573: -- Commit c27171bfa17a1bb39a1e195c22b17ee8c46dfd5d in cordova-docs's branch refs/heads/master from Jan Piotrowski [ https://gitbox.apache.org/repos/asf?p=cordova-docs.git;h=c27171b ] CB-13573: Clarify Cordova Android 6.4.0 blog post - add link to gradle install instructions - add link to crosswalk project and issue (I created for this) - reword and restructure text a bit > Clarify Cordova Android 6.4.0 blog post > --- > > Key: CB-13573 > URL: https://issues.apache.org/jira/browse/CB-13573 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-docs >Reporter: Jan Piotrowski (Sujan) >Assignee: Jan Piotrowski (Sujan) > > Talked to user that had problems understanding what was actually required of > them (install standalone Gradle) and why this was happening. -- 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-13573) Clarify Cordova Android 6.4.0 blog post
[ https://issues.apache.org/jira/browse/CB-13573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253984#comment-16253984 ] ASF GitHub Bot commented on CB-13573: - stevengill commented on issue #761: CB-13573: Clarify Cordova Android 6.4.0 blog post URL: https://github.com/apache/cordova-docs/pull/761#issuecomment-344698544 I wouldn't worry about the failures too much. Lets merge it in and keep an eye on travis for master to see if that passes. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Clarify Cordova Android 6.4.0 blog post > --- > > Key: CB-13573 > URL: https://issues.apache.org/jira/browse/CB-13573 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-docs >Reporter: Jan Piotrowski (Sujan) >Assignee: Jan Piotrowski (Sujan) > > Talked to user that had problems understanding what was actually required of > them (install standalone Gradle) and why this was happening. -- 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-13573) Clarify Cordova Android 6.4.0 blog post
[ https://issues.apache.org/jira/browse/CB-13573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253985#comment-16253985 ] ASF GitHub Bot commented on CB-13573: - stevengill closed pull request #761: CB-13573: Clarify Cordova Android 6.4.0 blog post URL: https://github.com/apache/cordova-docs/pull/761 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Clarify Cordova Android 6.4.0 blog post > --- > > Key: CB-13573 > URL: https://issues.apache.org/jira/browse/CB-13573 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-docs >Reporter: Jan Piotrowski (Sujan) >Assignee: Jan Piotrowski (Sujan) > > Talked to user that had problems understanding what was actually required of > them (install standalone Gradle) and why this was happening. -- 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-13573) Clarify Cordova Android 6.4.0 blog post
[ https://issues.apache.org/jira/browse/CB-13573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253987#comment-16253987 ] ASF subversion and git services commented on CB-13573: -- Commit 05933c1a275c2b57f3eae86db1a686ed5f7619c6 in cordova-docs's branch refs/heads/master from [~stevegill] [ https://gitbox.apache.org/repos/asf?p=cordova-docs.git;h=05933c1 ] Merge pull request #761 from apache/janpio-patch-1 CB-13573: Clarify Cordova Android 6.4.0 blog post > Clarify Cordova Android 6.4.0 blog post > --- > > Key: CB-13573 > URL: https://issues.apache.org/jira/browse/CB-13573 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-docs >Reporter: Jan Piotrowski (Sujan) >Assignee: Jan Piotrowski (Sujan) > > Talked to user that had problems understanding what was actually required of > them (install standalone Gradle) and why this was happening. -- 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] [Created] (CB-13579) Cordova-iOS Platform Release November 15, 2017
Suraj Pindoria created CB-13579: --- Summary: Cordova-iOS Platform Release November 15, 2017 Key: CB-13579 URL: https://issues.apache.org/jira/browse/CB-13579 Project: Apache Cordova Issue Type: Task Reporter: Suraj Pindoria Assignee: Suraj Pindoria Following steps at https://github.com/apache/cordova-coho/blob/master/docs/platforms-release-process.md -- 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-13523) Add build config option to enable Xcode automatic provisioning
[ https://issues.apache.org/jira/browse/CB-13523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253944#comment-16253944 ] ASF GitHub Bot commented on CB-13523: - dpogue commented on issue #762: CB-13523: Add automaticProvisioning to iOS signing docs URL: https://github.com/apache/cordova-docs/pull/762#issuecomment-344690609 The `--automaticProvisioning` flag won't be available until the next iOS release This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Add build config option to enable Xcode automatic provisioning > -- > > Key: CB-13523 > URL: https://issues.apache.org/jira/browse/CB-13523 > Project: Apache Cordova > Issue Type: Improvement > Components: cordova-ios > Environment: Xcode 9 > Cordova-iOS 4.5.3 >Reporter: Darryl Pogue >Assignee: Darryl Pogue > > Xcode 9 made more changes to how provisioning works for apps, particularly > around manual vs automatic signing. > The changes required to support manual signing of release builds was > implemented as part of CB-13315. > In order for automatic signing to work, we need to pass an additional flag to > xcodebuild to allow Xcode to manage automatically updating provisioning > profiles as needed. I want to keep this being a build config option because > many people may not want to grant Xcode such power by default. -- 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-13523) Add build config option to enable Xcode automatic provisioning
[ https://issues.apache.org/jira/browse/CB-13523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253941#comment-16253941 ] ASF GitHub Bot commented on CB-13523: - stevengill commented on issue #762: CB-13523: Add automaticProvisioning to iOS signing docs URL: https://github.com/apache/cordova-docs/pull/762#issuecomment-344690096 LGTM. @dpogue ready to merge or wait until after next iOS release? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Add build config option to enable Xcode automatic provisioning > -- > > Key: CB-13523 > URL: https://issues.apache.org/jira/browse/CB-13523 > Project: Apache Cordova > Issue Type: Improvement > Components: cordova-ios > Environment: Xcode 9 > Cordova-iOS 4.5.3 >Reporter: Darryl Pogue >Assignee: Darryl Pogue > > Xcode 9 made more changes to how provisioning works for apps, particularly > around manual vs automatic signing. > The changes required to support manual signing of release builds was > implemented as part of CB-13315. > In order for automatic signing to work, we need to pass an additional flag to > xcodebuild to allow Xcode to manage automatically updating provisioning > profiles as needed. I want to keep this being a build config option because > many people may not want to grant Xcode such power by default. -- 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-13558) Unable to upload AAR to bintray
[ https://issues.apache.org/jira/browse/CB-13558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253932#comment-16253932 ] ASF subversion and git services commented on CB-13558: -- Commit 026dce563b37b781f2ce299c643b3281fc961065 in cordova-android's branch refs/heads/master from [~bowserj] [ https://gitbox.apache.org/repos/asf?p=cordova-android.git;h=026dce5 ] CB-13558: Upgrading the gradle so we can upload the AAR > Unable to upload AAR to bintray > --- > > Key: CB-13558 > URL: https://issues.apache.org/jira/browse/CB-13558 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-android >Reporter: Joe Bowser >Assignee: Joe Bowser > > I was unable to upload to bintray with the old version of Gradle that was > saved on the framework project. When I updated it, I now get a 401 > Unauthorized Error. This was found when releasing Cordova-Android 6.4.0 > (CB-13528) -- 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-13558) Unable to upload AAR to bintray
[
https://issues.apache.org/jira/browse/CB-13558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253931#comment-16253931
]
ASF GitHub Bot commented on CB-13558:
-
infil00p closed pull request #416: CB-13558: Upgrading the gradle so we can
upload the AAR
URL: https://github.com/apache/cordova-android/pull/416
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git a/framework/build.gradle b/framework/build.gradle
index 31c53afe4..1ad622c9a 100644
--- a/framework/build.gradle
+++ b/framework/build.gradle
@@ -31,7 +31,7 @@ buildscript {
}
dependencies {
-classpath 'com.android.tools.build:gradle:2.2.3'
+classpath 'com.android.tools.build:gradle:3.0.0'
classpath 'com.github.dcendents:android-maven-gradle-plugin:1.5'
classpath 'com.jfrog.bintray.gradle:gradle-bintray-plugin:1.7.3'
}
diff --git a/framework/gradle/wrapper/gradle-wrapper.properties
b/framework/gradle/wrapper/gradle-wrapper.properties
index 04e285f34..c3a5fdabe 100644
--- a/framework/gradle/wrapper/gradle-wrapper.properties
+++ b/framework/gradle/wrapper/gradle-wrapper.properties
@@ -1,6 +1,6 @@
-#Mon Dec 28 10:00:20 PST 2015
+#Thu Nov 09 10:50:25 PST 2017
distributionBase=GRADLE_USER_HOME
distributionPath=wrapper/dists
zipStoreBase=GRADLE_USER_HOME
zipStorePath=wrapper/dists
-distributionUrl=https\://services.gradle.org/distributions/gradle-2.14.1-all.zip
+distributionUrl=https\://services.gradle.org/distributions/gradle-4.1-all.zip
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Unable to upload AAR to bintray
> ---
>
> Key: CB-13558
> URL: https://issues.apache.org/jira/browse/CB-13558
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-android
>Reporter: Joe Bowser
>Assignee: Joe Bowser
>
> I was unable to upload to bintray with the old version of Gradle that was
> saved on the framework project. When I updated it, I now get a 401
> Unauthorized Error. This was found when releasing Cordova-Android 6.4.0
> (CB-13528)
--
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-13558) Unable to upload AAR to bintray
[ https://issues.apache.org/jira/browse/CB-13558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253933#comment-16253933 ] ASF subversion and git services commented on CB-13558: -- Commit 3760616639eb8d264edc99c3b5c8794c4d378bc8 in cordova-android's branch refs/heads/master from [~bowserj] [ https://gitbox.apache.org/repos/asf?p=cordova-android.git;h=3760616 ] Merge pull request #416 from infil00p/bintray_fix CB-13558: Upgrading the gradle so we can upload the AAR > Unable to upload AAR to bintray > --- > > Key: CB-13558 > URL: https://issues.apache.org/jira/browse/CB-13558 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-android >Reporter: Joe Bowser >Assignee: Joe Bowser > > I was unable to upload to bintray with the old version of Gradle that was > saved on the framework project. When I updated it, I now get a 401 > Unauthorized Error. This was found when releasing Cordova-Android 6.4.0 > (CB-13528) -- 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-13558) Unable to upload AAR to bintray
[ https://issues.apache.org/jira/browse/CB-13558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253910#comment-16253910 ] ASF GitHub Bot commented on CB-13558: - codecov-io commented on issue #416: CB-13558: Upgrading the gradle so we can upload the AAR URL: https://github.com/apache/cordova-android/pull/416#issuecomment-344684272 # [Codecov](https://codecov.io/gh/apache/cordova-android/pull/416?src=pr&el=h1) Report > Merging [#416](https://codecov.io/gh/apache/cordova-android/pull/416?src=pr&el=desc) into [master](https://codecov.io/gh/apache/cordova-android/commit/83601dca2fa468a76bcb2c687b5baebfcb69588b?src=pr&el=desc) will **not change** coverage. > The diff coverage is `n/a`. [](https://codecov.io/gh/apache/cordova-android/pull/416?src=pr&el=tree) ```diff @@ Coverage Diff @@ ## master #416 +/- ## === Coverage 44.01% 44.01% === Files 17 17 Lines1679 1679 Branches 304 304 === Hits 739 739 Misses940 940 ``` -- [Continue to review full report at Codecov](https://codecov.io/gh/apache/cordova-android/pull/416?src=pr&el=continue). > **Legend** - [Click here to learn more](https://docs.codecov.io/docs/codecov-delta) > `Δ = absolute (impact)`, `ø = not affected`, `? = missing data` > Powered by [Codecov](https://codecov.io/gh/apache/cordova-android/pull/416?src=pr&el=footer). Last update [83601dc...026dce5](https://codecov.io/gh/apache/cordova-android/pull/416?src=pr&el=lastupdated). Read the [comment docs](https://docs.codecov.io/docs/pull-request-comments). This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Unable to upload AAR to bintray > --- > > Key: CB-13558 > URL: https://issues.apache.org/jira/browse/CB-13558 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-android >Reporter: Joe Bowser >Assignee: Joe Bowser > > I was unable to upload to bintray with the old version of Gradle that was > saved on the framework project. When I updated it, I now get a 401 > Unauthorized Error. This was found when releasing Cordova-Android 6.4.0 > (CB-13528) -- 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-13558) Unable to upload AAR to bintray
[ https://issues.apache.org/jira/browse/CB-13558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253888#comment-16253888 ] ASF GitHub Bot commented on CB-13558: - infil00p opened a new pull request #416: CB-13558: Upgrading the gradle so we can upload the AAR URL: https://github.com/apache/cordova-android/pull/416 ### Platforms affected Cordova-Android ### What does this PR do? Fixes the Framework Gradle so that we can upload the AAR ### What testing has been done on this change? Ran gradle bintrayUpload ### 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. - [ ] Added automated test coverage as appropriate for this change. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Unable to upload AAR to bintray > --- > > Key: CB-13558 > URL: https://issues.apache.org/jira/browse/CB-13558 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-android >Reporter: Joe Bowser >Assignee: Joe Bowser > > I was unable to upload to bintray with the old version of Gradle that was > saved on the framework project. When I updated it, I now get a 401 > Unauthorized Error. This was found when releasing Cordova-Android 6.4.0 > (CB-13528) -- 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-13573) Clarify Cordova Android 6.4.0 blog post
[ https://issues.apache.org/jira/browse/CB-13573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253882#comment-16253882 ] ASF GitHub Bot commented on CB-13573: - janpio commented on issue #761: CB-13573: Clarify Cordova Android 6.4.0 blog post URL: https://github.com/apache/cordova-docs/pull/761#issuecomment-344536870 @audreyso Could you have a look at the first failing Travis CI build here please? No idea what is happening and why. Update 1: Found out I can manually restart the build. Trying that right now. Update 2: Didn't help. Timeout I think... But why? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Clarify Cordova Android 6.4.0 blog post > --- > > Key: CB-13573 > URL: https://issues.apache.org/jira/browse/CB-13573 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-docs >Reporter: Jan Piotrowski (Sujan) >Assignee: Jan Piotrowski (Sujan) > > Talked to user that had problems understanding what was actually required of > them (install standalone Gradle) and why this was happening. -- 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-13573) Clarify Cordova Android 6.4.0 blog post
[ https://issues.apache.org/jira/browse/CB-13573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253860#comment-16253860 ] ASF GitHub Bot commented on CB-13573: - janpio commented on issue #761: CB-13573: Clarify Cordova Android 6.4.0 blog post URL: https://github.com/apache/cordova-docs/pull/761#issuecomment-344536870 @audreyso Could you have a look at the first failing Travis CI build here please? No idea what is happening and why. Update 1: Found out I can manually restart the build. Trying that right now. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Clarify Cordova Android 6.4.0 blog post > --- > > Key: CB-13573 > URL: https://issues.apache.org/jira/browse/CB-13573 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-docs >Reporter: Jan Piotrowski (Sujan) >Assignee: Jan Piotrowski (Sujan) > > Talked to user that had problems understanding what was actually required of > them (install standalone Gradle) and why this was happening. -- 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-12863) Can't install plugins from a branch (cordova@7)
[
https://issues.apache.org/jira/browse/CB-12863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253582#comment-16253582
]
Jim Trainor edited comment on CB-12863 at 11/15/17 5:12 PM:
Experiencing the same problem.
{code:java}
cordova --version && git --version && cordova plugin add
https://github.com/apache/cordova-plugins.git\#wkwebview-engine-localhost
7.1.0
git version 2.13.6 (Apple Git-96)
Error: Failed to fetch plugin
https://github.com/apache/cordova-plugins.git#wkwebview-engine-localhost via
registry.
Probably this is either a connection problem, or plugin spec is incorrect.
Check your connection and plugin name/version/URL.
Failed to get absolute path to installed module
{code}
My temporary work around is:
- remove references to the wkwebview and local-server plugins. (Not everyone
will be using the local-server plugin).
- rm -rf platforms plugins package.json
- cordova platfom add ios
- cordova plugin add cordova-plugin-file --nofetch
- cordova plugin add https://github.com/apache/cordova-plugins#local-webserver
--nofetch (if you use it)
- cordova plugin add
https://github.com/apache/cordova-plugins#wkwebview-engine-localhost --nofetch
There is a reference to the possible need for "nofetch" in the cordova 7
release notes. I could not find a way to specify "nofetch" in the config.xml
plugin entry however so I'm left running the above from a script until this is
resolved an will function correctly based on the config.xml spec alone.
was (Author: jptrainor):
Experiencing the same problem.
{code:java}
cordova --version && git --version && cordova plugin add
https://github.com/apache/cordova-plugins.git\#wkwebview-engine-localhost
7.1.0
git version 2.13.6 (Apple Git-96)
Error: Failed to fetch plugin
https://github.com/apache/cordova-plugins.git#wkwebview-engine-localhost via
registry.
Probably this is either a connection problem, or plugin spec is incorrect.
Check your connection and plugin name/version/URL.
Failed to get absolute path to installed module
{code}
My temporary work around is:
- remove references to the wkwebview and local-server plugins. (Not everyone
will be using the local-server plugin).
- rm -rf platforms plugins package.json
- cordova platfom add ios
- cordova plugin add cordova-plugin-file --nofetch
- cordova plugin add https://github.com/apache/cordova-plugins#local-webserver
--nofetch (if you use it)
- cordova plugin add
https://github.com/apache/cordova-plugins#wkwebview-engine-localhost --nofetch
There is a reference to the possible need for "--nofetch" in the cordova 7
release notes. I could not find a way to specify "--nofetch" in the config.xml
plugin entry however so I'm left running the above from a script until this is
resolved an will function correctly based on the config.xml spec alone.
> Can't install plugins from a branch (cordova@7)
> ---
>
> Key: CB-12863
> URL: https://issues.apache.org/jira/browse/CB-12863
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-fetch
> Environment: cordova-cli@7.0.1
> node@4.6.0
>Reporter: Shazron Abdullah
>Assignee: Shazron Abdullah
> Labels: cordova-8.0.0, reproduced, triage
> Fix For: cordova-labs-wkwebview-engine-localhost@0.5.1
>
>
> 1st try:
> {code}
> $ cordova plugin add
> https://github.com/apache/cordova-plugins.git\#wkwebview-engine-localhost
> Installing "cordova-labs-wkwebview-engine-localhost" for ios
> Failed to install 'cordova-labs-wkwebview-engine-localhost': CordovaError:
> Failed to fetch plugin
> https://git-wip-us.apache.org/repos/asf/cordova-plugins.git#local-webserver
> via registry.
> Probably this is either a connection problem, or plugin spec is incorrect.
> Check your connection and plugin name/version/URL.
> Error: npm: Command failed with exit code 254 Error output:
> npm WARN package.json helloworld@1.0.0 No repository field.
> npm WARN package.json helloworld@1.0.0 No README data
> npm ERR! not a package
> /var/folders/40/pyxnqlcj6bn_43qrjp3p0xtwgp/T/npm-28533-ff14b1ee/git-wip-us.apache.org/repos/asf/cordova-plugins.git/local-webserver
> npm ERR! Darwin 16.7.0
> npm ERR! argv "/Users/shazron/.nvm/versions/node/v4.6.0/bin/node"
> "/Users/shazron/.nvm/versions/node/v4.6.0/bin/npm" "install"
> "https://git-wip-us.apache.org/repos/asf/cordova-plugins.git#local-webserver";
> "--save"
> npm ERR! node v4.6.0
> npm ERR! npm v2.15.9
> npm ERR! path
> /var/folders/40/pyxnqlcj6bn_43qrjp3p0xtwgp/T/npm-28533-ff14b1ee/unpack-968d75f9eab2/package.json
> npm ERR! code ENOENT
> npm ERR! errno -2
> npm ERR! syscall open
> npm ERR! enoent ENOENT: no such file or directory, open
> '/var/folders/40/pyxnqlcj6bn_43qrjp3p0xtwgp/T/npm-28533-ff14b1ee/unpack-968d75f9eab2/package.json'
> npm E
[jira] [Comment Edited] (CB-12863) Can't install plugins from a branch (cordova@7)
[
https://issues.apache.org/jira/browse/CB-12863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253582#comment-16253582
]
Jim Trainor edited comment on CB-12863 at 11/15/17 5:11 PM:
Experiencing the same problem.
{code:java}
cordova --version && git --version && cordova plugin add
https://github.com/apache/cordova-plugins.git\#wkwebview-engine-localhost
7.1.0
git version 2.13.6 (Apple Git-96)
Error: Failed to fetch plugin
https://github.com/apache/cordova-plugins.git#wkwebview-engine-localhost via
registry.
Probably this is either a connection problem, or plugin spec is incorrect.
Check your connection and plugin name/version/URL.
Failed to get absolute path to installed module
{code}
My temporary work around is:
- remove references to the wkwebview and local-server plugins. (Not everyone
will be using the local-server plugin).
- rm -rf platforms plugins package.json
- cordova platfom add ios
- cordova plugin add cordova-plugin-file --nofetch
- cordova plugin add https://github.com/apache/cordova-plugins#local-webserver
--nofetch (if you use it)
- cordova plugin add
https://github.com/apache/cordova-plugins#wkwebview-engine-localhost --nofetch
There is a reference to the possible need for "--nofetch" in the cordova 7
release notes. I could not find a way to specify "--nofetch" in the config.xml
plugin entry however so I'm left running the above from a script until this is
resolved an will function correctly based on the config.xml spec alone.
was (Author: jptrainor):
Experiencing the same problem.
{code:java}
cordova --version && git --version && cordova plugin add
https://github.com/apache/cordova-plugins.git\#wkwebview-engine-localhost
7.1.0
git version 2.13.6 (Apple Git-96)
Error: Failed to fetch plugin
https://github.com/apache/cordova-plugins.git#wkwebview-engine-localhost via
registry.
Probably this is either a connection problem, or plugin spec is incorrect.
Check your connection and plugin name/version/URL.
Failed to get absolute path to installed module
{code}
> Can't install plugins from a branch (cordova@7)
> ---
>
> Key: CB-12863
> URL: https://issues.apache.org/jira/browse/CB-12863
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-fetch
> Environment: cordova-cli@7.0.1
> node@4.6.0
>Reporter: Shazron Abdullah
>Assignee: Shazron Abdullah
> Labels: cordova-8.0.0, reproduced, triage
> Fix For: cordova-labs-wkwebview-engine-localhost@0.5.1
>
>
> 1st try:
> {code}
> $ cordova plugin add
> https://github.com/apache/cordova-plugins.git\#wkwebview-engine-localhost
> Installing "cordova-labs-wkwebview-engine-localhost" for ios
> Failed to install 'cordova-labs-wkwebview-engine-localhost': CordovaError:
> Failed to fetch plugin
> https://git-wip-us.apache.org/repos/asf/cordova-plugins.git#local-webserver
> via registry.
> Probably this is either a connection problem, or plugin spec is incorrect.
> Check your connection and plugin name/version/URL.
> Error: npm: Command failed with exit code 254 Error output:
> npm WARN package.json helloworld@1.0.0 No repository field.
> npm WARN package.json helloworld@1.0.0 No README data
> npm ERR! not a package
> /var/folders/40/pyxnqlcj6bn_43qrjp3p0xtwgp/T/npm-28533-ff14b1ee/git-wip-us.apache.org/repos/asf/cordova-plugins.git/local-webserver
> npm ERR! Darwin 16.7.0
> npm ERR! argv "/Users/shazron/.nvm/versions/node/v4.6.0/bin/node"
> "/Users/shazron/.nvm/versions/node/v4.6.0/bin/npm" "install"
> "https://git-wip-us.apache.org/repos/asf/cordova-plugins.git#local-webserver";
> "--save"
> npm ERR! node v4.6.0
> npm ERR! npm v2.15.9
> npm ERR! path
> /var/folders/40/pyxnqlcj6bn_43qrjp3p0xtwgp/T/npm-28533-ff14b1ee/unpack-968d75f9eab2/package.json
> npm ERR! code ENOENT
> npm ERR! errno -2
> npm ERR! syscall open
> npm ERR! enoent ENOENT: no such file or directory, open
> '/var/folders/40/pyxnqlcj6bn_43qrjp3p0xtwgp/T/npm-28533-ff14b1ee/unpack-968d75f9eab2/package.json'
> npm ERR! enoent This is most likely not a problem with npm itself
> npm ERR! enoent and is related to npm not being able to find a file.
> npm ERR! enoent
> npm ERR! Please include the following file with any support request:
> npm ERR! /Users/shazron/Desktop/gtm/node_modules/npm-debug.log
> at
> /Users/shazron/.nvm/versions/node/v4.6.0/lib/node_modules/cordova/node_modules/cordova-lib/src/plugman/fetch.js:205:33
> at _rejected
> (/Users/shazron/.nvm/versions/node/v4.6.0/lib/node_modules/cordova/node_modules/cordova-lib/node_modules/cordova-fetch/node_modules/q/q.js:864:24)
> at
> /Users/shazron/.nvm/versions/node/v4.6.0/lib/node_modules/cordova/node_modules/cordova-lib/node_modules/cordova-fetch/node_modules/q/q.js:890:30
> at Promise.when
> (/Use
[jira] [Comment Edited] (CB-13536) cordova being called from "quasar wrap" not working - cordova-realted error: Could not install from (path_of_nodejs_modules) as it does not contain a package.json fi
[
https://issues.apache.org/jira/browse/CB-13536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253630#comment-16253630
]
Jan Piotrowski (Sujan) edited comment on CB-13536 at 11/15/17 3:31 PM:
---
Yeah, you seem to be messing up some things in your rant here. The default
install location of npm on Windows is in Roaming. That's why nvm-windows
explicitly tells you to delete that in the README so it can move all future
installs to your chosen nvm install path.
The rest I didn't really understand (or read tbh). It works fine for me and the
hundreds of users it helped to solve npm foo in the last few months.
> nvm_cordova_create.png
If you just installed that node version, you shouldn't even be able to run
`cordova create` on the command line without installing it with `-g`, correct?
I tried to reproduce locally, couldn't even with @ in folder name:
{code}
PS C:\> cd foo
PS C:\foo> cordova create bar
Creating a new cordova project.
PS C:\foo> cd ..
PS C:\> cd .\@foo\
PS C:\@foo> cordova create bar
Creating a new cordova project.
PS C:\@foo>
{code}
Can you just try if `cordova create` works in a normal folder, with a normal
global Cordova install?
was (Author: sujan12):
Yeah, you seem to be messing up some things in your rant here. The default
install location of npm on Windows in in Roaming. That's why nvm-windows
explicitly tells you to delete that so it can move all future installs to your
chosen nvm install path. The rest I didn't really understand (or read tbh).
> nvm_cordova_create.png
If you just installed that node version, you shouldn't even be able to run
`cordova create` on the command line without installing it with `-g`, correct?
I tried to reproduce locally, couldn't even with @ in folder name:
{code}
PS C:\> cd foo
PS C:\foo> cordova create bar
Creating a new cordova project.
PS C:\foo> cd ..
PS C:\> cd .\@foo\
PS C:\@foo> cordova create bar
Creating a new cordova project.
PS C:\@foo>
{code}
Can you just try if `cordova create` works in a normal folder, with a normal
global Cordova install?
> cordova being called from "quasar wrap" not working - cordova-realted error:
> Could not install from (path_of_nodejs_modules) as it does not contain a
> package.json file
> ---
>
> Key: CB-13536
> URL: https://issues.apache.org/jira/browse/CB-13536
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-app-hello-world, cordova-cli
>Reporter: Lukas Plachy
> Attachments: 2017-11-03T12_42_43_016Z-debug_anonymized.log,
> 2017-11-14T14_08_29_042Z-debug.log, cordova_create_cordova.png,
> cordova_create_on_empty.png, cordova_wrap_fail.png, nvm_cordova_create.png,
> nvm_install.png
>
>
> Hi, anybody an idea, whats wrong here (see attached image), before I'll have
> to make a deepdive into the sources? Such error does not help when doing
> first hands-on!
> Note: has been reported to and rejected by quasar as not quasar-related.
> Thanks
> [^cordova_wrap_fail.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] [Comment Edited] (CB-13536) cordova being called from "quasar wrap" not working - cordova-realted error: Could not install from (path_of_nodejs_modules) as it does not contain a package.json fi
[
https://issues.apache.org/jira/browse/CB-13536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253630#comment-16253630
]
Jan Piotrowski (Sujan) edited comment on CB-13536 at 11/15/17 3:30 PM:
---
Yeah, you seem to be messing up some things in your rant here. The default
install location of npm on Windows in in Roaming. That's why nvm-windows
explicitly tells you to delete that so it can move all future installs to your
chosen nvm install path. The rest I didn't really understand (or read tbh).
> nvm_cordova_create.png
If you just installed that node version, you shouldn't even be able to run
`cordova create` on the command line without installing it with `-g`, correct?
I tried to reproduce locally, couldn't even with @ in folder name:
{code}
PS C:\> cd foo
PS C:\foo> cordova create bar
Creating a new cordova project.
PS C:\foo> cd ..
PS C:\> cd .\@foo\
PS C:\@foo> cordova create bar
Creating a new cordova project.
PS C:\@foo>
{code}
Can you just try if `cordova create` works in a normal folder, with a normal
global Cordova install?
was (Author: sujan12):
Yeah, you seem to be messing up some things in your rant here. The default
install location of npm on Windows in in Roaming. That's why nvm-windows
explicitly tells you to delete that so it can move all future installs to your
chosen nvm install path. The rest I didn't really understand (or read tbh).
> nvm_cordova_create.png
If you just installed that node version, you shouldn't even be able to run
`cordova create` on the command line without installing it with `-g`, correct?
I tried to reproduce locally, couldn't even with @ in folder name:
{code}
PS C:\> cd foo
PS C:\foo> cordova create bar
Creating a new cordova project.
PS C:\foo> cd ..
PS C:\> cd .\@foo\
PS C:\@foo> cordova create bar
Creating a new cordova project.
PS C:\@foo>
{code}
Can you just try if `cordova create` works in a normal folder, with a normal
global Cordova install?
> cordova being called from "quasar wrap" not working - cordova-realted error:
> Could not install from (path_of_nodejs_modules) as it does not contain a
> package.json file
> ---
>
> Key: CB-13536
> URL: https://issues.apache.org/jira/browse/CB-13536
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-app-hello-world, cordova-cli
>Reporter: Lukas Plachy
> Attachments: 2017-11-03T12_42_43_016Z-debug_anonymized.log,
> 2017-11-14T14_08_29_042Z-debug.log, cordova_create_cordova.png,
> cordova_create_on_empty.png, cordova_wrap_fail.png, nvm_cordova_create.png,
> nvm_install.png
>
>
> Hi, anybody an idea, whats wrong here (see attached image), before I'll have
> to make a deepdive into the sources? Such error does not help when doing
> first hands-on!
> Note: has been reported to and rejected by quasar as not quasar-related.
> Thanks
> [^cordova_wrap_fail.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] [Comment Edited] (CB-13536) cordova being called from "quasar wrap" not working - cordova-realted error: Could not install from (path_of_nodejs_modules) as it does not contain a package.json fi
[
https://issues.apache.org/jira/browse/CB-13536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253630#comment-16253630
]
Jan Piotrowski (Sujan) edited comment on CB-13536 at 11/15/17 3:30 PM:
---
Yeah, you seem to be messing up some things in your rant here. The default
install location of npm on Windows in in Roaming. That's why nvm-windows
explicitly tells you to delete that so it can move all future installs to your
chosen nvm install path. The rest I didn't really understand (or read tbh).
> nvm_cordova_create.png
If you just installed that node version, you shouldn't even be able to run
`cordova create` on the command line without installing it with `-g`, correct?
I tried to reproduce locally, couldn't even with @ in folder name:
{code}
PS C:\> cd foo
PS C:\foo> cordova create bar
Creating a new cordova project.
PS C:\foo> cd ..
PS C:\> cd .\@foo\
PS C:\@foo> cordova create bar
Creating a new cordova project.
PS C:\@foo>
{code}
Can you just try if `cordova create` works in a normal folder, with a normal
global Cordova install?
was (Author: sujan12):
Yeah, you seem to be messing up some things in your rant here. The default
install location of npm on Windows in in Roaming. That's why nvm-windows
explicitly tells you to delete that so it can move all future installs to your
chosen nvm install path. The rest I didn't really understand.
> nvm_cordova_create.png
If you just installed that node version, you shouldn't even be able to run
`cordova create` on the command line without installing it with `-g`, correct?
I tried to reproduce locally, couldn't even with @ in folder name:
{code}
PS C:\> cd foo
PS C:\foo> cordova create bar
Creating a new cordova project.
PS C:\foo> cd ..
PS C:\> cd .\@foo\
PS C:\@foo> cordova create bar
Creating a new cordova project.
PS C:\@foo>
{code}
Can you just try if `cordova create` works in a normal folder, with a normal
global Cordova install?
> cordova being called from "quasar wrap" not working - cordova-realted error:
> Could not install from (path_of_nodejs_modules) as it does not contain a
> package.json file
> ---
>
> Key: CB-13536
> URL: https://issues.apache.org/jira/browse/CB-13536
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-app-hello-world, cordova-cli
>Reporter: Lukas Plachy
> Attachments: 2017-11-03T12_42_43_016Z-debug_anonymized.log,
> 2017-11-14T14_08_29_042Z-debug.log, cordova_create_cordova.png,
> cordova_create_on_empty.png, cordova_wrap_fail.png, nvm_cordova_create.png,
> nvm_install.png
>
>
> Hi, anybody an idea, whats wrong here (see attached image), before I'll have
> to make a deepdive into the sources? Such error does not help when doing
> first hands-on!
> Note: has been reported to and rejected by quasar as not quasar-related.
> Thanks
> [^cordova_wrap_fail.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-13536) cordova being called from "quasar wrap" not working - cordova-realted error: Could not install from (path_of_nodejs_modules) as it does not contain a package.json file
[
https://issues.apache.org/jira/browse/CB-13536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253630#comment-16253630
]
Jan Piotrowski (Sujan) commented on CB-13536:
-
Yeah, you seem to be messing up some things in your rant here. The default
install location of npm on Windows in in Roaming. That's why nvm-windows
explicitly tells you to delete that so it can move all future installs to your
chosen nvm install path. The rest I didn't really understand.
> nvm_cordova_create.png
If you just installed that node version, you shouldn't even be able to run
`cordova create` on the command line without installing it with `-g`, correct?
I tried to reproduce locally, couldn't even with @ in folder name:
{code}
PS C:\> cd foo
PS C:\foo> cordova create bar
Creating a new cordova project.
PS C:\foo> cd ..
PS C:\> cd .\@foo\
PS C:\@foo> cordova create bar
Creating a new cordova project.
PS C:\@foo>
{code}
Can you just try if `cordova create` works in a normal folder, with a normal
global Cordova install?
> cordova being called from "quasar wrap" not working - cordova-realted error:
> Could not install from (path_of_nodejs_modules) as it does not contain a
> package.json file
> ---
>
> Key: CB-13536
> URL: https://issues.apache.org/jira/browse/CB-13536
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-app-hello-world, cordova-cli
>Reporter: Lukas Plachy
> Attachments: 2017-11-03T12_42_43_016Z-debug_anonymized.log,
> 2017-11-14T14_08_29_042Z-debug.log, cordova_create_cordova.png,
> cordova_create_on_empty.png, cordova_wrap_fail.png, nvm_cordova_create.png,
> nvm_install.png
>
>
> Hi, anybody an idea, whats wrong here (see attached image), before I'll have
> to make a deepdive into the sources? Such error does not help when doing
> first hands-on!
> Note: has been reported to and rejected by quasar as not quasar-related.
> Thanks
> [^cordova_wrap_fail.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-13536) cordova being called from "quasar wrap" not working - cordova-realted error: Could not install from (path_of_nodejs_modules) as it does not contain a package.json file
[ https://issues.apache.org/jira/browse/CB-13536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253583#comment-16253583 ] Lukas Plachy commented on CB-13536: --- > nvm prerequisites: because this is only a blind branch of this dialogue > (since its content is not directly related to this cordova issue), adding > just a few of my opinions on the end of this post. > the VBScript error reporting: no, and honsetly at this point I have not more > resources to do so (including the opinions on how the nvm behaves I'm > mentioning above), maybe after we solve this entire issue. Btw the error is > stating, that there is no scripting engine for a ".vbs", which might be also > some setting on my PC, however Im running VBScripts here with wscript, so it > will rather be some odd way how to call it > testing the same with nodejs v 8.9.1. ... the error of cordova is the same, > see record [^nvm_cordova_create.png] (BRACKET: A few opinion on the nvm at first glance) - trying to install itself into "Roaming" by default - WRONG That is not a place for installing software or for any large files. The Roaming MUST BE ALLWAYS kept under 100MB (and that is allready an extreme) otherwise it completly destroys the usability of a Windows domain (if present, fortunately not on my PC, but that does not matter). (BTW the 'npm -g' uses the very same antipattern, completly ignoring the root directory where the nodejs+npm is installed and installing the package whose install was started with the '-g' param blindly into the "Roaming"!) - Noting and using its own base/home/root path into some register? system cmdline variable? or anywhere else? (seems to be %NVM_HOME%) while still having the "root" setting in "settings.txt". WRONG! If the settings.txt have the feature to set the "base path" (the 'root:' option), than IT MUST !NOT! BE, that the settings.txt are being searched based on some wacko setting (commandline var, register etc.). Moreover, if such alternate setting is used, then the settings.txt MUST in their default state use it, mening something like "root:%NVM_HOME%" or "root: //HKLM/...//MyKey" instead of creating a 'non-linked information' (eg. containing the same value, but not linked to the other container containing the very same value)! - no information about forcing any other path to settings.txt as cmdline arg in the 'nvm /?' help output text!!! Moreover, if the path (from %NVM_HOME% or somewhere else) of settings.txt is not found, then even the 'nvm /?' does not run!!! Good Lord! NEVER EVER must the '/?' (or '--help' in Linux) argument rely on anything other that the most basic I/O of the environment of the system. (BRACKET end) > cordova being called from "quasar wrap" not working - cordova-realted error: > Could not install from (path_of_nodejs_modules) as it does not contain a > package.json file > --- > > Key: CB-13536 > URL: https://issues.apache.org/jira/browse/CB-13536 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-app-hello-world, cordova-cli >Reporter: Lukas Plachy > Attachments: 2017-11-03T12_42_43_016Z-debug_anonymized.log, > 2017-11-14T14_08_29_042Z-debug.log, cordova_create_cordova.png, > cordova_create_on_empty.png, cordova_wrap_fail.png, nvm_cordova_create.png, > nvm_install.png > > > Hi, anybody an idea, whats wrong here (see attached image), before I'll have > to make a deepdive into the sources? Such error does not help when doing > first hands-on! > Note: has been reported to and rejected by quasar as not quasar-related. > Thanks > [^cordova_wrap_fail.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-12863) Can't install plugins from a branch (cordova@7)
[
https://issues.apache.org/jira/browse/CB-12863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253582#comment-16253582
]
Jim Trainor commented on CB-12863:
--
Experiencing the same problem.
{code:java}
cordova --version && git --version && cordova plugin add
https://github.com/apache/cordova-plugins.git\#wkwebview-engine-localhost
7.1.0
git version 2.13.6 (Apple Git-96)
Error: Failed to fetch plugin
https://github.com/apache/cordova-plugins.git#wkwebview-engine-localhost via
registry.
Probably this is either a connection problem, or plugin spec is incorrect.
Check your connection and plugin name/version/URL.
Failed to get absolute path to installed module
{code}
> Can't install plugins from a branch (cordova@7)
> ---
>
> Key: CB-12863
> URL: https://issues.apache.org/jira/browse/CB-12863
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-fetch
> Environment: cordova-cli@7.0.1
> node@4.6.0
>Reporter: Shazron Abdullah
>Assignee: Shazron Abdullah
> Labels: cordova-8.0.0, reproduced, triage
> Fix For: cordova-labs-wkwebview-engine-localhost@0.5.1
>
>
> 1st try:
> {code}
> $ cordova plugin add
> https://github.com/apache/cordova-plugins.git\#wkwebview-engine-localhost
> Installing "cordova-labs-wkwebview-engine-localhost" for ios
> Failed to install 'cordova-labs-wkwebview-engine-localhost': CordovaError:
> Failed to fetch plugin
> https://git-wip-us.apache.org/repos/asf/cordova-plugins.git#local-webserver
> via registry.
> Probably this is either a connection problem, or plugin spec is incorrect.
> Check your connection and plugin name/version/URL.
> Error: npm: Command failed with exit code 254 Error output:
> npm WARN package.json helloworld@1.0.0 No repository field.
> npm WARN package.json helloworld@1.0.0 No README data
> npm ERR! not a package
> /var/folders/40/pyxnqlcj6bn_43qrjp3p0xtwgp/T/npm-28533-ff14b1ee/git-wip-us.apache.org/repos/asf/cordova-plugins.git/local-webserver
> npm ERR! Darwin 16.7.0
> npm ERR! argv "/Users/shazron/.nvm/versions/node/v4.6.0/bin/node"
> "/Users/shazron/.nvm/versions/node/v4.6.0/bin/npm" "install"
> "https://git-wip-us.apache.org/repos/asf/cordova-plugins.git#local-webserver";
> "--save"
> npm ERR! node v4.6.0
> npm ERR! npm v2.15.9
> npm ERR! path
> /var/folders/40/pyxnqlcj6bn_43qrjp3p0xtwgp/T/npm-28533-ff14b1ee/unpack-968d75f9eab2/package.json
> npm ERR! code ENOENT
> npm ERR! errno -2
> npm ERR! syscall open
> npm ERR! enoent ENOENT: no such file or directory, open
> '/var/folders/40/pyxnqlcj6bn_43qrjp3p0xtwgp/T/npm-28533-ff14b1ee/unpack-968d75f9eab2/package.json'
> npm ERR! enoent This is most likely not a problem with npm itself
> npm ERR! enoent and is related to npm not being able to find a file.
> npm ERR! enoent
> npm ERR! Please include the following file with any support request:
> npm ERR! /Users/shazron/Desktop/gtm/node_modules/npm-debug.log
> at
> /Users/shazron/.nvm/versions/node/v4.6.0/lib/node_modules/cordova/node_modules/cordova-lib/src/plugman/fetch.js:205:33
> at _rejected
> (/Users/shazron/.nvm/versions/node/v4.6.0/lib/node_modules/cordova/node_modules/cordova-lib/node_modules/cordova-fetch/node_modules/q/q.js:864:24)
> at
> /Users/shazron/.nvm/versions/node/v4.6.0/lib/node_modules/cordova/node_modules/cordova-lib/node_modules/cordova-fetch/node_modules/q/q.js:890:30
> at Promise.when
> (/Users/shazron/.nvm/versions/node/v4.6.0/lib/node_modules/cordova/node_modules/cordova-lib/node_modules/cordova-fetch/node_modules/q/q.js:1142:31)
> at Promise.promise.promiseDispatch
> (/Users/shazron/.nvm/versions/node/v4.6.0/lib/node_modules/cordova/node_modules/cordova-lib/node_modules/cordova-fetch/node_modules/q/q.js:808:41)
> at
> /Users/shazron/.nvm/versions/node/v4.6.0/lib/node_modules/cordova/node_modules/cordova-lib/node_modules/cordova-fetch/node_modules/q/q.js:624:44
> at runSingle
> (/Users/shazron/.nvm/versions/node/v4.6.0/lib/node_modules/cordova/node_modules/cordova-lib/node_modules/cordova-fetch/node_modules/q/q.js:137:13)
> at flush
> (/Users/shazron/.nvm/versions/node/v4.6.0/lib/node_modules/cordova/node_modules/cordova-lib/node_modules/cordova-fetch/node_modules/q/q.js:125:13)
> at nextTickCallbackWith0Args (node.js:420:9)
> at process._tickCallback (node.js:349:13)
> Error: Failed to fetch plugin
> https://git-wip-us.apache.org/repos/asf/cordova-plugins.git#local-webserver
> via registry.
> Probably this is either a connection problem, or plugin spec is incorrect.
> Check your connection and plugin name/version/URL.
> Error: npm: Command failed with exit code 254 Error output:
> npm WARN package.json helloworld@1.0.0 No repository field.
> npm WARN package.json helloworld@1.0.0 No README data
> npm ERR! not
[jira] [Updated] (CB-13536) cordova being called from "quasar wrap" not working - cordova-realted error: Could not install from (path_of_nodejs_modules) as it does not contain a package.json file
[ https://issues.apache.org/jira/browse/CB-13536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Plachy updated CB-13536: -- Attachment: nvm_cordova_create.png > cordova being called from "quasar wrap" not working - cordova-realted error: > Could not install from (path_of_nodejs_modules) as it does not contain a > package.json file > --- > > Key: CB-13536 > URL: https://issues.apache.org/jira/browse/CB-13536 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-app-hello-world, cordova-cli >Reporter: Lukas Plachy > Attachments: 2017-11-03T12_42_43_016Z-debug_anonymized.log, > 2017-11-14T14_08_29_042Z-debug.log, cordova_create_cordova.png, > cordova_create_on_empty.png, cordova_wrap_fail.png, nvm_cordova_create.png, > nvm_install.png > > > Hi, anybody an idea, whats wrong here (see attached image), before I'll have > to make a deepdive into the sources? Such error does not help when doing > first hands-on! > Note: has been reported to and rejected by quasar as not quasar-related. > Thanks > [^cordova_wrap_fail.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-13536) cordova being called from "quasar wrap" not working - cordova-realted error: Could not install from (path_of_nodejs_modules) as it does not contain a package.json file
[ https://issues.apache.org/jira/browse/CB-13536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253467#comment-16253467 ] Jan Piotrowski (Sujan) commented on CB-13536: - > since it is unable to establish any prerequisites What do these words mean? > moreover it wrecks the nodejs install completly, see attached commandline > record nvm_install.png Node 9.2.0 is 1 day old. (You probably get the same result installing it directly from nodejs.org.) Node doesn't care if npm is ready or not it seems... Installing the recommended 8.9.1 LTS via nvm-windows (which has the same npm) works fine for me: nvm install 8.9.1, nvm use 8.9.1, npm install cordova -g PS: Did you report the mentioned VB Script error to nvm-windows? This shouldn't really happen. > cordova being called from "quasar wrap" not working - cordova-realted error: > Could not install from (path_of_nodejs_modules) as it does not contain a > package.json file > --- > > Key: CB-13536 > URL: https://issues.apache.org/jira/browse/CB-13536 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-app-hello-world, cordova-cli >Reporter: Lukas Plachy > Attachments: 2017-11-03T12_42_43_016Z-debug_anonymized.log, > 2017-11-14T14_08_29_042Z-debug.log, cordova_create_cordova.png, > cordova_create_on_empty.png, cordova_wrap_fail.png, nvm_install.png > > > Hi, anybody an idea, whats wrong here (see attached image), before I'll have > to make a deepdive into the sources? Such error does not help when doing > first hands-on! > Note: has been reported to and rejected by quasar as not quasar-related. > Thanks > [^cordova_wrap_fail.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-10941) captureAudio depends on a recorder app being installed
[ https://issues.apache.org/jira/browse/CB-10941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253442#comment-16253442 ] Andrea Lazzarotto commented on CB-10941: I can confirm this is a serious issue. Also, some recorder apps (see for instance the default recorder in LineageOS) *do not* return the audio file correctly. To be safe, an audio recorder should be implemented like it's done for the iOS plug-in. > captureAudio depends on a recorder app being installed > -- > > Key: CB-10941 > URL: https://issues.apache.org/jira/browse/CB-10941 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-plugin-media-capture > Environment: Marshmallow dev image >Reporter: Richard B Knoll > Labels: android, triaged > > captureAudio, much like captureImage and captureVideo, uses an intent to > perform its action (recording audio). However, Android does not come with an > audio recording app by default. The other two are not an issue since every > phone has a camera app. Right now captureAudio just fails if you don't have > the app installed. Only real solution is to implement an audio recorder. Not > sure if we want to do that or just document this quirk. -- 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-13536) cordova being called from "quasar wrap" not working - cordova-realted error: Could not install from (path_of_nodejs_modules) as it does not contain a package.json fi
[ https://issues.apache.org/jira/browse/CB-13536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253408#comment-16253408 ] Lukas Plachy edited comment on CB-13536 at 11/15/17 1:09 PM: - Uh, so using nvm is a VERY BAD solution, since it is unable to establish any prerequisites and fails even in its own simple commands, moreover it wrecks the nodejs install completly, see attached commandline record [^nvm_install.png] Going for reinstall of nodejs and npm/quasar-cli/cordova manually from the MSI (mean nodejs from the MSI and the others using the npm). (Just for the sake of completness: of course I did an uninstall of nodejs and all its traces from the system before trying the nvm path :-). Addendum: doing 'npm -v' prints 5.5.1., so there is no other binary/version left over. was (Author: rheingold): Uh, so using nvm is a VERY BAD solution, since it is unable to establish any prerequisites and fails even in its own simple commands, moreover it wrecks the nodejs install completly, see attached commandline record [^nvm_install.png] Going for reinstall of nodejs and npm/quasar-cli/cordova manually from the MSI (mean nodejs from the MSI and the others using the npm). (Just for the sake of completness: of course I did an uninstall of nodejs and all its traces from the system before trying the nvm path :-) > cordova being called from "quasar wrap" not working - cordova-realted error: > Could not install from (path_of_nodejs_modules) as it does not contain a > package.json file > --- > > Key: CB-13536 > URL: https://issues.apache.org/jira/browse/CB-13536 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-app-hello-world, cordova-cli >Reporter: Lukas Plachy > Attachments: 2017-11-03T12_42_43_016Z-debug_anonymized.log, > 2017-11-14T14_08_29_042Z-debug.log, cordova_create_cordova.png, > cordova_create_on_empty.png, cordova_wrap_fail.png, nvm_install.png > > > Hi, anybody an idea, whats wrong here (see attached image), before I'll have > to make a deepdive into the sources? Such error does not help when doing > first hands-on! > Note: has been reported to and rejected by quasar as not quasar-related. > Thanks > [^cordova_wrap_fail.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] [Comment Edited] (CB-13536) cordova being called from "quasar wrap" not working - cordova-realted error: Could not install from (path_of_nodejs_modules) as it does not contain a package.json fi
[ https://issues.apache.org/jira/browse/CB-13536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253408#comment-16253408 ] Lukas Plachy edited comment on CB-13536 at 11/15/17 1:07 PM: - Uh, so using nvm is a VERY BAD solution, since it is unable to establish any prerequisites and fails even in its own simple commands, moreover it wrecks the nodejs install completly, see attached commandline record [^nvm_install.png] Going for reinstall of nodejs and npm/quasar-cli/cordova manually from the MSI (mean nodejs from the MSI and the others using the npm). (Just for the sake of completness: of course I did an uninstall of nodejs and all its traces from the system before trying the nvm path :-) was (Author: rheingold): Uh, so using nvm is a VERY BAD solution, since it is unable to establish any prerequisites and fails even in its own simple commands, moreover it wrecks the nodejs install completly, see attached commandline record [^nvm_install.png] Going for reinstall of nodejs and npm/quasar-cli/cordova manually from the MSI (mean nodejs from the MSI and the others using the npm). > cordova being called from "quasar wrap" not working - cordova-realted error: > Could not install from (path_of_nodejs_modules) as it does not contain a > package.json file > --- > > Key: CB-13536 > URL: https://issues.apache.org/jira/browse/CB-13536 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-app-hello-world, cordova-cli >Reporter: Lukas Plachy > Attachments: 2017-11-03T12_42_43_016Z-debug_anonymized.log, > 2017-11-14T14_08_29_042Z-debug.log, cordova_create_cordova.png, > cordova_create_on_empty.png, cordova_wrap_fail.png, nvm_install.png > > > Hi, anybody an idea, whats wrong here (see attached image), before I'll have > to make a deepdive into the sources? Such error does not help when doing > first hands-on! > Note: has been reported to and rejected by quasar as not quasar-related. > Thanks > [^cordova_wrap_fail.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-13578) IntelliJ won't run APK on device due to "test mode"
[ https://issues.apache.org/jira/browse/CB-13578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253415#comment-16253415 ] Jan Piotrowski (Sujan) commented on CB-13578: - This looks relevant: https://stackoverflow.com/a/46661987/252627 > IntelliJ won't run APK on device due to "test mode" > --- > > Key: CB-13578 > URL: https://issues.apache.org/jira/browse/CB-13578 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-android >Affects Versions: 6.4.0 >Reporter: Tom Bell >Assignee: Joe Bowser > > I've upgraded cordova-android to 6.4.0 (`cordova platform update > android@6.4.0`) however now when I try running the app on a device from > within IntelliJ it errors with > *Failure [INSTALL_FAILED_TEST_ONLY: installPackageLI]* -- 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-13536) cordova being called from "quasar wrap" not working - cordova-realted error: Could not install from (path_of_nodejs_modules) as it does not contain a package.json file
[ https://issues.apache.org/jira/browse/CB-13536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253408#comment-16253408 ] Lukas Plachy commented on CB-13536: --- Uh, so using nvm is a VERY BAD solution, since it is unable to establish any prerequisites and fails even in its own simple commands, moreover it wrecks the nodejs install completly, see attached commandline record [^nvm_install.png] Going for reinstall of nodejs and npm/quasar-cli/cordova manually from the MSI (mean nodejs from the MSI and the others using the npm). > cordova being called from "quasar wrap" not working - cordova-realted error: > Could not install from (path_of_nodejs_modules) as it does not contain a > package.json file > --- > > Key: CB-13536 > URL: https://issues.apache.org/jira/browse/CB-13536 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-app-hello-world, cordova-cli >Reporter: Lukas Plachy > Attachments: 2017-11-03T12_42_43_016Z-debug_anonymized.log, > 2017-11-14T14_08_29_042Z-debug.log, cordova_create_cordova.png, > cordova_create_on_empty.png, cordova_wrap_fail.png, nvm_install.png > > > Hi, anybody an idea, whats wrong here (see attached image), before I'll have > to make a deepdive into the sources? Such error does not help when doing > first hands-on! > Note: has been reported to and rejected by quasar as not quasar-related. > Thanks > [^cordova_wrap_fail.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] [Updated] (CB-13536) cordova being called from "quasar wrap" not working - cordova-realted error: Could not install from (path_of_nodejs_modules) as it does not contain a package.json file
[ https://issues.apache.org/jira/browse/CB-13536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Plachy updated CB-13536: -- Attachment: nvm_install.png > cordova being called from "quasar wrap" not working - cordova-realted error: > Could not install from (path_of_nodejs_modules) as it does not contain a > package.json file > --- > > Key: CB-13536 > URL: https://issues.apache.org/jira/browse/CB-13536 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-app-hello-world, cordova-cli >Reporter: Lukas Plachy > Attachments: 2017-11-03T12_42_43_016Z-debug_anonymized.log, > 2017-11-14T14_08_29_042Z-debug.log, cordova_create_cordova.png, > cordova_create_on_empty.png, cordova_wrap_fail.png, nvm_install.png > > > Hi, anybody an idea, whats wrong here (see attached image), before I'll have > to make a deepdive into the sources? Such error does not help when doing > first hands-on! > Note: has been reported to and rejected by quasar as not quasar-related. > Thanks > [^cordova_wrap_fail.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] [Created] (CB-13578) IntelliJ won't run APK on device due to "test mode"
Tom Bell created CB-13578: - Summary: IntelliJ won't run APK on device due to "test mode" Key: CB-13578 URL: https://issues.apache.org/jira/browse/CB-13578 Project: Apache Cordova Issue Type: Bug Components: cordova-android Affects Versions: 6.4.0 Reporter: Tom Bell Assignee: Joe Bowser I've upgraded cordova-android to 6.4.0 (`cordova platform update android@6.4.0`) however now when I try running the app on a device from within IntelliJ it errors with *Failure [INSTALL_FAILED_TEST_ONLY: installPackageLI]* -- 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-13573) Clarify Cordova Android 6.4.0 blog post
[ https://issues.apache.org/jira/browse/CB-13573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253222#comment-16253222 ] ASF GitHub Bot commented on CB-13573: - janpio commented on issue #761: CB-13573: Clarify Cordova Android 6.4.0 blog post URL: https://github.com/apache/cordova-docs/pull/761#issuecomment-344536870 @audreyso Could you have a look at the first failing Travis CI build here please? No idea what is happening and why. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Clarify Cordova Android 6.4.0 blog post > --- > > Key: CB-13573 > URL: https://issues.apache.org/jira/browse/CB-13573 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-docs >Reporter: Jan Piotrowski (Sujan) >Assignee: Jan Piotrowski (Sujan) > > Talked to user that had problems understanding what was actually required of > them (install standalone Gradle) and why this was happening. -- 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-13573) Clarify Cordova Android 6.4.0 blog post
[ https://issues.apache.org/jira/browse/CB-13573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253187#comment-16253187 ] ASF GitHub Bot commented on CB-13573: - janpio commented on issue #761: CB-13573: Clarify Cordova Android 6.4.0 blog post URL: https://github.com/apache/cordova-docs/pull/761#issuecomment-344536870 @audreyso Could you have a look at the first filaing Travis CI build here please? No idea what is happening and why. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Clarify Cordova Android 6.4.0 blog post > --- > > Key: CB-13573 > URL: https://issues.apache.org/jira/browse/CB-13573 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-docs >Reporter: Jan Piotrowski (Sujan) >Assignee: Jan Piotrowski (Sujan) > > Talked to user that had problems understanding what was actually required of > them (install standalone Gradle) and why this was happening. -- 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-13573) Clarify Cordova Android 6.4.0 blog post
[ https://issues.apache.org/jira/browse/CB-13573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253186#comment-16253186 ] ASF GitHub Bot commented on CB-13573: - janpio commented on issue #761: CB-13573: Clarify Cordova Android 6.4.0 blog post URL: https://github.com/apache/cordova-docs/pull/761#issuecomment-344536870 @audreyso Could you have a look at the first filaing Travis CI build here? No idea what is happening and why. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Clarify Cordova Android 6.4.0 blog post > --- > > Key: CB-13573 > URL: https://issues.apache.org/jira/browse/CB-13573 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-docs >Reporter: Jan Piotrowski (Sujan) >Assignee: Jan Piotrowski (Sujan) > > Talked to user that had problems understanding what was actually required of > them (install standalone Gradle) and why this was happening. -- 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-12886) white area where status bar is in iOS 11
[ https://issues.apache.org/jira/browse/CB-12886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253078#comment-16253078 ] Darryl Pogue commented on CB-12886: --- I have a suspicion that this is due to Cordova using a .xib for the main app layout, rather than a .storyboard > white area where status bar is in iOS 11 > > > Key: CB-12886 > URL: https://issues.apache.org/jira/browse/CB-12886 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-ios > Environment: iOS 11 beta 1 >Reporter: Shazron Abdullah > Labels: backlog, ios11 > Fix For: cordova-ios@5.0.0 > > Attachments: ios11.png, screenshot-1.png, screenshot-2.png, > screenshot-3.png, screenshot-4.png, screenshot-5.png, screenshot-6.png > > > See attached screenshot. Using WKWebView plugin, new app. -- 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
