[jira] [Commented] (CB-7015) Support copying a lib-file from the SDK directory
[ https://issues.apache.org/jira/browse/CB-7015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149997#comment-15149997 ] ASF GitHub Bot commented on CB-7015: Github user mbektchiev commented on the pull request: https://github.com/apache/cordova-lib/pull/290#issuecomment-185053836 Won't fix. > Support copying a lib-file from the SDK directory > - > > Key: CB-7015 > URL: https://issues.apache.org/jira/browse/CB-7015 > Project: Apache Cordova > Issue Type: New Feature > Components: Plugman >Reporter: Martin Bektchiev >Assignee: Martin Bektchiev >Priority: Minor > > Many plugins need to refer to JARs from the Android SDK. They currently embed > a copy of the respective files in them and install it into the application's > libs/ directory. This however might create incompatibility issues with other > plugins which may use the same or dependent JARs. > A good alternative would be to be able to specify a relative path to the SDK > directory in as it is now possible with the element > with custom=false. > E.g. > target-dir="libs/" /> > could become > custom="false" /> > in > https://github.com/phonegap-build/PushPlugin/blob/54e59bce6092ec44fe2005c166350fd85e75449b/plugin.xml#L64 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Closed] (CB-7015) Support copying a lib-file from the SDK directory
[ https://issues.apache.org/jira/browse/CB-7015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Bektchiev closed CB-7015. Resolution: Won't Fix > Support copying a lib-file from the SDK directory > - > > Key: CB-7015 > URL: https://issues.apache.org/jira/browse/CB-7015 > Project: Apache Cordova > Issue Type: New Feature > Components: Plugman >Reporter: Martin Bektchiev >Assignee: Martin Bektchiev >Priority: Minor > > Many plugins need to refer to JARs from the Android SDK. They currently embed > a copy of the respective files in them and install it into the application's > libs/ directory. This however might create incompatibility issues with other > plugins which may use the same or dependent JARs. > A good alternative would be to be able to specify a relative path to the SDK > directory in as it is now possible with the element > with custom=false. > E.g. > target-dir="libs/" /> > could become > custom="false" /> > in > https://github.com/phonegap-build/PushPlugin/blob/54e59bce6092ec44fe2005c166350fd85e75449b/plugin.xml#L64 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-7015) Support copying a lib-file from the SDK directory
[ https://issues.apache.org/jira/browse/CB-7015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149995#comment-15149995 ] ASF GitHub Bot commented on CB-7015: Github user mbektchiev closed the pull request at: https://github.com/apache/cordova-lib/pull/290 > Support copying a lib-file from the SDK directory > - > > Key: CB-7015 > URL: https://issues.apache.org/jira/browse/CB-7015 > Project: Apache Cordova > Issue Type: New Feature > Components: Plugman >Reporter: Martin Bektchiev >Assignee: Martin Bektchiev >Priority: Minor > > Many plugins need to refer to JARs from the Android SDK. They currently embed > a copy of the respective files in them and install it into the application's > libs/ directory. This however might create incompatibility issues with other > plugins which may use the same or dependent JARs. > A good alternative would be to be able to specify a relative path to the SDK > directory in as it is now possible with the element > with custom=false. > E.g. > target-dir="libs/" /> > could become > custom="false" /> > in > https://github.com/phonegap-build/PushPlugin/blob/54e59bce6092ec44fe2005c166350fd85e75449b/plugin.xml#L64 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Closed] (CB-8198) Unified console output logic for core platforms
[ https://issues.apache.org/jira/browse/CB-8198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Shakhnazarov closed CB-8198. --- Resolution: Fixed > Unified console output logic for core platforms > --- > > Key: CB-8198 > URL: https://issues.apache.org/jira/browse/CB-8198 > Project: Apache Cordova > Issue Type: New Feature > Components: Android, iOS, Windows, WP8 (deprecated) >Reporter: Vladimir Kotikov >Assignee: Jesse MacFadyen > > Currently all major platform scripts doesn't recognize trace levels and > always logging all their output to console. > This could be unuseful, especially when a huge output from build tools is put > to console (ant build/xcodebuild output is really huge and in most cases is > unnecessary) > I propose to unify the way we write messages to console output: > 1. Pass verbosity arguments (-d, --debug ) downstream to platform scripts. > 2. Introduce special Log class which is shared across platform scripts > * automatically detects trace level according to command line arguments; > * support of output redirection (file, other) in the future? > 3. Add support for the following verbosity levels: Error, Normal, Debug > * by default: Error and Normal messages are traced > * -silent: only Error messages are traced > * -verbose: everything is traced -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Closed] (CB-8199) Add support for verbosity levels for platform scripts
[ https://issues.apache.org/jira/browse/CB-8199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Shakhnazarov closed CB-8199. --- Resolution: Fixed Assignee: (was: Jesse MacFadyen) > Add support for verbosity levels for platform scripts > -- > > Key: CB-8199 > URL: https://issues.apache.org/jira/browse/CB-8199 > Project: Apache Cordova > Issue Type: Sub-task > Components: Android, iOS, Windows, WP8 (deprecated) >Reporter: Vladimir Kotikov > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10595) Windows Store 8.1 builds finish with warning 'Expected undefined to be defined' on running mobilespec storage tests
[ https://issues.apache.org/jira/browse/CB-10595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149984#comment-15149984 ] ASF GitHub Bot commented on CB-10595: - Github user daserge commented on the pull request: https://github.com/apache/cordova-mobile-spec/pull/138#issuecomment-185047527 I believe `HTML 5 Storage`->`storage.spec.9` and `storage.spec.17` can be merged into one spec as they are testing the same thing. > Windows Store 8.1 builds finish with warning 'Expected undefined to be > defined' on running mobilespec storage tests > --- > > Key: CB-10595 > URL: https://issues.apache.org/jira/browse/CB-10595 > Project: Apache Cordova > Issue Type: Test >Reporter: Raghav >Assignee: Sarangan Rajamanickam >Priority: Critical > Labels: found-by-ci, windows-store-8.1 > > Recent build links: > https://ci.apache.org/builders/cordova-windows-store8.1/builds/1601 > https://ci.apache.org/builders/cordova-windows-store8.1/builds/1602 > Build Log: > Getting test results for cordova-windows-store8.1-1601-buildbot-vm > Results at > http://cordova-vm.apache.org:5984/_utils/document.html?mobilespec_results/cordova-windows-store8.1-1601-buildbot-vm__6.3.9600.16384__HP > Z420 Workstation > Total failures: 1 > Failing tests: > org.apache.cordova.mobilespec.tests.storage.tests >> Session Storage HTML > 5 Storage storage.spec.9 should exist > Expected undefined to be defined. > Error: Expected undefined to be defined. >at stack > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:1455:11) >at buildExpectationResult > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:1422:5) >at expectationResultFactory > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:572:11) >at Spec.prototype.addExpectationResult > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:321:5) >at addExpectationResult > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:516:9) >at Anonymous function > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:1379:7) >at Anonymous function > (ms-appx://org.apache.mobilespec/www/plugins/org.apache.cordova.mobilespec.tests/tests/storage.tests.js:183:17) >at attemptSync > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:1741:9) >at QueueRunner.prototype.run > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:1729:9) >at QueueRunner.prototype.execute > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:1714:5) > program finished with exit code 0 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10530) App freezes sometimes directly after starting on iOS
[ https://issues.apache.org/jira/browse/CB-10530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149928#comment-15149928 ] Louis Lor Jr. commented on CB-10530: Thanks for the update! It works perfectly for me, not able to reproduce the freeze again. > App freezes sometimes directly after starting on iOS > > > Key: CB-10530 > URL: https://issues.apache.org/jira/browse/CB-10530 > Project: Apache Cordova > Issue Type: Bug > Components: iOS >Affects Versions: 6.0.0 > Environment: OSX El Capitan 10.11.3, XCODE (7.2.1), iOS 9.2.1, > cordova 6.0.0, ionic 1.7.14 >Reporter: Florian Krüger >Assignee: Shazron Abdullah >Priority: Critical > Labels: cordova-ios-4.1.0, triaged > Attachments: Instruments.trace.zip > > > * Installed the "ionic start myApp sidemenu" example application > * Start XCODE (7.2.1) > * Start the app by clicking the run button from xCODE > * The app probably starts as expected. > * Repeat the start process until the app freezes. > The app sometimes freezes completely. If this happens you cannot do anything > with the app (you need to push the home button and close the app via task > manager). I had the same issue for another more complex app. > The CPU stays at around 99% workload. > I made a snapshot of the profiler (Instruments) > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10598) Unable to run javascript in Cordova iOS project on simulator
[
https://issues.apache.org/jira/browse/CB-10598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149891#comment-15149891
]
Sumit Soman commented on CB-10598:
--
I had asked on stackoverflow, but couldn't get anywhere. Would welcome help.
http://stackoverflow.com/q/35337905/3169868
> Unable to run javascript in Cordova iOS project on simulator
>
>
> Key: CB-10598
> URL: https://issues.apache.org/jira/browse/CB-10598
> Project: Apache Cordova
> Issue Type: Bug
> Components: CordovaJS, iOS
>Affects Versions: 5.4.1
> Environment: Mac OSX El Capitan, Xcode v7.2
>Reporter: Sumit Soman
>
> I created a cordova project, added the iOS platform and built the project.
> After that I opened the .xcodeproj in Xcode, built it and the homepage showed
> the sample app homescreen. I then created another js file with the following
> content in the Staging/js folder
> function testLoad(){
> alert("Loaded!");
> }
> In index.html, I added
>
> and called the function
>
> However no alert appears! How to fix? I am using xCode 7.2.1 and Cordova
> 5.4.1.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Closed] (CB-10550) no plugin id mapper enforced when a version is specified
[
https://issues.apache.org/jira/browse/CB-10550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Byoungro So closed CB-10550.
Resolution: Fixed
> no plugin id mapper enforced when a version is specified
>
>
> Key: CB-10550
> URL: https://issues.apache.org/jira/browse/CB-10550
> Project: Apache Cordova
> Issue Type: Bug
> Components: CordovaLib
>Reporter: Byoungro So
>Assignee: Byoungro So
>
> We now enforce the RDN-to-NPM plugin id mapping in various places in
> CordovaLib.
> This works when there is no version is specified, but does not work when a
> desired version is specified.
> For example, "cordova plugin add org.apache.cordova.device" will install
> cordova-plugin-device.
> However "cordova plugin add org.apache.cordova.device@1.1.1" will throw an
> error message.
> {code}
> [a] cordova plugin add org.apache.cordova.device@1.1.1
> Fetching plugin "org.apache.cordova.device@1.1.1" via npm
> Fetching plugin "org.apache.cordova.device@1.1.1" via cordova plugins registry
> Error: Failed to fetch plugin org.apache.cordova.device@1.1.1 via registry.
> Probably this is either a connection problem, or plugin spec is incorrect.
> Check your connection and plugin name/version/URL.
> Error: version not found: org.apache.cordova.device@1.1.1{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Closed] (CB-10611) --nohooks missed disabling before_plugin_install
[
https://issues.apache.org/jira/browse/CB-10611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Byoungro So closed CB-10611.
Resolution: Fixed
> --nohooks missed disabling before_plugin_install
>
>
> Key: CB-10611
> URL: https://issues.apache.org/jira/browse/CB-10611
> Project: Apache Cordova
> Issue Type: Bug
> Components: CordovaLib
>Reporter: Byoungro So
>Assignee: Byoungro So
>
> --nohooks option does not disable before_plugin_install hook.
> This was missed from CB-8455.
> Here is the test scenario.
> {code}
> [nohooks-test] cordova plugin add cordova-plugin-device --nohooks .
> Fetching plugin "cordova-plugin-device@~1.1.1" via npm
> Installing "cordova-plugin-device" for ios
> Running command:
> /Users/bso/cordova/test/nohooks-test/hooks/before_plugin_install/hook.js
> /Users/bso/cordova/test/nohooks-test
> before plugin install hook executed
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10550) no plugin id mapper enforced when a version is specified
[
https://issues.apache.org/jira/browse/CB-10550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149818#comment-15149818
]
ASF GitHub Bot commented on CB-10550:
-
Github user bso-intel closed the pull request at:
https://github.com/apache/cordova-lib/pull/387
> no plugin id mapper enforced when a version is specified
>
>
> Key: CB-10550
> URL: https://issues.apache.org/jira/browse/CB-10550
> Project: Apache Cordova
> Issue Type: Bug
> Components: CordovaLib
>Reporter: Byoungro So
>Assignee: Byoungro So
>
> We now enforce the RDN-to-NPM plugin id mapping in various places in
> CordovaLib.
> This works when there is no version is specified, but does not work when a
> desired version is specified.
> For example, "cordova plugin add org.apache.cordova.device" will install
> cordova-plugin-device.
> However "cordova plugin add org.apache.cordova.device@1.1.1" will throw an
> error message.
> {code}
> [a] cordova plugin add org.apache.cordova.device@1.1.1
> Fetching plugin "org.apache.cordova.device@1.1.1" via npm
> Fetching plugin "org.apache.cordova.device@1.1.1" via cordova plugins registry
> Error: Failed to fetch plugin org.apache.cordova.device@1.1.1 via registry.
> Probably this is either a connection problem, or plugin spec is incorrect.
> Check your connection and plugin name/version/URL.
> Error: version not found: org.apache.cordova.device@1.1.1{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10550) no plugin id mapper enforced when a version is specified
[
https://issues.apache.org/jira/browse/CB-10550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149802#comment-15149802
]
ASF GitHub Bot commented on CB-10550:
-
Github user TimBarham commented on the pull request:
https://github.com/apache/cordova-lib/pull/387#issuecomment-185005103
Thanks @bso-intel. I've merged this in
https://github.com/apache/cordova-lib/commit/87d8e171, but I rebased on forgot
to add "This closes #387" to the comment, so if you could close this PR
manually that'd be great!
> no plugin id mapper enforced when a version is specified
>
>
> Key: CB-10550
> URL: https://issues.apache.org/jira/browse/CB-10550
> Project: Apache Cordova
> Issue Type: Bug
> Components: CordovaLib
>Reporter: Byoungro So
>Assignee: Byoungro So
>
> We now enforce the RDN-to-NPM plugin id mapping in various places in
> CordovaLib.
> This works when there is no version is specified, but does not work when a
> desired version is specified.
> For example, "cordova plugin add org.apache.cordova.device" will install
> cordova-plugin-device.
> However "cordova plugin add org.apache.cordova.device@1.1.1" will throw an
> error message.
> {code}
> [a] cordova plugin add org.apache.cordova.device@1.1.1
> Fetching plugin "org.apache.cordova.device@1.1.1" via npm
> Fetching plugin "org.apache.cordova.device@1.1.1" via cordova plugins registry
> Error: Failed to fetch plugin org.apache.cordova.device@1.1.1 via registry.
> Probably this is either a connection problem, or plugin spec is incorrect.
> Check your connection and plugin name/version/URL.
> Error: version not found: org.apache.cordova.device@1.1.1{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10550) no plugin id mapper enforced when a version is specified
[
https://issues.apache.org/jira/browse/CB-10550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149800#comment-15149800
]
ASF subversion and git services commented on CB-10550:
--
Commit 87d8e171a1f0eaa252d6d2510190b51bd56d48ae in cordova-lib's branch
refs/heads/master from [~bso]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-lib.git;h=87d8e17 ]
CB-10550 Fix plugin id mapper not enforced when a version is specified
> no plugin id mapper enforced when a version is specified
>
>
> Key: CB-10550
> URL: https://issues.apache.org/jira/browse/CB-10550
> Project: Apache Cordova
> Issue Type: Bug
> Components: CordovaLib
>Reporter: Byoungro So
>Assignee: Byoungro So
>
> We now enforce the RDN-to-NPM plugin id mapping in various places in
> CordovaLib.
> This works when there is no version is specified, but does not work when a
> desired version is specified.
> For example, "cordova plugin add org.apache.cordova.device" will install
> cordova-plugin-device.
> However "cordova plugin add org.apache.cordova.device@1.1.1" will throw an
> error message.
> {code}
> [a] cordova plugin add org.apache.cordova.device@1.1.1
> Fetching plugin "org.apache.cordova.device@1.1.1" via npm
> Fetching plugin "org.apache.cordova.device@1.1.1" via cordova plugins registry
> Error: Failed to fetch plugin org.apache.cordova.device@1.1.1 via registry.
> Probably this is either a connection problem, or plugin spec is incorrect.
> Check your connection and plugin name/version/URL.
> Error: version not found: org.apache.cordova.device@1.1.1{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10595) Windows Store 8.1 builds finish with warning 'Expected undefined to be defined' on running mobilespec storage tests
[ https://issues.apache.org/jira/browse/CB-10595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149788#comment-15149788 ] ASF GitHub Bot commented on CB-10595: - Github user dblotsky commented on the pull request: https://github.com/apache/cordova-mobile-spec/pull/138#issuecomment-185000962 LGTM. > Windows Store 8.1 builds finish with warning 'Expected undefined to be > defined' on running mobilespec storage tests > --- > > Key: CB-10595 > URL: https://issues.apache.org/jira/browse/CB-10595 > Project: Apache Cordova > Issue Type: Test >Reporter: Raghav >Assignee: Sarangan Rajamanickam >Priority: Critical > Labels: found-by-ci, windows-store-8.1 > > Recent build links: > https://ci.apache.org/builders/cordova-windows-store8.1/builds/1601 > https://ci.apache.org/builders/cordova-windows-store8.1/builds/1602 > Build Log: > Getting test results for cordova-windows-store8.1-1601-buildbot-vm > Results at > http://cordova-vm.apache.org:5984/_utils/document.html?mobilespec_results/cordova-windows-store8.1-1601-buildbot-vm__6.3.9600.16384__HP > Z420 Workstation > Total failures: 1 > Failing tests: > org.apache.cordova.mobilespec.tests.storage.tests >> Session Storage HTML > 5 Storage storage.spec.9 should exist > Expected undefined to be defined. > Error: Expected undefined to be defined. >at stack > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:1455:11) >at buildExpectationResult > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:1422:5) >at expectationResultFactory > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:572:11) >at Spec.prototype.addExpectationResult > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:321:5) >at addExpectationResult > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:516:9) >at Anonymous function > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:1379:7) >at Anonymous function > (ms-appx://org.apache.mobilespec/www/plugins/org.apache.cordova.mobilespec.tests/tests/storage.tests.js:183:17) >at attemptSync > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:1741:9) >at QueueRunner.prototype.run > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:1729:9) >at QueueRunner.prototype.execute > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:1714:5) > program finished with exit code 0 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10611) --nohooks missed disabling before_plugin_install
[
https://issues.apache.org/jira/browse/CB-10611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149784#comment-15149784
]
ASF GitHub Bot commented on CB-10611:
-
Github user bso-intel commented on the pull request:
https://github.com/apache/cordova-lib/pull/388#issuecomment-184999128
Thank you very much, Tim.
> --nohooks missed disabling before_plugin_install
>
>
> Key: CB-10611
> URL: https://issues.apache.org/jira/browse/CB-10611
> Project: Apache Cordova
> Issue Type: Bug
> Components: CordovaLib
>Reporter: Byoungro So
>Assignee: Byoungro So
>
> --nohooks option does not disable before_plugin_install hook.
> This was missed from CB-8455.
> Here is the test scenario.
> {code}
> [nohooks-test] cordova plugin add cordova-plugin-device --nohooks .
> Fetching plugin "cordova-plugin-device@~1.1.1" via npm
> Installing "cordova-plugin-device" for ios
> Running command:
> /Users/bso/cordova/test/nohooks-test/hooks/before_plugin_install/hook.js
> /Users/bso/cordova/test/nohooks-test
> before plugin install hook executed
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10550) no plugin id mapper enforced when a version is specified
[
https://issues.apache.org/jira/browse/CB-10550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149783#comment-15149783
]
ASF GitHub Bot commented on CB-10550:
-
Github user bso-intel commented on the pull request:
https://github.com/apache/cordova-lib/pull/387#issuecomment-184998947
Hi @TimBarham
Thanks for reviewing this pull request.
I updated the comment as you requested.
> no plugin id mapper enforced when a version is specified
>
>
> Key: CB-10550
> URL: https://issues.apache.org/jira/browse/CB-10550
> Project: Apache Cordova
> Issue Type: Bug
> Components: CordovaLib
>Reporter: Byoungro So
>Assignee: Byoungro So
>
> We now enforce the RDN-to-NPM plugin id mapping in various places in
> CordovaLib.
> This works when there is no version is specified, but does not work when a
> desired version is specified.
> For example, "cordova plugin add org.apache.cordova.device" will install
> cordova-plugin-device.
> However "cordova plugin add org.apache.cordova.device@1.1.1" will throw an
> error message.
> {code}
> [a] cordova plugin add org.apache.cordova.device@1.1.1
> Fetching plugin "org.apache.cordova.device@1.1.1" via npm
> Fetching plugin "org.apache.cordova.device@1.1.1" via cordova plugins registry
> Error: Failed to fetch plugin org.apache.cordova.device@1.1.1 via registry.
> Probably this is either a connection problem, or plugin spec is incorrect.
> Check your connection and plugin name/version/URL.
> Error: version not found: org.apache.cordova.device@1.1.1{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-10595) Windows Store 8.1 builds finish with warning 'Expected undefined to be defined' on running mobilespec storage tests
[ https://issues.apache.org/jira/browse/CB-10595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sarangan Rajamanickam resolved CB-10595. Resolution: Fixed > Windows Store 8.1 builds finish with warning 'Expected undefined to be > defined' on running mobilespec storage tests > --- > > Key: CB-10595 > URL: https://issues.apache.org/jira/browse/CB-10595 > Project: Apache Cordova > Issue Type: Test >Reporter: Raghav >Assignee: Sarangan Rajamanickam >Priority: Critical > Labels: found-by-ci, windows-store-8.1 > > Recent build links: > https://ci.apache.org/builders/cordova-windows-store8.1/builds/1601 > https://ci.apache.org/builders/cordova-windows-store8.1/builds/1602 > Build Log: > Getting test results for cordova-windows-store8.1-1601-buildbot-vm > Results at > http://cordova-vm.apache.org:5984/_utils/document.html?mobilespec_results/cordova-windows-store8.1-1601-buildbot-vm__6.3.9600.16384__HP > Z420 Workstation > Total failures: 1 > Failing tests: > org.apache.cordova.mobilespec.tests.storage.tests >> Session Storage HTML > 5 Storage storage.spec.9 should exist > Expected undefined to be defined. > Error: Expected undefined to be defined. >at stack > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:1455:11) >at buildExpectationResult > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:1422:5) >at expectationResultFactory > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:572:11) >at Spec.prototype.addExpectationResult > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:321:5) >at addExpectationResult > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:516:9) >at Anonymous function > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:1379:7) >at Anonymous function > (ms-appx://org.apache.mobilespec/www/plugins/org.apache.cordova.mobilespec.tests/tests/storage.tests.js:183:17) >at attemptSync > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:1741:9) >at QueueRunner.prototype.run > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:1729:9) >at QueueRunner.prototype.execute > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:1714:5) > program finished with exit code 0 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10595) Windows Store 8.1 builds finish with warning 'Expected undefined to be defined' on running mobilespec storage tests
[ https://issues.apache.org/jira/browse/CB-10595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149613#comment-15149613 ] ASF GitHub Bot commented on CB-10595: - Github user asfgit closed the pull request at: https://github.com/apache/cordova-mobile-spec/pull/138 > Windows Store 8.1 builds finish with warning 'Expected undefined to be > defined' on running mobilespec storage tests > --- > > Key: CB-10595 > URL: https://issues.apache.org/jira/browse/CB-10595 > Project: Apache Cordova > Issue Type: Test >Reporter: Raghav >Assignee: Sarangan Rajamanickam >Priority: Critical > Labels: found-by-ci, windows-store-8.1 > > Recent build links: > https://ci.apache.org/builders/cordova-windows-store8.1/builds/1601 > https://ci.apache.org/builders/cordova-windows-store8.1/builds/1602 > Build Log: > Getting test results for cordova-windows-store8.1-1601-buildbot-vm > Results at > http://cordova-vm.apache.org:5984/_utils/document.html?mobilespec_results/cordova-windows-store8.1-1601-buildbot-vm__6.3.9600.16384__HP > Z420 Workstation > Total failures: 1 > Failing tests: > org.apache.cordova.mobilespec.tests.storage.tests >> Session Storage HTML > 5 Storage storage.spec.9 should exist > Expected undefined to be defined. > Error: Expected undefined to be defined. >at stack > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:1455:11) >at buildExpectationResult > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:1422:5) >at expectationResultFactory > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:572:11) >at Spec.prototype.addExpectationResult > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:321:5) >at addExpectationResult > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:516:9) >at Anonymous function > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:1379:7) >at Anonymous function > (ms-appx://org.apache.mobilespec/www/plugins/org.apache.cordova.mobilespec.tests/tests/storage.tests.js:183:17) >at attemptSync > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:1741:9) >at QueueRunner.prototype.run > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:1729:9) >at QueueRunner.prototype.execute > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:1714:5) > program finished with exit code 0 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10595) Windows Store 8.1 builds finish with warning 'Expected undefined to be defined' on running mobilespec storage tests
[ https://issues.apache.org/jira/browse/CB-10595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149611#comment-15149611 ] ASF subversion and git services commented on CB-10595: -- Commit 6d4a2b768b966a0efe1e4a89f528dcc65db5006e in cordova-mobile-spec's branch refs/heads/master from [~sarangan12] [ https://git-wip-us.apache.org/repos/asf?p=cordova-mobile-spec.git;h=6d4a2b7 ] CB-10595: Windows Store 8.1 builds finish with warning 'Expected undefined to be defined' on running mobilespec storage tests IE does not support openDatabase method. So, marking the test as pending. > Windows Store 8.1 builds finish with warning 'Expected undefined to be > defined' on running mobilespec storage tests > --- > > Key: CB-10595 > URL: https://issues.apache.org/jira/browse/CB-10595 > Project: Apache Cordova > Issue Type: Test >Reporter: Raghav >Assignee: Sarangan Rajamanickam >Priority: Critical > Labels: found-by-ci, windows-store-8.1 > > Recent build links: > https://ci.apache.org/builders/cordova-windows-store8.1/builds/1601 > https://ci.apache.org/builders/cordova-windows-store8.1/builds/1602 > Build Log: > Getting test results for cordova-windows-store8.1-1601-buildbot-vm > Results at > http://cordova-vm.apache.org:5984/_utils/document.html?mobilespec_results/cordova-windows-store8.1-1601-buildbot-vm__6.3.9600.16384__HP > Z420 Workstation > Total failures: 1 > Failing tests: > org.apache.cordova.mobilespec.tests.storage.tests >> Session Storage HTML > 5 Storage storage.spec.9 should exist > Expected undefined to be defined. > Error: Expected undefined to be defined. >at stack > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:1455:11) >at buildExpectationResult > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:1422:5) >at expectationResultFactory > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:572:11) >at Spec.prototype.addExpectationResult > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:321:5) >at addExpectationResult > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:516:9) >at Anonymous function > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:1379:7) >at Anonymous function > (ms-appx://org.apache.mobilespec/www/plugins/org.apache.cordova.mobilespec.tests/tests/storage.tests.js:183:17) >at attemptSync > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:1741:9) >at QueueRunner.prototype.run > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:1729:9) >at QueueRunner.prototype.execute > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:1714:5) > program finished with exit code 0 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10595) Windows Store 8.1 builds finish with warning 'Expected undefined to be defined' on running mobilespec storage tests
[ https://issues.apache.org/jira/browse/CB-10595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149585#comment-15149585 ] ASF GitHub Bot commented on CB-10595: - Github user rakatyal commented on the pull request: https://github.com/apache/cordova-mobile-spec/pull/138#issuecomment-184941366 LGTM! > Windows Store 8.1 builds finish with warning 'Expected undefined to be > defined' on running mobilespec storage tests > --- > > Key: CB-10595 > URL: https://issues.apache.org/jira/browse/CB-10595 > Project: Apache Cordova > Issue Type: Test >Reporter: Raghav >Assignee: Sarangan Rajamanickam >Priority: Critical > Labels: found-by-ci, windows-store-8.1 > > Recent build links: > https://ci.apache.org/builders/cordova-windows-store8.1/builds/1601 > https://ci.apache.org/builders/cordova-windows-store8.1/builds/1602 > Build Log: > Getting test results for cordova-windows-store8.1-1601-buildbot-vm > Results at > http://cordova-vm.apache.org:5984/_utils/document.html?mobilespec_results/cordova-windows-store8.1-1601-buildbot-vm__6.3.9600.16384__HP > Z420 Workstation > Total failures: 1 > Failing tests: > org.apache.cordova.mobilespec.tests.storage.tests >> Session Storage HTML > 5 Storage storage.spec.9 should exist > Expected undefined to be defined. > Error: Expected undefined to be defined. >at stack > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:1455:11) >at buildExpectationResult > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:1422:5) >at expectationResultFactory > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:572:11) >at Spec.prototype.addExpectationResult > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:321:5) >at addExpectationResult > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:516:9) >at Anonymous function > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:1379:7) >at Anonymous function > (ms-appx://org.apache.mobilespec/www/plugins/org.apache.cordova.mobilespec.tests/tests/storage.tests.js:183:17) >at attemptSync > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:1741:9) >at QueueRunner.prototype.run > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:1729:9) >at QueueRunner.prototype.execute > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:1714:5) > program finished with exit code 0 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10530) App freezes sometimes directly after starting on iOS
[ https://issues.apache.org/jira/browse/CB-10530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149528#comment-15149528 ] Shazron Abdullah commented on CB-10530: --- Done > App freezes sometimes directly after starting on iOS > > > Key: CB-10530 > URL: https://issues.apache.org/jira/browse/CB-10530 > Project: Apache Cordova > Issue Type: Bug > Components: iOS >Affects Versions: 6.0.0 > Environment: OSX El Capitan 10.11.3, XCODE (7.2.1), iOS 9.2.1, > cordova 6.0.0, ionic 1.7.14 >Reporter: Florian Krüger >Assignee: Shazron Abdullah >Priority: Critical > Labels: cordova-ios-4.1.0, triaged > Attachments: Instruments.trace.zip > > > * Installed the "ionic start myApp sidemenu" example application > * Start XCODE (7.2.1) > * Start the app by clicking the run button from xCODE > * The app probably starts as expected. > * Repeat the start process until the app freezes. > The app sometimes freezes completely. If this happens you cannot do anything > with the app (you need to push the home button and close the app via task > manager). I had the same issue for another more complex app. > The CPU stays at around 99% workload. > I made a snapshot of the profiler (Instruments) > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10530) App freezes sometimes directly after starting on iOS
[ https://issues.apache.org/jira/browse/CB-10530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149523#comment-15149523 ] Shazron Abdullah commented on CB-10530: --- Sorry give me half an hour - i forgot to re-generate cordova.js > App freezes sometimes directly after starting on iOS > > > Key: CB-10530 > URL: https://issues.apache.org/jira/browse/CB-10530 > Project: Apache Cordova > Issue Type: Bug > Components: iOS >Affects Versions: 6.0.0 > Environment: OSX El Capitan 10.11.3, XCODE (7.2.1), iOS 9.2.1, > cordova 6.0.0, ionic 1.7.14 >Reporter: Florian Krüger >Assignee: Shazron Abdullah >Priority: Critical > Labels: cordova-ios-4.1.0, triaged > Attachments: Instruments.trace.zip > > > * Installed the "ionic start myApp sidemenu" example application > * Start XCODE (7.2.1) > * Start the app by clicking the run button from xCODE > * The app probably starts as expected. > * Repeat the start process until the app freezes. > The app sometimes freezes completely. If this happens you cannot do anything > with the app (you need to push the home button and close the app via task > manager). I had the same issue for another more complex app. > The CPU stays at around 99% workload. > I made a snapshot of the profiler (Instruments) > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10530) App freezes sometimes directly after starting on iOS
[
https://issues.apache.org/jira/browse/CB-10530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149506#comment-15149506
]
Shazron Abdullah commented on CB-10530:
---
Pull request sent.
Please test by adding the platform:
{code}
cordova platform add https://github.com/shazron/cordova-ios.git#CB-10530
{code}
> App freezes sometimes directly after starting on iOS
>
>
> Key: CB-10530
> URL: https://issues.apache.org/jira/browse/CB-10530
> Project: Apache Cordova
> Issue Type: Bug
> Components: iOS
>Affects Versions: 6.0.0
> Environment: OSX El Capitan 10.11.3, XCODE (7.2.1), iOS 9.2.1,
> cordova 6.0.0, ionic 1.7.14
>Reporter: Florian Krüger
>Assignee: Shazron Abdullah
>Priority: Critical
> Labels: cordova-ios-4.1.0, triaged
> Attachments: Instruments.trace.zip
>
>
> * Installed the "ionic start myApp sidemenu" example application
> * Start XCODE (7.2.1)
> * Start the app by clicking the run button from xCODE
> * The app probably starts as expected.
> * Repeat the start process until the app freezes.
> The app sometimes freezes completely. If this happens you cannot do anything
> with the app (you need to push the home button and close the app via task
> manager). I had the same issue for another more complex app.
> The CPU stays at around 99% workload.
> I made a snapshot of the profiler (Instruments)
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10530) App freezes sometimes directly after starting on iOS
[ https://issues.apache.org/jira/browse/CB-10530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149503#comment-15149503 ] ASF GitHub Bot commented on CB-10530: - GitHub user shazron opened a pull request: https://github.com/apache/cordova-ios/pull/193 CB-10530 - App freezes sometimes directly after starting on iOS You can merge this pull request into a Git repository by running: $ git pull https://github.com/shazron/cordova-ios CB-10530 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-ios/pull/193.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #193 commit 7d6bc772e06999f62cea39bbb87f1508860d5cb6 Author: Shazron Abdullah Date: 2016-02-16T23:26:24Z CB-10530 - App freezes sometimes directly after starting on iOS > App freezes sometimes directly after starting on iOS > > > Key: CB-10530 > URL: https://issues.apache.org/jira/browse/CB-10530 > Project: Apache Cordova > Issue Type: Bug > Components: iOS >Affects Versions: 6.0.0 > Environment: OSX El Capitan 10.11.3, XCODE (7.2.1), iOS 9.2.1, > cordova 6.0.0, ionic 1.7.14 >Reporter: Florian Krüger >Assignee: Shazron Abdullah >Priority: Critical > Labels: cordova-ios-4.1.0, triaged > Attachments: Instruments.trace.zip > > > * Installed the "ionic start myApp sidemenu" example application > * Start XCODE (7.2.1) > * Start the app by clicking the run button from xCODE > * The app probably starts as expected. > * Repeat the start process until the app freezes. > The app sometimes freezes completely. If this happens you cannot do anything > with the app (you need to push the home button and close the app via task > manager). I had the same issue for another more complex app. > The CPU stays at around 99% workload. > I made a snapshot of the profiler (Instruments) > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10631) device is not populated in iOS 5.1.1
[ https://issues.apache.org/jira/browse/CB-10631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149498#comment-15149498 ] ASF GitHub Bot commented on CB-10631: - GitHub user agilethomas opened a pull request: https://github.com/apache/cordova-plugin-device/pull/49 CB-10631 ios: Fix for device.uuid in iOS 5.1.1 - Check if identifierForVendor exists and if not create a new UUID and store in on the device for future use. You can merge this pull request into a Git repository by running: $ git pull https://github.com/agilethomas/cordova-plugin-device CB-10631cordova-plugin-device Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-plugin-device/pull/49.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #49 commit b31206dd6566548337a63c26b87f4c03fcaacbad Author: Thomas Allen Date: 2016-02-16T20:12:24Z CB-10631 ios: Fix for device.uuid in iOS 5.1.1 - Check if identifierForVendor exists and if not create a new UUID and store in on the device for future use. > device is not populated in iOS 5.1.1 > > > Key: CB-10631 > URL: https://issues.apache.org/jira/browse/CB-10631 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Device > Environment: iOS 5.1.1 >Reporter: Thomas Allen > Original Estimate: 0h > Remaining Estimate: 0h > > The device plugin doesn't work in iOS 5.1.1 because the unique device > identifier uses identifierForVendor to get the device uuid. However this is > not valid in iOS older than 6.0. > In the method uniqueAppInstanceIdentifier, there is a reference to > maintaining backward compatibility for versions that didn't use > identiferForVendor. Unfortunately the code only works if the app had > previously been installed on that device (because it looks for the CDVUUID > that was previously stored on the device). If the install is new, this > app_uuid is nil and it tries to use identifierForVendor. > I realize that iOS 5 is no longer supported in Cordova, but since the code > attempts to be backward compatible (based on the inline comments), I figured > this could be fixed with a few lines of code (which I have done and will > submit shortly). -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10510) medic-run doesn't check to make sure the emulator started
[
https://issues.apache.org/jira/browse/CB-10510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149489#comment-15149489
]
ASF subversion and git services commented on CB-10510:
--
Commit 7682cd7205f153bc252ab8e1ef445169d34e11c2 in cordova-medic's branch
refs/heads/master from riknoll
[ https://git-wip-us.apache.org/repos/asf?p=cordova-medic.git;h=7682cd7 ]
CB-10510: Removing require statement for process to maintain 0.12.2
compatability
> medic-run doesn't check to make sure the emulator started
> -
>
> Key: CB-10510
> URL: https://issues.apache.org/jira/browse/CB-10510
> Project: Apache Cordova
> Issue Type: Test
> Components: Medic
> Environment: Windows, Android emulator
>Reporter: Richard B Knoll
>Assignee: Richard B Knoll
> Labels: android, found-by-ci
>
> Medic doesn't check to see if the emulator actually starts when invoking
> {{cordova run android}}. Instead, it starts polling cordova-vm immediately.
> This might also be considered a bug in cordova-android's run script, which
> just seems to hang if the emulator doesn't start. Example build is here:
> https://ci.apache.org/builders/cordova-android-win/builds/1488/steps/running-tests/logs/stdio
> And adb logs are here:
> https://ci.apache.org/builders/cordova-android-win/builds/1488/steps/gathering-logs/logs/stdio
>
> Log:
> C:\Users\buildbot\slaves\apache\cordova-android-win\mobilespec>node
> C:\Users\buildbot\slaves\apache\cordova-android-win\cordova-cli\bin\cordova
> run --emulator android -- --gradle
> ANDROID_HOME=C:\Android\android-sdk
> JAVA_HOME=C:\Program Files (x86)\Java\jdk1.7.0_55
> No emulator specified, defaulting to Galaxy_Nexus
> Waiting for emulator...
> WARNING: init: Missing WGL extension WGL_ARB_make_current_read
> emulator: warning: opening audio output failed
> emulator: emulator window was out of view and was recentered
> emulator: UpdateChecker: skipped version check
> Booting up emulator (this may take a
> while)query failed for
> mobilespec_results { [Error: connect ETIMEDOUT] code: 'ETIMEDOUT', errno:
> 'ETIMEDOUT', syscall: 'connect' }
> .query failed for mobilespec_results {
> [Error: connect ETIMEDOUT] code: 'ETIMEDOUT', errno: 'ETIMEDOUT', syscall:
> 'connect' }
> ..query failed for mobilespec_results { [Error: connect
> ETIMEDOUT] code: 'ETIMEDOUT', errno: 'ETIMEDOUT', syscall: 'connect' }
> query
> failed for mobilespec_results { [Error: connect ETIMEDOUT] code:
> 'ETIMEDOUT', errno: 'ETIMEDOUT', syscall: 'connect' }
> ...query
> failed for mobilespec_results { [Error: connect ETIMEDOUT] code:
> 'ETIMEDOUT', errno: 'ETIMEDOUT', syscall: 'connect' }
> ...didn't get test
> results: timed out
> program finished with exit code 1
> elapsedTime=1150.659000
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10530) App freezes sometimes directly after starting on iOS
[ https://issues.apache.org/jira/browse/CB-10530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149486#comment-15149486 ] Shazron Abdullah commented on CB-10530: --- Finished my investigation. The reasons for the proxy are listed in CB-10106. Like Torsten has found initially, there is faulty logic here: https://github.com/apache/cordova-ios/blob/4ca3f28bae30b0974da7a7a4033d158b08303c4c/cordova-js-src/exec.js#L139 The return value for cordovaExec() can be iosExec and not a proxy object, and that has to be taken into account. > App freezes sometimes directly after starting on iOS > > > Key: CB-10530 > URL: https://issues.apache.org/jira/browse/CB-10530 > Project: Apache Cordova > Issue Type: Bug > Components: iOS >Affects Versions: 6.0.0 > Environment: OSX El Capitan 10.11.3, XCODE (7.2.1), iOS 9.2.1, > cordova 6.0.0, ionic 1.7.14 >Reporter: Florian Krüger >Assignee: Shazron Abdullah >Priority: Critical > Labels: cordova-ios-4.1.0, triaged > Attachments: Instruments.trace.zip > > > * Installed the "ionic start myApp sidemenu" example application > * Start XCODE (7.2.1) > * Start the app by clicking the run button from xCODE > * The app probably starts as expected. > * Repeat the start process until the app freezes. > The app sometimes freezes completely. If this happens you cannot do anything > with the app (you need to push the home button and close the app via task > manager). I had the same issue for another more complex app. > The CPU stays at around 99% workload. > I made a snapshot of the profiler (Instruments) > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-7229) --browserify should be saved when creating a new project
[ https://issues.apache.org/jira/browse/CB-7229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149482#comment-15149482 ] Dan Polivy commented on CB-7229: [~stevegill] Is there any mechanism in the current releases to "remember" browserify as an option, so it doesn't have to be specified? > --browserify should be saved when creating a new project > > > Key: CB-7229 > URL: https://issues.apache.org/jira/browse/CB-7229 > Project: Apache Cordova > Issue Type: Sub-task > Components: CLI, CordovaLib >Reporter: Steve Gill > Fix For: 3.8.0 > > > "cordova create --browserify test com.example.test browserifyTest" > The browserify flag should be saved somewhere (config file?) to keep note > that the project is a browserify project. That way, adding/removing > platforms/plugins should be able to check to see if the project was created > as a browserify project. This will also stop the need to add --browserify > everytime you add/rm a plugin or platform. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10625) getPicture fails when getting a photo from the Photo Library
[
https://issues.apache.org/jira/browse/CB-10625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149479#comment-15149479
]
Joe Bowser commented on CB-10625:
-
Confirmed on Moto G running Android 4.4.4: Classic Image Gallery works, but not
new Photos URIs being passed from the Intent.
> getPicture fails when getting a photo from the Photo Library
>
>
> Key: CB-10625
> URL: https://issues.apache.org/jira/browse/CB-10625
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin Camera
>Affects Versions: Master, 6.0.0
> Environment: cordova-plugin-camera 2.1.0, cordova-android 5.1.0,
> android 5.0.2, no crosswalk
>Reporter: Tom Nonk
>Assignee: Joe Bowser
> Labels: Android
>
> Hi,
> Since I updated Cordova to 6.0.0, camera.getPicture always fails and returns:
> "error retrieving image".
> Here are the parameters I use:
> {
> quality: 100,
> targetHeight: 250,
> targetWidth: 250,
> destinationType: Camera.DestinationType.FILE_URI,
> sourceType: navigator.camera.PictureSourceType.PHOTOLIBRARY,
> allowEdit: true,
> encodingType: Camera.EncodingType.JPEG,
> correctOrientation: true
> }
> Thanks by advance
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Assigned] (CB-10625) getPicture fails when getting a photo from the Photo Library
[
https://issues.apache.org/jira/browse/CB-10625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bowser reassigned CB-10625:
---
Assignee: Joe Bowser
> getPicture fails when getting a photo from the Photo Library
>
>
> Key: CB-10625
> URL: https://issues.apache.org/jira/browse/CB-10625
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin Camera
>Affects Versions: Master, 6.0.0
> Environment: cordova-plugin-camera 2.1.0, cordova-android 5.1.0,
> android 5.0.2, no crosswalk
>Reporter: Tom Nonk
>Assignee: Joe Bowser
> Labels: Android
>
> Hi,
> Since I updated Cordova to 6.0.0, camera.getPicture always fails and returns:
> "error retrieving image".
> Here are the parameters I use:
> {
> quality: 100,
> targetHeight: 250,
> targetWidth: 250,
> destinationType: Camera.DestinationType.FILE_URI,
> sourceType: navigator.camera.PictureSourceType.PHOTOLIBRARY,
> allowEdit: true,
> encodingType: Camera.EncodingType.JPEG,
> correctOrientation: true
> }
> Thanks by advance
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10625) getPicture fails when getting a photo from the Photo Library
[
https://issues.apache.org/jira/browse/CB-10625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149474#comment-15149474
]
Joe Bowser commented on CB-10625:
-
This is entirely dependent on which application we use when we get the image.
If we use the Photos Application, it doesn't work, but it works better with the
Samsung Galaxy S6 in that it gets the correct file. I'm not sure why the
DocumentsContract.getDocumentId(uri) is causing an exception when fed a Google
Photos URI, but that's why this isn't working. As far as a fix, this isn't
trivial, but this could be worked around by using the built in gallery
application on most devices.
> getPicture fails when getting a photo from the Photo Library
>
>
> Key: CB-10625
> URL: https://issues.apache.org/jira/browse/CB-10625
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin Camera
>Affects Versions: Master, 6.0.0
> Environment: cordova-plugin-camera 2.1.0, cordova-android 5.1.0,
> android 5.0.2, no crosswalk
>Reporter: Tom Nonk
> Labels: Android
>
> Hi,
> Since I updated Cordova to 6.0.0, camera.getPicture always fails and returns:
> "error retrieving image".
> Here are the parameters I use:
> {
> quality: 100,
> targetHeight: 250,
> targetWidth: 250,
> destinationType: Camera.DestinationType.FILE_URI,
> sourceType: navigator.camera.PictureSourceType.PHOTOLIBRARY,
> allowEdit: true,
> encodingType: Camera.EncodingType.JPEG,
> correctOrientation: true
> }
> Thanks by advance
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-10625) getPicture fails when getting a photo from the Photo Library
[
https://issues.apache.org/jira/browse/CB-10625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bowser updated CB-10625:
Labels: Android (was: )
Component/s: (was: Android)
> getPicture fails when getting a photo from the Photo Library
>
>
> Key: CB-10625
> URL: https://issues.apache.org/jira/browse/CB-10625
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin Camera
>Affects Versions: Master, 6.0.0
> Environment: cordova-plugin-camera 2.1.0, cordova-android 5.1.0,
> android 5.0.2, no crosswalk
>Reporter: Tom Nonk
> Labels: Android
>
> Hi,
> Since I updated Cordova to 6.0.0, camera.getPicture always fails and returns:
> "error retrieving image".
> Here are the parameters I use:
> {
> quality: 100,
> targetHeight: 250,
> targetWidth: 250,
> destinationType: Camera.DestinationType.FILE_URI,
> sourceType: navigator.camera.PictureSourceType.PHOTOLIBRARY,
> allowEdit: true,
> encodingType: Camera.EncodingType.JPEG,
> correctOrientation: true
> }
> Thanks by advance
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Assigned] (CB-10595) Windows Store 8.1 builds finish with warning 'Expected undefined to be defined' on running mobilespec storage tests
[ https://issues.apache.org/jira/browse/CB-10595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sarangan Rajamanickam reassigned CB-10595: -- Assignee: Sarangan Rajamanickam (was: Sergey Shakhnazarov) > Windows Store 8.1 builds finish with warning 'Expected undefined to be > defined' on running mobilespec storage tests > --- > > Key: CB-10595 > URL: https://issues.apache.org/jira/browse/CB-10595 > Project: Apache Cordova > Issue Type: Test >Reporter: Raghav >Assignee: Sarangan Rajamanickam >Priority: Critical > Labels: found-by-ci, windows-store-8.1 > > Recent build links: > https://ci.apache.org/builders/cordova-windows-store8.1/builds/1601 > https://ci.apache.org/builders/cordova-windows-store8.1/builds/1602 > Build Log: > Getting test results for cordova-windows-store8.1-1601-buildbot-vm > Results at > http://cordova-vm.apache.org:5984/_utils/document.html?mobilespec_results/cordova-windows-store8.1-1601-buildbot-vm__6.3.9600.16384__HP > Z420 Workstation > Total failures: 1 > Failing tests: > org.apache.cordova.mobilespec.tests.storage.tests >> Session Storage HTML > 5 Storage storage.spec.9 should exist > Expected undefined to be defined. > Error: Expected undefined to be defined. >at stack > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:1455:11) >at buildExpectationResult > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:1422:5) >at expectationResultFactory > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:572:11) >at Spec.prototype.addExpectationResult > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:321:5) >at addExpectationResult > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:516:9) >at Anonymous function > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:1379:7) >at Anonymous function > (ms-appx://org.apache.mobilespec/www/plugins/org.apache.cordova.mobilespec.tests/tests/storage.tests.js:183:17) >at attemptSync > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:1741:9) >at QueueRunner.prototype.run > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:1729:9) >at QueueRunner.prototype.execute > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:1714:5) > program finished with exit code 0 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10595) Windows Store 8.1 builds finish with warning 'Expected undefined to be defined' on running mobilespec storage tests
[ https://issues.apache.org/jira/browse/CB-10595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149469#comment-15149469 ] ASF GitHub Bot commented on CB-10595: - GitHub user sarangan12 opened a pull request: https://github.com/apache/cordova-mobile-spec/pull/138 CB-10595: Windows Store 8.1 builds finish with warning 'Expected undefined to be defined' on running mobilespec storage tests IE does not support openDatabase method. So, marking the test as pending. (similar to storage.spec.17 test - the next test after the failing test) @dblotsky @riknoll @rakatyal @nikhilkh Can you please review and merge this PR? You can merge this pull request into a Git repository by running: $ git pull https://github.com/sarangan12/cordova-mobile-spec CB-10595 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-mobile-spec/pull/138.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #138 commit 6d4a2b768b966a0efe1e4a89f528dcc65db5006e Author: Sarangan Rajamanickam Date: 2016-02-16T22:42:01Z CB-10595: Windows Store 8.1 builds finish with warning 'Expected undefined to be defined' on running mobilespec storage tests IE does not support openDatabase method. So, marking the test as pending. > Windows Store 8.1 builds finish with warning 'Expected undefined to be > defined' on running mobilespec storage tests > --- > > Key: CB-10595 > URL: https://issues.apache.org/jira/browse/CB-10595 > Project: Apache Cordova > Issue Type: Test >Reporter: Raghav >Assignee: Sergey Shakhnazarov >Priority: Critical > Labels: found-by-ci, windows-store-8.1 > > Recent build links: > https://ci.apache.org/builders/cordova-windows-store8.1/builds/1601 > https://ci.apache.org/builders/cordova-windows-store8.1/builds/1602 > Build Log: > Getting test results for cordova-windows-store8.1-1601-buildbot-vm > Results at > http://cordova-vm.apache.org:5984/_utils/document.html?mobilespec_results/cordova-windows-store8.1-1601-buildbot-vm__6.3.9600.16384__HP > Z420 Workstation > Total failures: 1 > Failing tests: > org.apache.cordova.mobilespec.tests.storage.tests >> Session Storage HTML > 5 Storage storage.spec.9 should exist > Expected undefined to be defined. > Error: Expected undefined to be defined. >at stack > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:1455:11) >at buildExpectationResult > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:1422:5) >at expectationResultFactory > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:572:11) >at Spec.prototype.addExpectationResult > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:321:5) >at addExpectationResult > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:516:9) >at Anonymous function > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:1379:7) >at Anonymous function > (ms-appx://org.apache.mobilespec/www/plugins/org.apache.cordova.mobilespec.tests/tests/storage.tests.js:183:17) >at attemptSync > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:1741:9) >at QueueRunner.prototype.run > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:1729:9) >at QueueRunner.prototype.execute > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:1714:5) > program finished with exit code 0 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10510) medic-run doesn't check to make sure the emulator started
[
https://issues.apache.org/jira/browse/CB-10510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149462#comment-15149462
]
ASF GitHub Bot commented on CB-10510:
-
Github user riknoll closed the pull request at:
https://github.com/apache/cordova-medic/pull/77
> medic-run doesn't check to make sure the emulator started
> -
>
> Key: CB-10510
> URL: https://issues.apache.org/jira/browse/CB-10510
> Project: Apache Cordova
> Issue Type: Test
> Components: Medic
> Environment: Windows, Android emulator
>Reporter: Richard B Knoll
>Assignee: Richard B Knoll
> Labels: android, found-by-ci
>
> Medic doesn't check to see if the emulator actually starts when invoking
> {{cordova run android}}. Instead, it starts polling cordova-vm immediately.
> This might also be considered a bug in cordova-android's run script, which
> just seems to hang if the emulator doesn't start. Example build is here:
> https://ci.apache.org/builders/cordova-android-win/builds/1488/steps/running-tests/logs/stdio
> And adb logs are here:
> https://ci.apache.org/builders/cordova-android-win/builds/1488/steps/gathering-logs/logs/stdio
>
> Log:
> C:\Users\buildbot\slaves\apache\cordova-android-win\mobilespec>node
> C:\Users\buildbot\slaves\apache\cordova-android-win\cordova-cli\bin\cordova
> run --emulator android -- --gradle
> ANDROID_HOME=C:\Android\android-sdk
> JAVA_HOME=C:\Program Files (x86)\Java\jdk1.7.0_55
> No emulator specified, defaulting to Galaxy_Nexus
> Waiting for emulator...
> WARNING: init: Missing WGL extension WGL_ARB_make_current_read
> emulator: warning: opening audio output failed
> emulator: emulator window was out of view and was recentered
> emulator: UpdateChecker: skipped version check
> Booting up emulator (this may take a
> while)query failed for
> mobilespec_results { [Error: connect ETIMEDOUT] code: 'ETIMEDOUT', errno:
> 'ETIMEDOUT', syscall: 'connect' }
> .query failed for mobilespec_results {
> [Error: connect ETIMEDOUT] code: 'ETIMEDOUT', errno: 'ETIMEDOUT', syscall:
> 'connect' }
> ..query failed for mobilespec_results { [Error: connect
> ETIMEDOUT] code: 'ETIMEDOUT', errno: 'ETIMEDOUT', syscall: 'connect' }
> query
> failed for mobilespec_results { [Error: connect ETIMEDOUT] code:
> 'ETIMEDOUT', errno: 'ETIMEDOUT', syscall: 'connect' }
> ...query
> failed for mobilespec_results { [Error: connect ETIMEDOUT] code:
> 'ETIMEDOUT', errno: 'ETIMEDOUT', syscall: 'connect' }
> ...didn't get test
> results: timed out
> program finished with exit code 1
> elapsedTime=1150.659000
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10510) medic-run doesn't check to make sure the emulator started
[
https://issues.apache.org/jira/browse/CB-10510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149461#comment-15149461
]
ASF GitHub Bot commented on CB-10510:
-
Github user riknoll commented on the pull request:
https://github.com/apache/cordova-medic/pull/77#issuecomment-184904386
Merged in 90d06a39cbaf9313edae0fa3cc63a63003b65553
> medic-run doesn't check to make sure the emulator started
> -
>
> Key: CB-10510
> URL: https://issues.apache.org/jira/browse/CB-10510
> Project: Apache Cordova
> Issue Type: Test
> Components: Medic
> Environment: Windows, Android emulator
>Reporter: Richard B Knoll
>Assignee: Richard B Knoll
> Labels: android, found-by-ci
>
> Medic doesn't check to see if the emulator actually starts when invoking
> {{cordova run android}}. Instead, it starts polling cordova-vm immediately.
> This might also be considered a bug in cordova-android's run script, which
> just seems to hang if the emulator doesn't start. Example build is here:
> https://ci.apache.org/builders/cordova-android-win/builds/1488/steps/running-tests/logs/stdio
> And adb logs are here:
> https://ci.apache.org/builders/cordova-android-win/builds/1488/steps/gathering-logs/logs/stdio
>
> Log:
> C:\Users\buildbot\slaves\apache\cordova-android-win\mobilespec>node
> C:\Users\buildbot\slaves\apache\cordova-android-win\cordova-cli\bin\cordova
> run --emulator android -- --gradle
> ANDROID_HOME=C:\Android\android-sdk
> JAVA_HOME=C:\Program Files (x86)\Java\jdk1.7.0_55
> No emulator specified, defaulting to Galaxy_Nexus
> Waiting for emulator...
> WARNING: init: Missing WGL extension WGL_ARB_make_current_read
> emulator: warning: opening audio output failed
> emulator: emulator window was out of view and was recentered
> emulator: UpdateChecker: skipped version check
> Booting up emulator (this may take a
> while)query failed for
> mobilespec_results { [Error: connect ETIMEDOUT] code: 'ETIMEDOUT', errno:
> 'ETIMEDOUT', syscall: 'connect' }
> .query failed for mobilespec_results {
> [Error: connect ETIMEDOUT] code: 'ETIMEDOUT', errno: 'ETIMEDOUT', syscall:
> 'connect' }
> ..query failed for mobilespec_results { [Error: connect
> ETIMEDOUT] code: 'ETIMEDOUT', errno: 'ETIMEDOUT', syscall: 'connect' }
> query
> failed for mobilespec_results { [Error: connect ETIMEDOUT] code:
> 'ETIMEDOUT', errno: 'ETIMEDOUT', syscall: 'connect' }
> ...query
> failed for mobilespec_results { [Error: connect ETIMEDOUT] code:
> 'ETIMEDOUT', errno: 'ETIMEDOUT', syscall: 'connect' }
> ...didn't get test
> results: timed out
> program finished with exit code 1
> elapsedTime=1150.659000
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10510) medic-run doesn't check to make sure the emulator started
[
https://issues.apache.org/jira/browse/CB-10510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149458#comment-15149458
]
ASF subversion and git services commented on CB-10510:
--
Commit 90d06a39cbaf9313edae0fa3cc63a63003b65553 in cordova-medic's branch
refs/heads/master from riknoll
[ https://git-wip-us.apache.org/repos/asf?p=cordova-medic.git;h=90d06a3 ]
CB-10510: Retry starting the Android emulator if it hangs on boot
> medic-run doesn't check to make sure the emulator started
> -
>
> Key: CB-10510
> URL: https://issues.apache.org/jira/browse/CB-10510
> Project: Apache Cordova
> Issue Type: Test
> Components: Medic
> Environment: Windows, Android emulator
>Reporter: Richard B Knoll
>Assignee: Richard B Knoll
> Labels: android, found-by-ci
>
> Medic doesn't check to see if the emulator actually starts when invoking
> {{cordova run android}}. Instead, it starts polling cordova-vm immediately.
> This might also be considered a bug in cordova-android's run script, which
> just seems to hang if the emulator doesn't start. Example build is here:
> https://ci.apache.org/builders/cordova-android-win/builds/1488/steps/running-tests/logs/stdio
> And adb logs are here:
> https://ci.apache.org/builders/cordova-android-win/builds/1488/steps/gathering-logs/logs/stdio
>
> Log:
> C:\Users\buildbot\slaves\apache\cordova-android-win\mobilespec>node
> C:\Users\buildbot\slaves\apache\cordova-android-win\cordova-cli\bin\cordova
> run --emulator android -- --gradle
> ANDROID_HOME=C:\Android\android-sdk
> JAVA_HOME=C:\Program Files (x86)\Java\jdk1.7.0_55
> No emulator specified, defaulting to Galaxy_Nexus
> Waiting for emulator...
> WARNING: init: Missing WGL extension WGL_ARB_make_current_read
> emulator: warning: opening audio output failed
> emulator: emulator window was out of view and was recentered
> emulator: UpdateChecker: skipped version check
> Booting up emulator (this may take a
> while)query failed for
> mobilespec_results { [Error: connect ETIMEDOUT] code: 'ETIMEDOUT', errno:
> 'ETIMEDOUT', syscall: 'connect' }
> .query failed for mobilespec_results {
> [Error: connect ETIMEDOUT] code: 'ETIMEDOUT', errno: 'ETIMEDOUT', syscall:
> 'connect' }
> ..query failed for mobilespec_results { [Error: connect
> ETIMEDOUT] code: 'ETIMEDOUT', errno: 'ETIMEDOUT', syscall: 'connect' }
> query
> failed for mobilespec_results { [Error: connect ETIMEDOUT] code:
> 'ETIMEDOUT', errno: 'ETIMEDOUT', syscall: 'connect' }
> ...query
> failed for mobilespec_results { [Error: connect ETIMEDOUT] code:
> 'ETIMEDOUT', errno: 'ETIMEDOUT', syscall: 'connect' }
> ...didn't get test
> results: timed out
> program finished with exit code 1
> elapsedTime=1150.659000
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-10625) getPicture fails when getting a photo from the Photo Library
[
https://issues.apache.org/jira/browse/CB-10625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bowser updated CB-10625:
Summary: getPicture fails when getting a photo from the Photo Library
(was: getPicture always fail "error retrieving image")
> getPicture fails when getting a photo from the Photo Library
>
>
> Key: CB-10625
> URL: https://issues.apache.org/jira/browse/CB-10625
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android, Plugin Camera
>Affects Versions: Master, 6.0.0
> Environment: cordova-plugin-camera 2.1.0, cordova-android 5.1.0,
> android 5.0.2, no crosswalk
>Reporter: Tom Nonk
>
> Hi,
> Since I updated Cordova to 6.0.0, camera.getPicture always fails and returns:
> "error retrieving image".
> Here are the parameters I use:
> {
> quality: 100,
> targetHeight: 250,
> targetWidth: 250,
> destinationType: Camera.DestinationType.FILE_URI,
> sourceType: navigator.camera.PictureSourceType.PHOTOLIBRARY,
> allowEdit: true,
> encodingType: Camera.EncodingType.JPEG,
> correctOrientation: true
> }
> Thanks by advance
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Comment Edited] (CB-10625) getPicture fails when getting a photo from the Photo Library
[
https://issues.apache.org/jira/browse/CB-10625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149449#comment-15149449
]
Joe Bowser edited comment on CB-10625 at 2/16/16 10:34 PM:
---
Able to reproduce in MobileSpec on Nexus 5X running Android 6.0.1. Taking a
picture works, it's getting a photo from Photos that fails.
was (Author: bowserj):
Able to reproduce in MobileSpec on Nexus 5X running Android 6.0.1
> getPicture fails when getting a photo from the Photo Library
>
>
> Key: CB-10625
> URL: https://issues.apache.org/jira/browse/CB-10625
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android, Plugin Camera
>Affects Versions: Master, 6.0.0
> Environment: cordova-plugin-camera 2.1.0, cordova-android 5.1.0,
> android 5.0.2, no crosswalk
>Reporter: Tom Nonk
>
> Hi,
> Since I updated Cordova to 6.0.0, camera.getPicture always fails and returns:
> "error retrieving image".
> Here are the parameters I use:
> {
> quality: 100,
> targetHeight: 250,
> targetWidth: 250,
> destinationType: Camera.DestinationType.FILE_URI,
> sourceType: navigator.camera.PictureSourceType.PHOTOLIBRARY,
> allowEdit: true,
> encodingType: Camera.EncodingType.JPEG,
> correctOrientation: true
> }
> Thanks by advance
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10625) getPicture always fail "error retrieving image"
[
https://issues.apache.org/jira/browse/CB-10625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149449#comment-15149449
]
Joe Bowser commented on CB-10625:
-
Able to reproduce in MobileSpec on Nexus 5X running Android 6.0.1
> getPicture always fail "error retrieving image"
> ---
>
> Key: CB-10625
> URL: https://issues.apache.org/jira/browse/CB-10625
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android, Plugin Camera
>Affects Versions: Master, 6.0.0
> Environment: cordova-plugin-camera 2.1.0, cordova-android 5.1.0,
> android 5.0.2, no crosswalk
>Reporter: Tom Nonk
>
> Hi,
> Since I updated Cordova to 6.0.0, camera.getPicture always fails and returns:
> "error retrieving image".
> Here are the parameters I use:
> {
> quality: 100,
> targetHeight: 250,
> targetWidth: 250,
> destinationType: Camera.DestinationType.FILE_URI,
> sourceType: navigator.camera.PictureSourceType.PHOTOLIBRARY,
> allowEdit: true,
> encodingType: Camera.EncodingType.JPEG,
> correctOrientation: true
> }
> Thanks by advance
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-10408) FileTransfer methods upload filetransfer.spec.22 should get http status and body on failure
[ https://issues.apache.org/jira/browse/CB-10408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raghav updated CB-10408: Priority: Minor (was: Major) > FileTransfer methods upload filetransfer.spec.22 should get http status and > body on failure > --- > > Key: CB-10408 > URL: https://issues.apache.org/jira/browse/CB-10408 > Project: Apache Cordova > Issue Type: Test > Components: Plugin File Transfer >Reporter: Sarangan Rajamanickam >Assignee: Sergey Shakhnazarov >Priority: Minor > Labels: found-by-ci, triaged, windows, wp8.1 > > The following error happened during one of the CI builds: > Link: > https://ci.apache.org/builders/cordova-windows-phone8.1/builds/1368/steps/getting-test-results/logs/stdio > > Failing tests: > cordova-plugin-file-transfer-tests.tests >> FileTransfer methods upload > filetransfer.spec.22 should get http status and body on failure > Expected null to be 403. > Error: Expected null to be 403. >at stack > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:1455:11) >at buildExpectationResult > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:1422:5) >at expectationResultFactory > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:572:11) >at addExpectationResult > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:321:5) >at addExpectationResult > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:516:9) >at Anonymous function > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:1379:7) >at uploadFail > (ms-appx://org.apache.mobilespec/www/plugins/cordova-plugin-file-transfer-tests/tests.js:808:25) >at errorCallback > (ms-appx://org.apache.mobilespec/www/plugins/cordova-plugin-file-transfer/www/FileTransfer.js:150:9) >at callbackFromNative > (ms-appx://org.apache.mobilespec/www/cordova.js:295:38) >at callbackError > (ms-appx://org.apache.mobilespec/www/cordova.js:282:9) -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10625) getPicture always fail "error retrieving image"
[
https://issues.apache.org/jira/browse/CB-10625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149403#comment-15149403
]
Joe Bowser commented on CB-10625:
-
Can you provide more details, like which version of Android you're testing this
on, and whether this is on a device or on an emulator?
> getPicture always fail "error retrieving image"
> ---
>
> Key: CB-10625
> URL: https://issues.apache.org/jira/browse/CB-10625
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android, Plugin Camera
>Affects Versions: Master, 6.0.0
> Environment: cordova-plugin-camera 2.1.0, cordova-android 5.1.0,
> android 5.0.2, no crosswalk
>Reporter: Tom Nonk
>
> Hi,
> Since I updated Cordova to 6.0.0, camera.getPicture always fails and returns:
> "error retrieving image".
> Here are the parameters I use:
> {
> quality: 100,
> targetHeight: 250,
> targetWidth: 250,
> destinationType: Camera.DestinationType.FILE_URI,
> sourceType: navigator.camera.PictureSourceType.PHOTOLIBRARY,
> allowEdit: true,
> encodingType: Camera.EncodingType.JPEG,
> correctOrientation: true
> }
> Thanks by advance
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-10629) Cannot build Android due to missing decl
[
https://issues.apache.org/jira/browse/CB-10629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bowser resolved CB-10629.
-
Resolution: Won't Fix
This isn't an issue with Cordova-Android, and is instead a third-party plugin
issue. We have no AppPreferencesActivity.
> Cannot build Android due to missing decl
>
>
> Key: CB-10629
> URL: https://issues.apache.org/jira/browse/CB-10629
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Affects Versions: 6.0.0
>Reporter: Jordan Zimmerman
>
> android 5.1.0
> cordova-plugin-inappbrowser
> cordova-plugin-actionsheet
> cordova-plugin-facebook4
> uk.co.workingedge.phonegap.plugin.launchnavigator
> {panel}
> :compileDebugJavaWithJavac/.../AppPreferencesActivity.java:27: error: cannot
> find symbol
> addPreferencesFromResource(R.xml.apppreferences);
> ^
> symbol: variable apppreferences
> location: class xml
> Note: Some input files use or override a deprecated API.
> Note: Recompile with -Xlint:deprecation for details.
> 1 error
> FAILED
> {panel}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-10595) Windows Store 8.1 builds finish with warning 'Expected undefined to be defined' on running mobilespec storage tests
[ https://issues.apache.org/jira/browse/CB-10595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raghav updated CB-10595: Priority: Critical (was: Major) > Windows Store 8.1 builds finish with warning 'Expected undefined to be > defined' on running mobilespec storage tests > --- > > Key: CB-10595 > URL: https://issues.apache.org/jira/browse/CB-10595 > Project: Apache Cordova > Issue Type: Test >Reporter: Raghav >Assignee: Sergey Shakhnazarov >Priority: Critical > Labels: found-by-ci, windows-store-8.1 > > Recent build links: > https://ci.apache.org/builders/cordova-windows-store8.1/builds/1601 > https://ci.apache.org/builders/cordova-windows-store8.1/builds/1602 > Build Log: > Getting test results for cordova-windows-store8.1-1601-buildbot-vm > Results at > http://cordova-vm.apache.org:5984/_utils/document.html?mobilespec_results/cordova-windows-store8.1-1601-buildbot-vm__6.3.9600.16384__HP > Z420 Workstation > Total failures: 1 > Failing tests: > org.apache.cordova.mobilespec.tests.storage.tests >> Session Storage HTML > 5 Storage storage.spec.9 should exist > Expected undefined to be defined. > Error: Expected undefined to be defined. >at stack > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:1455:11) >at buildExpectationResult > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:1422:5) >at expectationResultFactory > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:572:11) >at Spec.prototype.addExpectationResult > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:321:5) >at addExpectationResult > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:516:9) >at Anonymous function > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:1379:7) >at Anonymous function > (ms-appx://org.apache.mobilespec/www/plugins/org.apache.cordova.mobilespec.tests/tests/storage.tests.js:183:17) >at attemptSync > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:1741:9) >at QueueRunner.prototype.run > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:1729:9) >at QueueRunner.prototype.execute > (ms-appx://org.apache.mobilespec/www/cdvtests/jasmine-2.2.0/jasmine.js:1714:5) > program finished with exit code 0 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-10633) File Transfer plugin test fails on cordova-ios
Raghav created CB-10633: --- Summary: File Transfer plugin test fails on cordova-ios Key: CB-10633 URL: https://issues.apache.org/jira/browse/CB-10633 Project: Apache Cordova Issue Type: Bug Reporter: Raghav Recent failed builds: https://ci.apache.org/builders/cordova-ios/builds/1787 https://ci.apache.org/builders/cordova-ios/builds/1786 Build Log: Failing tests: cordova-plugin-file-transfer-tests.tests >> FileTransfer methods download filetransfer.spec.10 should be stopped by abort() right away Error: Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL. in file:///Users/buildbot/Library/Developer/CoreSimulator/Devices/DA6D3C8F-39BE-486B-A6DB-362B7BA75FD3/data/Containers/Bundle/Application/8CD0A3E1-F56D-472F-A546-6B82D7F4A9C7/mobilespec.app/www/cdvtests/jasmine-2.2.0/jasmine.js (line 1764) file:///Users/buildbot/Library/Developer/CoreSimulator/Devices/DA6D3C8F-39BE-486B-A6DB-362B7BA75FD3/data/Containers/Bundle/Application/8CD0A3E1-F56D-472F-A546-6B82D7F4A9C7/mobilespec.app/www/cdvtests/jasmine-2.2.0/jasmine.js:1764:32 Expected spy httpWin not to have been called. stack@file:///Users/buildbot/Library/Developer/CoreSimulator/Devices/DA6D3C8F-39BE-486B-A6DB-362B7BA75FD3/data/Containers/Bundle/Application/8CD0A3E1-F56D-472F-A546-6B82D7F4A9C7/mobilespec.app/www/cdvtests/jasmine-2.2.0/jasmine.js:1455:26 buildExpectationResult@file:///Users/buildbot/Library/Developer/CoreSimulator/Devices/DA6D3C8F-39BE-486B-A6DB-362B7BA75FD3/data/Containers/Bundle/Application/8CD0A3E1-F56D-472F-A546-6B82D7F4A9C7/mobilespec.app/www/cdvtests/jasmine-2.2.0/jasmine.js:1425:19 expectationResultFactory@file:///Users/buildbot/Library/Developer/CoreSimulator/Devices/DA6D3C8F-39BE-486B-A6DB-362B7BA75FD3/data/Containers/Bundle/Application/8CD0A3E1-F56D-472F-A546-6B82D7F4A9C7/mobilespec.app/www/cdvtests/jasmine-2.2.0/jasmine.js:572:40 addExpectationResult@file:///Users/buildbot/Library/Developer/CoreSimulator/Devices/DA6D3C8F-39BE-486B-A6DB-362B7BA75FD3/data/Containers/Bundle/Application/8CD0A3E1-F56D-472F-A546-6B82D7F4A9C7/mobilespec.app/www/cdvtests/jasmine-2.2.0/jasmine.js:321:58 addExpectationResult@file:///Users/buildbot/Library/Developer/CoreSimulator/Devices/DA6D3C8F-39BE-486B-A6DB-362B7BA75FD3/data/Containers/Bundle/Application/8CD0A3E1-F56D-472F-A546-6B82D7F4A9C7/mobilespec.app/www/cdvtests/jasmine-2.2.0/jasmine.js:516:41 file:///Users/buildbot/Library/Developer/CoreSimulator/Devices/DA6D3C8F-39BE-486B-A6DB-362B7BA75FD3/data/Containers/Bundle/Application/8CD0A3E1-F56D-472F-A546-6B82D7F4A9C7/mobilespec.app/www/cdvtests/jasmine-2.2.0/jasmine.js:1379:32 file:///Users/buildbot/Library/Developer/CoreSimulator/Devices/DA6D3C8F-39BE-486B-A6DB-362B7BA75FD3/data/Containers/Bundle/Application/8CD0A3E1-F56D-472F-A546-6B82D7F4A9C7/mobilespec.app/www/plugins/cordova-plugin-file-transfer-tests/tests.js:253:79 attemptSync@file:///Users/buildbot/Library/Developer/CoreSimulator/Devices/DA6D3C8F-39BE-486B-A6DB-362B7BA75FD3/data/Containers/Bundle/Application/8CD0A3E1-F56D-472F-A546-6B82D7F4A9C7/mobilespec.app/www/cdvtests/jasmine-2.2.0/jasmine.js:1741:28 run@file:///Users/buildbot/Library/Developer/CoreSimulator/Devices/DA6D3C8F-39BE-486B-A6DB-362B7BA75FD3/data/Containers/Bundle/Application/8CD0A3E1-F56D-472F-A546-6B82D7F4A9C7/mobilespec.app/www/cdvtests/jasmine-2.2.0/jasmine.js:1729:20 file:///Users/buildbot/Library/Developer/CoreSimulator/Devices/DA6D3C8F-39BE-486B-A6DB-362B7BA75FD3/data/Containers/Bundle/Application/8CD0A3E1-F56D-472F-A546-6B82D7F4A9C7/mobilespec.app/www/cdvtests/jasmine-2.2.0/jasmine.js:1753:19 file:///Users/buildbot/Library/Developer/CoreSimulator/Devices/DA6D3C8F-39BE-486B-A6DB-362B7BA75FD3/data/Containers/Bundle/Application/8CD0A3E1-F56D-472F-A546-6B82D7F4A9C7/mobilespec.app/www/cdvtests/jasmine-2.2.0/jasmine.js:1697:11 file:///Users/buildbot/Library/Developer/CoreSimulator/Devices/DA6D3C8F-39BE-486B-A6DB-362B7BA75FD3/data/Containers/Bundle/Application/8CD0A3E1-F56D-472F-A546-6B82D7F4A9C7/mobilespec.app/www/plugins/cordova-plugin-file-transfer-tests/tests.js:126:33 callbackFromNative@file:///Users/buildbot/Library/Developer/CoreSimulator/Devices/DA6D3C8F-39BE-486B-A6DB-362B7BA75FD3/data/Containers/Bundle/Application/8CD0A3E1-F56D-472F-A546-6B82D7F4A9C7/mobilespec.app/www/cordova.js:293:63 nc2@file:///Users/buildbot/Library/Developer/CoreSimulator/Devices/DA6D3C8F-39BE-486B-A6DB-362B7BA75FD3/data/Containers/Bundle/Application/8CD0A3E1-F56D-472F-A546-6B82D7F4A9C7/mobilespec.app/www/cordova.js:1013:39 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: i
[jira] [Resolved] (CB-10522) Event binding in Hello World is misleading
[
https://issues.apache.org/jira/browse/CB-10522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sarangan Rajamanickam resolved CB-10522.
Resolution: Fixed
> Event binding in Hello World is misleading
> --
>
> Key: CB-10522
> URL: https://issues.apache.org/jira/browse/CB-10522
> Project: Apache Cordova
> Issue Type: Bug
> Components: App Hello World
>Reporter: Richard B Knoll
>Assignee: Sarangan Rajamanickam
>Priority: Minor
> Labels: triaged
>
> It is our recommendation that you bind to all of the Cordova events
> ({{pause}}, {{resume}}, etc.) in your {{deviceready}} callback so as to
> ensure that cordova.js and all your plugins are done being loaded. This is
> mentioned in the events guide [in the
> documentation|http://cordova.apache.org/docs/en/latest/cordova/events/events.pause.html]
> However, we include a {{bindEvents}} method in the template which implies
> that all event binding should happen there. We should probably just remove
> {{bindEvents}} altogether and add the event listener for {{deviceready}} in
> the {{initialize}} method since the other events we mention seem to be out of
> date. We should also add a comment explaining where Cordova related events
> should be bound to.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-10632) Contact Plugin tests fail on cordova-andorid-win
Raghav created CB-10632: --- Summary: Contact Plugin tests fail on cordova-andorid-win Key: CB-10632 URL: https://issues.apache.org/jira/browse/CB-10632 Project: Apache Cordova Issue Type: Bug Reporter: Raghav Recent build links: https://ci.apache.org/builders/cordova-android-win/builds/1626 https://ci.apache.org/builders/cordova-android-win/builds/1625 Build log: Failing tests: cordova-plugin-contacts-tests.tests >> Contacts (navigator.contacts) Round trip Contact tests (creating + save + delete + find) contacts.spec.25 Creating, saving, finding a contact should work Expected 2 to be 1. Error: Expected 2 to be 1. at stack (file:///android_asset/www/cdvtests/jasmine-2.2.0/jasmine.js:1455:17) at buildExpectationResult (file:///android_asset/www/cdvtests/jasmine-2.2.0/jasmine.js:1425:14) at Spec.Env.expectationResultFactory (file:///android_asset/www/cdvtests/jasmine-2.2.0/jasmine.js:572:18) at Spec.addExpectationResult (file:///android_asset/www/cdvtests/jasmine-2.2.0/jasmine.js:321:34) at Expectation.addExpectationResult (file:///android_asset/www/cdvtests/jasmine-2.2.0/jasmine.js:516:21) at Expectation.toBe (file:///android_asset/www/cdvtests/jasmine-2.2.0/jasmine.js:1379:12) at findWin (file:///android_asset/www/plugins/cordova-plugin-contacts-tests/tests.js:519:47) at win (file:///android_asset/www/plugins/cordova-plugin-contacts/www/contacts.js:57:17) at Object.cordova.callbackFromNative (file:///android_asset/www/cordova.js:293:58) at processMessage (file:///android_asset/www/cordova.js:1081:17) at processMessages (file:///android_asset/www/cordova.js:1104:9) cordova-plugin-contacts-tests.tests >> Contacts (navigator.contacts) Round trip Contact tests (creating + save + delete + find) contacts.spec.26 Creating, saving, finding a contact should work, removing it should work Expected 2 to be 1. Error: Expected 2 to be 1. at stack (file:///android_asset/www/cdvtests/jasmine-2.2.0/jasmine.js:1455:17) at buildExpectationResult (file:///android_asset/www/cdvtests/jasmine-2.2.0/jasmine.js:1425:14) at Spec.Env.expectationResultFactory (file:///android_asset/www/cdvtests/jasmine-2.2.0/jasmine.js:572:18) at Spec.addExpectationResult (file:///android_asset/www/cdvtests/jasmine-2.2.0/jasmine.js:321:34) at Expectation.addExpectationResult (file:///android_asset/www/cdvtests/jasmine-2.2.0/jasmine.js:516:21) at Expectation.toBe (file:///android_asset/www/cdvtests/jasmine-2.2.0/jasmine.js:1379:12) at findWin (file:///android_asset/www/plugins/cordova-plugin-contacts-tests/tests.js:519:47) at win (file:///android_asset/www/plugins/cordova-plugin-contacts/www/contacts.js:57:17) at Object.cordova.callbackFromNative (file:///android_asset/www/cordova.js:293:58) at processMessage (file:///android_asset/www/cordova.js:1081:17) cordova-plugin-contacts-tests.tests >> Contacts (navigator.contacts) Round trip Contact tests (creating + save + delete + find) contacts.spec.27 Should not be able to delete the same contact twice Expected 2 to be 1. Error: Expected 2 to be 1. at stack (file:///android_asset/www/cdvtests/jasmine-2.2.0/jasmine.js:1455:17) at buildExpectationResult (file:///android_asset/www/cdvtests/jasmine-2.2.0/jasmine.js:1425:14) at Spec.Env.expectationResultFactory (file:///android_asset/www/cdvtests/jasmine-2.2.0/jasmine.js:572:18) at Spec.addExpectationResult (file:///android_asset/www/cdvtests/jasmine-2.2.0/jasmine.js:321:34) at Expectation.addExpectationResult (file:///android_asset/www/cdvtests/jasmine-2.2.0/jasmine.js:516:21) at Expectation.toBe (file:///android_asset/www/cdvtests/jasmine-2.2.0/jasmine.js:1379:12) at findWin (file:///android_asset/www/plugins/cordova-plugin-contacts-tests/tests.js:519:47) at win (file:///android_asset/www/plugins/cordova-plugin-contacts/www/contacts.js:57:17) at Object.cordova.callbackFromNative (file:///android_asset/www/cordova.js:293:58) at processMessage (file:///android_asset/www/cordova.js:1081:17) Expected 1 to be 0. Error: Expected 1 to be 0. at stack (file:///android_asset/www/cdvtests/jasmine-2.2.0/jasmine.js:1455:17) at buildExpectationResult (file:///android_asset/www/cdvtests/jasmine-2.2.0/jasmine.js:1425:14) at Spec.Env.expectationResultFactory (file:///android_asset/www/cdvtests/jasmine-2.2.0
[jira] [Commented] (CB-10522) Event binding in Hello World is misleading
[
https://issues.apache.org/jira/browse/CB-10522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149373#comment-15149373
]
ASF GitHub Bot commented on CB-10522:
-
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-app-hello-world/pull/15
> Event binding in Hello World is misleading
> --
>
> Key: CB-10522
> URL: https://issues.apache.org/jira/browse/CB-10522
> Project: Apache Cordova
> Issue Type: Bug
> Components: App Hello World
>Reporter: Richard B Knoll
>Assignee: Sarangan Rajamanickam
>Priority: Minor
> Labels: triaged
>
> It is our recommendation that you bind to all of the Cordova events
> ({{pause}}, {{resume}}, etc.) in your {{deviceready}} callback so as to
> ensure that cordova.js and all your plugins are done being loaded. This is
> mentioned in the events guide [in the
> documentation|http://cordova.apache.org/docs/en/latest/cordova/events/events.pause.html]
> However, we include a {{bindEvents}} method in the template which implies
> that all event binding should happen there. We should probably just remove
> {{bindEvents}} altogether and add the event listener for {{deviceready}} in
> the {{initialize}} method since the other events we mention seem to be out of
> date. We should also add a comment explaining where Cordova related events
> should be bound to.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10522) Event binding in Hello World is misleading
[
https://issues.apache.org/jira/browse/CB-10522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149372#comment-15149372
]
ASF subversion and git services commented on CB-10522:
--
Commit 4413480de85942a008d2dd0a820e128656d58cf5 in cordova-app-hello-world's
branch refs/heads/master from [~sarangan12]
[
https://git-wip-us.apache.org/repos/asf?p=cordova-app-hello-world.git;h=4413480
]
CB-10522: Event binding in Hello World is misleading
Fixing the Hello World example
> Event binding in Hello World is misleading
> --
>
> Key: CB-10522
> URL: https://issues.apache.org/jira/browse/CB-10522
> Project: Apache Cordova
> Issue Type: Bug
> Components: App Hello World
>Reporter: Richard B Knoll
>Assignee: Sarangan Rajamanickam
>Priority: Minor
> Labels: triaged
>
> It is our recommendation that you bind to all of the Cordova events
> ({{pause}}, {{resume}}, etc.) in your {{deviceready}} callback so as to
> ensure that cordova.js and all your plugins are done being loaded. This is
> mentioned in the events guide [in the
> documentation|http://cordova.apache.org/docs/en/latest/cordova/events/events.pause.html]
> However, we include a {{bindEvents}} method in the template which implies
> that all event binding should happen there. We should probably just remove
> {{bindEvents}} altogether and add the event listener for {{deviceready}} in
> the {{initialize}} method since the other events we mention seem to be out of
> date. We should also add a comment explaining where Cordova related events
> should be bound to.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10522) Event binding in Hello World is misleading
[
https://issues.apache.org/jira/browse/CB-10522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149364#comment-15149364
]
ASF GitHub Bot commented on CB-10522:
-
Github user dblotsky commented on the pull request:
https://github.com/apache/cordova-app-hello-world/pull/15#issuecomment-184885794
Cool, seems like we've reached a consensus. Merging!
> Event binding in Hello World is misleading
> --
>
> Key: CB-10522
> URL: https://issues.apache.org/jira/browse/CB-10522
> Project: Apache Cordova
> Issue Type: Bug
> Components: App Hello World
>Reporter: Richard B Knoll
>Assignee: Sarangan Rajamanickam
>Priority: Minor
> Labels: triaged
>
> It is our recommendation that you bind to all of the Cordova events
> ({{pause}}, {{resume}}, etc.) in your {{deviceready}} callback so as to
> ensure that cordova.js and all your plugins are done being loaded. This is
> mentioned in the events guide [in the
> documentation|http://cordova.apache.org/docs/en/latest/cordova/events/events.pause.html]
> However, we include a {{bindEvents}} method in the template which implies
> that all event binding should happen there. We should probably just remove
> {{bindEvents}} altogether and add the event listener for {{deviceready}} in
> the {{initialize}} method since the other events we mention seem to be out of
> date. We should also add a comment explaining where Cordova related events
> should be bound to.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10628) Fix emulate android --target
[
https://issues.apache.org/jira/browse/CB-10628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149360#comment-15149360
]
ASF GitHub Bot commented on CB-10628:
-
Github user nikhilkh commented on the pull request:
https://github.com/apache/cordova-android/pull/260#issuecomment-184884824
How can we test this?
> Fix emulate android --target
>
>
> Key: CB-10628
> URL: https://issues.apache.org/jira/browse/CB-10628
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Reporter: Sergey Shakhnazarov
>Assignee: Sergey Shakhnazarov
> Labels: regression
>
> {noformat}
> λ cordova emulate android --target=a19
> ANDROID_HOME=e:\Android\Sdk
> JAVA_HOME=C:\Program Files (x86)\java\jdk1.7.0_55
> No emulator specified, defaulting to Nexus_5_API_23_x86
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10574) MobileSpec can't get results for WP8.1 Builds
[
https://issues.apache.org/jira/browse/CB-10574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149341#comment-15149341
]
ASF GitHub Bot commented on CB-10574:
-
Github user dblotsky commented on the pull request:
https://github.com/apache/cordova-plugin-geolocation/pull/71#issuecomment-184882741
LGTM.
> MobileSpec can't get results for WP8.1 Builds
> -
>
> Key: CB-10574
> URL: https://issues.apache.org/jira/browse/CB-10574
> Project: Apache Cordova
> Issue Type: Bug
> Environment: Windows
>Reporter: Omar Mefire
>Assignee: Sarangan Rajamanickam
>Priority: Critical
> Labels: found-by-ci, wp8.1
>
> Log 1:
> (https://ci.apache.org/builders/cordova-windows-phone8.1/builds/1524/steps/running-tests/logs/stdio)
> ==
> CordovaApp.Phone ->
> C:\Users\buildbot\slaves\apache\cordova-windows-phone8_1\mobilespec\platforms\windows\AppPackages\CordovaApp.Phone_0.0.1.0_AnyCPU_bundle_debug.appxupload
> Your package has been successfully created.
> Deploying phone package to emulator:
> C:\Users\buildbot\slaves\apache\cordova-windows-phone8_1\mobilespec\platforms\windows\AppPackages\CordovaApp.Phone_0.0.1.0_debug_Test\CordovaApp.Phone_0.0.1.0_AnyCPU_debug.appxbundle
> Attempting to remove previously installed application...
> Deploying app package...
> didn't get test results: timed out
> program finished with exit code 1
> elapsedTime=1143.444000
>
> Log 2:
> ---
> ERROR running one or more of the platforms: Unexpected error from
> installation: C:\Program Files (x86)\Microsoft SDKs\Windows
> Phone\v8.1\Tools\AppDeploy\AppDeployCmd.exe: Command failed with exit code
> 2148734208 Error output:
> Error: Deployment failed because no Windows Phone was detected. Make sure a
> phone is connected and powered on. You may have previously installed the app
> with an earlier version of cordova-windows. Ensure the app is uninstalled
> from the phone and then try to run again.
> You may not have the required environment or OS to run this project
> [MEDIC LOG Mon, 08 Feb 2016 16:39:10 GMT] no device found, so switching to
> emulator
> ==
> Log 3:
> https://ci.apache.org/builders/cordova-windows-phone8.1/builds/1506/steps/running-tests/logs/stdio
> ---
> Attempting to remove previously installed application...
> Deploying app package...
> query failed for mobilespec_results { [Error: connect ETIMEDOUT] code:
> 'ETIMEDOUT', errno: 'ETIMEDOUT', syscall: 'connect' }
> query failed for mobilespec_results { [Error: connect ETIMEDOUT] code:
> 'ETIMEDOUT', errno: 'ETIMEDOUT', syscall: 'connect' }
> didn't get test results: timed out
> program finished with exit code 1
> elapsedTime=1142.741000
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10574) MobileSpec can't get results for WP8.1 Builds
[
https://issues.apache.org/jira/browse/CB-10574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149339#comment-15149339
]
ASF GitHub Bot commented on CB-10574:
-
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-plugin-geolocation/pull/71
> MobileSpec can't get results for WP8.1 Builds
> -
>
> Key: CB-10574
> URL: https://issues.apache.org/jira/browse/CB-10574
> Project: Apache Cordova
> Issue Type: Bug
> Environment: Windows
>Reporter: Omar Mefire
>Assignee: Sarangan Rajamanickam
>Priority: Critical
> Labels: found-by-ci, wp8.1
>
> Log 1:
> (https://ci.apache.org/builders/cordova-windows-phone8.1/builds/1524/steps/running-tests/logs/stdio)
> ==
> CordovaApp.Phone ->
> C:\Users\buildbot\slaves\apache\cordova-windows-phone8_1\mobilespec\platforms\windows\AppPackages\CordovaApp.Phone_0.0.1.0_AnyCPU_bundle_debug.appxupload
> Your package has been successfully created.
> Deploying phone package to emulator:
> C:\Users\buildbot\slaves\apache\cordova-windows-phone8_1\mobilespec\platforms\windows\AppPackages\CordovaApp.Phone_0.0.1.0_debug_Test\CordovaApp.Phone_0.0.1.0_AnyCPU_debug.appxbundle
> Attempting to remove previously installed application...
> Deploying app package...
> didn't get test results: timed out
> program finished with exit code 1
> elapsedTime=1143.444000
>
> Log 2:
> ---
> ERROR running one or more of the platforms: Unexpected error from
> installation: C:\Program Files (x86)\Microsoft SDKs\Windows
> Phone\v8.1\Tools\AppDeploy\AppDeployCmd.exe: Command failed with exit code
> 2148734208 Error output:
> Error: Deployment failed because no Windows Phone was detected. Make sure a
> phone is connected and powered on. You may have previously installed the app
> with an earlier version of cordova-windows. Ensure the app is uninstalled
> from the phone and then try to run again.
> You may not have the required environment or OS to run this project
> [MEDIC LOG Mon, 08 Feb 2016 16:39:10 GMT] no device found, so switching to
> emulator
> ==
> Log 3:
> https://ci.apache.org/builders/cordova-windows-phone8.1/builds/1506/steps/running-tests/logs/stdio
> ---
> Attempting to remove previously installed application...
> Deploying app package...
> query failed for mobilespec_results { [Error: connect ETIMEDOUT] code:
> 'ETIMEDOUT', errno: 'ETIMEDOUT', syscall: 'connect' }
> query failed for mobilespec_results { [Error: connect ETIMEDOUT] code:
> 'ETIMEDOUT', errno: 'ETIMEDOUT', syscall: 'connect' }
> didn't get test results: timed out
> program finished with exit code 1
> elapsedTime=1142.741000
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10574) MobileSpec can't get results for WP8.1 Builds
[
https://issues.apache.org/jira/browse/CB-10574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149338#comment-15149338
]
ASF subversion and git services commented on CB-10574:
--
Commit aa69e1bf15c5a317d5790045336fd5457eaa8ec7 in cordova-plugin-geolocation's
branch refs/heads/master from [~sarangan12]
[
https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-geolocation.git;h=aa69e1b
]
CB-10574: MobileSpec can't get results for WP8.1 Builds
Adding 'var' to make the variable local.
> MobileSpec can't get results for WP8.1 Builds
> -
>
> Key: CB-10574
> URL: https://issues.apache.org/jira/browse/CB-10574
> Project: Apache Cordova
> Issue Type: Bug
> Environment: Windows
>Reporter: Omar Mefire
>Assignee: Sarangan Rajamanickam
>Priority: Critical
> Labels: found-by-ci, wp8.1
>
> Log 1:
> (https://ci.apache.org/builders/cordova-windows-phone8.1/builds/1524/steps/running-tests/logs/stdio)
> ==
> CordovaApp.Phone ->
> C:\Users\buildbot\slaves\apache\cordova-windows-phone8_1\mobilespec\platforms\windows\AppPackages\CordovaApp.Phone_0.0.1.0_AnyCPU_bundle_debug.appxupload
> Your package has been successfully created.
> Deploying phone package to emulator:
> C:\Users\buildbot\slaves\apache\cordova-windows-phone8_1\mobilespec\platforms\windows\AppPackages\CordovaApp.Phone_0.0.1.0_debug_Test\CordovaApp.Phone_0.0.1.0_AnyCPU_debug.appxbundle
> Attempting to remove previously installed application...
> Deploying app package...
> didn't get test results: timed out
> program finished with exit code 1
> elapsedTime=1143.444000
>
> Log 2:
> ---
> ERROR running one or more of the platforms: Unexpected error from
> installation: C:\Program Files (x86)\Microsoft SDKs\Windows
> Phone\v8.1\Tools\AppDeploy\AppDeployCmd.exe: Command failed with exit code
> 2148734208 Error output:
> Error: Deployment failed because no Windows Phone was detected. Make sure a
> phone is connected and powered on. You may have previously installed the app
> with an earlier version of cordova-windows. Ensure the app is uninstalled
> from the phone and then try to run again.
> You may not have the required environment or OS to run this project
> [MEDIC LOG Mon, 08 Feb 2016 16:39:10 GMT] no device found, so switching to
> emulator
> ==
> Log 3:
> https://ci.apache.org/builders/cordova-windows-phone8.1/builds/1506/steps/running-tests/logs/stdio
> ---
> Attempting to remove previously installed application...
> Deploying app package...
> query failed for mobilespec_results { [Error: connect ETIMEDOUT] code:
> 'ETIMEDOUT', errno: 'ETIMEDOUT', syscall: 'connect' }
> query failed for mobilespec_results { [Error: connect ETIMEDOUT] code:
> 'ETIMEDOUT', errno: 'ETIMEDOUT', syscall: 'connect' }
> didn't get test results: timed out
> program finished with exit code 1
> elapsedTime=1142.741000
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10510) medic-run doesn't check to make sure the emulator started
[
https://issues.apache.org/jira/browse/CB-10510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149332#comment-15149332
]
ASF GitHub Bot commented on CB-10510:
-
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-android/pull/258
> medic-run doesn't check to make sure the emulator started
> -
>
> Key: CB-10510
> URL: https://issues.apache.org/jira/browse/CB-10510
> Project: Apache Cordova
> Issue Type: Test
> Components: Medic
> Environment: Windows, Android emulator
>Reporter: Richard B Knoll
>Assignee: Richard B Knoll
> Labels: android, found-by-ci
>
> Medic doesn't check to see if the emulator actually starts when invoking
> {{cordova run android}}. Instead, it starts polling cordova-vm immediately.
> This might also be considered a bug in cordova-android's run script, which
> just seems to hang if the emulator doesn't start. Example build is here:
> https://ci.apache.org/builders/cordova-android-win/builds/1488/steps/running-tests/logs/stdio
> And adb logs are here:
> https://ci.apache.org/builders/cordova-android-win/builds/1488/steps/gathering-logs/logs/stdio
>
> Log:
> C:\Users\buildbot\slaves\apache\cordova-android-win\mobilespec>node
> C:\Users\buildbot\slaves\apache\cordova-android-win\cordova-cli\bin\cordova
> run --emulator android -- --gradle
> ANDROID_HOME=C:\Android\android-sdk
> JAVA_HOME=C:\Program Files (x86)\Java\jdk1.7.0_55
> No emulator specified, defaulting to Galaxy_Nexus
> Waiting for emulator...
> WARNING: init: Missing WGL extension WGL_ARB_make_current_read
> emulator: warning: opening audio output failed
> emulator: emulator window was out of view and was recentered
> emulator: UpdateChecker: skipped version check
> Booting up emulator (this may take a
> while)query failed for
> mobilespec_results { [Error: connect ETIMEDOUT] code: 'ETIMEDOUT', errno:
> 'ETIMEDOUT', syscall: 'connect' }
> .query failed for mobilespec_results {
> [Error: connect ETIMEDOUT] code: 'ETIMEDOUT', errno: 'ETIMEDOUT', syscall:
> 'connect' }
> ..query failed for mobilespec_results { [Error: connect
> ETIMEDOUT] code: 'ETIMEDOUT', errno: 'ETIMEDOUT', syscall: 'connect' }
> query
> failed for mobilespec_results { [Error: connect ETIMEDOUT] code:
> 'ETIMEDOUT', errno: 'ETIMEDOUT', syscall: 'connect' }
> ...query
> failed for mobilespec_results { [Error: connect ETIMEDOUT] code:
> 'ETIMEDOUT', errno: 'ETIMEDOUT', syscall: 'connect' }
> ...didn't get test
> results: timed out
> program finished with exit code 1
> elapsedTime=1150.659000
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10510) medic-run doesn't check to make sure the emulator started
[
https://issues.apache.org/jira/browse/CB-10510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149331#comment-15149331
]
ASF subversion and git services commented on CB-10510:
--
Commit 723393168127524f5f23d931bbcf171edbd08d39 in cordova-android's branch
refs/heads/master from riknoll
[ https://git-wip-us.apache.org/repos/asf?p=cordova-android.git;h=7233931 ]
CB-10510: Add an optional timeout to emu start script
The script used to wait forever for the emulator to boot.
If the emulator got stuck, it would never terminate.
This timeout is being added to support cordova-medic and
the CI.
> medic-run doesn't check to make sure the emulator started
> -
>
> Key: CB-10510
> URL: https://issues.apache.org/jira/browse/CB-10510
> Project: Apache Cordova
> Issue Type: Test
> Components: Medic
> Environment: Windows, Android emulator
>Reporter: Richard B Knoll
>Assignee: Richard B Knoll
> Labels: android, found-by-ci
>
> Medic doesn't check to see if the emulator actually starts when invoking
> {{cordova run android}}. Instead, it starts polling cordova-vm immediately.
> This might also be considered a bug in cordova-android's run script, which
> just seems to hang if the emulator doesn't start. Example build is here:
> https://ci.apache.org/builders/cordova-android-win/builds/1488/steps/running-tests/logs/stdio
> And adb logs are here:
> https://ci.apache.org/builders/cordova-android-win/builds/1488/steps/gathering-logs/logs/stdio
>
> Log:
> C:\Users\buildbot\slaves\apache\cordova-android-win\mobilespec>node
> C:\Users\buildbot\slaves\apache\cordova-android-win\cordova-cli\bin\cordova
> run --emulator android -- --gradle
> ANDROID_HOME=C:\Android\android-sdk
> JAVA_HOME=C:\Program Files (x86)\Java\jdk1.7.0_55
> No emulator specified, defaulting to Galaxy_Nexus
> Waiting for emulator...
> WARNING: init: Missing WGL extension WGL_ARB_make_current_read
> emulator: warning: opening audio output failed
> emulator: emulator window was out of view and was recentered
> emulator: UpdateChecker: skipped version check
> Booting up emulator (this may take a
> while)query failed for
> mobilespec_results { [Error: connect ETIMEDOUT] code: 'ETIMEDOUT', errno:
> 'ETIMEDOUT', syscall: 'connect' }
> .query failed for mobilespec_results {
> [Error: connect ETIMEDOUT] code: 'ETIMEDOUT', errno: 'ETIMEDOUT', syscall:
> 'connect' }
> ..query failed for mobilespec_results { [Error: connect
> ETIMEDOUT] code: 'ETIMEDOUT', errno: 'ETIMEDOUT', syscall: 'connect' }
> query
> failed for mobilespec_results { [Error: connect ETIMEDOUT] code:
> 'ETIMEDOUT', errno: 'ETIMEDOUT', syscall: 'connect' }
> ...query
> failed for mobilespec_results { [Error: connect ETIMEDOUT] code:
> 'ETIMEDOUT', errno: 'ETIMEDOUT', syscall: 'connect' }
> ...didn't get test
> results: timed out
> program finished with exit code 1
> elapsedTime=1150.659000
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10574) MobileSpec can't get results for WP8.1 Builds
[
https://issues.apache.org/jira/browse/CB-10574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149329#comment-15149329
]
ASF GitHub Bot commented on CB-10574:
-
GitHub user sarangan12 opened a pull request:
https://github.com/apache/cordova-plugin-geolocation/pull/71
CB-10574: MobileSpec can't get results for WP8.1 Builds
Adding 'var' to make the variable local.
@dblotsky @rakatyal Can you review and merge this PR?
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sarangan12/cordova-plugin-geolocation CB-10574
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cordova-plugin-geolocation/pull/71.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #71
commit aa69e1bf15c5a317d5790045336fd5457eaa8ec7
Author: Sarangan Rajamanickam
Date: 2016-02-16T21:24:58Z
CB-10574: MobileSpec can't get results for WP8.1 Builds
Adding 'var' to make the variable local.
> MobileSpec can't get results for WP8.1 Builds
> -
>
> Key: CB-10574
> URL: https://issues.apache.org/jira/browse/CB-10574
> Project: Apache Cordova
> Issue Type: Bug
> Environment: Windows
>Reporter: Omar Mefire
>Assignee: Sarangan Rajamanickam
>Priority: Critical
> Labels: found-by-ci, wp8.1
>
> Log 1:
> (https://ci.apache.org/builders/cordova-windows-phone8.1/builds/1524/steps/running-tests/logs/stdio)
> ==
> CordovaApp.Phone ->
> C:\Users\buildbot\slaves\apache\cordova-windows-phone8_1\mobilespec\platforms\windows\AppPackages\CordovaApp.Phone_0.0.1.0_AnyCPU_bundle_debug.appxupload
> Your package has been successfully created.
> Deploying phone package to emulator:
> C:\Users\buildbot\slaves\apache\cordova-windows-phone8_1\mobilespec\platforms\windows\AppPackages\CordovaApp.Phone_0.0.1.0_debug_Test\CordovaApp.Phone_0.0.1.0_AnyCPU_debug.appxbundle
> Attempting to remove previously installed application...
> Deploying app package...
> didn't get test results: timed out
> program finished with exit code 1
> elapsedTime=1143.444000
>
> Log 2:
> ---
> ERROR running one or more of the platforms: Unexpected error from
> installation: C:\Program Files (x86)\Microsoft SDKs\Windows
> Phone\v8.1\Tools\AppDeploy\AppDeployCmd.exe: Command failed with exit code
> 2148734208 Error output:
> Error: Deployment failed because no Windows Phone was detected. Make sure a
> phone is connected and powered on. You may have previously installed the app
> with an earlier version of cordova-windows. Ensure the app is uninstalled
> from the phone and then try to run again.
> You may not have the required environment or OS to run this project
> [MEDIC LOG Mon, 08 Feb 2016 16:39:10 GMT] no device found, so switching to
> emulator
> ==
> Log 3:
> https://ci.apache.org/builders/cordova-windows-phone8.1/builds/1506/steps/running-tests/logs/stdio
> ---
> Attempting to remove previously installed application...
> Deploying app package...
> query failed for mobilespec_results { [Error: connect ETIMEDOUT] code:
> 'ETIMEDOUT', errno: 'ETIMEDOUT', syscall: 'connect' }
> query failed for mobilespec_results { [Error: connect ETIMEDOUT] code:
> 'ETIMEDOUT', errno: 'ETIMEDOUT', syscall: 'connect' }
> didn't get test results: timed out
> program finished with exit code 1
> elapsedTime=1142.741000
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-10631) device is not populated in iOS 5.1.1
Thomas Allen created CB-10631: - Summary: device is not populated in iOS 5.1.1 Key: CB-10631 URL: https://issues.apache.org/jira/browse/CB-10631 Project: Apache Cordova Issue Type: Bug Components: Plugin Device Environment: iOS 5.1.1 Reporter: Thomas Allen The device plugin doesn't work in iOS 5.1.1 because the unique device identifier uses identifierForVendor to get the device uuid. However this is not valid in iOS older than 6.0. In the method uniqueAppInstanceIdentifier, there is a reference to maintaining backward compatibility for versions that didn't use identiferForVendor. Unfortunately the code only works if the app had previously been installed on that device (because it looks for the CDVUUID that was previously stored on the device). If the install is new, this app_uuid is nil and it tries to use identifierForVendor. I realize that iOS 5 is no longer supported in Cordova, but since the code attempts to be backward compatible (based on the inline comments), I figured this could be fixed with a few lines of code (which I have done and will submit shortly). -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10522) Event binding in Hello World is misleading
[
https://issues.apache.org/jira/browse/CB-10522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149214#comment-15149214
]
ASF GitHub Bot commented on CB-10522:
-
Github user devgeeks commented on the pull request:
https://github.com/apache/cordova-app-hello-world/pull/15#issuecomment-184856505
LGTM. That third layer of binding always seemed confusing.
:+1:
> Event binding in Hello World is misleading
> --
>
> Key: CB-10522
> URL: https://issues.apache.org/jira/browse/CB-10522
> Project: Apache Cordova
> Issue Type: Bug
> Components: App Hello World
>Reporter: Richard B Knoll
>Assignee: Sarangan Rajamanickam
>Priority: Minor
> Labels: triaged
>
> It is our recommendation that you bind to all of the Cordova events
> ({{pause}}, {{resume}}, etc.) in your {{deviceready}} callback so as to
> ensure that cordova.js and all your plugins are done being loaded. This is
> mentioned in the events guide [in the
> documentation|http://cordova.apache.org/docs/en/latest/cordova/events/events.pause.html]
> However, we include a {{bindEvents}} method in the template which implies
> that all event binding should happen there. We should probably just remove
> {{bindEvents}} altogether and add the event listener for {{deviceready}} in
> the {{initialize}} method since the other events we mention seem to be out of
> date. We should also add a comment explaining where Cordova related events
> should be bound to.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-10401) Connectivity Issue to github from cordova-medic
[ https://issues.apache.org/jira/browse/CB-10401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Khandelwal updated CB-10401: --- Issue Type: Test (was: Bug) > Connectivity Issue to github from cordova-medic > --- > > Key: CB-10401 > URL: https://issues.apache.org/jira/browse/CB-10401 > Project: Apache Cordova > Issue Type: Test >Reporter: Sarangan Rajamanickam >Assignee: Sarangan Rajamanickam > Labels: found-by-ci > > In the Apache CI for Cordova, there is code that clones git repositories from > GitHub. There are intermittent issues and when the github server could not be > connected, the task fails and this impacts the CI builds. > Ref Links: > - > https://ci.apache.org/builders/cordova-android-win/builds/1389/steps/cloning%20cordova-plugin-media/logs/stdio > - > https://ci.apache.org/builders/cordova-windows-store8.1/builds/1404/steps/cloning%20cordova-plugin-geolocation/logs/stdio -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-10474) Gathering logs fails in cordova-ios CI
[
https://issues.apache.org/jira/browse/CB-10474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikhil Khandelwal updated CB-10474:
---
Issue Type: Test (was: Bug)
> Gathering logs fails in cordova-ios CI
> --
>
> Key: CB-10474
> URL: https://issues.apache.org/jira/browse/CB-10474
> Project: Apache Cordova
> Issue Type: Test
> Components: Medic
> Environment: OSX
>Reporter: Richard B Knoll
>Assignee: Richard B Knoll
> Labels: found-by-ci, ios, triaged
>
> In the cordova-ios Build Bot CI, the gathering logs step always fails. It
> tries to {{cat}} a file for the log that does not exist. Here is an example
> build:
> https://ci.apache.org/builders/cordova-ios/builds/1607/steps/gathering-logs/logs/stdio
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-10510) medic-run doesn't check to make sure the emulator started
[
https://issues.apache.org/jira/browse/CB-10510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikhil Khandelwal updated CB-10510:
---
Issue Type: Test (was: Bug)
> medic-run doesn't check to make sure the emulator started
> -
>
> Key: CB-10510
> URL: https://issues.apache.org/jira/browse/CB-10510
> Project: Apache Cordova
> Issue Type: Test
> Components: Medic
> Environment: Windows, Android emulator
>Reporter: Richard B Knoll
>Assignee: Richard B Knoll
> Labels: android, found-by-ci
>
> Medic doesn't check to see if the emulator actually starts when invoking
> {{cordova run android}}. Instead, it starts polling cordova-vm immediately.
> This might also be considered a bug in cordova-android's run script, which
> just seems to hang if the emulator doesn't start. Example build is here:
> https://ci.apache.org/builders/cordova-android-win/builds/1488/steps/running-tests/logs/stdio
> And adb logs are here:
> https://ci.apache.org/builders/cordova-android-win/builds/1488/steps/gathering-logs/logs/stdio
>
> Log:
> C:\Users\buildbot\slaves\apache\cordova-android-win\mobilespec>node
> C:\Users\buildbot\slaves\apache\cordova-android-win\cordova-cli\bin\cordova
> run --emulator android -- --gradle
> ANDROID_HOME=C:\Android\android-sdk
> JAVA_HOME=C:\Program Files (x86)\Java\jdk1.7.0_55
> No emulator specified, defaulting to Galaxy_Nexus
> Waiting for emulator...
> WARNING: init: Missing WGL extension WGL_ARB_make_current_read
> emulator: warning: opening audio output failed
> emulator: emulator window was out of view and was recentered
> emulator: UpdateChecker: skipped version check
> Booting up emulator (this may take a
> while)query failed for
> mobilespec_results { [Error: connect ETIMEDOUT] code: 'ETIMEDOUT', errno:
> 'ETIMEDOUT', syscall: 'connect' }
> .query failed for mobilespec_results {
> [Error: connect ETIMEDOUT] code: 'ETIMEDOUT', errno: 'ETIMEDOUT', syscall:
> 'connect' }
> ..query failed for mobilespec_results { [Error: connect
> ETIMEDOUT] code: 'ETIMEDOUT', errno: 'ETIMEDOUT', syscall: 'connect' }
> query
> failed for mobilespec_results { [Error: connect ETIMEDOUT] code:
> 'ETIMEDOUT', errno: 'ETIMEDOUT', syscall: 'connect' }
> ...query
> failed for mobilespec_results { [Error: connect ETIMEDOUT] code:
> 'ETIMEDOUT', errno: 'ETIMEDOUT', syscall: 'connect' }
> ...didn't get test
> results: timed out
> program finished with exit code 1
> elapsedTime=1150.659000
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-10542) cordova-plugin-inappbrowser.spec.4 test timeout issue
[ https://issues.apache.org/jira/browse/CB-10542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Khandelwal updated CB-10542: --- Issue Type: Test (was: Bug) > cordova-plugin-inappbrowser.spec.4 test timeout issue > - > > Key: CB-10542 > URL: https://issues.apache.org/jira/browse/CB-10542 > Project: Apache Cordova > Issue Type: Test >Reporter: Omar Mefire > Labels: found-by-ci, inappbrowser, medic > > Link: > https://ci.apache.org/builders/cordova-android-win/builds/1484/steps/getting-test-results/logs/stdio > === > cordova-plugin-inappbrowser-tests.tests >> open method inappbrowser.spec.4 > should support loadstart and loadstop events > Error: Timeout - Async callback was not invoked within timeout > specified by jasmine.DEFAULT_TIMEOUT_INTERVAL. > Error: Timeout - Async callback was not invoked within timeout > specified by jasmine.DEFAULT_TIMEOUT_INTERVAL. > at > file:///android_asset/www/cdvtests/jasmine-2.2.0/jasmine.js:1764:23 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-10535) cordova-plugin-media causes iOS app crash - 'NSInvalidArgumentException'
[ https://issues.apache.org/jira/browse/CB-10535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omar Mefire resolved CB-10535. -- Resolution: Fixed > cordova-plugin-media causes iOS app crash - 'NSInvalidArgumentException' > > > Key: CB-10535 > URL: https://issues.apache.org/jira/browse/CB-10535 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Media >Reporter: Omar Mefire >Assignee: Omar Mefire >Priority: Critical > Labels: found-by-ci, ios, triaged > > CI fails with timeout: > https://ci.apache.org/builders/cordova-ios/builds/1663/steps/running-tests/logs/stdio > This might be due to this crash: > https://ci.apache.org/builders/cordova-ios/builds/1663/steps/gathering-logs/logs/stdio > I suspect this might be caused by a cordova-plugin-media failure > == > File Content: > Feb 4 12:23:29 dbtiefighter mobilespec[62230]: Playing stream with AVPlayer > & custom rate > Feb 4 12:23:30 dbtiefighter mobilespec[62230]: Stopped playing audio sample > 'http://cordova.apache.org/downloads/BlueZedEx.mp3' > Feb 4 12:23:30 dbtiefighter mobilespec[62230]: Media with id > 609de056-dc4d-d301-d0e4-ee6df181 released > Feb 4 12:23:30 dbtiefighter mobilespec[62230]: Will use resource > 'http://cordova.apache.org/downloads/BlueZedEx.mp3' from the Internet. > Feb 4 12:23:30 dbtiefighter mobilespec[62230]: Playing audio sample > 'http://cordova.apache.org/downloads/BlueZedEx.mp3' > Feb 4 12:23:30 dbtiefighter mobilespec[62230]: Playing stream with AVPlayer > & custom rate > Feb 4 12:23:30 dbtiefighter mobilespec[62230]: *** Terminating app due to > uncaught exception 'NSInvalidArgumentException', reason: 'AVPlayerItem cannot > service a seek request with a completion handler until its status is > AVPlayerItemStatusReadyToPlay.' > *** First throw call stack: > ( > 0 CoreFoundation 0x01cb4a84 > __exceptionPreprocess + 180 > 1 libobjc.A.dylib 0x0174ee02 > objc_exception_throw + 50 > 2 AVFoundation0x007855ae > -[AVPlayerItem seekToTime:toleranceBefore:toleranceAfter:completionHandler:] > + 1714 > 3 AVFoundation0x0076e49e -[AVPlayer > seekToTime:toleranceBefore:toleranceAfter:completionHandler:] + 174 > 4 mobilespec 0x0014cb96 -[CDVSound > seekToAudio:] + 2054 > 5 mobilespec 0x001791a8 > -[CDVCommandQueue execute:] + 888 > 6 mobilespec 0x00178a00 > -[CDVCommandQueue executePending] + 848 > 7 mobilespec 0x0016df2d > __40-[CDVCommandDelegateImpl evalJsHelper2:]_block_invoke + 349 > 8 mobilespec 0x0017be35 > -[CDVUIWebViewEngine evaluateJavaScript:completionHandler:] + 181 > 9 mobilespec 0x0016dd7d > -[CDVCommandDelegateImpl evalJsHelper2:] + 237 > 10 libobjc.A.dylib 0x01763059 -[NSObject > performSelector:withObject:] + 70 > 11 Foundation 0x0135d178 > __NSThreadPerformPerform + 323 > 12 CoreFoundation 0x01bced1f > __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 15 > 13 CoreFoundation 0x01bc49ab > __CFRunLoopDoSources0 + 523 > 14 CoreFoundation 0x01bc3dc8 > __CFRunLoopRun + 1032 > 15 CoreFoundation 0x01bc3706 > CFRunLoopRunSpecific + 470 > 16 CoreFoundation 0x01bc351b > CFRunLoopRunInMode + 123 > 17 GraphicsServices0x05f2f664 > GSEventRunModal + 192 > 18 GraphicsServices0x05f2f4a1 GSEventRun + > 104 > 19 UIKit 0x024801eb > UIApplicationMain + 160 > 20 mobilespec 0x000e42a9 main + 89 > 21 libdyld.dylib 0x04039a21 start + 1 > ) > Feb 4 12:23:30 dbtiefighter SpringBoard[16597]: HW kbd: Failed to set (null) > as keyboard focus > Feb 4 12:23:30 dbtiefighter > com.apple.CoreSimulator.SimDevice.DA6D3C8F-39BE-486B-A6DB-362B7BA75FD3.launchd_sim[16580] > (UIKitApplication:org.apache.mobilespec[0x7778][62230]): Service exited due > to signal: Abort trap: 6 > Feb 4 12:23:31 dbtiefighter SpringBoard[16597]: Application > 'UIKitApplication:org.apache.mobilespec[0x7778]' crashed. > Feb 4 12:23:31 dbtiefighter assertiond[16601]: assertion failed: 14F1509 > 13B137: assertiond +
[jira] [Resolved] (CB-10540) Mobilespec failure: ENOENT, no such file or directory 'mobilespec/www/medic.json'
[ https://issues.apache.org/jira/browse/CB-10540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raghav resolved CB-10540. - Resolution: Fixed > Mobilespec failure: ENOENT, no such file or directory > 'mobilespec/www/medic.json' > - > > Key: CB-10540 > URL: https://issues.apache.org/jira/browse/CB-10540 > Project: Apache Cordova > Issue Type: Test > Components: mobile-spec >Reporter: Omar Mefire >Assignee: Raghav > Labels: Android, found-by-ci > > Link: > https://ci.apache.org/builders/cordova-android-osx/builds/1692/steps/running-tests/logs/stdio > === > [MEDIC LOG Thu, 04 Feb 2016 12:49:15 GMT] sha: > cordova-android-osx-1692-buildbot-vm > [MEDIC LOG Thu, 04 Feb 2016 12:49:15 GMT] couchdb: > http://cordova-vm.apache.org:5984 > fs.js:500 > return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode); > ^ > Error: ENOENT, no such file or directory 'mobilespec/www/medic.json' > at Error (native) > at Object.fs.openSync (fs.js:500:18) > at Object.fs.writeFileSync (fs.js:1099:15) > at createMedicJson > (/Users/buildbot/slaves/apache/cordova-android-osx/cordova-medic/medic/medic-run.js:86:8) > at > /Users/buildbot/slaves/apache/cordova-android-osx/cordova-medic/medic/medic-run.js:356:9 > at Request. > (/Users/buildbot/slaves/apache/cordova-android-osx/cordova-medic/medic/medic-run.js:305:9) > at Request.emit (events.js:107:17) > at Request.onRequestResponse > (/Users/buildbot/slaves/apache/cordova-android-osx/cordova-medic/node_modules/request/request.js:1156:10) > at ClientRequest.emit (events.js:107:17) > at HTTPParser.parserOnIncomingClient [as onIncoming] > (_http_client.js:426:21) > program finished with exit code 1 > elapsedTime=40.421384 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-10628) Fix emulate android --target
[
https://issues.apache.org/jira/browse/CB-10628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikhil Khandelwal updated CB-10628:
---
Labels: regression (was: )
> Fix emulate android --target
>
>
> Key: CB-10628
> URL: https://issues.apache.org/jira/browse/CB-10628
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Reporter: Sergey Shakhnazarov
>Assignee: Sergey Shakhnazarov
> Labels: regression
>
> {noformat}
> λ cordova emulate android --target=a19
> ANDROID_HOME=e:\Android\Sdk
> JAVA_HOME=C:\Program Files (x86)\java\jdk1.7.0_55
> No emulator specified, defaulting to Nexus_5_API_23_x86
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-10235) Add clearer error message for info command when Android SDK is setup incorrectly
[ https://issues.apache.org/jira/browse/CB-10235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Tran resolved CB-10235. - Resolution: Fixed Assignee: Karen Tran > Add clearer error message for info command when Android SDK is setup > incorrectly > > > Key: CB-10235 > URL: https://issues.apache.org/jira/browse/CB-10235 > Project: Apache Cordova > Issue Type: Improvement > Components: CordovaLib >Affects Versions: Master > Environment: Android >Reporter: Karen Tran >Assignee: Karen Tran >Priority: Minor > Labels: android, info, triaged > Fix For: Master > > > Issuing a 'cordova info' command without having the Android SDK setup > correctly prints an unhelpful error message. > Error retrieving Android platform information: Error: cmd: Command failed > with exit code 1 Error output: 'android' is not recognized as an internal or > external command, operable program or batch file. > Should add a message to make sure Android SDK tools and platform-tools > directories are added to the PATH variable. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10510) medic-run doesn't check to make sure the emulator started
[
https://issues.apache.org/jira/browse/CB-10510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149070#comment-15149070
]
ASF GitHub Bot commented on CB-10510:
-
Github user riknoll commented on the pull request:
https://github.com/apache/cordova-android/pull/258#issuecomment-184821410
@omefire
> medic-run doesn't check to make sure the emulator started
> -
>
> Key: CB-10510
> URL: https://issues.apache.org/jira/browse/CB-10510
> Project: Apache Cordova
> Issue Type: Bug
> Components: Medic
> Environment: Windows, Android emulator
>Reporter: Richard B Knoll
>Assignee: Richard B Knoll
> Labels: android, found-by-ci
>
> Medic doesn't check to see if the emulator actually starts when invoking
> {{cordova run android}}. Instead, it starts polling cordova-vm immediately.
> This might also be considered a bug in cordova-android's run script, which
> just seems to hang if the emulator doesn't start. Example build is here:
> https://ci.apache.org/builders/cordova-android-win/builds/1488/steps/running-tests/logs/stdio
> And adb logs are here:
> https://ci.apache.org/builders/cordova-android-win/builds/1488/steps/gathering-logs/logs/stdio
>
> Log:
> C:\Users\buildbot\slaves\apache\cordova-android-win\mobilespec>node
> C:\Users\buildbot\slaves\apache\cordova-android-win\cordova-cli\bin\cordova
> run --emulator android -- --gradle
> ANDROID_HOME=C:\Android\android-sdk
> JAVA_HOME=C:\Program Files (x86)\Java\jdk1.7.0_55
> No emulator specified, defaulting to Galaxy_Nexus
> Waiting for emulator...
> WARNING: init: Missing WGL extension WGL_ARB_make_current_read
> emulator: warning: opening audio output failed
> emulator: emulator window was out of view and was recentered
> emulator: UpdateChecker: skipped version check
> Booting up emulator (this may take a
> while)query failed for
> mobilespec_results { [Error: connect ETIMEDOUT] code: 'ETIMEDOUT', errno:
> 'ETIMEDOUT', syscall: 'connect' }
> .query failed for mobilespec_results {
> [Error: connect ETIMEDOUT] code: 'ETIMEDOUT', errno: 'ETIMEDOUT', syscall:
> 'connect' }
> ..query failed for mobilespec_results { [Error: connect
> ETIMEDOUT] code: 'ETIMEDOUT', errno: 'ETIMEDOUT', syscall: 'connect' }
> query
> failed for mobilespec_results { [Error: connect ETIMEDOUT] code:
> 'ETIMEDOUT', errno: 'ETIMEDOUT', syscall: 'connect' }
> ...query
> failed for mobilespec_results { [Error: connect ETIMEDOUT] code:
> 'ETIMEDOUT', errno: 'ETIMEDOUT', syscall: 'connect' }
> ...didn't get test
> results: timed out
> program finished with exit code 1
> elapsedTime=1150.659000
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10518) Cordova reports error events with incorrect log level
[
https://issues.apache.org/jira/browse/CB-10518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149069#comment-15149069
]
ASF GitHub Bot commented on CB-10518:
-
Github user nikhilkh commented on a diff in the pull request:
https://github.com/apache/cordova-lib/pull/383#discussion_r53056714
--- Diff: cordova-lib/src/cordova/compile.js ---
@@ -40,7 +40,7 @@ module.exports = function compile(options) {
}).then(function() {
return hooksRunner.fire('after_compile', options);
}, function(error) {
-events.emit('log', 'ERROR building one of the platforms: ' + error
+ '\nYou may not have the required environment or OS to build this project');
+events.emit('warn', 'ERROR building one of the platforms: ' +
error + '\nYou may not have the required environment or OS to build this
project');
--- End diff --
Let's remove the warning if it's not needed and looks like other commands
do not log anyway.
> Cordova reports error events with incorrect log level
> -
>
> Key: CB-10518
> URL: https://issues.apache.org/jira/browse/CB-10518
> Project: Apache Cordova
> Issue Type: Bug
> Components: CordovaLib
>Affects Versions: 6.0.0
>Reporter: Vladimir Kotikov
>Priority: Minor
> Labels: triaged
>
> In case of fatal errors {{cordova run}} and {{cordova emulate}} methods emit
> error messages using {{log}} event. This code probably should be changed to
> use 'warn' level. (We can't use 'error' here due to its special meaning in
> Node: https://nodejs.org/api/events.html#events_error_events)
> There is also other places, where 'log' events is used incorrectly:
> cordova-lib\src\cordova\targets.js:events.emit('log', 'An unexpected
> error has occured');
> cordova-lib\src\plugman\browserify.js:events.emit('log', 'error while
> generating cordova.js');
> cordova-lib\src\plugman\browserify.js:events.emit('log', 'Error
> running platform version script');
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-8198) Unified console output logic for core platforms
[ https://issues.apache.org/jira/browse/CB-8198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149061#comment-15149061 ] Vladimir Kotikov commented on CB-8198: -- [~daserge], Isn't this resolved already? > Unified console output logic for core platforms > --- > > Key: CB-8198 > URL: https://issues.apache.org/jira/browse/CB-8198 > Project: Apache Cordova > Issue Type: New Feature > Components: Android, iOS, Windows, WP8 (deprecated) >Reporter: Vladimir Kotikov >Assignee: Jesse MacFadyen > > Currently all major platform scripts doesn't recognize trace levels and > always logging all their output to console. > This could be unuseful, especially when a huge output from build tools is put > to console (ant build/xcodebuild output is really huge and in most cases is > unnecessary) > I propose to unify the way we write messages to console output: > 1. Pass verbosity arguments (-d, --debug ) downstream to platform scripts. > 2. Introduce special Log class which is shared across platform scripts > * automatically detects trace level according to command line arguments; > * support of output redirection (file, other) in the future? > 3. Add support for the following verbosity levels: Error, Normal, Debug > * by default: Error and Normal messages are traced > * -silent: only Error messages are traced > * -verbose: everything is traced -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-8199) Add support for verbosity levels for platform scripts
[ https://issues.apache.org/jira/browse/CB-8199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149060#comment-15149060 ] Vladimir Kotikov commented on CB-8199: -- [~daserge], i think this should be closed as stale. This functionality is now replaces by unified console logging. > Add support for verbosity levels for platform scripts > -- > > Key: CB-8199 > URL: https://issues.apache.org/jira/browse/CB-8199 > Project: Apache Cordova > Issue Type: Sub-task > Components: Android, iOS, Windows, WP8 (deprecated) >Reporter: Vladimir Kotikov >Assignee: Jesse MacFadyen > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10332) Improve Android Guide
[ https://issues.apache.org/jira/browse/CB-10332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149052#comment-15149052 ] ASF GitHub Bot commented on CB-10332: - Github user riknoll commented on the pull request: https://github.com/apache/cordova-docs/pull/471#issuecomment-184817446 Rebased to master and updated to fix the redirects merged in with #494 > Improve Android Guide > - > > Key: CB-10332 > URL: https://issues.apache.org/jira/browse/CB-10332 > Project: Apache Cordova > Issue Type: Task > Components: Docs >Reporter: Raghav >Assignee: Richard B Knoll > Labels: Docs-6.x > > We did a document scrub and found the following issues. Please feel free to > correct other things as well. > - Android Platform Guide > -- Install Cordova Shell tools is out of date > -- Environment variable instructions for Windows are out of date > -- Emulator section can just point to > http://developer.android.com/tools/devices/emulator.html > -- Lots of duplicated content for create/build/deploy from CLI page > -- Page keeps switching between CLI and platform-centric workflow > - Android Shell Tool Guide > -- Second paragraph is out of date > -- Create/build/run/logging/clean should be clear that this is the > platform-centric workflow. Also duplicated in Android Platform guide > -- Platform-centric workflow should probably just get its own explicit page > -- Signing an app doesn't actually say how to sign an app. Gives arguments > for some mystery command > --- Does this belong in our docs? We might just mention it and point to > Google's app signing instructions > - Android WebViews > -- Needs investigation if this is still supported. > --- Step 1 is wrong (should be getting cordova-android by cloning or from npm) > --- Step 3 needs to have instructions for adding jars to gradle > --- Step 5 is out of date. CordovaActivity does not implement > CordovaInterface... Think they should be extending/modifying CordovaActivity. > Needs investigation > --- Step 6 does not appear to be camera plugin specific > --- Step 7 example is useless, it needs to be fleshed out > - Android plugins > -- Should be moved to plugin developer docs > -- Need a reference for the classes that plugins have access to > --- CordovaWebView, CallbackContext, CordovaPlugin, etc. > --- Most already have javadoc > -- Android Integration should be renamed and link to the Android classes it's > talking about > -- Debugging Android plugins is out of date (mentions Eclipse and jars) and > should probably be fleshed out a bit > - Android Configuration > -- Should be a reference > - Upgrading Android > -- Ends at 4.0.0 (current is 4.1.1, soon to be 5.0.0) > -- Needs to be reorganized in some way > --- The instructions seem to be pretty much the same for versions 1.6.0 + > -- Goes back to the phonegap days! Should probably only include Cordova > versions (1.5.0 +) > -- Upgrade to 1.8.0 from 1.7.0 repeated twice > -- Upgrade to 1.8.0 from 1.8.0 is a typo > General guidelines: > - While giving examples, keep them short. Do not repeat for all > plugins/platforms. > - Remove all references to cordova plugin registry. > - Remove Tizen references. The platform is deprecated > (http://markmail.org/message/hryg6sjswecpgndu) > - Keep information up to date for the platforms, CLI and plugins -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10510) medic-run doesn't check to make sure the emulator started
[
https://issues.apache.org/jira/browse/CB-10510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149024#comment-15149024
]
ASF GitHub Bot commented on CB-10510:
-
Github user riknoll commented on the pull request:
https://github.com/apache/cordova-android/pull/258#issuecomment-184808170
@vladimir-kotikov can you take a quick look at this? I want to make sure
I'm not messing with the platform API at all given that we don't have any tests
for this code path.
> medic-run doesn't check to make sure the emulator started
> -
>
> Key: CB-10510
> URL: https://issues.apache.org/jira/browse/CB-10510
> Project: Apache Cordova
> Issue Type: Bug
> Components: Medic
> Environment: Windows, Android emulator
>Reporter: Richard B Knoll
>Assignee: Richard B Knoll
> Labels: android, found-by-ci
>
> Medic doesn't check to see if the emulator actually starts when invoking
> {{cordova run android}}. Instead, it starts polling cordova-vm immediately.
> This might also be considered a bug in cordova-android's run script, which
> just seems to hang if the emulator doesn't start. Example build is here:
> https://ci.apache.org/builders/cordova-android-win/builds/1488/steps/running-tests/logs/stdio
> And adb logs are here:
> https://ci.apache.org/builders/cordova-android-win/builds/1488/steps/gathering-logs/logs/stdio
>
> Log:
> C:\Users\buildbot\slaves\apache\cordova-android-win\mobilespec>node
> C:\Users\buildbot\slaves\apache\cordova-android-win\cordova-cli\bin\cordova
> run --emulator android -- --gradle
> ANDROID_HOME=C:\Android\android-sdk
> JAVA_HOME=C:\Program Files (x86)\Java\jdk1.7.0_55
> No emulator specified, defaulting to Galaxy_Nexus
> Waiting for emulator...
> WARNING: init: Missing WGL extension WGL_ARB_make_current_read
> emulator: warning: opening audio output failed
> emulator: emulator window was out of view and was recentered
> emulator: UpdateChecker: skipped version check
> Booting up emulator (this may take a
> while)query failed for
> mobilespec_results { [Error: connect ETIMEDOUT] code: 'ETIMEDOUT', errno:
> 'ETIMEDOUT', syscall: 'connect' }
> .query failed for mobilespec_results {
> [Error: connect ETIMEDOUT] code: 'ETIMEDOUT', errno: 'ETIMEDOUT', syscall:
> 'connect' }
> ..query failed for mobilespec_results { [Error: connect
> ETIMEDOUT] code: 'ETIMEDOUT', errno: 'ETIMEDOUT', syscall: 'connect' }
> query
> failed for mobilespec_results { [Error: connect ETIMEDOUT] code:
> 'ETIMEDOUT', errno: 'ETIMEDOUT', syscall: 'connect' }
> ...query
> failed for mobilespec_results { [Error: connect ETIMEDOUT] code:
> 'ETIMEDOUT', errno: 'ETIMEDOUT', syscall: 'connect' }
> ...didn't get test
> results: timed out
> program finished with exit code 1
> elapsedTime=1150.659000
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-8198) Unified console output logic for core platforms
[ https://issues.apache.org/jira/browse/CB-8198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Shakhnazarov updated CB-8198: Assignee: Jesse MacFadyen (was: Sergey Shakhnazarov) > Unified console output logic for core platforms > --- > > Key: CB-8198 > URL: https://issues.apache.org/jira/browse/CB-8198 > Project: Apache Cordova > Issue Type: New Feature > Components: Android, iOS, Windows, WP8 (deprecated) >Reporter: Vladimir Kotikov >Assignee: Jesse MacFadyen > > Currently all major platform scripts doesn't recognize trace levels and > always logging all their output to console. > This could be unuseful, especially when a huge output from build tools is put > to console (ant build/xcodebuild output is really huge and in most cases is > unnecessary) > I propose to unify the way we write messages to console output: > 1. Pass verbosity arguments (-d, --debug ) downstream to platform scripts. > 2. Introduce special Log class which is shared across platform scripts > * automatically detects trace level according to command line arguments; > * support of output redirection (file, other) in the future? > 3. Add support for the following verbosity levels: Error, Normal, Debug > * by default: Error and Normal messages are traced > * -silent: only Error messages are traced > * -verbose: everything is traced -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-8199) Add support for verbosity levels for platform scripts
[ https://issues.apache.org/jira/browse/CB-8199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Shakhnazarov updated CB-8199: Assignee: Jesse MacFadyen (was: Sergey Shakhnazarov) > Add support for verbosity levels for platform scripts > -- > > Key: CB-8199 > URL: https://issues.apache.org/jira/browse/CB-8199 > Project: Apache Cordova > Issue Type: Sub-task > Components: Android, iOS, Windows, WP8 (deprecated) >Reporter: Vladimir Kotikov >Assignee: Jesse MacFadyen > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-9133) CDVFILE NOT WORKING???
[ https://issues.apache.org/jira/browse/CB-9133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Shakhnazarov updated CB-9133: Assignee: (was: Sergey Shakhnazarov) > CDVFILE NOT WORKING??? > -- > > Key: CB-9133 > URL: https://issues.apache.org/jira/browse/CB-9133 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Whitelist >Reporter: Michael Romanovsky >Priority: Critical > > I used the instructions here: > https://github.com/apache/cordova-plugin-whitelist > I have this in my config.xml file: > > > > I have this in my .HTML file: > > I get these errors: > Refused to load the script 'http://d3aq14vri881or.cloudfront.net/kiip.js' > because it violates the following Content Security Policy directive: > "script-src 'self' 'unsafe-inline' 'unsafe-eval'". > Refused to load the script 'cdvfile://localhost/persistent/free.min.js' > because it violates the following Content Security Policy directive: > "script-src 'self' 'unsafe-inline' 'unsafe-eval'". > HELP?! -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-9928) Add support for PATCH request uploads
[ https://issues.apache.org/jira/browse/CB-9928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Shakhnazarov updated CB-9928: Assignee: (was: Sergey Shakhnazarov) > Add support for PATCH request uploads > - > > Key: CB-9928 > URL: https://issues.apache.org/jira/browse/CB-9928 > Project: Apache Cordova > Issue Type: Improvement > Components: Plugin File Transfer >Reporter: Sergey Shakhnazarov > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-9744) Plugin documentation should be generated from source code
[ https://issues.apache.org/jira/browse/CB-9744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Shakhnazarov updated CB-9744: Assignee: (was: Sergey Shakhnazarov) > Plugin documentation should be generated from source code > - > > Key: CB-9744 > URL: https://issues.apache.org/jira/browse/CB-9744 > Project: Apache Cordova > Issue Type: Task >Reporter: Sergey Shakhnazarov > > [cordova-discuss PR|https://github.com/cordova/cordova-discuss/pull/16] -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-9839) Add gzip support to file-transfer.download on wp8
[ https://issues.apache.org/jira/browse/CB-9839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Shakhnazarov updated CB-9839: Assignee: (was: Sergey Shakhnazarov) > Add gzip support to file-transfer.download on wp8 > - > > Key: CB-9839 > URL: https://issues.apache.org/jira/browse/CB-9839 > Project: Apache Cordova > Issue Type: New Feature > Components: Plugin File Transfer >Reporter: Sergey Shakhnazarov > Labels: gzip, wp8 > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Closed] (CB-10557) Plugins Release Feb 8, 2016
[ https://issues.apache.org/jira/browse/CB-10557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Kotikov closed CB-10557. - Resolution: Fixed > Plugins Release Feb 8, 2016 > --- > > Key: CB-10557 > URL: https://issues.apache.org/jira/browse/CB-10557 > Project: Apache Cordova > Issue Type: Task > Components: Plugin File, Plugin Media, Plugin SplashScreen, Plugin > Statusbar, Plugin WKWebViewEngine >Reporter: Vladimir Kotikov >Assignee: Vladimir Kotikov > > Following steps at > https://github.com/apache/cordova-coho/blob/master/docs/plugins-release-process.md > The following patches to be included into this release: > cordova-plugin-file: > CB-10419 cordova-plugin-file 4.0.0 error with browserify workflow > cordova-plugin-wkwebview-engine: > CB-10269: Replace cordova exec only when present in wkwebview > cordova-plugin-media: > CB-10476 cordova-plugin-media 2.1.0 dos not fire mediaSuccess > CB-10455 android: Adding permission helper to remove cordova-android 5.0.0 > constraint > cordova-plugin-splashscreen: > CB-10422 Splashscreen displays black screen with no image on Android > CB-10412 AutoHideSplashScreen "false" isn't taken in account on iOS > CB-9516 Android SplashScreen - Spinner Does Not Display > CB-9094: Smarter autohide logic on Android > CB-8396 Add AutoHideSplashScreen logic to Android's Splashscreen > cordova-plugin-statusbar > CB-10102 statusbar removeObserver is wrong -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10604) resource-file tag in plugin.xml for cordova-windows generates incorrect link
[ https://issues.apache.org/jira/browse/CB-10604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15148935#comment-15148935 ] Nikhil Khandelwal commented on CB-10604: Good to see that this is now resolved with the PR here: https://github.com/apache/cordova-windows/pull/139. > resource-file tag in plugin.xml for cordova-windows generates incorrect link > > > Key: CB-10604 > URL: https://issues.apache.org/jira/browse/CB-10604 > Project: Apache Cordova > Issue Type: Bug > Components: Windows >Reporter: James Dubee > > When using the resource-file tag in plugin.xml for cordova-windows, the link > tag generated in the .jsproj has the wrong value. > plugin.xml example: > device-target="win" > target="plugins/cordova-plugin-mfp-jsonstore/win/ARM/msvcr110.dll" > custom="true" arch="ARM" /> > .jsproj file content: > > Include="plugins/cordova-plugin-mfp-jsonstore/win/ARM/sqlite3.dll"> > > plugins/cordova-plugin-mfp-jsonstore/win/ARM/sqlite3.dll > Always > > > Wanted .jsproj content: > > Include="plugins/cordova-plugin-mfp-jsonstore/win/ARM/sqlite3.dll"> > sqlite3.dll > Always > > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10618) A logic for gradle frameworks processing should be in platform instead of LIB
[
https://issues.apache.org/jira/browse/CB-10618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15148928#comment-15148928
]
ASF GitHub Bot commented on CB-10618:
-
Github user nikhilkh commented on the pull request:
https://github.com/apache/cordova-android/pull/259#issuecomment-184778783
LGTM. How can we add tests for this scenario?
> A logic for gradle frameworks processing should be in platform instead of LIB
> -
>
> Key: CB-10618
> URL: https://issues.apache.org/jira/browse/CB-10618
> Project: Apache Cordova
> Issue Type: Task
> Components: Android, CordovaLib
>Affects Versions: 5.2.0, 6.0.1
>Reporter: Vladimir Kotikov
>Assignee: Vladimir Kotikov
>
> After each plugin installtion/uninstallation LIB calls
> {{build.prepBuildFiles()}} from android platform. However, since this is
> platform-specific logic, this should be something that happens inside
> addPlugin() function in cordova-android Api.js
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10628) Fix emulate android --target
[
https://issues.apache.org/jira/browse/CB-10628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15148864#comment-15148864
]
ASF GitHub Bot commented on CB-10628:
-
GitHub user daserge opened a pull request:
https://github.com/apache/cordova-android/pull/260
CB-10628 Fix emulate android --target
[Jira issue](https://issues.apache.org/jira/browse/CB-10628)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/MSOpenTech/cordova-android CB-10628
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cordova-android/pull/260.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #260
commit faecaed409f7c9736882ba29601f6d3976ea2ce0
Author: daserge
Date: 2016-02-16T16:20:49Z
CB-10628 Fix emulate android --target
> Fix emulate android --target
>
>
> Key: CB-10628
> URL: https://issues.apache.org/jira/browse/CB-10628
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Reporter: Sergey Shakhnazarov
>Assignee: Sergey Shakhnazarov
>
> {noformat}
> λ cordova emulate android --target=a19
> ANDROID_HOME=e:\Android\Sdk
> JAVA_HOME=C:\Program Files (x86)\java\jdk1.7.0_55
> No emulator specified, defaulting to Nexus_5_API_23_x86
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10624) whitelist.js shouldn't detect for CSP and throw error message
[ https://issues.apache.org/jira/browse/CB-10624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15148826#comment-15148826 ] ASF GitHub Bot commented on CB-10624: - Github user eymorale commented on the pull request: https://github.com/apache/cordova-plugin-whitelist/pull/17#issuecomment-184741324 @infil00p and @csantanapr can you take a look at this and see if you have any problems with it? > whitelist.js shouldn't detect for CSP and throw error message > - > > Key: CB-10624 > URL: https://issues.apache.org/jira/browse/CB-10624 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Whitelist >Reporter: Edna Morales >Assignee: Edna Morales >Priority: Minor > > Whitelist plugin throws "No Content-Security-Policy meta tag found. Please > add one when using the cordova-plugin-whitelist plugin." error. whitelist.js > shouldn't detect for CSP and throw an error if not present since it's only > applicable to Android and is not necessary for the whitelist plugin to work. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10624) whitelist.js shouldn't detect for CSP and throw error message
[ https://issues.apache.org/jira/browse/CB-10624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15148823#comment-15148823 ] ASF GitHub Bot commented on CB-10624: - GitHub user eymorale opened a pull request: https://github.com/apache/cordova-plugin-whitelist/pull/17 CB-10624 remove error message from whitelist.js, which leaves it empty You can merge this pull request into a Git repository by running: $ git pull https://github.com/eymorale/cordova-plugin-whitelist CB-10624 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-plugin-whitelist/pull/17.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #17 commit a50abe34afb4d62f84eec844f733e5fd8c890c86 Author: Edna Morales Date: 2016-02-16T14:57:56Z CB-10624 remove error message from whitelist.js, which leaves it empty > whitelist.js shouldn't detect for CSP and throw error message > - > > Key: CB-10624 > URL: https://issues.apache.org/jira/browse/CB-10624 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Whitelist >Reporter: Edna Morales >Assignee: Edna Morales >Priority: Minor > > Whitelist plugin throws "No Content-Security-Policy meta tag found. Please > add one when using the cordova-plugin-whitelist plugin." error. whitelist.js > shouldn't detect for CSP and throw an error if not present since it's only > applicable to Android and is not necessary for the whitelist plugin to work. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-10574) MobileSpec can't get results for WP8.1 Builds
[
https://issues.apache.org/jira/browse/CB-10574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sarangan Rajamanickam resolved CB-10574.
Resolution: Fixed
> MobileSpec can't get results for WP8.1 Builds
> -
>
> Key: CB-10574
> URL: https://issues.apache.org/jira/browse/CB-10574
> Project: Apache Cordova
> Issue Type: Bug
> Environment: Windows
>Reporter: Omar Mefire
>Assignee: Sarangan Rajamanickam
>Priority: Critical
> Labels: found-by-ci, wp8.1
>
> Log 1:
> (https://ci.apache.org/builders/cordova-windows-phone8.1/builds/1524/steps/running-tests/logs/stdio)
> ==
> CordovaApp.Phone ->
> C:\Users\buildbot\slaves\apache\cordova-windows-phone8_1\mobilespec\platforms\windows\AppPackages\CordovaApp.Phone_0.0.1.0_AnyCPU_bundle_debug.appxupload
> Your package has been successfully created.
> Deploying phone package to emulator:
> C:\Users\buildbot\slaves\apache\cordova-windows-phone8_1\mobilespec\platforms\windows\AppPackages\CordovaApp.Phone_0.0.1.0_debug_Test\CordovaApp.Phone_0.0.1.0_AnyCPU_debug.appxbundle
> Attempting to remove previously installed application...
> Deploying app package...
> didn't get test results: timed out
> program finished with exit code 1
> elapsedTime=1143.444000
>
> Log 2:
> ---
> ERROR running one or more of the platforms: Unexpected error from
> installation: C:\Program Files (x86)\Microsoft SDKs\Windows
> Phone\v8.1\Tools\AppDeploy\AppDeployCmd.exe: Command failed with exit code
> 2148734208 Error output:
> Error: Deployment failed because no Windows Phone was detected. Make sure a
> phone is connected and powered on. You may have previously installed the app
> with an earlier version of cordova-windows. Ensure the app is uninstalled
> from the phone and then try to run again.
> You may not have the required environment or OS to run this project
> [MEDIC LOG Mon, 08 Feb 2016 16:39:10 GMT] no device found, so switching to
> emulator
> ==
> Log 3:
> https://ci.apache.org/builders/cordova-windows-phone8.1/builds/1506/steps/running-tests/logs/stdio
> ---
> Attempting to remove previously installed application...
> Deploying app package...
> query failed for mobilespec_results { [Error: connect ETIMEDOUT] code:
> 'ETIMEDOUT', errno: 'ETIMEDOUT', syscall: 'connect' }
> query failed for mobilespec_results { [Error: connect ETIMEDOUT] code:
> 'ETIMEDOUT', errno: 'ETIMEDOUT', syscall: 'connect' }
> didn't get test results: timed out
> program finished with exit code 1
> elapsedTime=1142.741000
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-10552) Pull all the plugin docs to Cordova
[ https://issues.apache.org/jira/browse/CB-10552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sarangan Rajamanickam resolved CB-10552. Resolution: Fixed > Pull all the plugin docs to Cordova > --- > > Key: CB-10552 > URL: https://issues.apache.org/jira/browse/CB-10552 > Project: Apache Cordova > Issue Type: Task >Reporter: Sarangan Rajamanickam >Assignee: Sarangan Rajamanickam > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Assigned] (CB-10624) whitelist.js shouldn't detect for CSP and throw error message
[ https://issues.apache.org/jira/browse/CB-10624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edna Morales reassigned CB-10624: - Assignee: Edna Morales > whitelist.js shouldn't detect for CSP and throw error message > - > > Key: CB-10624 > URL: https://issues.apache.org/jira/browse/CB-10624 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Whitelist >Reporter: Edna Morales >Assignee: Edna Morales >Priority: Minor > > Whitelist plugin throws "No Content-Security-Policy meta tag found. Please > add one when using the cordova-plugin-whitelist plugin." error. whitelist.js > shouldn't detect for CSP and throw an error if not present since it's only > applicable to Android and is not necessary for the whitelist plugin to work. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10619) Appium tests fail to switch context to webview on Windows slave's Android emulator
[
https://issues.apache.org/jira/browse/CB-10619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15148600#comment-15148600
]
ASF GitHub Bot commented on CB-10619:
-
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-plugin-camera/pull/171
> Appium tests fail to switch context to webview on Windows slave's Android
> emulator
> --
>
> Key: CB-10619
> URL: https://issues.apache.org/jira/browse/CB-10619
> Project: Apache Cordova
> Issue Type: Bug
> Components: Medic
>Reporter: Alexander Sorokin
>Assignee: Alexander Sorokin
>
> Here's a log sample
> {noformat}
> > RESPONSE
> > init({"browserName":"","appium-version":"1.3","platformName":"Android","platformVersion":19,"deviceName":"Galaxy_Nexus","app":"C:\\Users\\buildbot\\slaves\\apache\\cordova-android-win\\mobilespec\\platforms\\android\\build\\outputs\\apk\\android-debug.apk","autoAcceptAlerts":true})
> > "7dc6d1dd-d4ef-41aa-ac32-a3400d333e6b",null
> > CALL setImplicitWaitTimeout(1)
> > POST /session/:sessionID/timeouts/implicit_wait {"ms":1}
> > RESPONSE setImplicitWaitTimeout(1)
> > CALL sleep(2)
> > RESPONSE sleep(2)
> > CALL sleep(1)
> > RESPONSE sleep(1)
> [MEDIC LOG Mon, 15 Feb 2016 07:54:00 GMT] Spec passed: camera.ui.util
> configuring driver and starting a session
> [MEDIC LOG Mon, 15 Feb 2016 07:54:00 GMT] Starting new spec: camera.ui.spec.1
> Saving the picture to photo library
> > CALL context("WEBVIEW")
> > POST /session/:sessionID/context {"name":"WEBVIEW"}
> > CALL context("WEBVIEW")
> > POST /session/:sessionID/context {"name":"WEBVIEW"}
> > CALL elementById("middle")
> > POST /session/:sessionID/element {"using":"id","value":"middle"}
> [MEDIC LOG Mon, 15 Feb 2016 07:59:20 GMT] Spec failed: camera.ui.spec.1
> Saving the picture to photo library
> [MEDIC LOG Mon, 15 Feb 2016 07:59:20 GMT] Starting new spec: camera.ui.spec.2
> Selecting only videos
> > CALL context("WEBVIEW")
> > POST /session/:sessionID/context {"name":"WEBVIEW"}
> > CALL context("WEBVIEW")
> > POST /session/:sessionID/context {"name":"WEBVIEW"}
> > CALL elementById("middle")
> > POST /session/:sessionID/element {"using":"id","value":"middle"}
> > CALL execute("var info = document.createElement(\"div\"); info.id =
> \"info\"; document.body.appendChild(info);")
> > POST /session/:sessionID/execute {"script":"var info =
> document.createElement(\"div\"); info.id = \"info\";
> document.body.appendChild(info);","args":[]}
> An error occured: [execute("var info = document.createElement(\"div\");
> info.id = \"info\"; document.body.appendChild(info);")] Error response
> status: 6,
> Failing with message: [execute("var info = document.createElement(\"div\");
> info.id = \"info\"; document.body.appendChild(info);")] Error response
> status: 6,
> [MEDIC LOG Mon, 15 Feb 2016 07:59:20 GMT] Spec failed: camera.ui.spec.2
> Selecting only videos
> {noformat}
> Upon initial investigation I found that it is a bug in chromedriver:
> https://github.com/appium/appium/issues/5616
> It has been fixed in a new chromedriver version but Appium didn't bundle it
> yet.
> As a temporary workaround we can specify "chromedriverBinary" as a desired
> capability when starting appium session and point it to a newer chromedriver
> binary.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10619) Appium tests fail to switch context to webview on Windows slave's Android emulator
[
https://issues.apache.org/jira/browse/CB-10619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15148599#comment-15148599
]
ASF subversion and git services commented on CB-10619:
--
Commit 61b77951e11cfdae8eaf5e6b2f8392b4822239f5 in cordova-plugin-camera's
branch refs/heads/master from [~alsorokin]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-camera.git;h=61b7795
]
CB-10619 Appium tests: Properly switch to webview
> Appium tests fail to switch context to webview on Windows slave's Android
> emulator
> --
>
> Key: CB-10619
> URL: https://issues.apache.org/jira/browse/CB-10619
> Project: Apache Cordova
> Issue Type: Bug
> Components: Medic
>Reporter: Alexander Sorokin
>Assignee: Alexander Sorokin
>
> Here's a log sample
> {noformat}
> > RESPONSE
> > init({"browserName":"","appium-version":"1.3","platformName":"Android","platformVersion":19,"deviceName":"Galaxy_Nexus","app":"C:\\Users\\buildbot\\slaves\\apache\\cordova-android-win\\mobilespec\\platforms\\android\\build\\outputs\\apk\\android-debug.apk","autoAcceptAlerts":true})
> > "7dc6d1dd-d4ef-41aa-ac32-a3400d333e6b",null
> > CALL setImplicitWaitTimeout(1)
> > POST /session/:sessionID/timeouts/implicit_wait {"ms":1}
> > RESPONSE setImplicitWaitTimeout(1)
> > CALL sleep(2)
> > RESPONSE sleep(2)
> > CALL sleep(1)
> > RESPONSE sleep(1)
> [MEDIC LOG Mon, 15 Feb 2016 07:54:00 GMT] Spec passed: camera.ui.util
> configuring driver and starting a session
> [MEDIC LOG Mon, 15 Feb 2016 07:54:00 GMT] Starting new spec: camera.ui.spec.1
> Saving the picture to photo library
> > CALL context("WEBVIEW")
> > POST /session/:sessionID/context {"name":"WEBVIEW"}
> > CALL context("WEBVIEW")
> > POST /session/:sessionID/context {"name":"WEBVIEW"}
> > CALL elementById("middle")
> > POST /session/:sessionID/element {"using":"id","value":"middle"}
> [MEDIC LOG Mon, 15 Feb 2016 07:59:20 GMT] Spec failed: camera.ui.spec.1
> Saving the picture to photo library
> [MEDIC LOG Mon, 15 Feb 2016 07:59:20 GMT] Starting new spec: camera.ui.spec.2
> Selecting only videos
> > CALL context("WEBVIEW")
> > POST /session/:sessionID/context {"name":"WEBVIEW"}
> > CALL context("WEBVIEW")
> > POST /session/:sessionID/context {"name":"WEBVIEW"}
> > CALL elementById("middle")
> > POST /session/:sessionID/element {"using":"id","value":"middle"}
> > CALL execute("var info = document.createElement(\"div\"); info.id =
> \"info\"; document.body.appendChild(info);")
> > POST /session/:sessionID/execute {"script":"var info =
> document.createElement(\"div\"); info.id = \"info\";
> document.body.appendChild(info);","args":[]}
> An error occured: [execute("var info = document.createElement(\"div\");
> info.id = \"info\"; document.body.appendChild(info);")] Error response
> status: 6,
> Failing with message: [execute("var info = document.createElement(\"div\");
> info.id = \"info\"; document.body.appendChild(info);")] Error response
> status: 6,
> [MEDIC LOG Mon, 15 Feb 2016 07:59:20 GMT] Spec failed: camera.ui.spec.2
> Selecting only videos
> {noformat}
> Upon initial investigation I found that it is a bug in chromedriver:
> https://github.com/appium/appium/issues/5616
> It has been fixed in a new chromedriver version but Appium didn't bundle it
> yet.
> As a temporary workaround we can specify "chromedriverBinary" as a desired
> capability when starting appium session and point it to a newer chromedriver
> binary.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10619) Appium tests fail to switch context to webview on Windows slave's Android emulator
[
https://issues.apache.org/jira/browse/CB-10619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15148584#comment-15148584
]
ASF GitHub Bot commented on CB-10619:
-
GitHub user alsorokin opened a pull request:
https://github.com/apache/cordova-plugin-camera/pull/171
CB-10619 Appium tests: Properly switch to webview
https://issues.apache.org/jira/browse/CB-10619
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/MSOpenTech/cordova-plugin-camera CB-10619
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cordova-plugin-camera/pull/171.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #171
commit 61b77951e11cfdae8eaf5e6b2f8392b4822239f5
Author: Alexander Sorokin
Date: 2016-02-16T13:28:43Z
CB-10619 Appium tests: Properly switch to webview
> Appium tests fail to switch context to webview on Windows slave's Android
> emulator
> --
>
> Key: CB-10619
> URL: https://issues.apache.org/jira/browse/CB-10619
> Project: Apache Cordova
> Issue Type: Bug
> Components: Medic
>Reporter: Alexander Sorokin
>Assignee: Alexander Sorokin
>
> Here's a log sample
> {noformat}
> > RESPONSE
> > init({"browserName":"","appium-version":"1.3","platformName":"Android","platformVersion":19,"deviceName":"Galaxy_Nexus","app":"C:\\Users\\buildbot\\slaves\\apache\\cordova-android-win\\mobilespec\\platforms\\android\\build\\outputs\\apk\\android-debug.apk","autoAcceptAlerts":true})
> > "7dc6d1dd-d4ef-41aa-ac32-a3400d333e6b",null
> > CALL setImplicitWaitTimeout(1)
> > POST /session/:sessionID/timeouts/implicit_wait {"ms":1}
> > RESPONSE setImplicitWaitTimeout(1)
> > CALL sleep(2)
> > RESPONSE sleep(2)
> > CALL sleep(1)
> > RESPONSE sleep(1)
> [MEDIC LOG Mon, 15 Feb 2016 07:54:00 GMT] Spec passed: camera.ui.util
> configuring driver and starting a session
> [MEDIC LOG Mon, 15 Feb 2016 07:54:00 GMT] Starting new spec: camera.ui.spec.1
> Saving the picture to photo library
> > CALL context("WEBVIEW")
> > POST /session/:sessionID/context {"name":"WEBVIEW"}
> > CALL context("WEBVIEW")
> > POST /session/:sessionID/context {"name":"WEBVIEW"}
> > CALL elementById("middle")
> > POST /session/:sessionID/element {"using":"id","value":"middle"}
> [MEDIC LOG Mon, 15 Feb 2016 07:59:20 GMT] Spec failed: camera.ui.spec.1
> Saving the picture to photo library
> [MEDIC LOG Mon, 15 Feb 2016 07:59:20 GMT] Starting new spec: camera.ui.spec.2
> Selecting only videos
> > CALL context("WEBVIEW")
> > POST /session/:sessionID/context {"name":"WEBVIEW"}
> > CALL context("WEBVIEW")
> > POST /session/:sessionID/context {"name":"WEBVIEW"}
> > CALL elementById("middle")
> > POST /session/:sessionID/element {"using":"id","value":"middle"}
> > CALL execute("var info = document.createElement(\"div\"); info.id =
> \"info\"; document.body.appendChild(info);")
> > POST /session/:sessionID/execute {"script":"var info =
> document.createElement(\"div\"); info.id = \"info\";
> document.body.appendChild(info);","args":[]}
> An error occured: [execute("var info = document.createElement(\"div\");
> info.id = \"info\"; document.body.appendChild(info);")] Error response
> status: 6,
> Failing with message: [execute("var info = document.createElement(\"div\");
> info.id = \"info\"; document.body.appendChild(info);")] Error response
> status: 6,
> [MEDIC LOG Mon, 15 Feb 2016 07:59:20 GMT] Spec failed: camera.ui.spec.2
> Selecting only videos
> {noformat}
> Upon initial investigation I found that it is a bug in chromedriver:
> https://github.com/appium/appium/issues/5616
> It has been fixed in a new chromedriver version but Appium didn't bundle it
> yet.
> As a temporary workaround we can specify "chromedriverBinary" as a desired
> capability when starting appium session and point it to a newer chromedriver
> binary.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10519) Using cordova.raw API outside of cordova project results in uncaught exception instead or promise rejection
[
https://issues.apache.org/jira/browse/CB-10519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15148555#comment-15148555
]
ASF GitHub Bot commented on CB-10519:
-
Github user TimBarham commented on the pull request:
https://github.com/apache/cordova-lib/pull/384#issuecomment-184676141
Thanks @vladimir-kotikov. Looks good on a quick look through. Will take a
closer look in the morning.
> Using cordova.raw API outside of cordova project results in uncaught
> exception instead or promise rejection
> ---
>
> Key: CB-10519
> URL: https://issues.apache.org/jira/browse/CB-10519
> Project: Apache Cordova
> Issue Type: Bug
> Components: CordovaLib
>Affects Versions: 6.0.0
>Reporter: Vladimir Kotikov
>Assignee: Vladimir Kotikov
> Labels: triaged
>
> When trying to {{cordova.raw.platfom('add', ...)}} outside of cordova project
> the following error message logged to console:
> > Error: Current working directory is not a Cordova-based project.
> However, the error callback for {{cordova.raw.platfom('add', ...)}} isn't
> called at all.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-10630) Add plugin overrides platform's www directory with project's root www directory.
Ramesh Katare created CB-10630: -- Summary: Add plugin overrides platform's www directory with project's root www directory. Key: CB-10630 URL: https://issues.apache.org/jira/browse/CB-10630 Project: Apache Cordova Issue Type: Bug Components: CLI Affects Versions: 5.4.0, 6.0.0 Reporter: Ramesh Katare When add plugin cordova overrides platform's www folder with project's root www directory. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10519) Using cordova.raw API outside of cordova project results in uncaught exception instead or promise rejection
[
https://issues.apache.org/jira/browse/CB-10519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15148534#comment-15148534
]
ASF GitHub Bot commented on CB-10519:
-
Github user vladimir-kotikov commented on the pull request:
https://github.com/apache/cordova-lib/pull/384#issuecomment-184667609
@TimBarham, updated
> Using cordova.raw API outside of cordova project results in uncaught
> exception instead or promise rejection
> ---
>
> Key: CB-10519
> URL: https://issues.apache.org/jira/browse/CB-10519
> Project: Apache Cordova
> Issue Type: Bug
> Components: CordovaLib
>Affects Versions: 6.0.0
>Reporter: Vladimir Kotikov
>Assignee: Vladimir Kotikov
> Labels: triaged
>
> When trying to {{cordova.raw.platfom('add', ...)}} outside of cordova project
> the following error message logged to console:
> > Error: Current working directory is not a Cordova-based project.
> However, the error callback for {{cordova.raw.platfom('add', ...)}} isn't
> called at all.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10598) Unable to run javascript in Cordova iOS project on simulator
[
https://issues.apache.org/jira/browse/CB-10598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15148501#comment-15148501
]
jcesarmobile commented on CB-10598:
---
You don't have to open the index.html on safari, you have to use the Safari
feature called "Remote web inspector". You run the app on your device or
simulator and then use that feature. For more information read this:
http://developer.telerik.com/featured/a-concise-guide-to-remote-debugging-on-ios-android-and-windows-phone/
This is not the place to help newbiews, if you have problems with app
development, ask on the phonegap google group or stack overflow.
> Unable to run javascript in Cordova iOS project on simulator
>
>
> Key: CB-10598
> URL: https://issues.apache.org/jira/browse/CB-10598
> Project: Apache Cordova
> Issue Type: Bug
> Components: CordovaJS, iOS
>Affects Versions: 5.4.1
> Environment: Mac OSX El Capitan, Xcode v7.2
>Reporter: Sumit Soman
>
> I created a cordova project, added the iOS platform and built the project.
> After that I opened the .xcodeproj in Xcode, built it and the homepage showed
> the sample app homescreen. I then created another js file with the following
> content in the Staging/js folder
> function testLoad(){
> alert("Loaded!");
> }
> In index.html, I added
>
> and called the function
>
> However no alert appears! How to fix? I am using xCode 7.2.1 and Cordova
> 5.4.1.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10598) Unable to run javascript in Cordova iOS project on simulator
[
https://issues.apache.org/jira/browse/CB-10598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15148496#comment-15148496
]
Sumit Soman commented on CB-10598:
--
I'm a newbie with this and would appreciate if I could be helped with these
issues that may be trivial to you.
I opened the index.html file in Safari and got the following error in the web
inspector:
Refused to load the script
'file:///Users/testProj/platforms/ios/www/cordova.js' because it violates the
following Content Security Policy directive: "default-src 'unsafe-inline' data:
gap: https://ssl.gstatic.com 'unsafe-eval'". Note that 'script-src' was not
explicitly set, so 'default-src' is used as a fallback.
My index.html Content Security Policy reads as:
https://ssl.gstatic.com 'unsafe-eval'; style-src 'self'
'unsafe-inline'; media-src *">
Could you please tell me how this can be fixed?
> Unable to run javascript in Cordova iOS project on simulator
>
>
> Key: CB-10598
> URL: https://issues.apache.org/jira/browse/CB-10598
> Project: Apache Cordova
> Issue Type: Bug
> Components: CordovaJS, iOS
>Affects Versions: 5.4.1
> Environment: Mac OSX El Capitan, Xcode v7.2
>Reporter: Sumit Soman
>
> I created a cordova project, added the iOS platform and built the project.
> After that I opened the .xcodeproj in Xcode, built it and the homepage showed
> the sample app homescreen. I then created another js file with the following
> content in the Staging/js folder
> function testLoad(){
> alert("Loaded!");
> }
> In index.html, I added
>
> and called the function
>
> However no alert appears! How to fix? I am using xCode 7.2.1 and Cordova
> 5.4.1.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10519) Using cordova.raw API outside of cordova project results in uncaught exception instead or promise rejection
[
https://issues.apache.org/jira/browse/CB-10519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15148431#comment-15148431
]
ASF GitHub Bot commented on CB-10519:
-
Github user TimBarham commented on a diff in the pull request:
https://github.com/apache/cordova-lib/pull/384#discussion_r52993992
--- Diff: cordova-lib/src/cordova/build.js ---
@@ -17,22 +17,26 @@
under the License.
*/
-var cordovaUtil = require('./util'),
-HooksRunner = require('../hooks/HooksRunner');
+var Q = require('q'),
+cordovaUtil = require('./util'),
+HooksRunner = require('../hooks/HooksRunner');
// Returns a promise.
module.exports = function build(options) {
-var projectRoot = cordovaUtil.cdProjectRoot();
-options = cordovaUtil.preProcessOptions(options);
-
-// fire build hooks
-var hooksRunner = new HooksRunner(projectRoot);
-return hooksRunner.fire('before_build', options)
-.then(function() {
-return require('./cordova').raw.prepare(options);
-}).then(function() {
-return require('./cordova').raw.compile(options);
-}).then(function() {
-return hooksRunner.fire('after_build', options);
+return Q().then(function() {
+var opts = cordovaUtil.preProcessOptions(options);
+var projectRoot = cordovaUtil.cdProjectRoot();
+return [new HooksRunner(projectRoot), opts];
+})
+.spread(function (hooksRunner, options) {
--- End diff --
Well, that'd be my preference, as the code ends up much simpler and easy to
read, to my mind. Otherwise we're arbitrarily splitting out the synchronous
part of the process into its own separate promise, when there's no need to. But
ultimately it's up to you :smile:.
> Using cordova.raw API outside of cordova project results in uncaught
> exception instead or promise rejection
> ---
>
> Key: CB-10519
> URL: https://issues.apache.org/jira/browse/CB-10519
> Project: Apache Cordova
> Issue Type: Bug
> Components: CordovaLib
>Affects Versions: 6.0.0
>Reporter: Vladimir Kotikov
>Assignee: Vladimir Kotikov
> Labels: triaged
>
> When trying to {{cordova.raw.platfom('add', ...)}} outside of cordova project
> the following error message logged to console:
> > Error: Current working directory is not a Cordova-based project.
> However, the error callback for {{cordova.raw.platfom('add', ...)}} isn't
> called at all.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-10629) Cannot build Android due to missing decl
[
https://issues.apache.org/jira/browse/CB-10629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jordan Zimmerman updated CB-10629:
--
Description:
android 5.1.0
cordova-plugin-inappbrowser
cordova-plugin-actionsheet
cordova-plugin-facebook4
uk.co.workingedge.phonegap.plugin.launchnavigator
{panel}
:compileDebugJavaWithJavac/.../AppPreferencesActivity.java:27: error: cannot
find symbol
addPreferencesFromResource(R.xml.apppreferences);
^
symbol: variable apppreferences
location: class xml
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
1 error
FAILED
{panel}
was:
android 5.1.0
cordova-plugin-inappbrowser
cordova-plugin-actionsheet
cordova-plugin-facebook4
uk.co.workingedge.phonegap.plugin.launchnavigator
{panel}
:compileDebugJavaWithJavac/Users/jordanzimmerman/dev/ubica/app/platforms/android/src/me/apla/cordova/AppPreferencesActivity.java:27:
error: cannot find symbol
addPreferencesFromResource(R.xml.apppreferences);
^
symbol: variable apppreferences
location: class xml
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
1 error
FAILED
{panel}
> Cannot build Android due to missing decl
>
>
> Key: CB-10629
> URL: https://issues.apache.org/jira/browse/CB-10629
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Affects Versions: 6.0.0
>Reporter: Jordan Zimmerman
>
> android 5.1.0
> cordova-plugin-inappbrowser
> cordova-plugin-actionsheet
> cordova-plugin-facebook4
> uk.co.workingedge.phonegap.plugin.launchnavigator
> {panel}
> :compileDebugJavaWithJavac/.../AppPreferencesActivity.java:27: error: cannot
> find symbol
> addPreferencesFromResource(R.xml.apppreferences);
> ^
> symbol: variable apppreferences
> location: class xml
> Note: Some input files use or override a deprecated API.
> Note: Recompile with -Xlint:deprecation for details.
> 1 error
> FAILED
> {panel}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-10629) Cannot build Android due to missing decl
Jordan Zimmerman created CB-10629:
-
Summary: Cannot build Android due to missing decl
Key: CB-10629
URL: https://issues.apache.org/jira/browse/CB-10629
Project: Apache Cordova
Issue Type: Bug
Components: Android
Affects Versions: 6.0.0
Reporter: Jordan Zimmerman
android 5.1.0
cordova-plugin-inappbrowser
cordova-plugin-actionsheet
cordova-plugin-facebook4
uk.co.workingedge.phonegap.plugin.launchnavigator
{panel}
:compileDebugJavaWithJavac/Users/jordanzimmerman/dev/ubica/app/platforms/android/src/me/apla/cordova/AppPreferencesActivity.java:27:
error: cannot find symbol
addPreferencesFromResource(R.xml.apppreferences);
^
symbol: variable apppreferences
location: class xml
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
1 error
FAILED
{panel}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-10628) Fix emulate android --target
[
https://issues.apache.org/jira/browse/CB-10628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Shakhnazarov updated CB-10628:
-
Description:
{noformat}
λ cordova emulate android --target=a19
ANDROID_HOME=e:\Android\Sdk
JAVA_HOME=C:\Program Files (x86)\java\jdk1.7.0_55
No emulator specified, defaulting to Nexus_5_API_23_x86
{noformat}
was:
{{λ cordova emulate android --target=a19
ANDROID_HOME=e:\Android\Sdk
JAVA_HOME=C:\Program Files (x86)\java\jdk1.7.0_55
No emulator specified, defaulting to Nexus_5_API_23_x86}}
> Fix emulate android --target
>
>
> Key: CB-10628
> URL: https://issues.apache.org/jira/browse/CB-10628
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Reporter: Sergey Shakhnazarov
>Assignee: Sergey Shakhnazarov
>
> {noformat}
> λ cordova emulate android --target=a19
> ANDROID_HOME=e:\Android\Sdk
> JAVA_HOME=C:\Program Files (x86)\java\jdk1.7.0_55
> No emulator specified, defaulting to Nexus_5_API_23_x86
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
