[jira] [Commented] (CB-6686) [3.5.0rc][Windows8] Build error if path contains whitespaces
[ https://issues.apache.org/jira/browse/CB-6686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13997017#comment-13997017 ] ASF subversion and git services commented on CB-6686: - Commit 1d2c5123a12fd4b5969d7ef4432aa131cf09a32a in cordova-windows's branch refs/heads/3.5.x from sgrebnov [ https://git-wip-us.apache.org/repos/asf?p=cordova-windows.git;h=1d2c512 ] CB-6686 [3.5.0rc][Windows8] Build error if path contains whitespaces [3.5.0rc][Windows8] Build error if path contains whitespaces - Key: CB-6686 URL: https://issues.apache.org/jira/browse/CB-6686 Project: Apache Cordova Issue Type: Bug Components: Windows 8 Affects Versions: 3.5.0 Reporter: Sergey Grebnov Assignee: Jesse MacFadyen Create project in path w/ whitespaces Add windows platform Run build Building Cordova Windows 8 Project: Configuration : Debug Directory : c:\temp\_rc3 5 0\app\platforms\windows8 MSBuildToolsPath: C:\Program Files (x86)\MSBuild\12.0\bin\ cmd /c C:\Program Files (x86)\MSBuild\12.0\bin\msbuild c:\temp\_rc3 5 0\app\platforms\windows8\CordovaApp.sln /clp:NoSummary;NoItemAndPropertyList;Verbosity=minimal /nologo /p:Configuration=Debug Building the projects in this solution one at a time. To enable parallel build, please add the /m switch. Unblock-File : A positional parameter cannot be found that accepts argument '5'. At line:1 char:1 + Unblock-File c:\temp\_rc3 5 Error: cmd: Command failed with exit code 2 at ChildProcess.whenDone (C:\Users\Sergei\AppData\Roaming\npm\node_modules\cordova\node_modules\cordova-lib\src\cordova\superspawn.js:131:23) at ChildProcess.EventEmitter.emit (events.js:98:17) at maybeClose (child_process.js:743:16) at Process.ChildProcess._handle.onexit (child_process.js:810:5) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-5675) Can't get rid of nameHello Cordova/name from config.xml
[ https://issues.apache.org/jira/browse/CB-5675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13997274#comment-13997274 ] Axel Nennker commented on CB-5675: -- Adding name and description to SINGLETONS is not in 3.5.0-0.2.3 yet. I think this is a good fix although it misses the mark http://www.w3.org/TR/widgets/#the-name-element-and-its-attributes E.g. name is only a singleton for same xml:lang values... So name xml:lang=deHallo Welt/name and name xml:lang=enHello World/name are allowed in one config.xml Can't get rid of nameHello Cordova/name from config.xml - Key: CB-5675 URL: https://issues.apache.org/jira/browse/CB-5675 Project: Apache Cordova Issue Type: Bug Components: CLI Affects Versions: 3.2.0 Environment: OSX/IOS Reporter: Michael Stanford Fix For: Master config_parser.js merges your www/config.xml in on top of cordova/defaults.xml to produce your platform/project/config.xml. I don't like seeing Hello Cordova in there as the name of the project in addition to the one that I gave it. Same with the description. I am concerned that it confuses Xcode as well. So I changed the SINGLETONS array in config_parser.merge_with() from: [content, author] to: [content, author,description,name] Which seems to have fixed my problem. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CB-6445) Cannot build android project if www folder contains long js file name
[ https://issues.apache.org/jira/browse/CB-6445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser resolved CB-6445. Resolution: Won't Fix This is an Android Build limitation. Your filename must be under 100 characters in length to be included in the APK. We can't change this limitation. Cannot build android project if www folder contains long js file name - Key: CB-6445 URL: https://issues.apache.org/jira/browse/CB-6445 Project: Apache Cordova Issue Type: Bug Components: Android Affects Versions: 3.4.0 Environment: Mac OS X 10.9.2 Reporter: Bobby Nguyen Labels: android, filename, js Test Procedure : 1. Create a new android cordova project 2. Build to check that it works 3. Add in the www folder a js file with a very long file name 4. Build again and it see that if fails This is a link to download the sample project that failed to build. https://dl.dropboxusercontent.com/u/9154761/cordova/cb-6445/development.zip -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CB-6617) inAppBrowser does not contain the localStorage of the parent window
[
https://issues.apache.org/jira/browse/CB-6617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bowser resolved CB-6617.
Resolution: Won't Fix
The iOS version of this issue needs to be created separately, closing this
issue as won't fix, since this is a clear security vulnerability.
inAppBrowser does not contain the localStorage of the parent window
---
Key: CB-6617
URL: https://issues.apache.org/jira/browse/CB-6617
Project: Apache Cordova
Issue Type: Bug
Components: Android, iOS, Plugin InAppBrowser
Affects Versions: 3.4.0
Reporter: Ralph S Theart
Assignee: Joe Bowser
Labels: android, localstorage
Why is it that I can share localStorage information between wbeviews(I refer
to my app and a inappbrowser instance) in iOS but not in Android.
If I do...
{code}
//location: index.html (in my app)
localStorage.setItem('Cheese':'Brie');
{code}
Then if I try to retrieve this data from locally served html file via
inappbroweser in android
{code}
var item = localStorage.getItem('Cheese');
item = null
{code}
It never get set... BUT if I recompile my app and locally served html file
via inAppBroweser then it's there.
I feel like i'm missing something..
How in the world are people passing data back and forth between the app view
and the iab view?? I need to pass deep objects back and forth ...so using url
parameters is unacceptable. Neither is using inject js...as it is not
consistent in android the data does not always make it to the iab
instance and sometimes becomes undefined...I have tested this with LoadStart,
LoadStop...it's just not consistent.
iOS just works...could you help me thanks.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CB-5941) document hooks !
[ https://issues.apache.org/jira/browse/CB-5941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13997262#comment-13997262 ] Raghuram commented on CB-5941: -- [~agrieve] This is linked from the the README.md file of [cordova-cli | https://github.com/apache/cordova-cli ] in github. It is in Hooks section and specifically the line Refer to templates/hooks-README.md for more information. I guess the link can be updated. document hooks ! Key: CB-5941 URL: https://issues.apache.org/jira/browse/CB-5941 Project: Apache Cordova Issue Type: Bug Components: CLI Reporter: Brian LeRoux -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6686) [3.5.0rc][Windows8] Build error if path contains whitespaces
[ https://issues.apache.org/jira/browse/CB-6686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13997059#comment-13997059 ] ASF GitHub Bot commented on CB-6686: Github user asfgit closed the pull request at: https://github.com/apache/cordova-windows/pull/31 [3.5.0rc][Windows8] Build error if path contains whitespaces - Key: CB-6686 URL: https://issues.apache.org/jira/browse/CB-6686 Project: Apache Cordova Issue Type: Bug Components: Windows 8 Affects Versions: 3.5.0 Reporter: Sergey Grebnov Assignee: Jesse MacFadyen Create project in path w/ whitespaces Add windows platform Run build Building Cordova Windows 8 Project: Configuration : Debug Directory : c:\temp\_rc3 5 0\app\platforms\windows8 MSBuildToolsPath: C:\Program Files (x86)\MSBuild\12.0\bin\ cmd /c C:\Program Files (x86)\MSBuild\12.0\bin\msbuild c:\temp\_rc3 5 0\app\platforms\windows8\CordovaApp.sln /clp:NoSummary;NoItemAndPropertyList;Verbosity=minimal /nologo /p:Configuration=Debug Building the projects in this solution one at a time. To enable parallel build, please add the /m switch. Unblock-File : A positional parameter cannot be found that accepts argument '5'. At line:1 char:1 + Unblock-File c:\temp\_rc3 5 Error: cmd: Command failed with exit code 2 at ChildProcess.whenDone (C:\Users\Sergei\AppData\Roaming\npm\node_modules\cordova\node_modules\cordova-lib\src\cordova\superspawn.js:131:23) at ChildProcess.EventEmitter.emit (events.js:98:17) at maybeClose (child_process.js:743:16) at Process.ChildProcess._handle.onexit (child_process.js:810:5) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CB-6688) target-device preference in config.xml is completely ignored for iOS
Daniel Hough created CB-6688: Summary: target-device preference in config.xml is completely ignored for iOS Key: CB-6688 URL: https://issues.apache.org/jira/browse/CB-6688 Project: Apache Cordova Issue Type: Bug Affects Versions: 3.4.0 Reporter: Daniel Hough -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CB-6684) [3.5.0rc][Windows8] Splash screen setting breaks the build
[ https://issues.apache.org/jira/browse/CB-6684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Grebnov updated CB-6684: --- Assignee: Jesse MacFadyen (was: Sergey Grebnov) [3.5.0rc][Windows8] Splash screen setting breaks the build -- Key: CB-6684 URL: https://issues.apache.org/jira/browse/CB-6684 Project: Apache Cordova Issue Type: Bug Components: Windows 8 Reporter: Sergey Grebnov Assignee: Jesse MacFadyen Add dummy splash screen settings to config.xml preference name=SplashScreen value=screen / Run build C:\temp\_rc3_5_0\app λ cordova build windows8 Running command: C:\temp\_rc3_5_0\app\platforms\windows8\cordova\build.bat Building Cordova Windows 8 Project: Configuration : Debug Directory : C:\temp\_rc3_5_0\app\platforms\windows8 MSBuildToolsPath: C:\Program Files (x86)\MSBuild\12.0\bin\ cmd /c C:\Program Files (x86)\MSBuild\12.0\bin\msbuild C:\temp\_rc3_5_0\app\platforms\windows8\CordovaApp.sln /clp:NoSummary;NoItemAndPropertyList;Verbosity=minimal /nologo /p:Configuration=Debug Building the projects in this solution one at a time. To enable parallel build, please add the /m switch. Applying Platform Config ... Setting SplashScreen = screen package.appxmanifest(20,31): error APPX1617: App manifest references the splash screen image 'screen' which has an unsupported extension. Extension must be JPG, JPEG, or PNG. [C:\temp\_rc3_5_0\app\platforms\windows8\CordovaApp.jsproj] Error: C:\temp\_rc3_5_0\app\platforms\windows8\cordova\build.bat: Command failed with exit code 2 at ChildProcess.whenDone (C:\Users\Sergei\AppData\Roaming\npm\node_modules\cordova\node_modules\cordova-lib\src\cordova\superspawn.js:131:23) at ChildProcess.EventEmitter.emit (events.js:98:17) at maybeClose (child_process.js:743:16) at Process.ChildProcess._handle.onexit (child_process.js:810:5) We should check that file exists and if not then echo warning message instead of fail -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CB-6601) [Release + 3.5.0] Test Tag 3.5.0 for BlackBerry
[ https://issues.apache.org/jira/browse/CB-6601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Higgins resolved CB-6601. --- Resolution: Fixed Tested and working. Comments in CB-6590 [Release + 3.5.0] Test Tag 3.5.0 for BlackBerry - Key: CB-6601 URL: https://issues.apache.org/jira/browse/CB-6601 Project: Apache Cordova Issue Type: Sub-task Components: BlackBerry Reporter: Steve Gill Assignee: Bryan Higgins 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] [Commented] (CB-6668) plugins don't have to have a text property - plugin list crashes if it's missing
[ https://issues.apache.org/jira/browse/CB-6668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13993858#comment-13993858 ] Josh Soref commented on CB-6668: [~shazron] notes that this field is purely informational, perh http://cordova.apache.org/docs/en/edge/plugin_ref_spec.md So it really should not have been treated as mandatory (crashing). plugins don't have to have a text property - plugin list crashes if it's missing Key: CB-6668 URL: https://issues.apache.org/jira/browse/CB-6668 Project: Apache Cordova Issue Type: Bug Components: CordovaLib Affects Versions: 3.5.0 Reporter: Josh Soref Assignee: Josh Soref Priority: Blocker steps: 1. install com.blackberry.utils into a project (use an old cordova ) 2. cordova plugin list actual results: TypeError: Cannot read property 'text' of null at new PluginInfo (cordova-lib/src/PluginInfo.js:54:32) at cordova-lib/src/PluginInfo.js:78:17 at Array.forEach (native) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CB-6690) UIWebview freezes while page behind the link with target='_system' opens in mobile safari
Jake McAllister created CB-6690: --- Summary: UIWebview freezes while page behind the link with target='_system' opens in mobile safari Key: CB-6690 URL: https://issues.apache.org/jira/browse/CB-6690 Project: Apache Cordova Issue Type: Bug Components: Plugin InAppBrowser Affects Versions: 3.4.0 Environment: iOS 7.1, iPhone Reporter: Jake McAllister When opening an external link in cordova app using the inAppBrowser plugin with target='_blank' the cordova app freezes until the page in safari has loaded. This posses a problem where if the user accidentally presses it and wants to go back to the app before the page has loaded in safari the app remain frozen. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-5941) document hooks !
[ https://issues.apache.org/jira/browse/CB-5941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13997535#comment-13997535 ] ASF subversion and git services commented on CB-5941: - Commit 9832fab19c22edbeda35fcffcb20d6ec64681f8b in cordova-cli's branch refs/heads/master from [~agrieve] [ https://git-wip-us.apache.org/repos/asf?p=cordova-cli.git;h=9832fab ] CB-5941 Update link to hooks-README.md file from README.md document hooks ! Key: CB-5941 URL: https://issues.apache.org/jira/browse/CB-5941 Project: Apache Cordova Issue Type: Bug Components: CLI Reporter: Brian LeRoux -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6570) mobile-spec has inline JavaScript which is forbidden for Firefox OS privileged apps
[ https://issues.apache.org/jira/browse/CB-6570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13997553#comment-13997553 ] ASF GitHub Bot commented on CB-6570: GitHub user zalun opened a pull request: https://github.com/apache/cordova-mobile-spec/pull/64 CB-6570 FFOS privileged apps compatibility All tests are now compatible with FFOS privileged apps (CSP restrictions) - inline scripts moved to JavaScript files - added addListenerToClass function which is used to connect buttons with test functions. - moved test initialization to JS file (for DRY and privileged apps compatibility) Please check it on all platforms and r+ if working. There should be no change in behaviour of the app. You can merge this pull request into a Git repository by running: $ git pull https://github.com/zalun/cordova-mobile-spec ffos_privileged_compatible Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-mobile-spec/pull/64.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 #64 commit a7c88d8fc696179356db7759db82782fee4e Author: Piotr Zalewa pi...@zalewa.info Date: 2014-04-30T13:14:04Z Manual tests fixed Removing inline scripts from mobile-spec to make it compatible with FFOS priveleged type apps (i.e. using contacts) added addListenerToClass function which is used to connect buttons with test functions. Please check it on all platforms and r+ if working. moved test initialization to JS file (for DRY and privileged apps compatibility) commit 53a34221c2c78ccfb742e8e793225bec195be0ff Author: Piotr Zalewa pi...@zalewa.info Date: 2014-05-14T13:42:17Z Merge branch 'master' into ffos_privileged_compatible mobile-spec has inline JavaScript which is forbidden for Firefox OS privileged apps --- Key: CB-6570 URL: https://issues.apache.org/jira/browse/CB-6570 Project: Apache Cordova Issue Type: Bug Components: FirefoxOS, mobile-spec Reporter: Piotr Zalewa Assignee: Piotr Zalewa -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CB-6692) Launching the camera on Android fails with the Play Store version of (Google) Camera.
[
https://issues.apache.org/jira/browse/CB-6692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Björn Vermeule updated CB-6692:
---
Description:
Google recently released the Android Camera as an app in the Play Store
([Link|https://play.google.com/store/apps/details?id=com.google.android.GoogleCamera]).
It seems that the most recent version of Google Camera prevents Cordova to
launch/connect to the app.
When removing Google Camera (and thus reverting to the system Camera) Cordova
can successfully take pictures. Cordova fails when I reinstall Google Camera
again.
Cordova fails with the error message Can't connect to the camera. (see
attached screenshot). The camera does start and I am able to take pictures
(from the camera's point of view) but Cordova will always fail and call the
error handler.
JavaScript code I'm using to launch the camera:
{code:JavaScript}
navigator.camera.getPicture(
function(imageData) {
$('.taken-image').attr('src', imageData);
},
function() {
alert('Picture has not been taken ...');
}, {
quality: 50,
destinationType: Camera.DestinationType.FILE_URI,
sourceType: Camera.PictureSourceType.CAMERA
});
{code}
was:
Google recently released the Android Camera as an app in the Play Store
([Link|https://play.google.com/store/apps/details?id=com.google.android.GoogleCamera]).
It seems that the most recent version of Google Camera prevents Cordova to
launch/connect to the app.
When removing Google Camera (and thus reverting to the system Camera) Cordova
can successfully take pictures. Cordova fails when I reinstall Google Camera
again.
Launching the camera on Android fails with the Play Store version of (Google)
Camera.
-
Key: CB-6692
URL: https://issues.apache.org/jira/browse/CB-6692
Project: Apache Cordova
Issue Type: Bug
Components: Plugin Camera
Affects Versions: 3.4.0
Reporter: Björn Vermeule
Attachments: Screenshot_2014-05-14-16-58-40.png
Google recently released the Android Camera as an app in the Play Store
([Link|https://play.google.com/store/apps/details?id=com.google.android.GoogleCamera]).
It seems that the most recent version of Google Camera prevents Cordova to
launch/connect to the app.
When removing Google Camera (and thus reverting to the system Camera) Cordova
can successfully take pictures. Cordova fails when I reinstall Google Camera
again.
Cordova fails with the error message Can't connect to the camera. (see
attached screenshot). The camera does start and I am able to take pictures
(from the camera's point of view) but Cordova will always fail and call the
error handler.
JavaScript code I'm using to launch the camera:
{code:JavaScript}
navigator.camera.getPicture(
function(imageData) {
$('.taken-image').attr('src', imageData);
},
function() {
alert('Picture has not been taken ...');
}, {
quality: 50,
destinationType: Camera.DestinationType.FILE_URI,
sourceType: Camera.PictureSourceType.CAMERA
});
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CB-5650) make visible the version of the Cordova native lib
[
https://issues.apache.org/jira/browse/CB-5650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13997636#comment-13997636
]
Marcel Kinard commented on CB-5650:
---
I would suggest the following output string:
{code}
Apache Cordova native platform version %s is starting.
{code}
make visible the version of the Cordova native lib
--
Key: CB-5650
URL: https://issues.apache.org/jira/browse/CB-5650
Project: Apache Cordova
Issue Type: Improvement
Components: Android, BlackBerry, iOS, Ubuntu, WP8
Reporter: Marcel Kinard
Priority: Minor
We recently had a situation where a consumer had mismatched the runtime: one
version of cordova.js and another version of the Cordova native code. The
consumer gave us their compiled app, so we didn't have access to the native's
source in the project. We had an idea that it would be nice if the native
code compiled in some marker so we could tell what version it was without the
source. Perhaps issue a log on startup saying Greetings from Cordova native
code 3.2.0, or have something compiled in that would appear in strings
cordova.jar | grep version.
See some discussion at http://markmail.org/thread/m4h4csvcq4cs3dcr
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (CB-6692) Launching the camera on Android fails with the Play Store version of (Google) Camera.
Björn Vermeule created CB-6692: -- Summary: Launching the camera on Android fails with the Play Store version of (Google) Camera. Key: CB-6692 URL: https://issues.apache.org/jira/browse/CB-6692 Project: Apache Cordova Issue Type: Bug Components: Plugin Camera Affects Versions: 3.4.0 Reporter: Björn Vermeule Attachments: Screenshot_2014-05-14-16-58-40.png Google recently released the Android Camera as an app in the Play Store ([Link|https://play.google.com/store/apps/details?id=com.google.android.GoogleCamera]). It seems that the most recent version of Google Camera prevents Cordova to launch/connect to the app. When removing Google Camera (and thus reverting to the system Camera) Cordova can successfully take pictures. Cordova fails when I reinstall Google Camera again. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CB-5650) make visible the version of the Cordova native lib
[ https://issues.apache.org/jira/browse/CB-5650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Kinard reassigned CB-5650: - Assignee: Marcel Kinard make visible the version of the Cordova native lib -- Key: CB-5650 URL: https://issues.apache.org/jira/browse/CB-5650 Project: Apache Cordova Issue Type: Improvement Components: Android, BlackBerry, iOS, Ubuntu, WP8 Reporter: Marcel Kinard Assignee: Marcel Kinard Priority: Minor We recently had a situation where a consumer had mismatched the runtime: one version of cordova.js and another version of the Cordova native code. The consumer gave us their compiled app, so we didn't have access to the native's source in the project. We had an idea that it would be nice if the native code compiled in some marker so we could tell what version it was without the source. Perhaps issue a log on startup saying Greetings from Cordova native code 3.2.0, or have something compiled in that would appear in strings cordova.jar | grep version. See some discussion at http://markmail.org/thread/m4h4csvcq4cs3dcr -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CB-6693) Investigate Certificate Pinning for Third-Party WebViews
Joe Bowser created CB-6693: -- Summary: 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 Reporter: Joe Bowser -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CB-6688) target-device preference in config.xml is completely ignored for iOS
[ https://issues.apache.org/jira/browse/CB-6688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Hough updated CB-6688: - Description: The following line in config.xml should cause the xcodeproj generated to have it's Targeted Device Family different depending on the value. For instance, handset should cause it to be iPhone. Yet, even when handset is chose, it becomes a universal (iPad/iPhone) app. preference name=target-device value=handset / This is a *real* problem, because if you don't realise that this is happening when you submit to the App Store after three hours of screenshots and descriptions, you're rejected because there are no iPad screenshots. target-device preference in config.xml is completely ignored for iOS -- Key: CB-6688 URL: https://issues.apache.org/jira/browse/CB-6688 Project: Apache Cordova Issue Type: Bug Affects Versions: 3.4.0 Reporter: Daniel Hough The following line in config.xml should cause the xcodeproj generated to have it's Targeted Device Family different depending on the value. For instance, handset should cause it to be iPhone. Yet, even when handset is chose, it becomes a universal (iPad/iPhone) app. preference name=target-device value=handset / This is a *real* problem, because if you don't realise that this is happening when you submit to the App Store after three hours of screenshots and descriptions, you're rejected because there are no iPad screenshots. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-5658) Move plugin docs to plugin repos
[ https://issues.apache.org/jira/browse/CB-5658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13997840#comment-13997840 ] Jesse MacFadyen commented on CB-5658: - I think this is done isn't it? Ping [~agrieve] Move plugin docs to plugin repos Key: CB-5658 URL: https://issues.apache.org/jira/browse/CB-5658 Project: Apache Cordova Issue Type: Bug Components: Docs, Plugin Battery Status, Plugin Camera, Plugin Console, Plugin Contacts, Plugin Device, Plugin Device Motion, Plugin Device Orientation, Plugin Dialogs, Plugin File, Plugin File Transfer, Plugin Geolocation, Plugin Globalization, Plugin InAppBrowser, Plugin Media, Plugin Media Capture, Plugin Network Information, Plugin SplashScreen, Plugin Vibration Reporter: Andrew Grieve Assignee: Andrew Grieve This involves: 1. Delete the docs/ directory from all plugins - They contain stale copies of what's in cordova-docs 2. Move plugin information found in cordova-docs into a single doc/index.md file within the respective plugin repos - Link to this file within each plugin's README.md file 3. Delete the API Reference section of cordova-docs 4. Add a guide called Cordova Plugins, which contains: - a link to plugins.cordova.io, - a list of the org.apache.cordova plugins, which link to their index.md files on github - e.g. https://github.com/apache/cordova-plugin-media-capture/blob/master/README.md - These can be changed to point at their plugins.cordova.io page when that shows READMEs. - A link to the 3.3 docs, which still have plugin API reference - Mostly, this is for finding non-english versions. Motivation: - Plugins are on a separate release cycle from platforms docs. - The documentation is often mismatched due to this - Pull requests for plugins don't update the plugin docs - But I think they would if the docs were in the same repo Caveats: - This will mess up our current translations story for plugins. - I think this can be fixed up though, by changing out http://crowdin.net push / pull scripts - E.g. have README.md translations go in: cordova-plugin-foo/translations/fr/README.md -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CB-6675) [amazon-fireos]Adding amazon-fireos fails with an error in amazon_fireos_parser.js
[ https://issues.apache.org/jira/browse/CB-6675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Archana Naik resolved CB-6675. -- Resolution: Fixed [amazon-fireos]Adding amazon-fireos fails with an error in amazon_fireos_parser.js -- Key: CB-6675 URL: https://issues.apache.org/jira/browse/CB-6675 Project: Apache Cordova Issue Type: Bug Components: Amazon FireOS Affects Versions: 3.5.0 Reporter: Archana Naik Assignee: Archana Naik Fix For: 3.5.0 Adding amazon-fireos platform fails with this error: TypeError: Cannot read property 'attrib' of undefined at Object.module.exports.update_from_config (/usr/local/lib/node_modules/cordova/node_modules/cordova-lib/src/cordova/metadata/amazon_fireos_parser.js:215:23) at Object.module.exports.update_project (/usr/local/lib/node_modules/cordova/node_modules/cordova-lib/src/cordova/metadata/amazon_fireos_parser.js:287:18) at /usr/local/lib/node_modules/cordova/node_modules/cordova-lib/src/cordova/prepare.js:113:31 at _fulfilled (/usr/local/lib/node_modules/cordova/node_modules/q/q.js:798:54) at self.promiseDispatch.done (/usr/local/lib/node_modules/cordova/node_modules/q/q.js:827:30) at Promise.promise.promiseDispatch (/usr/local/lib/node_modules/cordova/node_modules/q/q.js:760:13) at /usr/local/lib/node_modules/cordova/node_modules/q/q.js:821:14 at flush (/usr/local/lib/node_modules/cordova/node_modules/q/q.js:108:17) at process._tickCallback (node.js:339:11) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CB-6692) Launching the camera on Android fails with the Play Store version of (Google) Camera.
[ https://issues.apache.org/jira/browse/CB-6692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Björn Vermeule updated CB-6692: --- Attachment: Screenshot_2014-05-14-16-58-40.png Launching the camera on Android fails with the Play Store version of (Google) Camera. - Key: CB-6692 URL: https://issues.apache.org/jira/browse/CB-6692 Project: Apache Cordova Issue Type: Bug Components: Plugin Camera Affects Versions: 3.4.0 Reporter: Björn Vermeule Attachments: Screenshot_2014-05-14-16-58-40.png Google recently released the Android Camera as an app in the Play Store ([Link|https://play.google.com/store/apps/details?id=com.google.android.GoogleCamera]). It seems that the most recent version of Google Camera prevents Cordova to launch/connect to the app. When removing Google Camera (and thus reverting to the system Camera) Cordova can successfully take pictures. Cordova fails when I reinstall Google Camera again. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6661) Web Platform Target
[ https://issues.apache.org/jira/browse/CB-6661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13997902#comment-13997902 ] Daniel commented on CB-6661: Good to know that project was thinking in that way! However.. this is definitely not strictly for testing purposes. For instance we guess that HipChat uses this setup. All of their clients (android, ios, and web) have the same look and feel. This idea would expose the cordova api's to any server and any implementation of the apis. For instance you could nodejs server on anything (a chip in motorcycle registering gps info etc.) then have your mobile app connect to that server and exchange information. Web Platform Target --- Key: CB-6661 URL: https://issues.apache.org/jira/browse/CB-6661 Project: Apache Cordova Issue Type: Improvement Components: CordovaJS Affects Versions: 3.4.0 Environment: All Reporter: Daniel Priority: Minor Labels: cordova-js, features, platform Fix For: 3.4.0 I have not been able to find built in functionality for cordova to deploy an app to a server platform. This purpose of this new platform is to allow an HTML5 application within a Cordova project to be deployed on a web server, available for access over standard internet protocols. My team and I will be actively working this at https://github.com/CollinearGroup/cordova-js We intend to build this functionality with a nodejs server but hope that we can provide the server with varying backends like Grails and Rails. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-5421) Add BOM to all html, js, css files to ensure app can pass Windows Store Certification
[ https://issues.apache.org/jira/browse/CB-5421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13997938#comment-13997938 ] Josh Soref commented on CB-5421: [~purplecabbage]: Please integrate https://github.com/apache/cordova-lib/pull/8 -- your change broke the tests' pretty dots Add BOM to all html, js, css files to ensure app can pass Windows Store Certification - Key: CB-5421 URL: https://issues.apache.org/jira/browse/CB-5421 Project: Apache Cordova Issue Type: Improvement Components: CLI, Windows 8 Reporter: Maxime LUCE Assignee: Sergey Grebnov Windows Store Certification requires each javascript, html and css files to be encoded in utf-8, with BOM (byte order mark). So it could be helpful to ensure this encoding during project update. It could be added in windows8_parser.js. -- 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-tabpanelfocusedCommentId=13997146#comment-13997146 ] ASF GitHub Bot commented on CB-6469: Github user gorkem closed the pull request at: https://github.com/apache/cordova-cli/pull/165 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. feature name=Console param name=id value=org.apache.cordova.core.console / param name=version value=0.2.8 / /feature 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] [Commented] (CB-6469) Restore plugins from config.xml
[ https://issues.apache.org/jira/browse/CB-6469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13997147#comment-13997147 ] ASF GitHub Bot commented on CB-6469: Github user gorkem commented on the pull request: https://github.com/apache/cordova-cli/pull/165#issuecomment-43031932 new PR coming 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. feature name=Console param name=id value=org.apache.cordova.core.console / param name=version value=0.2.8 / /feature 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] [Updated] (CB-5650) make visible the version of the Cordova native lib
[ https://issues.apache.org/jira/browse/CB-5650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Kinard updated CB-5650: -- Assignee: Martin Gonzalez (was: Marcel Kinard) make visible the version of the Cordova native lib -- Key: CB-5650 URL: https://issues.apache.org/jira/browse/CB-5650 Project: Apache Cordova Issue Type: Improvement Components: Android, BlackBerry, iOS, Ubuntu, WP8 Reporter: Marcel Kinard Assignee: Martin Gonzalez Priority: Minor We recently had a situation where a consumer had mismatched the runtime: one version of cordova.js and another version of the Cordova native code. The consumer gave us their compiled app, so we didn't have access to the native's source in the project. We had an idea that it would be nice if the native code compiled in some marker so we could tell what version it was without the source. Perhaps issue a log on startup saying Greetings from Cordova native code 3.2.0, or have something compiled in that would appear in strings cordova.jar | grep version. See some discussion at http://markmail.org/thread/m4h4csvcq4cs3dcr -- 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-tabpanelfocusedCommentId=13997710#comment-13997710 ] Gorkem ERCAN commented on CB-6469: -- New PRs created for cordova-lib and cordova-cli https://github.com/apache/cordova-lib/pull/6 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. feature name=Console param name=id value=org.apache.cordova.core.console / param name=version value=0.2.8 / /feature 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] [Resolved] (CB-6590) [Release + 3.5.0] Branch Test Tag RC1 for BlackBerry
[ https://issues.apache.org/jira/browse/CB-6590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Gill resolved CB-6590. Resolution: Fixed I tagged it 3.5.0. Please review to make sure it works [Release + 3.5.0] Branch Test Tag RC1 for BlackBerry Key: CB-6590 URL: https://issues.apache.org/jira/browse/CB-6590 Project: Apache Cordova Issue Type: Sub-task Components: BlackBerry Reporter: Steve Gill Assignee: Bryan Higgins 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] [Commented] (CB-2606) Add support for icon elements in config.xml
[
https://issues.apache.org/jira/browse/CB-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13992754#comment-13992754
]
ASF GitHub Bot commented on CB-2606:
Github user cmarcelk commented on the pull request:
https://github.com/apache/cordova-docs/pull/201#issuecomment-42548695
Looks like the code for these docs has already been merged in. Bryan /
Sergey, is there anything remaining here before doing a merge?
Add support for icon elements in config.xml
-
Key: CB-2606
URL: https://issues.apache.org/jira/browse/CB-2606
Project: Apache Cordova
Issue Type: Wish
Components: Docs
Reporter: Filip Maj
Assignee: Mark Koudritsky
This feature would add support for specifying the application icon by
changing values inside the {{config.xml}} document.
Relevant details for Cordova:
- {{icon}} elements _may_ have {{width}} and {{height}} attributes
representing the preferred size of the icon in CSS pixels.
- {{icon}} elements _must_ have a {{src}} attribute, which contains a path
string relative to the {{www/}} folder (or equivalent) in the platform.
See [the Widget Spec's section on
icons|http://www.w3.org/TR/widgets/#the-icon-element-and-its-attributes] for
specifics.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Assigned] (CB-4519) batterylow and batterycritical may never happen because of exact level check
[
https://issues.apache.org/jira/browse/CB-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse MacFadyen reassigned CB-4519:
---
Assignee: Jesse MacFadyen (was: Mike Billau)
batterylow and batterycritical may never happen because of exact level
check
Key: CB-4519
URL: https://issues.apache.org/jira/browse/CB-4519
Project: Apache Cordova
Issue Type: Bug
Components: CordovaJS, Plugin Battery Status
Affects Versions: 2.9.0
Reporter: Peter
Assignee: Jesse MacFadyen
The battery JavaScript code fires events when charge reaches some threshold
percentages 20 and 5:
{code}
if (level === 20 || level === 5) {
if (level === 20) {
cordova.fireWindowEvent(batterylow, info);
}
else {
cordova.fireWindowEvent(batterycritical, info);
}
}
{code}
But this logic makes an assumption that the level will at some point be
*exactly* 20 or 5. It is not a valid assumption. AFAIK there is no guarantee
that the device reports absolutely every percentage point 0-100, so if by bad
luck the device reports levels 25,22,19,16... then clearly level===20 was
missed so in this scenario the batterylow event the user was expecting is
simply not going to happen.
Ref
http://stackoverflow.com/questions/10189218/detect-changing-battery-state-at-every-percentage-in-android
IMO the code should be checking when the previous lvel versus current level
has crossed over the threshold, rather checking the current level is exactly
equal to the threshold value.
--
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-tabpanelfocusedCommentId=13997972#comment-13997972 ] ASF GitHub Bot commented on CB-6469: Github user gorkem commented on the pull request: https://github.com/apache/cordova-cli/pull/176#issuecomment-43131037 I am not %100 sure about how the experimental works but here is my shot 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. feature name=Console param name=id value=org.apache.cordova.core.console / param name=version value=0.2.8 / /feature 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] [Commented] (CB-6669) createmobilespec.js doesn't work with the blackberry10 option
[
https://issues.apache.org/jira/browse/CB-6669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13994222#comment-13994222
]
ASF GitHub Bot commented on CB-6669:
GitHub user BBosman opened a pull request:
https://github.com/apache/cordova-mobile-spec/pull/63
CB-6669 Fix blackberry10 path
The blackberry10 code doesn't reside in the root of the blackberry
respository, as is the case with the other platform repositories.
This commit adds the required blackberry10 subdirectory to the config.json
written by createmobilespec.js
Output after calling
```
cordova-mobile-spec\createmobilespec\createmobilespec.js --blackberry10
```
```
Creating project. If you have any errors, it may be from missing
repositories.
To clone needed repositories (android as an example):
./cordova-coho/coho repo-clone -r plugins -r mobile-spec -r android -r cli
To update all repositories:
./cordova-coho/coho repo-update
Creating project mobilespec...
Creating a new cordova project with name MobileSpec_Tests and id
org.apache.cordova.mobilespec at location C:\GitHub\mobilespec
Using custom www assets from C:\GitHub\cordova-mobile-spec
C:\GitHub\mobilespec C:\GitHub
Adding platforms...
Adding Platform: blackberry10
Checking if platform blackberry10 passes minimum requirements...
Requirements check failed: blackberry-nativepackager cannot be found on the
path. Aborting.```
```
I don't have the blackberry10 toolset installed, so check_req fails, but
check_req is now at least invoked. :)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/BBosman/cordova-mobile-spec CB-6669
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cordova-mobile-spec/pull/63.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 #63
commit 12c29a5e4f6af1a5703f511aea159620603d0ad1
Author: Bas Bosman git...@nazgul.nu
Date: 2014-05-10T11:59:41Z
Fix path
createmobilespec.js doesn't work with the blackberry10 option
-
Key: CB-6669
URL: https://issues.apache.org/jira/browse/CB-6669
Project: Apache Cordova
Issue Type: Bug
Components: mobile-spec
Reporter: Shazron Abdullah
Assignee: Bas Bosman
In the root folder of all my repos:
{code}
./cordova-mobile-spec/createmobilespec/createmobilespec.js --blackberry10
{code}
I get this error:
{code}
Creating project. If you have any errors, it may be from missing repositories.
To clone needed repositories (android as an example):
./cordova-coho/coho repo-clone -r plugins -r mobile-spec -r android -r cli
To update all repositories:
./cordova-coho/coho repo-update
Creating project mobilespec...
Creating a new cordova project with name MobileSpec_Tests and id
org.apache.cordova.mobilespec at location
/Users/shaz/Documents/Git/Apache/mobilespec
Using custom www assets from
/Users/shaz/Documents/Git/Apache/cordova-mobile-spec
/Users/shaz/Documents/Git/Apache/mobilespec /Users/shaz/Documents/Git/Apache
Adding platforms...
Adding Platform: blackberry10
Checking if platform blackberry10 passes minimum requirements...
Requirements check failed: /bin/sh:
/Users/shaz/Documents/Git/Apache/cordova-blackberry/bin/check_reqs: No such
file or directory
{code}
Note here that check_reqs should be in
`Users/shaz/Documents/Git/Apache/cordova-blackberry/*blackberry10*/bin/check_reqs`
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Resolved] (CB-6548) getCurrentPosition returns last known position when the Location services are turned off in Android (KITKAT) V4.4.2
[ https://issues.apache.org/jira/browse/CB-6548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser resolved CB-6548. Resolution: Won't Fix We use the default browser's Geolocation implementation. This is a WebView bug, not an issue with any of the code we currently maintain. getCurrentPosition returns last known position when the Location services are turned off in Android (KITKAT) V4.4.2 --- Key: CB-6548 URL: https://issues.apache.org/jira/browse/CB-6548 Project: Apache Cordova Issue Type: Bug Components: Android, Plugin Geolocation Affects Versions: 2.9.0 Environment: Android 4.4.2 Reporter: Mandeep Pasbola Labels: Android4.4.x, geolocation, getCurrentPosition I am developing a Cordova App and facing an issue in Android V4.4.2 (KITKAT ). geolocation.getCurrentPosition method returns a position even if the Location services are turned off in settings and position returned is the last known position. Options : maximumAge: 0, timeout: 6, enableHighAccuracy: false Method throws Access Denied error in previous versions of android which is correct. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6669) createmobilespec.js doesn't work with the blackberry10 option
[
https://issues.apache.org/jira/browse/CB-6669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13995482#comment-13995482
]
ASF GitHub Bot commented on CB-6669:
Github user BBosman closed the pull request at:
https://github.com/apache/cordova-mobile-spec/pull/63
createmobilespec.js doesn't work with the blackberry10 option
-
Key: CB-6669
URL: https://issues.apache.org/jira/browse/CB-6669
Project: Apache Cordova
Issue Type: Bug
Components: mobile-spec
Reporter: Shazron Abdullah
Assignee: Bas Bosman
In the root folder of all my repos:
{code}
./cordova-mobile-spec/createmobilespec/createmobilespec.js --blackberry10
{code}
I get this error:
{code}
Creating project. If you have any errors, it may be from missing repositories.
To clone needed repositories (android as an example):
./cordova-coho/coho repo-clone -r plugins -r mobile-spec -r android -r cli
To update all repositories:
./cordova-coho/coho repo-update
Creating project mobilespec...
Creating a new cordova project with name MobileSpec_Tests and id
org.apache.cordova.mobilespec at location
/Users/shaz/Documents/Git/Apache/mobilespec
Using custom www assets from
/Users/shaz/Documents/Git/Apache/cordova-mobile-spec
/Users/shaz/Documents/Git/Apache/mobilespec /Users/shaz/Documents/Git/Apache
Adding platforms...
Adding Platform: blackberry10
Checking if platform blackberry10 passes minimum requirements...
Requirements check failed: /bin/sh:
/Users/shaz/Documents/Git/Apache/cordova-blackberry/bin/check_reqs: No such
file or directory
{code}
Note here that check_reqs should be in
`Users/shaz/Documents/Git/Apache/cordova-blackberry/*blackberry10*/bin/check_reqs`
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CB-6684) [3.5.0rc][Windows8] Splash screen setting breaks the build
[ https://issues.apache.org/jira/browse/CB-6684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13997022#comment-13997022 ] ASF subversion and git services commented on CB-6684: - Commit d3dd1803aa7d8474aadbcb850ed0a572d23bb71a in cordova-windows's branch refs/heads/3.5.x from sgrebnov [ https://git-wip-us.apache.org/repos/asf?p=cordova-windows.git;h=d3dd180 ] CB-6684 [3.5.0rc][Windows8] Splash screen setting breaks the build [3.5.0rc][Windows8] Splash screen setting breaks the build -- Key: CB-6684 URL: https://issues.apache.org/jira/browse/CB-6684 Project: Apache Cordova Issue Type: Bug Components: Windows 8 Reporter: Sergey Grebnov Assignee: Jesse MacFadyen Add dummy splash screen settings to config.xml preference name=SplashScreen value=screen / Run build C:\temp\_rc3_5_0\app λ cordova build windows8 Running command: C:\temp\_rc3_5_0\app\platforms\windows8\cordova\build.bat Building Cordova Windows 8 Project: Configuration : Debug Directory : C:\temp\_rc3_5_0\app\platforms\windows8 MSBuildToolsPath: C:\Program Files (x86)\MSBuild\12.0\bin\ cmd /c C:\Program Files (x86)\MSBuild\12.0\bin\msbuild C:\temp\_rc3_5_0\app\platforms\windows8\CordovaApp.sln /clp:NoSummary;NoItemAndPropertyList;Verbosity=minimal /nologo /p:Configuration=Debug Building the projects in this solution one at a time. To enable parallel build, please add the /m switch. Applying Platform Config ... Setting SplashScreen = screen package.appxmanifest(20,31): error APPX1617: App manifest references the splash screen image 'screen' which has an unsupported extension. Extension must be JPG, JPEG, or PNG. [C:\temp\_rc3_5_0\app\platforms\windows8\CordovaApp.jsproj] Error: C:\temp\_rc3_5_0\app\platforms\windows8\cordova\build.bat: Command failed with exit code 2 at ChildProcess.whenDone (C:\Users\Sergei\AppData\Roaming\npm\node_modules\cordova\node_modules\cordova-lib\src\cordova\superspawn.js:131:23) at ChildProcess.EventEmitter.emit (events.js:98:17) at maybeClose (child_process.js:743:16) at Process.ChildProcess._handle.onexit (child_process.js:810:5) We should check that file exists and if not then echo warning message instead of fail -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CB-6669) createmobilespec.js doesn't work with the blackberry10 option
[
https://issues.apache.org/jira/browse/CB-6669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bas Bosman resolved CB-6669.
Resolution: Fixed
Fixed by a commit on CB-6415 according to bryanhiggins.
createmobilespec.js doesn't work with the blackberry10 option
-
Key: CB-6669
URL: https://issues.apache.org/jira/browse/CB-6669
Project: Apache Cordova
Issue Type: Bug
Components: mobile-spec
Reporter: Shazron Abdullah
Assignee: Bas Bosman
In the root folder of all my repos:
{code}
./cordova-mobile-spec/createmobilespec/createmobilespec.js --blackberry10
{code}
I get this error:
{code}
Creating project. If you have any errors, it may be from missing repositories.
To clone needed repositories (android as an example):
./cordova-coho/coho repo-clone -r plugins -r mobile-spec -r android -r cli
To update all repositories:
./cordova-coho/coho repo-update
Creating project mobilespec...
Creating a new cordova project with name MobileSpec_Tests and id
org.apache.cordova.mobilespec at location
/Users/shaz/Documents/Git/Apache/mobilespec
Using custom www assets from
/Users/shaz/Documents/Git/Apache/cordova-mobile-spec
/Users/shaz/Documents/Git/Apache/mobilespec /Users/shaz/Documents/Git/Apache
Adding platforms...
Adding Platform: blackberry10
Checking if platform blackberry10 passes minimum requirements...
Requirements check failed: /bin/sh:
/Users/shaz/Documents/Git/Apache/cordova-blackberry/bin/check_reqs: No such
file or directory
{code}
Note here that check_reqs should be in
`Users/shaz/Documents/Git/Apache/cordova-blackberry/*blackberry10*/bin/check_reqs`
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Assigned] (CB-6596) [Release + 3.5.0] Branch Tag RC1 of cordova-cli
[ https://issues.apache.org/jira/browse/CB-6596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Gill reassigned CB-6596: -- Assignee: Steve Gill [Release + 3.5.0] Branch Tag RC1 of cordova-cli - Key: CB-6596 URL: https://issues.apache.org/jira/browse/CB-6596 Project: Apache Cordova Issue Type: Sub-task Components: CLI 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] [Assigned] (CB-6669) createmobilespec.js doesn't work with the blackberry10 option
[
https://issues.apache.org/jira/browse/CB-6669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bas Bosman reassigned CB-6669:
--
Assignee: Bas Bosman
createmobilespec.js doesn't work with the blackberry10 option
-
Key: CB-6669
URL: https://issues.apache.org/jira/browse/CB-6669
Project: Apache Cordova
Issue Type: Bug
Components: mobile-spec
Reporter: Shazron Abdullah
Assignee: Bas Bosman
In the root folder of all my repos:
{code}
./cordova-mobile-spec/createmobilespec/createmobilespec.js --blackberry10
{code}
I get this error:
{code}
Creating project. If you have any errors, it may be from missing repositories.
To clone needed repositories (android as an example):
./cordova-coho/coho repo-clone -r plugins -r mobile-spec -r android -r cli
To update all repositories:
./cordova-coho/coho repo-update
Creating project mobilespec...
Creating a new cordova project with name MobileSpec_Tests and id
org.apache.cordova.mobilespec at location
/Users/shaz/Documents/Git/Apache/mobilespec
Using custom www assets from
/Users/shaz/Documents/Git/Apache/cordova-mobile-spec
/Users/shaz/Documents/Git/Apache/mobilespec /Users/shaz/Documents/Git/Apache
Adding platforms...
Adding Platform: blackberry10
Checking if platform blackberry10 passes minimum requirements...
Requirements check failed: /bin/sh:
/Users/shaz/Documents/Git/Apache/cordova-blackberry/bin/check_reqs: No such
file or directory
{code}
Note here that check_reqs should be in
`Users/shaz/Documents/Git/Apache/cordova-blackberry/*blackberry10*/bin/check_reqs`
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CB-6644) [amazon-fireos]Add a check for webview being null in template code
[ https://issues.apache.org/jira/browse/CB-6644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13993075#comment-13993075 ] ASF subversion and git services commented on CB-6644: - Commit 0ae3c2dc5ffa84ca8bb881c0144b976886179465 in cordova-amazon-fireos's branch refs/heads/master from [~naika] [ https://git-wip-us.apache.org/repos/asf?p=cordova-amazon-fireos.git;h=0ae3c2d ] [CB-6644][amazon-fireos]Add a check for webview being null in template code Added a check and some comments to guide devs. [amazon-fireos]Add a check for webview being null in template code -- Key: CB-6644 URL: https://issues.apache.org/jira/browse/CB-6644 Project: Apache Cordova Issue Type: Bug Components: Amazon FireOS Affects Versions: 3.4.0 Reporter: Archana Naik Assignee: Archana Naik Fix For: 3.5.0 amazon-fireos uses AmazonWebView which provides chromium based webapp runtime. Port needs webview sdk which ships with 2 different jars - awv_interface.jar and awv_android_factory.jar. By default, adding amazon-fireos platform to the app copies awv_interface.jar to project's libs folder so its bundled with the app. However, that means app will work on Kindle fire devices but on generic android devices it will not. In order for it to work on android devices, app developer needs to copy awv_android_factory.jar to libs folder so app will automatically use fallback mechanism to instantiate stock android webview. Now, in case of no fallback mechanism CordovaActivity's appview will be null so if developer uses this.appview in onCreate() method app will crash. Solution: add boilder plate code to check for this.appview not being null. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6691) cordova plugin rm of depended plugin stops with warning, but then prints stack trace anyway
[ https://issues.apache.org/jira/browse/CB-6691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13997651#comment-13997651 ] ASF subversion and git services commented on CB-6691: - Commit 6f4022bd88b5fc2deca96121a0278c0c72f89e3f in cordova-lib's branch refs/heads/master from [~kamrik] [ https://git-wip-us.apache.org/repos/asf?p=cordova-lib.git;h=6f4022b ] CB-6691: Change some instances of Error() to CordovaError() Full stack is printed out when Error is thrown, but only the message for CordovaError. Left it as Error in several paces I wasn't sure about. cordova plugin rm of depended plugin stops with warning, but then prints stack trace anyway --- Key: CB-6691 URL: https://issues.apache.org/jira/browse/CB-6691 Project: Apache Cordova Issue Type: Bug Components: CLI, Plugman Reporter: Michal Mocny Assignee: Mark Koudritsky Priority: Minor cordova plugin rm [any plugin that is dependency of another installed plugin] E.g.: Error: The plugin 'com.google.playservices' is required by (org.chromium.identity, org.chromium.syncFileSystem), skipping uninstallation. at runUninstallPlatform (/Users/mmocny/dev/cordova/cordova-lib/cordova-lib/src/plugman/uninstall.js:183:30) at Function.module.exports.uninstallPlatform (/Users/mmocny/dev/cordova/cordova-lib/cordova-lib/src/plugman/uninstall.js:55:12) at /Users/mmocny/dev/cordova/cordova-lib/cordova-lib/src/cordova/plugin.js:188:58 at _fulfilled (/Users/mmocny/dev/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:798:54) at self.promiseDispatch.done (/Users/mmocny/dev/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:827:30) at Promise.promise.promiseDispatch (/Users/mmocny/dev/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:760:13) at /Users/mmocny/dev/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:821:14 at flush (/Users/mmocny/dev/cordova/cordova-lib/cordova-lib/node_modules/q/q.js:108:17) at process._tickCallback (node.js:339:11) at Function.Module.runMain (module.js:492:11) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Comment Edited] (CB-5650) make visible the version of the Cordova native lib
[
https://issues.apache.org/jira/browse/CB-5650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13997636#comment-13997636
]
Marcel Kinard edited comment on CB-5650 at 5/14/14 3:22 PM:
I would suggest the following output string:
{code}
Apache Cordova native platform version X.Y.Z is starting.
{code}
was (Author: cmarcelk):
I would suggest the following output string:
{code}
Apache Cordova native platform version %s is starting.
{code}
make visible the version of the Cordova native lib
--
Key: CB-5650
URL: https://issues.apache.org/jira/browse/CB-5650
Project: Apache Cordova
Issue Type: Improvement
Components: Android, BlackBerry, iOS, Ubuntu, WP8
Reporter: Marcel Kinard
Assignee: Marcel Kinard
Priority: Minor
We recently had a situation where a consumer had mismatched the runtime: one
version of cordova.js and another version of the Cordova native code. The
consumer gave us their compiled app, so we didn't have access to the native's
source in the project. We had an idea that it would be nice if the native
code compiled in some marker so we could tell what version it was without the
source. Perhaps issue a log on startup saying Greetings from Cordova native
code 3.2.0, or have something compiled in that would appear in strings
cordova.jar | grep version.
See some discussion at http://markmail.org/thread/m4h4csvcq4cs3dcr
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CB-6654) cordova run wp8 freezes after application starts and until app is closed.
[ https://issues.apache.org/jira/browse/CB-6654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13992590#comment-13992590 ] ASF GitHub Bot commented on CB-6654: GitHub user vladimir-kotikov opened a pull request: https://github.com/apache/cordova-wp8/pull/32 Remove inconsistency of `cordova run` behaviour between WP8 and other platforms. Adds '-wait' flag to CordovaDeploy. Also removes unnecessary Program class. This is PR for [CB-6654](https://issues.apache.org/jira/browse/CB-6654) You can merge this pull request into a Git repository by running: $ git pull https://github.com/MSOpenTech/cordova-wp8 CB-6654 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-wp8/pull/32.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 #32 commit 0e7f7df7b9c0e4b38fe71139a3ea7265c28c0fae Author: Vladimir Kotikov v-vlk...@microsoft.com Date: 2014-05-08T07:50:48Z Adds'-wait' flag to CordovaDeploy. Removes unnecessary Program class. cordova run wp8 freezes after application starts and until app is closed. - Key: CB-6654 URL: https://issues.apache.org/jira/browse/CB-6654 Project: Apache Cordova Issue Type: Bug Components: CLI, WP8 Reporter: Vladimir Kotikov Assignee: Jesse MacFadyen Repro steps: 1. create new cordova app 2. add wp8 platform to app created 3. start application from CLI (cordova emulate/run) On all platforms except wp8 this causes application to start in emulator/device and then then deploy script exits. On wp8 deploy script freezes, until application is closed, and only then exit. This is inconsistent across platforms and may be confusing to developers. This is because of CB-802, which is still not resolved. I propose to hide this behaviour behind '--wait' flag of Cordova Deploy, and make this behaviour default when all (or most important) platform will support it. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CB-6654) cordova run wp8 freezes after application starts and until app is closed.
[ https://issues.apache.org/jira/browse/CB-6654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Kotikov updated CB-6654: - Summary: cordova run wp8 freezes after application starts and until app is closed. (was: cordova run wp8 tries to pass app console log events to dev console.) cordova run wp8 freezes after application starts and until app is closed. - Key: CB-6654 URL: https://issues.apache.org/jira/browse/CB-6654 Project: Apache Cordova Issue Type: Bug Components: CLI, WP8 Reporter: Vladimir Kotikov Assignee: Jesse MacFadyen Repro steps: 1. create new cordova app 2. add wp8 platform to app created 3. start application from CLI (cordova emulate/run) On all platforms except wp8 this causes application to start in emulator/device and then then deploy script exits. On wp8 deploy script freezes, until application is closed, and only then exit. This is inconsistent across platforms and may be confusing to developers. This is because of CB-802, which is still not resolved. I propose to hide this behaviour behind '--wait' flag of Cordova Deploy, and make this behaviour default when all (or most important) platform will support it. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CB-6629) App crashed with file function
[
https://issues.apache.org/jira/browse/CB-6629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ian Clelland reassigned CB-6629:
Assignee: Ian Clelland
App crashed with file function
--
Key: CB-6629
URL: https://issues.apache.org/jira/browse/CB-6629
Project: Apache Cordova
Issue Type: Bug
Components: Plugin File
Affects Versions: 3.4.0
Environment: Android
Reporter: alpg 78
Assignee: Ian Clelland
Priority: Blocker
When i try to use this code :
{code}
window.requestFileSystem = window.requestFileSystem ||
window.webkitRequestFileSystem;
window.LocalFileSystem = window.LocalFileSystem || {PERSISTENT:
window.PERSISTENT};
window.requestFileSystem(LocalFileSystem.PERSISTENT, 0, gotFS, fail);
function gotFS(fileSystem) {
fileSystem.root.getDirectory(DO_NOT_DELETE,
{create: true, exclusive: false},
gotDirEntry,
fail);
}
function gotDirEntry(dirEntry) {
dir = dirEntry;
dirEntry.getFile(sample.json,
{create: false, exclusive: false},
readSuccess,
fileDonotexist);
}
function fileDonotexist(dirEntry) {
dir.getFile(sample.json,
{create: true, exclusive: false},
gotFileEntry,
fail);
}
function gotFileEntry(fileEntryWrite) {
fileEntryWrite.createWriter(gotFileWriter, fail);
}
function gotFileWriter(writer) {
writer.onerror = function(evt) {
};
writer.write(localData);
writer.onwriteend = function(evt) {
dir.getFile(sample.json,
{create: false, exclusive: false},
readSuccess,
fail);
};
}
function readSuccess(fileE) {
fileE.file(readAsText, fail);
}
function fail(error) {
alert(fail);
}
function readAsText(readerDummy) {
var reader = new FileReader();
reader.onloadstart = function(evt) {};
reader.onprogress = function(evt) {};
reader.onerror = function(evt) {};
reader.onloadend = function(evt) {
console.log(read success);
};
reader.readAsText(readerDummy);
}
{code}
my app crashed and she is turning off. what's wrong ?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CB-6366) Automate Downloading the Amazon WebView SDK from the Amazon Developer Portal.
[ https://issues.apache.org/jira/browse/CB-6366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13994040#comment-13994040 ] Steve Gill commented on CB-6366: [~naika] This would be a big win! :) Automate Downloading the Amazon WebView SDK from the Amazon Developer Portal. - Key: CB-6366 URL: https://issues.apache.org/jira/browse/CB-6366 Project: Apache Cordova Issue Type: Bug Components: Amazon FireOS Reporter: Steve Gill Assignee: Archana Naik It would be nice if this was an automated step instead of manual! -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CB-6661) Web Platform Target
Daniel created CB-6661: -- Summary: Web Platform Target Key: CB-6661 URL: https://issues.apache.org/jira/browse/CB-6661 Project: Apache Cordova Issue Type: Improvement Components: CordovaJS Affects Versions: 3.4.0 Environment: All Reporter: Daniel Priority: Minor Fix For: 3.4.0 I have not been able to find built in functionality for cordova to deploy an app to a server platform. This purpose of this new platform is to allow an HTML5 application within a Cordova project to be deployed on a web server, available for access over standard internet protocols. My team and I will be actively working this at https://github.com/CollinearGroup/cordova-js We intend to build this functionality with a nodejs server but hope that we can provide the server with varying backends like Grails and Rails. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CB-6696) Set flash mode for capture video plugin
Max Franz created CB-6696: - Summary: Set flash mode for capture video plugin Key: CB-6696 URL: https://issues.apache.org/jira/browse/CB-6696 Project: Apache Cordova Issue Type: Improvement Components: Plugin Media Capture Reporter: Max Franz The capture video plugin is great, but there are usecases where the default option for the camera flash mode does not suffice. A lot of the time, the user would prefer the flash be off unless manually set otherwise. An option to set the flash mode would be great (right now, I have to patch the plugin for all platforms manually). The following enums would be required: * flash on * flash off * flash auto e.g. for iphone see https://developer.apple.com/library/ios/documentation/uikit/reference/UIImagePickerController_Class/UIImagePickerController/UIImagePickerController.html#//apple_ref/occ/instp/UIImagePickerController/cameraFlashMode As an alternative: If having an option to expose this is not preferable, it's also possible * to change the default from flash auto to flash off, or * to start by default with flash off and save the value the user set last in the app. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CB-6682) File transfer tests need bb10 specific whitelisting applied
Bryan Higgins created CB-6682: - Summary: File transfer tests need bb10 specific whitelisting applied Key: CB-6682 URL: https://issues.apache.org/jira/browse/CB-6682 Project: Apache Cordova Issue Type: Bug Components: BlackBerry, mobile-spec Reporter: Bryan Higgins BB10 doesn't respect *.domain.com whitelisting Mobile-spec needs the following elements to work properly: access origin=file:/// / access origin=https://www.apache.org; / access origin=http://cordova.apache.org; / access origin=http://foobar.apache.org; / access origin=http://www.apache.org; / I'm going to wrap these in a platform tag. -- This message was sent by Atlassian JIRA (v6.2#6252)
