[jira] [Comment Edited] (CB-6721) iOS Failed test: battery.spec.4 should fire batterycritical events
[ https://issues.apache.org/jira/browse/CB-6721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14003786#comment-14003786 ] Jesse MacFadyen edited comment on CB-6721 at 5/21/14 1:58 AM: -- The reason for checking me._level is that we need to compare the previous value AND the present value. ie. before the added tests, - a change of 21->19 would NOT cause a batterylow event - a change of 11-4 would NOT cause a batterycritical event - a change of 19->20 ( ie charging ) DID cause a batterylow event - a change of 4->5( ie charging ) DID cause a batterycritical event re: #L88-L89 That is a matter of preference, yes inside the block would be better, but it is benign. Regardless, I will fix it while I am there. was (Author: purplecabbage): The reason for checking me._level is that we need to compare the previous value AND the present value. ie. before the added tests, - a change of 21->19 would NOT cause a batterylow event - a change of 11-9 would NOT cause a batterycritical event - a change of 19->20 ( ie charging ) DID cause a batterylow event - a change of 9->10 ( ie charging ) DID cause a batterycritical event re: #L88-L89 That is a matter of preference, yes inside the block would be better, but it is benign. Regardless, I will fix it while I am there. > iOS Failed test: battery.spec.4 should fire batterycritical events > -- > > Key: CB-6721 > URL: https://issues.apache.org/jira/browse/CB-6721 > Project: Apache Cordova > Issue Type: Bug > Components: mobile-spec, Plugin Battery Status >Reporter: Shazron Abdullah >Assignee: Jesse MacFadyen > > Battery (navigator.battery) battery.spec.4 should fire batterycritical events. > timeout: timed out after 100 msec waiting for batterycritical onEvent was not > called when level goes from 19->5 > This test is new for CB-4520 CB-4519: > https://github.com/apache/cordova-mobile-spec/commit/b5b80a6ff80d3c8b3d7618fe051c824ec0d3771f -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6726) Android Webview Not Intercepting Resource Requests Properly
[ https://issues.apache.org/jira/browse/CB-6726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14004150#comment-14004150 ] Andrew Grieve commented on CB-6726: --- Sounds like this is likely a caching issue. Try calling webview.clearCache(true) before loading the page. > Android Webview Not Intercepting Resource Requests Properly > --- > > Key: CB-6726 > URL: https://issues.apache.org/jira/browse/CB-6726 > Project: Apache Cordova > Issue Type: Bug > Components: Android >Affects Versions: 3.5.0 >Reporter: Tim Kim >Assignee: Andrew Grieve > > The shouldInterceptRequest method in IceCreamCordovaWebViewClient.java > doesn't seem to fire for every request. Only for things like xhrs or > resources prefixed with http:// > Steps to reproduce: > - pull down latest > - ./bin/create test > - cd into test/ > - find the shouldInterceptRequest method in IceCreamCordovaWebViewClient.java > and add a log statement to know when it fired > - ./cordova/run > - ./cordova/log > - only 'file:///android_asset/www/cordova_plugins.js' will make > shouldInterceptRequest fire and not the reference to 'cordova.js' or > 'js/index.js'. > - add in ' src="http://code.jquery.com/jquery-1.11.0.min.js";>' to the > index.html to see the shouldInterceptRequest fire > Tested on 4.4 with cordova-android 3.5.0 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6693) Investigate Certificate Pinning for Third-Party WebViews
[ https://issues.apache.org/jira/browse/CB-6693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14004026#comment-14004026 ] Marcel Kinard commented on CB-6693: --- Although I freely admit it would be a hack and not "true cert pinning", one idea I've been kicking around for the default webview on Android would be a JS API to "check the server's cert now". So it would be it-only-gets-checked-at-specific-times instead of checked-on-every-connection. It might be enough of an approximation to be good enough with disclaimers. It seems a shame for lack-of-support on Android to prevent us from doing it right on iOS. But yeah, if third-party webviews have the ability to do it right, it should be done. > Investigate Certificate Pinning for Third-Party WebViews > > > Key: CB-6693 > URL: https://issues.apache.org/jira/browse/CB-6693 > Project: Apache Cordova > Issue Type: Sub-task > Components: Android >Reporter: Joe Bowser > Fix For: 4.0.0 > > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CB-6726) Android Webview Not Intercepting Resource Requests Properly
Tim Kim created CB-6726: --- Summary: Android Webview Not Intercepting Resource Requests Properly Key: CB-6726 URL: https://issues.apache.org/jira/browse/CB-6726 Project: Apache Cordova Issue Type: Bug Components: Android Affects Versions: 3.5.0 Reporter: Tim Kim Assignee: Andrew Grieve The shouldInterceptRequest method in IceCreamCordovaWebViewClient.java doesn't seem to fire for every request. Only for things like xhrs or resources prefixed with http:// Steps to reproduce: - pull down latest - ./bin/create test - cd into test/ - find the shouldInterceptRequest method in IceCreamCordovaWebViewClient.java and add a log statement to know when it fired - ./cordova/run - ./cordova/log - only 'file:///android_asset/www/cordova_plugins.js' will make shouldInterceptRequest fire and not the reference to 'cordova.js' or 'js/index.js'. - add in ' http://code.jquery.com/jquery-1.11.0.min.js";>' to the index.html to see the shouldInterceptRequest fire Tested on 4.4 with cordova-android 3.5.0 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6721) iOS Failed test: battery.spec.4 should fire batterycritical events
[ https://issues.apache.org/jira/browse/CB-6721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14004023#comment-14004023 ] ASF subversion and git services commented on CB-6721: - Commit 8f8c92a056c6ef08cd2580270db7644543342156 in cordova-plugin-battery-status's branch refs/heads/master from [~purplecabbage] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-battery-status.git;h=8f8c92a ] CB-6721 Test for batterycritical change before batterylow change > iOS Failed test: battery.spec.4 should fire batterycritical events > -- > > Key: CB-6721 > URL: https://issues.apache.org/jira/browse/CB-6721 > Project: Apache Cordova > Issue Type: Bug > Components: mobile-spec, Plugin Battery Status >Reporter: Shazron Abdullah >Assignee: Jesse MacFadyen > > Battery (navigator.battery) battery.spec.4 should fire batterycritical events. > timeout: timed out after 100 msec waiting for batterycritical onEvent was not > called when level goes from 19->5 > This test is new for CB-4520 CB-4519: > https://github.com/apache/cordova-mobile-spec/commit/b5b80a6ff80d3c8b3d7618fe051c824ec0d3771f -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CB-5416) Need to auto generate manifest.webapp with appropriate plugin permissions
[ https://issues.apache.org/jira/browse/CB-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rodrigo Silveira resolved CB-5416. -- Resolution: Fixed Fix Version/s: 3.5.0 > Need to auto generate manifest.webapp with appropriate plugin permissions > - > > Key: CB-5416 > URL: https://issues.apache.org/jira/browse/CB-5416 > Project: Apache Cordova > Issue Type: Task > Components: CLI, FirefoxOS >Affects Versions: 3.2.0 >Reporter: Herm Wong >Assignee: Herm Wong > Fix For: 3.5.0 > > > When FxOS apps are built, the CLI needs to determine which plugins are used > and also generate the correct permissions in the manifest.webapp file. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CB-6602) [Release + 3.5.0] Test & Tag 3.5.0 for Windows
[ https://issues.apache.org/jira/browse/CB-6602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Gill resolved CB-6602. Resolution: Fixed > [Release + 3.5.0] Test & Tag 3.5.0 for Windows > -- > > Key: CB-6602 > URL: https://issues.apache.org/jira/browse/CB-6602 > Project: Apache Cordova > Issue Type: Sub-task > Components: Windows 8 >Reporter: Steve Gill >Assignee: Jesse MacFadyen > Fix For: 3.5.0 > > > Refer to Workflow here: > http://wiki.apache.org/cordova/CuttingReleases -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CB-6603) [Release + 3.5.0] Test & Tag 3.5.0 for Windows Phone 7 & 8
[ https://issues.apache.org/jira/browse/CB-6603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Gill resolved CB-6603. Resolution: Fixed > [Release + 3.5.0] Test & Tag 3.5.0 for Windows Phone 7 & 8 > -- > > Key: CB-6603 > URL: https://issues.apache.org/jira/browse/CB-6603 > Project: Apache Cordova > Issue Type: Sub-task > Components: WP8 >Reporter: Steve Gill >Assignee: Jesse MacFadyen > Fix For: 3.5.0 > > > Refer to Workflow here: > http://wiki.apache.org/cordova/CuttingReleases -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CB-6608) [Release + 3.5.0] Create blog post for final release & get reviewed
[ https://issues.apache.org/jira/browse/CB-6608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Gill reassigned CB-6608: -- Assignee: Steve Gill > [Release + 3.5.0] Create blog post for final release & get reviewed > --- > > Key: CB-6608 > URL: https://issues.apache.org/jira/browse/CB-6608 > Project: Apache Cordova > Issue Type: Sub-task > Components: Amazon FireOS, Android, App Hello World, BlackBerry, > CLI, CordovaJS, Docs, FirefoxOS, iOS, mobile-spec, Ubuntu, Windows 8, WP8 >Reporter: Steve Gill >Assignee: Steve Gill > Fix For: 3.5.0 > > > Refer to Workflow here: > http://wiki.apache.org/cordova/CuttingReleases -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CB-6608) [Release + 3.5.0] Create blog post for final release & get reviewed
[ https://issues.apache.org/jira/browse/CB-6608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Gill resolved CB-6608. Resolution: Fixed > [Release + 3.5.0] Create blog post for final release & get reviewed > --- > > Key: CB-6608 > URL: https://issues.apache.org/jira/browse/CB-6608 > Project: Apache Cordova > Issue Type: Sub-task > Components: Amazon FireOS, Android, App Hello World, BlackBerry, > CLI, CordovaJS, Docs, FirefoxOS, iOS, mobile-spec, Ubuntu, Windows 8, WP8 >Reporter: Steve Gill >Assignee: Steve Gill > Fix For: 3.5.0 > > > Refer to Workflow here: > http://wiki.apache.org/cordova/CuttingReleases -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CB-6511) When display name is 16-bit based language, Android platform can't create Activty class when adding support
[ https://issues.apache.org/jira/browse/CB-6511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser resolved CB-6511. Resolution: Won't Fix This is a limitation of the Android SDK Tools, which the create scripts depend upon. Even though Java supports Unicode, Android SDK tools don't. I have no idea why this is the case. :( > When display name is 16-bit based language, Android platform can't create > Activty class when adding support > --- > > Key: CB-6511 > URL: https://issues.apache.org/jira/browse/CB-6511 > Project: Apache Cordova > Issue Type: Bug > Components: Android >Affects Versions: 3.3.0, 3.4.0 >Reporter: Victor Adrian Sosa Herrera > > Adding android support when the Display name of the Cordova application has a > value based on 16-bit language (like Japanese) makes that the Activity class > (based on that value) isn't created correctly. Instead, the class is > generated as a file named ".java" and the Java class declaration is "public > class extends CordovaActivity". > To reproduce the error: > 1. Change the text file encoding of container to UTF-8 > 2. Create a cordova project and enter a project name with ASCII characters > and display name with G11N characters (like Japanese) > 3. Once the project is created, add android support. > 4. Go to /platforms/android/src/ and verify you have a > file named ".java". If you are in Linux, it is a hidden file -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-2179) Warn developers about including third-party content in their apps.
[ https://issues.apache.org/jira/browse/CB-2179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14003838#comment-14003838 ] Mike Billau commented on CB-2179: - Added a new Security guide, documented that they should use InAppBrowser for any and all third party content and explained that otherwise, those third party pages will have access to the bridge. https://git-wip-us.apache.org/repos/asf?p=cordova-docs.git;a=commit;h=7e6d5b9bc51c5249f20f7c3f2493923d609c7418 > Warn developers about including third-party content in their apps. > -- > > Key: CB-2179 > URL: https://issues.apache.org/jira/browse/CB-2179 > Project: Apache Cordova > Issue Type: Bug > Components: Docs >Affects Versions: 2.4.0, 2.5.0, 2.6.0 >Reporter: Andrew Grieve >Assignee: Andrew Grieve >Priority: Minor > Fix For: 3.5.0 > > > We expose our native APIs to iframes as well as top-level content, so we > should warn against using iframes for third-party code. > Might make sense to change "Domain Whitelist Guide" -> "Security & Whitelist > Guide" and then add a section to it about the dangers of embedding untrusted > content. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CB-2179) Warn developers about including third-party content in their apps.
[ https://issues.apache.org/jira/browse/CB-2179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Billau resolved CB-2179. - Resolution: Fixed > Warn developers about including third-party content in their apps. > -- > > Key: CB-2179 > URL: https://issues.apache.org/jira/browse/CB-2179 > Project: Apache Cordova > Issue Type: Bug > Components: Docs >Affects Versions: 2.4.0, 2.5.0, 2.6.0 >Reporter: Andrew Grieve >Assignee: Andrew Grieve >Priority: Minor > Fix For: 3.5.0 > > > We expose our native APIs to iframes as well as top-level content, so we > should warn against using iframes for third-party code. > Might make sense to change "Domain Whitelist Guide" -> "Security & Whitelist > Guide" and then add a section to it about the dangers of embedding untrusted > content. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (CB-5786) document security best practices
[ https://issues.apache.org/jira/browse/CB-5786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Billau closed CB-5786. --- Resolution: Fixed Fix Version/s: 3.5.0 Added the first draft. Thanks everybody for the help. https://git-wip-us.apache.org/repos/asf?p=cordova-docs.git;a=commit;h=7e6d5b9bc51c5249f20f7c3f2493923d609c7418 Will continue to iterate on it as we go alone. > document security best practices > > > Key: CB-5786 > URL: https://issues.apache.org/jira/browse/CB-5786 > Project: Apache Cordova > Issue Type: Improvement > Components: Docs >Reporter: Marcel Kinard >Priority: Minor > Fix For: 3.5.0 > > > Would be nice if cordova-docs included a section on security in general. > Potential content could include: > - in general how does Cordova work > - common areas where devs may shoot themselves in the foot > - what the whitelist does and doesn't do > - when to consider InAppBrowser -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6719) < video > tag not working for FireTV OS
[ https://issues.apache.org/jira/browse/CB-6719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14003825#comment-14003825 ] Gene Ellis commented on CB-6719: Thank you very much. Sure thing. It happens with any URL, but here is one: http://hwcdn.net/k3r6e6e8/cds/Secure/Johnnyswim/JohnnySwim_Session.mp4 > < video > tag not working for FireTV OS > > > Key: CB-6719 > URL: https://issues.apache.org/jira/browse/CB-6719 > Project: Apache Cordova > Issue Type: Bug > Components: Amazon FireOS >Affects Versions: 3.4.0 >Reporter: Gene Ellis >Assignee: Archana Naik > > I am using PhoneGap/Cordova (http://www.phonegap.com) to build an app for > Amazon FireTV OS, which is built on Android. I am using HTML, Javascript, CSS > and everything is working fine. However, when I try to use the < video > tag > to pull in an .MP4 video, all I am getting is a gray background and film > strip logo (picture: http://imgur.com/MXLvwy7). What does this mean? The > documentation says is supported and I am 100% positive of the path and any > other silly pitfalls. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-5416) Need to auto generate manifest.webapp with appropriate plugin permissions
[ https://issues.apache.org/jira/browse/CB-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14003816#comment-14003816 ] ASF subversion and git services commented on CB-5416: - Commit d4558831838ae3070de46ef8bcaa5e7174a1db7d in cordova-plugin-geolocation's branch refs/heads/master from [~rsilveira] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-geolocation.git;h=d455883 ] CB-5416 - Adding support for auto-managing permissions > Need to auto generate manifest.webapp with appropriate plugin permissions > - > > Key: CB-5416 > URL: https://issues.apache.org/jira/browse/CB-5416 > Project: Apache Cordova > Issue Type: Task > Components: CLI, FirefoxOS >Affects Versions: 3.2.0 >Reporter: Herm Wong >Assignee: Herm Wong > > When FxOS apps are built, the CLI needs to determine which plugins are used > and also generate the correct permissions in the manifest.webapp file. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-5416) Need to auto generate manifest.webapp with appropriate plugin permissions
[ https://issues.apache.org/jira/browse/CB-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14003817#comment-14003817 ] ASF GitHub Bot commented on CB-5416: Github user asfgit closed the pull request at: https://github.com/apache/cordova-plugin-geolocation/pull/17 > Need to auto generate manifest.webapp with appropriate plugin permissions > - > > Key: CB-5416 > URL: https://issues.apache.org/jira/browse/CB-5416 > Project: Apache Cordova > Issue Type: Task > Components: CLI, FirefoxOS >Affects Versions: 3.2.0 >Reporter: Herm Wong >Assignee: Herm Wong > > When FxOS apps are built, the CLI needs to determine which plugins are used > and also generate the correct permissions in the manifest.webapp file. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6719) < video > tag not working for FireTV OS
[ https://issues.apache.org/jira/browse/CB-6719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14003805#comment-14003805 ] Archana Naik commented on CB-6719: -- Can you provide us the URL that you used for tag? > < video > tag not working for FireTV OS > > > Key: CB-6719 > URL: https://issues.apache.org/jira/browse/CB-6719 > Project: Apache Cordova > Issue Type: Bug > Components: Amazon FireOS >Affects Versions: 3.4.0 >Reporter: Gene Ellis >Assignee: Archana Naik > > I am using PhoneGap/Cordova (http://www.phonegap.com) to build an app for > Amazon FireTV OS, which is built on Android. I am using HTML, Javascript, CSS > and everything is working fine. However, when I try to use the < video > tag > to pull in an .MP4 video, all I am getting is a gray background and film > strip logo (picture: http://imgur.com/MXLvwy7). What does this mean? The > documentation says is supported and I am 100% positive of the path and any > other silly pitfalls. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CB-6721) iOS Failed test: battery.spec.4 should fire batterycritical events
[ https://issues.apache.org/jira/browse/CB-6721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse MacFadyen reassigned CB-6721: --- Assignee: Jesse MacFadyen > iOS Failed test: battery.spec.4 should fire batterycritical events > -- > > Key: CB-6721 > URL: https://issues.apache.org/jira/browse/CB-6721 > Project: Apache Cordova > Issue Type: Bug > Components: mobile-spec, Plugin Battery Status >Reporter: Shazron Abdullah >Assignee: Jesse MacFadyen > > Battery (navigator.battery) battery.spec.4 should fire batterycritical events. > timeout: timed out after 100 msec waiting for batterycritical onEvent was not > called when level goes from 19->5 > This test is new for CB-4520 CB-4519: > https://github.com/apache/cordova-mobile-spec/commit/b5b80a6ff80d3c8b3d7618fe051c824ec0d3771f -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6721) iOS Failed test: battery.spec.4 should fire batterycritical events
[ https://issues.apache.org/jira/browse/CB-6721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14003786#comment-14003786 ] Jesse MacFadyen commented on CB-6721: - The reason for checking me._level is that we need to compare the previous value AND the present value. ie. before the added tests, - a change of 21->19 would NOT cause a batterylow event - a change of 11-9 would NOT cause a batterycritical event - a change of 19->20 ( ie charging ) DID cause a batterylow event - a change of 9->10 ( ie charging ) DID cause a batterycritical event re: #L88-L89 That is a matter of preference, yes inside the block would be better, but it is benign. Regardless, I will fix it while I am there. > iOS Failed test: battery.spec.4 should fire batterycritical events > -- > > Key: CB-6721 > URL: https://issues.apache.org/jira/browse/CB-6721 > Project: Apache Cordova > Issue Type: Bug > Components: mobile-spec, Plugin Battery Status >Reporter: Shazron Abdullah > > Battery (navigator.battery) battery.spec.4 should fire batterycritical events. > timeout: timed out after 100 msec waiting for batterycritical onEvent was not > called when level goes from 19->5 > This test is new for CB-4520 CB-4519: > https://github.com/apache/cordova-mobile-spec/commit/b5b80a6ff80d3c8b3d7618fe051c824ec0d3771f -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CB-6630) Remove okhttp from source directory, make HTTP a library project dependency
[ https://issues.apache.org/jira/browse/CB-6630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser updated CB-6630: --- Summary: Remove okhttp from source directory, make HTTP a library project dependency (was: Remove okhttp from source directory, make HTTP a library project depeendency) > Remove okhttp from source directory, make HTTP a library project dependency > --- > > Key: CB-6630 > URL: https://issues.apache.org/jira/browse/CB-6630 > Project: Apache Cordova > Issue Type: Bug > Components: Android >Reporter: Joe Bowser > > From Stack Overflow: > http://stackoverflow.com/questions/23446603/conversion-to-dalvik-format-failed-unable-to-execute-dex-multiple-dex-files-de > Basically, we should be including third party libraries as libraries, and not > just dumping the source in our own tree. This leads to major problems when > people use other Java libraries. We'll probably need to modify the CLI to do > this, of course. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CB-6020) Media object callbacks not firing
[ https://issues.apache.org/jira/browse/CB-6020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser updated CB-6020: --- Priority: Minor (was: Major) Since it's only Android 4.0.4, making it a lower priority. > Media object callbacks not firing > - > > Key: CB-6020 > URL: https://issues.apache.org/jira/browse/CB-6020 > Project: Apache Cordova > Issue Type: Bug > Components: Android, Plugin Media >Affects Versions: 2.9.0, 3.1.0 > Environment: Sony Ericsson Xperia Arc (LT15i), Android 4.0.4 >Reporter: Martin Mikeln >Priority: Minor > Attachments: media_callback_bug.zip > > > When using example code from docs for media playback, _success_, _error_ and > _status_ callbacks are not fired. When media file stop playing, JS console on > remote debugging shows: "Received Media.onStatus callback for unknown media > :: b7815dd0-b2e7-2a46-c04a-b9bb919a4141" . The media file itself plays > successfully and all other tested cordova functionalities are working, the > problem is solely in callbacks. > Code works on Sony Xperia J (ST26i) with Android 4.1.2 but not on Sony > Ericsson Xperia Arc (LT15i) with Android 4.0.4. Tested with Cordova version > 3.1.0 and 2.9.0, with two different media formats(.mp3 and .amr). Build with > PhoneGap build service. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Comment Edited] (CB-3498) Certificate Pinning
[ https://issues.apache.org/jira/browse/CB-3498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14003766#comment-14003766 ] Joe Bowser edited comment on CB-3498 at 5/20/14 6:18 PM: - Well, since we can't do Cert Pinning on the Android WebView, we should investigate it for third parties at CB-6693 was (Author: bowserj): Well, since we can't do Cert Pinning on the Android WebView, we should investigate it for third parties at CB-6698 > Certificate Pinning > --- > > Key: CB-3498 > URL: https://issues.apache.org/jira/browse/CB-3498 > Project: Apache Cordova > Issue Type: Wish > Components: Android, iOS >Affects Versions: 2.7.0 >Reporter: mgill >Assignee: Joe Bowser >Priority: Minor > Labels: certificate, security > > It would be a handy feature to have certificate pinning supported > Examples: > https://github.com/iSECPartners/ssl-conservatory/tree/master/ios > https://github.com/moxie0/AndroidPinning -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Comment Edited] (CB-3498) Certificate Pinning
[ https://issues.apache.org/jira/browse/CB-3498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14003766#comment-14003766 ] Joe Bowser edited comment on CB-3498 at 5/20/14 6:17 PM: - Well, since we can't do Cert Pinning on the Android WebView, we should investigate it for third parties at CB-6698 was (Author: bowserj): Well, since we can't do Cert Pinning on the Android WebView, we should invesitgate it for third parties at CB-6698 > Certificate Pinning > --- > > Key: CB-3498 > URL: https://issues.apache.org/jira/browse/CB-3498 > Project: Apache Cordova > Issue Type: Wish > Components: Android, iOS >Affects Versions: 2.7.0 >Reporter: mgill >Assignee: Joe Bowser >Priority: Minor > Labels: certificate, security > > It would be a handy feature to have certificate pinning supported > Examples: > https://github.com/iSECPartners/ssl-conservatory/tree/master/ios > https://github.com/moxie0/AndroidPinning -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CB-3498) Certificate Pinning
[ https://issues.apache.org/jira/browse/CB-3498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser resolved CB-3498. Resolution: Duplicate Well, since we can't do Cert Pinning on the Android WebView, we should invesitgate it for third parties at CB-6698 > Certificate Pinning > --- > > Key: CB-3498 > URL: https://issues.apache.org/jira/browse/CB-3498 > Project: Apache Cordova > Issue Type: Wish > Components: Android, iOS >Affects Versions: 2.7.0 >Reporter: mgill >Assignee: Joe Bowser >Priority: Minor > Labels: certificate, security > > It would be a handy feature to have certificate pinning supported > Examples: > https://github.com/iSECPartners/ssl-conservatory/tree/master/ios > https://github.com/moxie0/AndroidPinning -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CB-4071) Capture error callback (should be an object)
[
https://issues.apache.org/jira/browse/CB-4071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bowser updated CB-4071:
---
Assignee: (was: Joe Bowser)
So, yeah, what's going on with this?
> Capture error callback (should be an object)
>
>
> Key: CB-4071
> URL: https://issues.apache.org/jira/browse/CB-4071
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android, Docs, iOS, Plugin Media Capture, Windows 8
>Affects Versions: 2.9.0
> Environment: All
>Reporter: Jonathan Bond
>Priority: Minor
> Fix For: 3.5.0
>
>
> When using camera.getPicture(), the cameraError is documented as a string but
> on Android & iOS, it's actually an object.
> On the native side in 2.7:
> Android:
> private static final int CAPTURE_INTERNAL_ERR = 0;
> // private static final int CAPTURE_APPLICATION_BUSY = 1;
> // private static final int CAPTURE_INVALID_ARGUMENT = 2;
>
> private static final int CAPTURE_NO_MEDIA_FILES = 3;
> iOS:
> enum CDVCaptureError {
>
> CAPTURE_INTERNAL_ERR = 0,
>
> CAPTURE_APPLICATION_BUSY = 1,
>
> CAPTURE_INVALID_ARGUMENT = 2,
>
> CAPTURE_NO_MEDIA_FILES = 3,
>
> CAPTURE_NOT_SUPPORTED = 20
> };
> Windows 8:
> only string errors
> Android and iOS have the same looking api on the native side, error callback
> Android returns JSON: {message: '', code: int}, iOS returns JSON: {message:
> '', status: int},
> Looking at the javascript api, it looks like it should return a 'new
> CaptureError()' on the errorCallback, is that the direction for 3.0?
> Windows only sends a string as the callback error, it's difficult to know if
> the user just cancelled taking a picture or what kind of specific error
> occurred.
> Should I look into creating a patch?
> This probably affects other apis, overall I'd like to see the CaptureError()
> returned more consistently instead of strings.
> It would make sense to improve this in 3.0 and possibly break BC for those
> expecting strings.
> CaptureError() could implement 'toString()' to mitigate potential issues.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CB-6693) Investigate Certificate Pinning for Third-Party WebViews
[ https://issues.apache.org/jira/browse/CB-6693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14003763#comment-14003763 ] Joe Bowser commented on CB-6693: This is where CB-3498 lives on. > Investigate Certificate Pinning for Third-Party WebViews > > > Key: CB-6693 > URL: https://issues.apache.org/jira/browse/CB-6693 > Project: Apache Cordova > Issue Type: Sub-task > Components: Android >Reporter: Joe Bowser > Fix For: 4.0.0 > > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CB-5351) Support context menu plugins with postMessage
[ https://issues.apache.org/jira/browse/CB-5351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser resolved CB-5351. Resolution: Won't Fix I don't think this is going to happen. If we do support context menus, there will probably be another hook added to the Activity. > Support context menu plugins with postMessage > - > > Key: CB-5351 > URL: https://issues.apache.org/jira/browse/CB-5351 > Project: Apache Cordova > Issue Type: Improvement > Components: Android >Affects Versions: Master >Reporter: Abel Muiño >Assignee: Joe Bowser >Priority: Minor > > There is [support in > `CordovaActivity`|https://github.com/apache/cordova-android/blob/master/framework/src/org/apache/cordova/CordovaActivity.java#L1006-L1026] > for menu plugins. > It would be great to have the same support for context menus. Currently we > need to tell the user to [modify their class in a similar > way|https://github.com/amuino/cordova-actionsheet/blob/master/plugin.xml#L29-L50]. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6718) cordova firefox reports wrong version
[
https://issues.apache.org/jira/browse/CB-6718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14003674#comment-14003674
]
ASF GitHub Bot commented on CB-6718:
GitHub user csantanapr opened a pull request:
https://github.com/apache/cordova-coho/pull/24
CB-6718 cordova firefox reports wrong version
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/csantanapr/cordova-coho CB-6718
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cordova-coho/pull/24.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 #24
commit cadf0b374468ea8c40a3a46f23334a9881b12792
Author: Carlos Santana
Date: 2014-05-20T16:15:53Z
CB-6718 cordova firefox reports wrong version
> cordova firefox reports wrong version
> -
>
> Key: CB-6718
> URL: https://issues.apache.org/jira/browse/CB-6718
> Project: Apache Cordova
> Issue Type: Bug
> Components: FirefoxOS
>Affects Versions: 3.5.0
> Environment: MacOSX
>Reporter: Carlos Santana
>
> While doing rc testing platform cordova-firefoxos reports 3.4.0-dev when it
> should report 3.5.0
> Steps to replicate
> Install cordova cli 3.5.0-0.2.4
> {code}
> $ ../../node_modules/.bin/cordova -v
> 3.5.0-0.2.4
> $ ./node_modules/.bin/cordova create firefox350/newProj
> Creating a new cordova project with name "HelloCordova" and id
> "io.cordova.hellocordova" at location
> "/Users/csantana23/Documents/cordova/firefox350/newProj"
> Downloading cordova library for www...
> Download complete
> /Users/csantana23/Documents/cordova/firefox350/newProj
> $ ../../node_modules/.bin/cordova platform add firefoxos
> Downloading cordova library for firefoxos...
> Download complete
> Creating firefoxos project...
> Creating Firefox OS project
> Project Path platforms/firefoxos
> Package Name io.cordova.hellocordova
> Project Name HelloCordova
> /Users/csantana23/Documents/cordova/firefox350/newProj
> $ ../../node_modules/.bin/cordova platform ls
> Installed platforms: firefoxos 3.4.0-dev
> Available platforms: amazon-fireos, android, blackberry10, ios
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CB-6718) cordova firefox reports wrong version
[
https://issues.apache.org/jira/browse/CB-6718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14003688#comment-14003688
]
ASF GitHub Bot commented on CB-6718:
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-coho/pull/24
> cordova firefox reports wrong version
> -
>
> Key: CB-6718
> URL: https://issues.apache.org/jira/browse/CB-6718
> Project: Apache Cordova
> Issue Type: Bug
> Components: FirefoxOS
>Affects Versions: 3.5.0
> Environment: MacOSX
>Reporter: Carlos Santana
>
> While doing rc testing platform cordova-firefoxos reports 3.4.0-dev when it
> should report 3.5.0
> Steps to replicate
> Install cordova cli 3.5.0-0.2.4
> {code}
> $ ../../node_modules/.bin/cordova -v
> 3.5.0-0.2.4
> $ ./node_modules/.bin/cordova create firefox350/newProj
> Creating a new cordova project with name "HelloCordova" and id
> "io.cordova.hellocordova" at location
> "/Users/csantana23/Documents/cordova/firefox350/newProj"
> Downloading cordova library for www...
> Download complete
> /Users/csantana23/Documents/cordova/firefox350/newProj
> $ ../../node_modules/.bin/cordova platform add firefoxos
> Downloading cordova library for firefoxos...
> Download complete
> Creating firefoxos project...
> Creating Firefox OS project
> Project Path platforms/firefoxos
> Package Name io.cordova.hellocordova
> Project Name HelloCordova
> /Users/csantana23/Documents/cordova/firefox350/newProj
> $ ../../node_modules/.bin/cordova platform ls
> Installed platforms: firefoxos 3.4.0-dev
> Available platforms: amazon-fireos, android, blackberry10, ios
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CB-6718) cordova firefox reports wrong version
[
https://issues.apache.org/jira/browse/CB-6718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14003687#comment-14003687
]
ASF subversion and git services commented on CB-6718:
-
Commit cadf0b374468ea8c40a3a46f23334a9881b12792 in cordova-coho's branch
refs/heads/master from [~csantana]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-coho.git;h=cadf0b3 ]
CB-6718 cordova firefox reports wrong version
> cordova firefox reports wrong version
> -
>
> Key: CB-6718
> URL: https://issues.apache.org/jira/browse/CB-6718
> Project: Apache Cordova
> Issue Type: Bug
> Components: FirefoxOS
>Affects Versions: 3.5.0
> Environment: MacOSX
>Reporter: Carlos Santana
>
> While doing rc testing platform cordova-firefoxos reports 3.4.0-dev when it
> should report 3.5.0
> Steps to replicate
> Install cordova cli 3.5.0-0.2.4
> {code}
> $ ../../node_modules/.bin/cordova -v
> 3.5.0-0.2.4
> $ ./node_modules/.bin/cordova create firefox350/newProj
> Creating a new cordova project with name "HelloCordova" and id
> "io.cordova.hellocordova" at location
> "/Users/csantana23/Documents/cordova/firefox350/newProj"
> Downloading cordova library for www...
> Download complete
> /Users/csantana23/Documents/cordova/firefox350/newProj
> $ ../../node_modules/.bin/cordova platform add firefoxos
> Downloading cordova library for firefoxos...
> Download complete
> Creating firefoxos project...
> Creating Firefox OS project
> Project Path platforms/firefoxos
> Package Name io.cordova.hellocordova
> Project Name HelloCordova
> /Users/csantana23/Documents/cordova/firefox350/newProj
> $ ../../node_modules/.bin/cordova platform ls
> Installed platforms: firefoxos 3.4.0-dev
> Available platforms: amazon-fireos, android, blackberry10, ios
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CB-6718) cordova firefox reports wrong version
[
https://issues.apache.org/jira/browse/CB-6718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14003681#comment-14003681
]
ASF subversion and git services commented on CB-6718:
-
Commit cadf0b374468ea8c40a3a46f23334a9881b12792 in cordova-coho's branch
refs/heads/CB-6718 from [~csantana]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-coho.git;h=cadf0b3 ]
CB-6718 cordova firefox reports wrong version
> cordova firefox reports wrong version
> -
>
> Key: CB-6718
> URL: https://issues.apache.org/jira/browse/CB-6718
> Project: Apache Cordova
> Issue Type: Bug
> Components: FirefoxOS
>Affects Versions: 3.5.0
> Environment: MacOSX
>Reporter: Carlos Santana
>
> While doing rc testing platform cordova-firefoxos reports 3.4.0-dev when it
> should report 3.5.0
> Steps to replicate
> Install cordova cli 3.5.0-0.2.4
> {code}
> $ ../../node_modules/.bin/cordova -v
> 3.5.0-0.2.4
> $ ./node_modules/.bin/cordova create firefox350/newProj
> Creating a new cordova project with name "HelloCordova" and id
> "io.cordova.hellocordova" at location
> "/Users/csantana23/Documents/cordova/firefox350/newProj"
> Downloading cordova library for www...
> Download complete
> /Users/csantana23/Documents/cordova/firefox350/newProj
> $ ../../node_modules/.bin/cordova platform add firefoxos
> Downloading cordova library for firefoxos...
> Download complete
> Creating firefoxos project...
> Creating Firefox OS project
> Project Path platforms/firefoxos
> Package Name io.cordova.hellocordova
> Project Name HelloCordova
> /Users/csantana23/Documents/cordova/firefox350/newProj
> $ ../../node_modules/.bin/cordova platform ls
> Installed platforms: firefoxos 3.4.0-dev
> Available platforms: amazon-fireos, android, blackberry10, ios
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Resolved] (CB-6574) Fix JUnit Tests, add missing method signatures to make JUnit Tests work
[ https://issues.apache.org/jira/browse/CB-6574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser resolved CB-6574. Resolution: Fixed Fixed on the pluggable_webview branch > Fix JUnit Tests, add missing method signatures to make JUnit Tests work > --- > > Key: CB-6574 > URL: https://issues.apache.org/jira/browse/CB-6574 > Project: Apache Cordova > Issue Type: Sub-task > Components: Android >Reporter: Joe Bowser >Assignee: Joe Bowser > Fix For: 4.0.0 > > > Not all of the JUnit Tests are going to work, so we have to go through and > modify them. It doesn't look like we're going to be able to use Robotium as > it currently exists, and we should remove the horribly out of date ones, but > it would be good to have these running again with each of the custom WebViews > so WebView developers can check their work. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6719) < video > tag not working for FireTV OS
[ https://issues.apache.org/jira/browse/CB-6719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14003424#comment-14003424 ] Archana Naik commented on CB-6719: -- Hi, Ellis Thank you for reporting this issue. I will look into it asap and let you know what the issue it. Archana > < video > tag not working for FireTV OS > > > Key: CB-6719 > URL: https://issues.apache.org/jira/browse/CB-6719 > Project: Apache Cordova > Issue Type: Bug > Components: Amazon FireOS >Affects Versions: 3.4.0 >Reporter: Gene Ellis >Assignee: Archana Naik > > I am using PhoneGap/Cordova (http://www.phonegap.com) to build an app for > Amazon FireTV OS, which is built on Android. I am using HTML, Javascript, CSS > and everything is working fine. However, when I try to use the < video > tag > to pull in an .MP4 video, all I am getting is a gray background and film > strip logo (picture: http://imgur.com/MXLvwy7). What does this mean? The > documentation says is supported and I am 100% positive of the path and any > other silly pitfalls. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6469) Restore plugins from config.xml
[ https://issues.apache.org/jira/browse/CB-6469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14003405#comment-14003405 ] ASF GitHub Bot commented on CB-6469: Github user asfgit closed the pull request at: https://github.com/apache/cordova-cli/pull/176 > Restore plugins from config.xml > --- > > Key: CB-6469 > URL: https://issues.apache.org/jira/browse/CB-6469 > Project: Apache Cordova > Issue Type: New Feature > Components: CLI >Affects Versions: 3.4.0 >Reporter: Gorkem ERCAN >Assignee: Gorkem ERCAN > > CLI should be able to restore plugins that are listed on the top level > config.xml. > Essentially an entry like below, should cause the > org.apache.cordova.core.console plugin version 0.2.8 to be installed from > registry. If version is omitted is should just use the latest available from > registry. > > > > > Moreover we should add a save plugins command to save the currently installed > plugins to config.xml -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CB-6725) [BlackBerry10] Add preference for BAR file name
Bryan Higgins created CB-6725: - Summary: [BlackBerry10] Add preference for BAR file name Key: CB-6725 URL: https://issues.apache.org/jira/browse/CB-6725 Project: Apache Cordova Issue Type: Bug Components: BlackBerry Affects Versions: 3.5.0 Reporter: Bryan Higgins Fix For: 3.6.0 Some users have expressed interest in a preference for the generated bar file name, which is always bb10app.bar. This is a fairly trivial change. - document the preference name - modify genBarName in utils.js This file used to be generated based on the app id, but there were conflicts between the character set allowed in each. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CB-6464) [Russian] Elements which should not be translated are translated and locked
[ https://issues.apache.org/jira/browse/CB-6464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lisa Seacat DeLuca resolved CB-6464. Resolution: Fixed Andrey, I went through each of the pages that you identified as having issues and corrected the issues. Thank you for taking the time to open this JIRA issue. In the future just open them against the Translation component rather than the Docs component and assign to myself. Just so you are aware, it is not possible to lock inline code. Which is too bad. I have asked the Crowdin team to make it possible. Thanks [~akurdyumov] > [Russian] Elements which should not be translated are translated and locked > --- > > Key: CB-6464 > URL: https://issues.apache.org/jira/browse/CB-6464 > Project: Apache Cordova > Issue Type: Bug > Components: Translation >Reporter: Andrey Kurdyumov >Assignee: Lisa Seacat DeLuca > > Elements which should not be translated are locked now, but their translation > is incorrect. > Here the pages where I discover following issue: > https://crowdin.net/translate/cordova/117/en-ru (under "Event Types" section) > https://crowdin.net/translate/cordova/122/en-ru (Resume header) > https://crowdin.net/translate/cordova/28/en-ru (Path to Android SDK) > https://crowdin.net/translate/cordova/3689/en-ru (Android SDK section, > example of adding tools to PATH) > https://crowdin.net/translate/cordova/23/en-ru (Plugin Class Mappings section) > https://crowdin.net/translate/cordova/3837/en-ru (Apache License header) > https://crowdin.net/translate/cordova/3838/en-ru (Apache License header) > - > Following page has elements which should be locked and existing translation > should be removed: > https://crowdin.net/translate/cordova/3687/en-ru (Apache License header) > https://crowdin.net/translate/cordova/35/en-ru (Create app) > - > Following page has elements which should be locked: > https://crowdin.net/translate/cordova/36/en-ru (Install the BlackBerry Native > SDK, Create a Project, Deploy to Emulator) > https://crowdin.net/translate/cordova/3839/en-ru (Apache License header, > Update to 3.2.0 from 3.1.0) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6640) saveToPhotoAlbum, saves picture with wrong date
[ https://issues.apache.org/jira/browse/CB-6640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14003274#comment-14003274 ] Ollie Edwards commented on CB-6640: --- I've dug into this a bit. Additionally I note that the image roll shows the file size as 0b. When the device is restarted the date and size are displayed correctly. If I view the exif data on the image file itself it appears present and correct. My educated guess was initially that the two stage writing process used by the ExifHelper in the camera plugin means that at the Android system caches the exif data before the file has actually been written to? Upon system restart the data is then re-indexed. However, I attempted to workaround this issue by copying the final file to a new file, which by my theory would mean the exif data would be indexed correctly for the new file. Alas, the problem persisted. This is not an area I'm particularly familiar with but I'll continue to experiment. I hope this information will be useful to anyone else investigating this issue. Tested on a Nexus 7 running android 4.4, cordova 3.4 with camera plugin 2.9. > saveToPhotoAlbum, saves picture with wrong date > --- > > Key: CB-6640 > URL: https://issues.apache.org/jira/browse/CB-6640 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Camera >Affects Versions: 3.4.0 > Environment: Android, Nexus 4, Nexus 5 (4.4.2); HTC One Mini (4.4.2) >Reporter: diDev > > Using the camera plugin from cordova and setting the Attribute > saveToPhotoAlbum to true, will save the picture to the phone. No problems > here. But testing it on the Nexus 4 & 5 it saves the picture with date > 01.01.1970 01:00:00 > Seems to be the same problem on S4: > http://stackoverflow.com/questions/22372055/cordova-plugin-camera-why-my-save-image-appear-at-the-bottom-of-my-gallery > Btw.: using the App on HTC one mini, the date ist correct. But the picture > will be saved twice in different folder. The normal 'camera' folder and the > '100media' folder. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CB-6724) manual tests should have docs indicating the expected result
Marcel Kinard created CB-6724: - Summary: manual tests should have docs indicating the expected result Key: CB-6724 URL: https://issues.apache.org/jira/browse/CB-6724 Project: Apache Cordova Issue Type: Improvement Components: mobile-spec Reporter: Marcel Kinard Priority: Minor The manual tests in mobile-spec have buttons that do things and test the functions, but there is no indication and no documentation associated with those tests that indicate what the expected result should be. So it becomes difficult to compare the expected result with the actual result, unless you are very familiar with the function and know in your head what the expected result should be. It would be good if the expected result is documented, so non-experts can run the manual tests and validate the results. The manual tests for InAppBrowser do include some documentation of the expected inline with the buttons, so that may be considered a prototype of what is needed here. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-5963) createmobilespec only works on MacOS
[ https://issues.apache.org/jira/browse/CB-5963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14003203#comment-14003203 ] Marcel Kinard commented on CB-5963: --- Jesse, would you consider this solved and ready to be closed? > createmobilespec only works on MacOS > > > Key: CB-5963 > URL: https://issues.apache.org/jira/browse/CB-5963 > Project: Apache Cordova > Issue Type: Bug > Components: mobile-spec >Affects Versions: 3.4.0 >Reporter: Jesse MacFadyen >Assignee: Jesse MacFadyen > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CB-6464) [Russian] Elements which should not be translated are translated and locked
[ https://issues.apache.org/jira/browse/CB-6464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ian Clelland updated CB-6464: - Assignee: Lisa Seacat DeLuca > [Russian] Elements which should not be translated are translated and locked > --- > > Key: CB-6464 > URL: https://issues.apache.org/jira/browse/CB-6464 > Project: Apache Cordova > Issue Type: Bug > Components: Translation >Reporter: Andrey Kurdyumov >Assignee: Lisa Seacat DeLuca > > Elements which should not be translated are locked now, but their translation > is incorrect. > Here the pages where I discover following issue: > https://crowdin.net/translate/cordova/117/en-ru (under "Event Types" section) > https://crowdin.net/translate/cordova/122/en-ru (Resume header) > https://crowdin.net/translate/cordova/28/en-ru (Path to Android SDK) > https://crowdin.net/translate/cordova/3689/en-ru (Android SDK section, > example of adding tools to PATH) > https://crowdin.net/translate/cordova/23/en-ru (Plugin Class Mappings section) > https://crowdin.net/translate/cordova/3837/en-ru (Apache License header) > https://crowdin.net/translate/cordova/3838/en-ru (Apache License header) > - > Following page has elements which should be locked and existing translation > should be removed: > https://crowdin.net/translate/cordova/3687/en-ru (Apache License header) > https://crowdin.net/translate/cordova/35/en-ru (Create app) > - > Following page has elements which should be locked: > https://crowdin.net/translate/cordova/36/en-ru (Install the BlackBerry Native > SDK, Create a Project, Deploy to Emulator) > https://crowdin.net/translate/cordova/3839/en-ru (Apache License header, > Update to 3.2.0 from 3.1.0) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CB-6464) [Russian] Elements which should not be translated are translated and locked
[ https://issues.apache.org/jira/browse/CB-6464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ian Clelland updated CB-6464: - Component/s: Translation > [Russian] Elements which should not be translated are translated and locked > --- > > Key: CB-6464 > URL: https://issues.apache.org/jira/browse/CB-6464 > Project: Apache Cordova > Issue Type: Bug > Components: Translation >Reporter: Andrey Kurdyumov > > Elements which should not be translated are locked now, but their translation > is incorrect. > Here the pages where I discover following issue: > https://crowdin.net/translate/cordova/117/en-ru (under "Event Types" section) > https://crowdin.net/translate/cordova/122/en-ru (Resume header) > https://crowdin.net/translate/cordova/28/en-ru (Path to Android SDK) > https://crowdin.net/translate/cordova/3689/en-ru (Android SDK section, > example of adding tools to PATH) > https://crowdin.net/translate/cordova/23/en-ru (Plugin Class Mappings section) > https://crowdin.net/translate/cordova/3837/en-ru (Apache License header) > https://crowdin.net/translate/cordova/3838/en-ru (Apache License header) > - > Following page has elements which should be locked and existing translation > should be removed: > https://crowdin.net/translate/cordova/3687/en-ru (Apache License header) > https://crowdin.net/translate/cordova/35/en-ru (Create app) > - > Following page has elements which should be locked: > https://crowdin.net/translate/cordova/36/en-ru (Install the BlackBerry Native > SDK, Create a Project, Deploy to Emulator) > https://crowdin.net/translate/cordova/3839/en-ru (Apache License header, > Update to 3.2.0 from 3.1.0) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CB-6464) [Russian] Elements which should not be translated are translated and locked
[ https://issues.apache.org/jira/browse/CB-6464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ian Clelland updated CB-6464: - Component/s: (was: Docs) > [Russian] Elements which should not be translated are translated and locked > --- > > Key: CB-6464 > URL: https://issues.apache.org/jira/browse/CB-6464 > Project: Apache Cordova > Issue Type: Bug > Components: Translation >Reporter: Andrey Kurdyumov >Assignee: Lisa Seacat DeLuca > > Elements which should not be translated are locked now, but their translation > is incorrect. > Here the pages where I discover following issue: > https://crowdin.net/translate/cordova/117/en-ru (under "Event Types" section) > https://crowdin.net/translate/cordova/122/en-ru (Resume header) > https://crowdin.net/translate/cordova/28/en-ru (Path to Android SDK) > https://crowdin.net/translate/cordova/3689/en-ru (Android SDK section, > example of adding tools to PATH) > https://crowdin.net/translate/cordova/23/en-ru (Plugin Class Mappings section) > https://crowdin.net/translate/cordova/3837/en-ru (Apache License header) > https://crowdin.net/translate/cordova/3838/en-ru (Apache License header) > - > Following page has elements which should be locked and existing translation > should be removed: > https://crowdin.net/translate/cordova/3687/en-ru (Apache License header) > https://crowdin.net/translate/cordova/35/en-ru (Create app) > - > Following page has elements which should be locked: > https://crowdin.net/translate/cordova/36/en-ru (Install the BlackBerry Native > SDK, Create a Project, Deploy to Emulator) > https://crowdin.net/translate/cordova/3839/en-ru (Apache License header, > Update to 3.2.0 from 3.1.0) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CB-6723) Android native tests won't compile
[ https://issues.apache.org/jira/browse/CB-6723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Kinard resolved CB-6723. --- Resolution: Fixed Fix Version/s: (was: 3.5.0) 3.6.0 > Android native tests won't compile > -- > > Key: CB-6723 > URL: https://issues.apache.org/jira/browse/CB-6723 > Project: Apache Cordova > Issue Type: Bug > Components: Android >Reporter: Marcel Kinard >Assignee: Marcel Kinard >Priority: Minor > Fix For: 3.6.0 > > > The Android native test project won't compile. Looks like the package name > for Robotium has changed from com.jayway.android.robotium.solo to > com.robotium.solo (I'm looking at the most recent Robotium jar - 1.5). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6723) Android native tests won't compile
[ https://issues.apache.org/jira/browse/CB-6723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14003094#comment-14003094 ] ASF subversion and git services commented on CB-6723: - Commit e98f6ae570766d648521f353966d25b86c0b0260 in cordova-android's branch refs/heads/master from [~cmarcelk] [ https://git-wip-us.apache.org/repos/asf?p=cordova-android.git;h=e98f6ae ] CB-6723 Update package name for Robotium > Android native tests won't compile > -- > > Key: CB-6723 > URL: https://issues.apache.org/jira/browse/CB-6723 > Project: Apache Cordova > Issue Type: Bug > Components: Android >Reporter: Marcel Kinard >Assignee: Marcel Kinard >Priority: Minor > Fix For: 3.5.0 > > > The Android native test project won't compile. Looks like the package name > for Robotium has changed from com.jayway.android.robotium.solo to > com.robotium.solo (I'm looking at the most recent Robotium jar - 1.5). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CB-6723) Android native tests won't compile
Marcel Kinard created CB-6723: - Summary: Android native tests won't compile Key: CB-6723 URL: https://issues.apache.org/jira/browse/CB-6723 Project: Apache Cordova Issue Type: Bug Components: Android Reporter: Marcel Kinard Assignee: Marcel Kinard Priority: Minor Fix For: 3.5.0 The Android native test project won't compile. Looks like the package name for Robotium has changed from com.jayway.android.robotium.solo to com.robotium.solo (I'm looking at the most recent Robotium jar - 1.5). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6707) Clarify in docs regarding the minimum Android level supported by Cordova
[ https://issues.apache.org/jira/browse/CB-6707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14003080#comment-14003080 ] ASF subversion and git services commented on CB-6707: - Commit 0b5bf0c0985ca2238b6739004de1d5b901dde516 in cordova-android's branch refs/heads/master from [~cmarcelk] [ https://git-wip-us.apache.org/repos/asf?p=cordova-android.git;h=0b5bf0c ] CB-6707 Update minSdkVersion to 10 consistently Update minSdkVersion in the AndroidManifest for the cordova.jar and the test project. > Clarify in docs regarding the minimum Android level supported by Cordova > > > Key: CB-6707 > URL: https://issues.apache.org/jira/browse/CB-6707 > Project: Apache Cordova > Issue Type: Improvement > Components: Docs >Reporter: Marcel Kinard >Assignee: Marcel Kinard >Priority: Minor > Fix For: 3.5.0 > > > I had a discussion here with someone who was asking about what to use as the > minSdkVersion in Cordova. I think there are 2 issues in the docs: > 1) the Platform Guide for Android in the docs still says (as of Cordova 3.4) > that Android 2.2 is supported. I believe support for Froyo was removed in > Cordova 3.0. That needs to be changed to say Android 2.3 is the min > supported, in all the doc versions from current back to Cordova 3.0. > (Correct?) > 2) For 2.3, it's a bit ambiguous if that means API 9 (2.3.0 - 2.3.2) or API > 10 (2.3.3-2.3.7). I'd suggest that instead of just saying "2.3" in the > Platform Guide for Android, that for the minimum supported version it include > the 3rd digit of the version and also state the API level. I see in > https://github.com/apache/cordova-android/blob/3.0.x/bin/templates/project/AndroidManifest.xml > that the minSdkVersion is set to 10 there. And API 9 does not appear on the > Google Dashboard ( https://developer.android.com/about/dashboards/index.html > ). So the documented minimum API level should be 10. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CB-6722) add function to coho to check licenses of third-party dependencies
Marcel Kinard created CB-6722: - Summary: add function to coho to check licenses of third-party dependencies Key: CB-6722 URL: https://issues.apache.org/jira/browse/CB-6722 Project: Apache Cordova Issue Type: New Feature Components: Coho Reporter: Marcel Kinard Assignee: Marcel Kinard Priority: Minor It would be nice if https://www.npmjs.org/package/license-checker could be added to coho to make it easier to check the licenses of node modules that are 3rd-party dependencies. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6721) iOS Failed test: battery.spec.4 should fire batterycritical events
[ https://issues.apache.org/jira/browse/CB-6721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14003043#comment-14003043 ] Shazron Abdullah commented on CB-6721: -- "null" (unknown) *is* a change however, so perhaps the null check is not needed. After testing some more -- the culprit I think is when the tests are running, the actual battery value is being set (in this case of my device it is 100), so the test values are not what are expected. 19 was set, then set to 5. But in the meantime the native side sets it to 100. 19 -> 100 -> 5. In this case, because of the if statements in battery.js (100->5), it would have sent out a batterylow event (thus the test failed because it expected a batterycritical event). I'm not sure why the if statements check me._level - if the thresholds are at 20 (batterylow) and 5 (batterycritical), we would only care about the info.level value. It is clear that a 100->5 transition is a batterycritical event, for example. > iOS Failed test: battery.spec.4 should fire batterycritical events > -- > > Key: CB-6721 > URL: https://issues.apache.org/jira/browse/CB-6721 > Project: Apache Cordova > Issue Type: Bug > Components: mobile-spec, Plugin Battery Status >Reporter: Shazron Abdullah > > Battery (navigator.battery) battery.spec.4 should fire batterycritical events. > timeout: timed out after 100 msec waiting for batterycritical onEvent was not > called when level goes from 19->5 > This test is new for CB-4520 CB-4519: > https://github.com/apache/cordova-mobile-spec/commit/b5b80a6ff80d3c8b3d7618fe051c824ec0d3771f -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6721) iOS Failed test: battery.spec.4 should fire batterycritical events
[ https://issues.apache.org/jira/browse/CB-6721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14003033#comment-14003033 ] Shazron Abdullah commented on CB-6721: -- The fix is, you must do a null check on info.level (level can be null -- https://github.com/apache/cordova-plugin-battery-status/blob/dbdcbebaa9a524f9dcef7816345ffa4b82109f21/src/ios/CDVBattery.m#L90) Line: https://github.com/apache/cordova-plugin-battery-status/blob/dbdcbebaa9a524f9dcef7816345ffa4b82109f21/www/battery.js#L71 Also, these assignments below should only happen when something changed, so it should be in the if block mentioned above: https://github.com/apache/cordova-plugin-battery-status/blob/dbdcbebaa9a524f9dcef7816345ffa4b82109f21/www/battery.js#L88-L89 > iOS Failed test: battery.spec.4 should fire batterycritical events > -- > > Key: CB-6721 > URL: https://issues.apache.org/jira/browse/CB-6721 > Project: Apache Cordova > Issue Type: Bug > Components: mobile-spec, Plugin Battery Status >Reporter: Shazron Abdullah > > Battery (navigator.battery) battery.spec.4 should fire batterycritical events. > timeout: timed out after 100 msec waiting for batterycritical onEvent was not > called when level goes from 19->5 > This test is new for CB-4520 CB-4519: > https://github.com/apache/cordova-mobile-spec/commit/b5b80a6ff80d3c8b3d7618fe051c824ec0d3771f -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CB-6720) Cordova File-Transfer download fails on iOS
[
https://issues.apache.org/jira/browse/CB-6720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zcs Mobile updated CB-6720:
---
Description:
File-Transfer download function exits with
*"TypeError: 'null' is not an object (evaluating 'result.lengthComputable')"*
Plugin version is 0.4.3, i tried 0.4.2 but the error is still the same. Please
refer to this post:
http://stackoverflow.com/questions/23317010/cordova-file-transfer-download-result-null-error
Same exact code works fine on Android 4.0.2 .
EDIT:
Sample code used for testing:
{code:JavaScript}
function win(entry){
console.log("OK!");
}
function fail(error){
console.log("ERROR!");
console.log(error.code);
}
var url =
"http://upload.wikimedia.org/wikipedia/commons/5/5b/Ultraviolet_image_of_the_Cygnus_Loop_Nebula_crop.jpg";;
var filename = "filename.jpg";
var uri = encodeURI(url);
window.requestFileSystem(LocalFileSystem.PERSISTENT, 0, function(fileSystem) {
fileSystem.root.getFile(filename, {create: true, exclusive: false},
function(fileEntry) {
var localPath = fileEntry.toURL();
var ft = new FileTransfer();
ft.download(uri,localPath,win,fail,false);
},function(error){console.log("errore 1: " + error.code);});
},function(error){console.log("errore 2: " + error.code);});
{code}
was:
File-Transfer download function exits with
*"TypeError: 'null' is not an object (evaluating 'result.lengthComputable')"*
Plugin version is 0.4.3, i tried 0.4.2 but the error is still the same. Please
refer to this post:
http://stackoverflow.com/questions/23317010/cordova-file-transfer-download-result-null-error
Same exact code works fine on Android 4.0.2 .
> Cordova File-Transfer download fails on iOS
> ---
>
> Key: CB-6720
> URL: https://issues.apache.org/jira/browse/CB-6720
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin File Transfer
> Environment: iOS 7.0.3 on iPad2 - Cordova 3.4.1-0.1.0
>Reporter: Zcs Mobile
>
> File-Transfer download function exits with
> *"TypeError: 'null' is not an object (evaluating 'result.lengthComputable')"*
> Plugin version is 0.4.3, i tried 0.4.2 but the error is still the same.
> Please refer to this post:
> http://stackoverflow.com/questions/23317010/cordova-file-transfer-download-result-null-error
> Same exact code works fine on Android 4.0.2 .
> EDIT:
> Sample code used for testing:
> {code:JavaScript}
> function win(entry){
> console.log("OK!");
> }
> function fail(error){
> console.log("ERROR!");
> console.log(error.code);
> }
> var url =
> "http://upload.wikimedia.org/wikipedia/commons/5/5b/Ultraviolet_image_of_the_Cygnus_Loop_Nebula_crop.jpg";;
> var filename = "filename.jpg";
> var uri = encodeURI(url);
> window.requestFileSystem(LocalFileSystem.PERSISTENT, 0, function(fileSystem) {
>fileSystem.root.getFile(filename, {create: true, exclusive: false},
> function(fileEntry) {
>var localPath = fileEntry.toURL();
>var ft = new FileTransfer();
>ft.download(uri,localPath,win,fail,false);
>},function(error){console.log("errore 1: " + error.code);});
> },function(error){console.log("errore 2: " + error.code);});
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (CB-6721) iOS Failed test: battery.spec.4 should fire batterycritical events
Shazron Abdullah created CB-6721: Summary: iOS Failed test: battery.spec.4 should fire batterycritical events Key: CB-6721 URL: https://issues.apache.org/jira/browse/CB-6721 Project: Apache Cordova Issue Type: Bug Components: mobile-spec, Plugin Battery Status Reporter: Shazron Abdullah Battery (navigator.battery) battery.spec.4 should fire batterycritical events. timeout: timed out after 100 msec waiting for batterycritical onEvent was not called when level goes from 19->5 This test is new for CB-4520 CB-4519: https://github.com/apache/cordova-mobile-spec/commit/b5b80a6ff80d3c8b3d7618fe051c824ec0d3771f -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-5653) [WP8] make visible the version of the Cordova native lib
[ https://issues.apache.org/jira/browse/CB-5653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14002986#comment-14002986 ] ASF GitHub Bot commented on CB-5653: GitHub user martincgg opened a pull request: https://github.com/apache/cordova-wp8/pull/35 [CB-5653][WP8] make visible cordova version Added static class to record the cordova version on the native side, keep in it clean, and consistent. Class added to Lib & template to get it compiled. The varible it will be printed in console, during execution of CordovaView. You can merge this pull request into a Git repository by running: $ git pull https://github.com/martincgg/cordova-wp8 CB-5653 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-wp8/pull/35.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 #35 commit efd7625e361068383514c859f4ebabc2d6f30aac Author: Martin Gonzalez Date: 2014-05-20T09:04:50Z [CB-5653][WP8] make visible cordova version Added static class to record the cordova version on the native side, keep in it clean, and consistent. Class added to Lib & template to get it compiled. The varible it will be printed in console, during execution of CordovaView. > [WP8] make visible the version of the Cordova native lib > > > Key: CB-5653 > URL: https://issues.apache.org/jira/browse/CB-5653 > Project: Apache Cordova > Issue Type: Sub-task > Components: WP8 >Reporter: Marcel Kinard >Priority: Minor > > See the parent task. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CB-6720) Cordova File-Transfer download fails on iOS
Zcs Mobile created CB-6720: -- Summary: Cordova File-Transfer download fails on iOS Key: CB-6720 URL: https://issues.apache.org/jira/browse/CB-6720 Project: Apache Cordova Issue Type: Bug Components: Plugin File Transfer Environment: iOS 7.0.3 on iPad2 - Cordova 3.4.1-0.1.0 Reporter: Zcs Mobile File-Transfer download function exits with *"TypeError: 'null' is not an object (evaluating 'result.lengthComputable')"* Plugin version is 0.4.3, i tried 0.4.2 but the error is still the same. Please refer to this post: http://stackoverflow.com/questions/23317010/cordova-file-transfer-download-result-null-error Same exact code works fine on Android 4.0.2 . -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6718) cordova firefox reports wrong version
[
https://issues.apache.org/jira/browse/CB-6718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14002898#comment-14002898
]
ASF GitHub Bot commented on CB-6718:
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-firefoxos/pull/10
> cordova firefox reports wrong version
> -
>
> Key: CB-6718
> URL: https://issues.apache.org/jira/browse/CB-6718
> Project: Apache Cordova
> Issue Type: Bug
> Components: FirefoxOS
>Affects Versions: 3.5.0
> Environment: MacOSX
>Reporter: Carlos Santana
>
> While doing rc testing platform cordova-firefoxos reports 3.4.0-dev when it
> should report 3.5.0
> Steps to replicate
> Install cordova cli 3.5.0-0.2.4
> {code}
> $ ../../node_modules/.bin/cordova -v
> 3.5.0-0.2.4
> $ ./node_modules/.bin/cordova create firefox350/newProj
> Creating a new cordova project with name "HelloCordova" and id
> "io.cordova.hellocordova" at location
> "/Users/csantana23/Documents/cordova/firefox350/newProj"
> Downloading cordova library for www...
> Download complete
> /Users/csantana23/Documents/cordova/firefox350/newProj
> $ ../../node_modules/.bin/cordova platform add firefoxos
> Downloading cordova library for firefoxos...
> Download complete
> Creating firefoxos project...
> Creating Firefox OS project
> Project Path platforms/firefoxos
> Package Name io.cordova.hellocordova
> Project Name HelloCordova
> /Users/csantana23/Documents/cordova/firefox350/newProj
> $ ../../node_modules/.bin/cordova platform ls
> Installed platforms: firefoxos 3.4.0-dev
> Available platforms: amazon-fireos, android, blackberry10, ios
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CB-6718) cordova firefox reports wrong version
[
https://issues.apache.org/jira/browse/CB-6718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14002897#comment-14002897
]
ASF subversion and git services commented on CB-6718:
-
Commit 1192f0bb296fb29eb5fc2c2eaf4557e2793606bb in cordova-firefoxos's branch
refs/heads/master from [~zalun]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-firefoxos.git;h=1192f0b ]
version fixed (CB-6718)
> cordova firefox reports wrong version
> -
>
> Key: CB-6718
> URL: https://issues.apache.org/jira/browse/CB-6718
> Project: Apache Cordova
> Issue Type: Bug
> Components: FirefoxOS
>Affects Versions: 3.5.0
> Environment: MacOSX
>Reporter: Carlos Santana
>
> While doing rc testing platform cordova-firefoxos reports 3.4.0-dev when it
> should report 3.5.0
> Steps to replicate
> Install cordova cli 3.5.0-0.2.4
> {code}
> $ ../../node_modules/.bin/cordova -v
> 3.5.0-0.2.4
> $ ./node_modules/.bin/cordova create firefox350/newProj
> Creating a new cordova project with name "HelloCordova" and id
> "io.cordova.hellocordova" at location
> "/Users/csantana23/Documents/cordova/firefox350/newProj"
> Downloading cordova library for www...
> Download complete
> /Users/csantana23/Documents/cordova/firefox350/newProj
> $ ../../node_modules/.bin/cordova platform add firefoxos
> Downloading cordova library for firefoxos...
> Download complete
> Creating firefoxos project...
> Creating Firefox OS project
> Project Path platforms/firefoxos
> Package Name io.cordova.hellocordova
> Project Name HelloCordova
> /Users/csantana23/Documents/cordova/firefox350/newProj
> $ ../../node_modules/.bin/cordova platform ls
> Installed platforms: firefoxos 3.4.0-dev
> Available platforms: amazon-fireos, android, blackberry10, ios
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
