[jira] [Created] (CB-6239) splash screen issue with Phonegap in BlackBerry 10 devices
uday created CB-6239: Summary: splash screen issue with Phonegap in BlackBerry 10 devices Key: CB-6239 URL: https://issues.apache.org/jira/browse/CB-6239 Project: Apache Cordova Issue Type: Bug Components: BlackBerry, CordovaJS Affects Versions: 2.7.0 Environment: Phone gap in BlackBerry 10 Reporter: uday Hi all, This is Uday Vallabhaneni,i am working on BlackBerry 10 mobile applications through phonegap.while doing this i'm getting the splash screen problem for BB10.I tried all things which are available in Phonegap official site as weel as BlackBerry official site but i'm not getting the splash screen for blackberry 10 devices.Please Help me regarding this issue as soon as possible. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-5816) FirefoxOS - add build script
[ https://issues.apache.org/jira/browse/CB-5816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13932970#comment-13932970 ] ASF GitHub Bot commented on CB-5816: Github user Steckelfisch commented on the pull request: https://github.com/apache/cordova-firefoxos/pull/7#issuecomment-37507856 so build --debug (as the default) is what this pullrequest provides build --create builds a zip. should the --create option be filed under a new issue? or add it in this one? > FirefoxOS - add build script > > > Key: CB-5816 > URL: https://issues.apache.org/jira/browse/CB-5816 > Project: Apache Cordova > Issue Type: Bug > Components: FirefoxOS >Reporter: Axel Nennker > > run: cordova build firefoxos > output: > Generating config.xml from defaults for platform "firefoxos" > Preparing firefoxos project > Compiling app on platform "firefoxos" via command > "/project/platforms/firefoxos/cordova/build" > events.js:72 > throw er; // Unhandled 'error' event > ^ > Error: spawn ENOENT > at errnoException (child_process.js:980:11) > at Process.ChildProcess._handle.onexit (child_process.js:771:34) > project$ > expected output: > nothing > - > platforms/firefoxos/cordova/build does not exist so the "cordova build > firefoxos" command fails. > Please add a "build" script (although it does nothing) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-5520) Should we add "DEBUG=1" to "Preprocessor Macros"->"Debug" ?
[
https://issues.apache.org/jira/browse/CB-5520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13933196#comment-13933196
]
Alan Rahlf commented on CB-5520:
I'm also running into this issue. I found that this was broken + fixed in an
older version (https://issues.apache.org/jira/browse/CB-253) as well.
> Should we add "DEBUG=1" to "Preprocessor Macros"->"Debug" ?
> ---
>
> Key: CB-5520
> URL: https://issues.apache.org/jira/browse/CB-5520
> Project: Apache Cordova
> Issue Type: Wish
> Components: iOS
>Affects Versions: 3.2.0
>Reporter: glmnbeyond
>Priority: Minor
>
> I created a helloCordova project via Cordova CLI, and added some debug info
> to native code:
> DLog('This is a debug info');
> But the debug info is never outputted.If I use ALog, the info can be
> outputted, so I think it probably has something to do with the "DEBUG" macro.
> After I added "DEBUG=1" to "Preprocessor Macros", ran the helloCordova
> target, DLog can be outputted.
> So here is my question:
> Should we add "DEBUG=1" to iOS template project->"Build Settings"->
> "Preprocessor Macros" ->"Debug" ?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Resolved] (CB-2419) On Windows 8, Camera.getPicture does not return file URI
[
https://issues.apache.org/jira/browse/CB-2419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Grebnov resolved CB-2419.
Resolution: Fixed
> On Windows 8, Camera.getPicture does not return file URI
>
>
> Key: CB-2419
> URL: https://issues.apache.org/jira/browse/CB-2419
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin Camera, Windows 8
>Affects Versions: 2.4.0
>Reporter: Youval Bronicki
>Assignee: Jesse MacFadyen
>
> The camera.getPicture method returns a blob: URI when a File URI is requested.
> I've been able to tweak it to my needs by changing:
> {{_imageUrl = URL.createObjectURL(storageFile);}}
> to:
> {{var _imageUrl = storageFile.path;}}
> However the result is not strictly speaking a FILE URI, so that may not be
> the preferred solution.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CB-2419) On Windows 8, Camera.getPicture does not return file URI
[
https://issues.apache.org/jira/browse/CB-2419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13933204#comment-13933204
]
Sergey Grebnov commented on CB-2419:
No repro on the current plugin version (also reviewed code, the issue has been
fixed).
File uri like 'ms-appdata:///local/picture004.jpg' is now passed to success
callback.
> On Windows 8, Camera.getPicture does not return file URI
>
>
> Key: CB-2419
> URL: https://issues.apache.org/jira/browse/CB-2419
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin Camera, Windows 8
>Affects Versions: 2.4.0
>Reporter: Youval Bronicki
>Assignee: Jesse MacFadyen
>
> The camera.getPicture method returns a blob: URI when a File URI is requested.
> I've been able to tweak it to my needs by changing:
> {{_imageUrl = URL.createObjectURL(storageFile);}}
> to:
> {{var _imageUrl = storageFile.path;}}
> However the result is not strictly speaking a FILE URI, so that may not be
> the preferred solution.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Resolved] (CB-5532) WP8. Add binary data support to FileWriter
[ https://issues.apache.org/jira/browse/CB-5532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Grebnov resolved CB-5532. Resolution: Fixed > WP8. Add binary data support to FileWriter > -- > > Key: CB-5532 > URL: https://issues.apache.org/jira/browse/CB-5532 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin File, WP8 >Reporter: Sergey Grebnov >Assignee: Jesse MacFadyen > > Could be tested/reproduced for example on the following mobile spec tests: > file.spec.104 should be able to write binary data from an ArrayBuffer > file.spec.105 should be able to write binary data from a Blob -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6016) capture.captureAudio is not supported on BlackBerry10
[ https://issues.apache.org/jira/browse/CB-6016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13933215#comment-13933215 ] ASF subversion and git services commented on CB-6016: - Commit bd6af454227a9c791acfdb70ea592a54c888ef98 in cordova-plugin-media-capture's branch refs/heads/dev from [~bhigg...@blackberry.com] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-media-capture.git;h=bd6af45 ] CB-6016 [BlackBerry10] Add audio capture capability > capture.captureAudio is not supported on BlackBerry10 > - > > Key: CB-6016 > URL: https://issues.apache.org/jira/browse/CB-6016 > Project: Apache Cordova > Issue Type: Bug > Components: BlackBerry >Affects Versions: 3.3.0 >Reporter: Doug Moscrop >Assignee: Bryan Higgins > > In a similar fashion to CB-117, captureAudio is stubbed out in the > media-capture plugin and simply always calls error with > NOT_SUPPORTED_ERROR_CODE. > I suspect this may be due to the API offerings from BlackBerry - however, > captureAudio is plainly listed as being supported on BlackBerry 10 in all > documentation and even goes as far as to claim it will attempt to launch the > voice note app and return the above error status if it is not installed. > Recording works if I repackage my Android APK (built via Cordova) to a BAR > and run it via the Android runtime on BB. > Sincere apologies if I've missed something. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CB-3777) Implement FileWriter.write(|) on Windows Phone
[ https://issues.apache.org/jira/browse/CB-3777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Grebnov resolved CB-3777. Resolution: Fixed Assignee: Jesse MacFadyen > Implement FileWriter.write(|) on Windows Phone > - > > Key: CB-3777 > URL: https://issues.apache.org/jira/browse/CB-3777 > Project: Apache Cordova > Issue Type: Sub-task > Components: Plugin File, Windows 8, WP7, WP8 >Reporter: Ian Clelland >Assignee: Jesse MacFadyen > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6208) Docs do not mention Git requirement for plugin adding
[ https://issues.apache.org/jira/browse/CB-6208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13933219#comment-13933219 ] ASF subversion and git services commented on CB-6208: - Commit 2c5fde6c910523082a38b0b3f038e4ba8e6f7bf1 in cordova-docs's branch refs/heads/master from [~cmarcelk] [ https://git-wip-us.apache.org/repos/asf?p=cordova-docs.git;h=2c5fde6 ] CB-6208 Add link to git downloads > Docs do not mention Git requirement for plugin adding > - > > Key: CB-6208 > URL: https://issues.apache.org/jira/browse/CB-6208 > Project: Apache Cordova > Issue Type: Bug > Components: Docs >Reporter: Raymond Camden >Priority: Minor > > Twice now I've run into people who have an issue adding a plugin because they > don't have Git installed. While the error is pretty clear, it is in the > middle of a bunch of other output and the docs should note that this is a > dependancy. To be fair, it isn't necessarily something you need to run a CLI, > but as soon as you add a plugin (which is pretty much *always* required now), > you run into it. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6208) Docs do not mention Git requirement for plugin adding
[ https://issues.apache.org/jira/browse/CB-6208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13933220#comment-13933220 ] Andrew Grieve commented on CB-6208: --- I think you only need git when you install a plugin from a git URL. Installing via the registry (by ID), does not require git. I don't think we should list git a strict dependency. npm works in the same way. > Docs do not mention Git requirement for plugin adding > - > > Key: CB-6208 > URL: https://issues.apache.org/jira/browse/CB-6208 > Project: Apache Cordova > Issue Type: Bug > Components: Docs >Reporter: Raymond Camden >Priority: Minor > > Twice now I've run into people who have an issue adding a plugin because they > don't have Git installed. While the error is pretty clear, it is in the > middle of a bunch of other output and the docs should note that this is a > dependancy. To be fair, it isn't necessarily something you need to run a CLI, > but as soon as you add a plugin (which is pretty much *always* required now), > you run into it. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6016) capture.captureAudio is not supported on BlackBerry10
[ https://issues.apache.org/jira/browse/CB-6016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13933225#comment-13933225 ] ASF GitHub Bot commented on CB-6016: Github user bryanhiggins closed the pull request at: https://github.com/apache/cordova-plugin-media-capture/pull/16 > capture.captureAudio is not supported on BlackBerry10 > - > > Key: CB-6016 > URL: https://issues.apache.org/jira/browse/CB-6016 > Project: Apache Cordova > Issue Type: Bug > Components: BlackBerry >Affects Versions: 3.3.0 >Reporter: Doug Moscrop >Assignee: Bryan Higgins > > In a similar fashion to CB-117, captureAudio is stubbed out in the > media-capture plugin and simply always calls error with > NOT_SUPPORTED_ERROR_CODE. > I suspect this may be due to the API offerings from BlackBerry - however, > captureAudio is plainly listed as being supported on BlackBerry 10 in all > documentation and even goes as far as to claim it will attempt to launch the > voice note app and return the above error status if it is not installed. > Recording works if I repackage my Android APK (built via Cordova) to a BAR > and run it via the Android runtime on BB. > Sincere apologies if I've missed something. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6016) capture.captureAudio is not supported on BlackBerry10
[ https://issues.apache.org/jira/browse/CB-6016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13933224#comment-13933224 ] ASF GitHub Bot commented on CB-6016: Github user bryanhiggins commented on the pull request: https://github.com/apache/cordova-plugin-media-capture/pull/16#issuecomment-37531680 https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-media-capture.git;h=bd6af45 > capture.captureAudio is not supported on BlackBerry10 > - > > Key: CB-6016 > URL: https://issues.apache.org/jira/browse/CB-6016 > Project: Apache Cordova > Issue Type: Bug > Components: BlackBerry >Affects Versions: 3.3.0 >Reporter: Doug Moscrop >Assignee: Bryan Higgins > > In a similar fashion to CB-117, captureAudio is stubbed out in the > media-capture plugin and simply always calls error with > NOT_SUPPORTED_ERROR_CODE. > I suspect this may be due to the API offerings from BlackBerry - however, > captureAudio is plainly listed as being supported on BlackBerry 10 in all > documentation and even goes as far as to claim it will attempt to launch the > voice note app and return the above error status if it is not installed. > Recording works if I repackage my Android APK (built via Cordova) to a BAR > and run it via the Android runtime on BB. > Sincere apologies if I've missed something. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6212) fix plugin warnings compiled under arm64 64-bit
[ https://issues.apache.org/jira/browse/CB-6212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13933233#comment-13933233 ] ASF subversion and git services commented on CB-6212: - Commit 0f84287df03e7372eebe1d8620f8a78bb4900b4e in cordova-plugin-file-transfer's branch refs/heads/dev from [~wjamesjong] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-file-transfer.git;h=0f84287 ] CB-6212 iOS: fix warnings compiled under arm64 64-bit > fix plugin warnings compiled under arm64 64-bit > --- > > Key: CB-6212 > URL: https://issues.apache.org/jira/browse/CB-6212 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Camera, Plugin Contacts, Plugin File, Plugin > Geolocation, Plugin InAppBrowser, Plugin Media, Plugin Media Capture >Reporter: James Jong >Assignee: James Jong >Priority: Minor > Fix For: 3.5.0 > > > Fix plugin warnings compiled under arm64 64-bit. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6212) fix plugin warnings compiled under arm64 64-bit
[ https://issues.apache.org/jira/browse/CB-6212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13933252#comment-13933252 ] ASF subversion and git services commented on CB-6212: - Commit 910f80fae8fe79eb8342bcd737b663c2d5f62d78 in cordova-plugin-contacts's branch refs/heads/dev from [~wjamesjong] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-contacts.git;h=910f80f ] CB-6212 iOS: fix warnings compiled under arm64 64-bit -for CDVContacts.m > fix plugin warnings compiled under arm64 64-bit > --- > > Key: CB-6212 > URL: https://issues.apache.org/jira/browse/CB-6212 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Camera, Plugin Contacts, Plugin File, Plugin > Geolocation, Plugin InAppBrowser, Plugin Media, Plugin Media Capture >Reporter: James Jong >Assignee: James Jong >Priority: Minor > Fix For: 3.5.0 > > > Fix plugin warnings compiled under arm64 64-bit. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (CB-6016) capture.captureAudio is not supported on BlackBerry10
[ https://issues.apache.org/jira/browse/CB-6016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Higgins closed CB-6016. - Resolution: Fixed > capture.captureAudio is not supported on BlackBerry10 > - > > Key: CB-6016 > URL: https://issues.apache.org/jira/browse/CB-6016 > Project: Apache Cordova > Issue Type: Bug > Components: BlackBerry >Affects Versions: 3.3.0 >Reporter: Doug Moscrop >Assignee: Bryan Higgins > > In a similar fashion to CB-117, captureAudio is stubbed out in the > media-capture plugin and simply always calls error with > NOT_SUPPORTED_ERROR_CODE. > I suspect this may be due to the API offerings from BlackBerry - however, > captureAudio is plainly listed as being supported on BlackBerry 10 in all > documentation and even goes as far as to claim it will attempt to launch the > voice note app and return the above error status if it is not installed. > Recording works if I repackage my Android APK (built via Cordova) to a BAR > and run it via the Android runtime on BB. > Sincere apologies if I've missed something. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6212) fix plugin warnings compiled under arm64 64-bit
[ https://issues.apache.org/jira/browse/CB-6212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13933258#comment-13933258 ] ASF subversion and git services commented on CB-6212: - Commit c9bab1f94c89e53c0ad8dbc77e1027eaa89527f1 in cordova-plugin-camera's branch refs/heads/dev from [~wjamesjong] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-camera.git;h=c9bab1f ] CB-6212 iOS: fix warnings compiled under arm64 64-bit > fix plugin warnings compiled under arm64 64-bit > --- > > Key: CB-6212 > URL: https://issues.apache.org/jira/browse/CB-6212 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Camera, Plugin Contacts, Plugin File, Plugin > Geolocation, Plugin InAppBrowser, Plugin Media, Plugin Media Capture >Reporter: James Jong >Assignee: James Jong >Priority: Minor > Fix For: 3.5.0 > > > Fix plugin warnings compiled under arm64 64-bit. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6212) fix plugin warnings compiled under arm64 64-bit
[ https://issues.apache.org/jira/browse/CB-6212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13933264#comment-13933264 ] ASF subversion and git services commented on CB-6212: - Commit 9c7d4442f4f74cba573cff8a65deeb4437f21840 in cordova-plugin-dialogs's branch refs/heads/dev from [~wjamesjong] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-dialogs.git;h=9c7d444 ] CB-6212 iOS: fix warnings compiled under arm64 64-bit > fix plugin warnings compiled under arm64 64-bit > --- > > Key: CB-6212 > URL: https://issues.apache.org/jira/browse/CB-6212 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Camera, Plugin Contacts, Plugin File, Plugin > Geolocation, Plugin InAppBrowser, Plugin Media, Plugin Media Capture >Reporter: James Jong >Assignee: James Jong >Priority: Minor > Fix For: 3.5.0 > > > Fix plugin warnings compiled under arm64 64-bit. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6212) fix plugin warnings compiled under arm64 64-bit
[ https://issues.apache.org/jira/browse/CB-6212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13933270#comment-13933270 ] ASF subversion and git services commented on CB-6212: - Commit d1b5e5bdebc954e149feecd745bdf9e4d5e2a668 in cordova-plugin-globalization's branch refs/heads/dev from [~wjamesjong] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-globalization.git;h=d1b5e5b ] CB-6212 iOS: fix warnings compiled under arm64 64-bit > fix plugin warnings compiled under arm64 64-bit > --- > > Key: CB-6212 > URL: https://issues.apache.org/jira/browse/CB-6212 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Camera, Plugin Contacts, Plugin File, Plugin > Geolocation, Plugin InAppBrowser, Plugin Media, Plugin Media Capture >Reporter: James Jong >Assignee: James Jong >Priority: Minor > Fix For: 3.5.0 > > > Fix plugin warnings compiled under arm64 64-bit. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6212) fix plugin warnings compiled under arm64 64-bit
[ https://issues.apache.org/jira/browse/CB-6212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13933292#comment-13933292 ] ASF subversion and git services commented on CB-6212: - Commit 91d6e10b29e492d8d72a2d5c759ebf7b876ecc3b in cordova-plugin-camera's branch refs/heads/dev from [~wjamesjong] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-camera.git;h=91d6e10 ] CB-6212 iOS: fix warnings compiled under arm64 64-bit -one update to CDVCamera.m > fix plugin warnings compiled under arm64 64-bit > --- > > Key: CB-6212 > URL: https://issues.apache.org/jira/browse/CB-6212 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Camera, Plugin Contacts, Plugin File, Plugin > Geolocation, Plugin InAppBrowser, Plugin Media, Plugin Media Capture >Reporter: James Jong >Assignee: James Jong >Priority: Minor > Fix For: 3.5.0 > > > Fix plugin warnings compiled under arm64 64-bit. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CB-6212) fix plugin warnings compiled under arm64 64-bit
[ https://issues.apache.org/jira/browse/CB-6212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Jong updated CB-6212: --- Component/s: Plugin Globalization Plugin File Transfer Plugin Dialogs > fix plugin warnings compiled under arm64 64-bit > --- > > Key: CB-6212 > URL: https://issues.apache.org/jira/browse/CB-6212 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Camera, Plugin Contacts, Plugin Dialogs, Plugin > File, Plugin File Transfer, Plugin Geolocation, Plugin Globalization, Plugin > InAppBrowser, Plugin Media, Plugin Media Capture >Reporter: James Jong >Assignee: James Jong >Priority: Minor > Fix For: 3.5.0 > > > Fix plugin warnings compiled under arm64 64-bit. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CB-6240) install-device and install-emulator don't work
Josh Soref created CB-6240: -- Summary: install-device and install-emulator don't work Key: CB-6240 URL: https://issues.apache.org/jira/browse/CB-6240 Project: Apache Cordova Issue Type: Bug Components: BlackBerry Affects Versions: 3.4.0 Reporter: Josh Soref Assignee: Josh Soref CB-5741 removed the uninstall method from runUtils -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CB-6241) Default to prompting for passwords (replace --query with --no-query)
Josh Soref created CB-6241: -- Summary: Default to prompting for passwords (replace --query with --no-query) Key: CB-6241 URL: https://issues.apache.org/jira/browse/CB-6241 Project: Apache Cordova Issue Type: Bug Components: BlackBerry Affects Versions: 3.4.0 Reporter: Josh Soref Assignee: Josh Soref BlackBerry 10 has supported prompting for passwords for a while using the --query flag, and we've used it for our end users. This behavior makes sense as a default, and more or less matches the behavior for Android. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6241) Default to prompting for passwords (replace --query with --no-query)
[ https://issues.apache.org/jira/browse/CB-6241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13933352#comment-13933352 ] ASF GitHub Bot commented on CB-6241: GitHub user jsoref opened a pull request: https://github.com/apache/cordova-blackberry/pull/150 CB-6241 Default to prompting for passwords (replace --query with --no-qu... ...ery) https://issues.apache.org/jira/browse/CB-6241 As a consequence, if you don't specify --no-query, and a password is needed, you will be prompted. If you have a build script which includes --query, the build will fail. You can merge this pull request into a Git repository by running: $ git pull https://github.com/jsoref/cordova-blackberry no-query Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-blackberry/pull/150.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 #150 commit fe441beb4b8adfe98b81e4a481aeadac27a4bf44 Author: Josh Soref Date: 2014-03-10T20:14:24Z CB-6241 Default to prompting for passwords (replace --query with --no-query) As a consequence, if you don't specify --no-query, and a password is needed, you will be prompted. If you have a build script which includes --query, the build will fail. > Default to prompting for passwords (replace --query with --no-query) > > > Key: CB-6241 > URL: https://issues.apache.org/jira/browse/CB-6241 > Project: Apache Cordova > Issue Type: Bug > Components: BlackBerry >Affects Versions: 3.4.0 >Reporter: Josh Soref >Assignee: Josh Soref > > BlackBerry 10 has supported prompting for passwords for a while using the > --query flag, and we've used it for our end users. > This behavior makes sense as a default, and more or less matches the behavior > for Android. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6241) Default to prompting for passwords (replace --query with --no-query)
[ https://issues.apache.org/jira/browse/CB-6241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13933354#comment-13933354 ] Josh Soref commented on CB-6241: https://github.com/apache/cordova-blackberry/pull/150 > Default to prompting for passwords (replace --query with --no-query) > > > Key: CB-6241 > URL: https://issues.apache.org/jira/browse/CB-6241 > Project: Apache Cordova > Issue Type: Bug > Components: BlackBerry >Affects Versions: 3.4.0 >Reporter: Josh Soref >Assignee: Josh Soref > > BlackBerry 10 has supported prompting for passwords for a while using the > --query flag, and we've used it for our end users. > This behavior makes sense as a default, and more or less matches the behavior > for Android. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CB-6242) [BlackBerry10] resolveLocalFileSystemURL not mapped correctly
Bryan Higgins created CB-6242: - Summary: [BlackBerry10] resolveLocalFileSystemURL not mapped correctly Key: CB-6242 URL: https://issues.apache.org/jira/browse/CB-6242 Project: Apache Cordova Issue Type: Bug Components: Plugin File Reporter: Bryan Higgins Assignee: Bryan Higgins resolveLocalFileSystemURI is working correctly, but this has been deprecated in favour of resolveLocalFileSystemURL -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CB-6237) Explicitly added plugin gets deleted as dependent of other plugin
[ https://issues.apache.org/jira/browse/CB-6237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Bond reassigned CB-6237: - Assignee: Jonathan Bond > Explicitly added plugin gets deleted as dependent of other plugin > - > > Key: CB-6237 > URL: https://issues.apache.org/jira/browse/CB-6237 > Project: Apache Cordova > Issue Type: Bug > Components: CLI >Affects Versions: 3.4.0 >Reporter: Jonathan Li >Assignee: Jonathan Bond > Fix For: 3.5.0 > > > On 3/12/14 12:58 PM, "Shazron" wrote: > Just tested it with File and File-Transfer - looks like a bug. Please file > it, thanks! > On Wed, Mar 12, 2014 at 7:46 AM, Li, Jonathan wrote: > When testing with cordova 3.4.0-0.1.3, if a plugin A is a dependent of > plugin B, then running the following command will automatically delete > plugin B from the project > cordova plugin add PluginB > cordova plugin add pluginA > cordova plugin rm pluginB > As pluginA is explicitly added into the project, unless it is explicated > removed from project by using "cordova plugin rm pluginA" command, then it > should not be deleted from the project when deleting pluginB. > The test is done on iOS platform. > Please let me know if this is a known issue, or whether I need to submit a > bug for it > Thanks > Jonathan -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CB-6237) Explicitly added plugin gets deleted as dependent of other plugin
[ https://issues.apache.org/jira/browse/CB-6237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Bond updated CB-6237: -- Description: On 3/12/14 12:58 PM, "Shazron" wrote: Just tested it with File and File-Transfer - looks like a bug. Please file it, thanks! On Wed, Mar 12, 2014 at 7:46 AM, Li, Jonathan wrote: When testing with cordova 3.4.0-0.1.3, if a plugin A is a dependent of plugin B, then running the following command will automatically delete plugin B from the project cordova plugin add PluginB cordova plugin add pluginA cordova plugin rm pluginB As pluginA is explicitly added into the project, unless it is explicated removed from project by using "cordova plugin rm pluginA" command, then it should not be deleted from the project when deleting pluginB. The test is done on iOS platform. Please let me know if this is a known issue, or whether I need to submit a bug for it Thanks Jonathan was: On 3/12/14 12:58 PM, "Shazron" wrote: Just tested it with File and File-Transfer - looks like a bug. Please file it, thanks! On Wed, Mar 12, 2014 at 7:46 AM, Li, Jonathan wrote: When testing with cordova 3.4.0-0.1.3, if a plugin A is a dependent of plugin B, then running the following command will automatically delete plugin B from the project cordova plugin add PluginB cordova plugin add pluginA cordova plugin rm pluginB As pluginA is explicitly added into the project, unless it is explicated removed from project by using "cordova plugin rm pluginA" command, then it should not be deleted from the project when deleting pluginB. The test is done on iOS platform. Please let me know if this is a known issue, or whether I need to submit a bug for it Thanks Jonathan Fix Version/s: 3.5.0 > Explicitly added plugin gets deleted as dependent of other plugin > - > > Key: CB-6237 > URL: https://issues.apache.org/jira/browse/CB-6237 > Project: Apache Cordova > Issue Type: Bug > Components: CLI >Affects Versions: 3.4.0 >Reporter: Jonathan Li >Assignee: Jonathan Bond > Fix For: 3.5.0 > > > On 3/12/14 12:58 PM, "Shazron" wrote: > Just tested it with File and File-Transfer - looks like a bug. Please file > it, thanks! > On Wed, Mar 12, 2014 at 7:46 AM, Li, Jonathan wrote: > When testing with cordova 3.4.0-0.1.3, if a plugin A is a dependent of > plugin B, then running the following command will automatically delete > plugin B from the project > cordova plugin add PluginB > cordova plugin add pluginA > cordova plugin rm pluginB > As pluginA is explicitly added into the project, unless it is explicated > removed from project by using "cordova plugin rm pluginA" command, then it > should not be deleted from the project when deleting pluginB. > The test is done on iOS platform. > Please let me know if this is a known issue, or whether I need to submit a > bug for it > Thanks > Jonathan -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6237) Explicitly added plugin gets deleted as dependent of other plugin
[ https://issues.apache.org/jira/browse/CB-6237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13933371#comment-13933371 ] Jonathan Bond commented on CB-6237: --- Already fixed in master but will double check. > Explicitly added plugin gets deleted as dependent of other plugin > - > > Key: CB-6237 > URL: https://issues.apache.org/jira/browse/CB-6237 > Project: Apache Cordova > Issue Type: Bug > Components: CLI >Affects Versions: 3.4.0 >Reporter: Jonathan Li >Assignee: Jonathan Bond > Fix For: 3.5.0 > > > On 3/12/14 12:58 PM, "Shazron" wrote: > Just tested it with File and File-Transfer - looks like a bug. Please file > it, thanks! > On Wed, Mar 12, 2014 at 7:46 AM, Li, Jonathan wrote: > When testing with cordova 3.4.0-0.1.3, if a plugin A is a dependent of > plugin B, then running the following command will automatically delete > plugin B from the project > cordova plugin add PluginB > cordova plugin add pluginA > cordova plugin rm pluginB > As pluginA is explicitly added into the project, unless it is explicated > removed from project by using "cordova plugin rm pluginA" command, then it > should not be deleted from the project when deleting pluginB. > The test is done on iOS platform. > Please let me know if this is a known issue, or whether I need to submit a > bug for it > Thanks > Jonathan -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6241) Default to prompting for passwords (replace --query with --no-query)
[ https://issues.apache.org/jira/browse/CB-6241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13933385#comment-13933385 ] ASF GitHub Bot commented on CB-6241: Github user bryanhiggins commented on the pull request: https://github.com/apache/cordova-blackberry/pull/150#issuecomment-37544828 r+, tested on 3.4.0-0.1.3 with multiple platforms added > Default to prompting for passwords (replace --query with --no-query) > > > Key: CB-6241 > URL: https://issues.apache.org/jira/browse/CB-6241 > Project: Apache Cordova > Issue Type: Bug > Components: BlackBerry >Affects Versions: 3.4.0 >Reporter: Josh Soref >Assignee: Josh Soref > > BlackBerry 10 has supported prompting for passwords for a while using the > --query flag, and we've used it for our end users. > This behavior makes sense as a default, and more or less matches the behavior > for Android. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6189) Spelling errors
[ https://issues.apache.org/jira/browse/CB-6189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13933458#comment-13933458 ] Marcel Kinard commented on CB-6189: --- Pull request merged. > Spelling errors > --- > > Key: CB-6189 > URL: https://issues.apache.org/jira/browse/CB-6189 > Project: Apache Cordova > Issue Type: Bug > Components: Coho >Affects Versions: 3.4.0 >Reporter: Josh Soref >Assignee: Josh Soref >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6189) Spelling errors
[ https://issues.apache.org/jira/browse/CB-6189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13933456#comment-13933456 ] ASF subversion and git services commented on CB-6189: - Commit c3d03d3d3cb1ca1e9faeb41845cbd4563e1e6b46 in cordova-coho's branch refs/heads/master from [~jsoref] [ https://git-wip-us.apache.org/repos/asf?p=cordova-coho.git;h=c3d03d3 ] CB-6189 Spelling: release github: close #15 > Spelling errors > --- > > Key: CB-6189 > URL: https://issues.apache.org/jira/browse/CB-6189 > Project: Apache Cordova > Issue Type: Bug > Components: Coho >Affects Versions: 3.4.0 >Reporter: Josh Soref >Assignee: Josh Soref >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6189) Spelling errors
[ https://issues.apache.org/jira/browse/CB-6189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13933462#comment-13933462 ] ASF GitHub Bot commented on CB-6189: Github user asfgit closed the pull request at: https://github.com/apache/cordova-coho/pull/15 > Spelling errors > --- > > Key: CB-6189 > URL: https://issues.apache.org/jira/browse/CB-6189 > Project: Apache Cordova > Issue Type: Bug > Components: Coho >Affects Versions: 3.4.0 >Reporter: Josh Soref >Assignee: Josh Soref >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CB-6243) FileEntry.toURL() "cdvfile://localhost/persistent/file://"
David Normington created CB-6243:
Summary: FileEntry.toURL() "cdvfile://localhost/persistent/file://"
Key: CB-6243
URL: https://issues.apache.org/jira/browse/CB-6243
Project: Apache Cordova
Issue Type: Bug
Components: Plugin File
Affects Versions: 3.4.0
Environment: Android 4.4 using Genymotion emulator
Reporter: David Normington
When I run something like this:
{code}
window.resolveLocalFileSystemURL('file:///storage/emulated/0/DCIM/Camera/1394726081689.jpg',
function(entry) {
console.log(entry.fullPath);
console.log(entry.toURL());
entry.file(fileSuccess, fail);
});
{code}
The logcat shows this result:
{code}
I/chromium( 3022): [INFO:CONSOLE(28)]
"file:///storage/emulated/0/DCIM/Camera/1394726081689.jpg", source:
file:///android_asset/www/js/pdf.js (28)
I/chromium( 3022): [INFO:CONSOLE(29)]
"cdvfile://localhost/temporary/file://storage/emulated/0/DCIM/Camera/1394726081689.jpg",
source: file:///android_asset/www/js/pdf.js (29)
W/System.err( 2928): java.io.FileNotFoundException: File:
cdvfile://localhost/persistent/file://storage/emulated/0/DCIM/Camera/1394726081689.jpg
does not exist.
W/System.err( 2928):at
org.apache.cordova.file.FileUtils.getFileMetadata(FileUtils.java:953)
W/System.err( 2928):at
org.apache.cordova.file.FileUtils.access$400(FileUtils.java:53)
W/System.err( 2928):at
org.apache.cordova.file.FileUtils$14.run(FileUtils.java:220)
W/System.err( 2928):at
org.apache.cordova.file.FileUtils$23.run(FileUtils.java:325)
W/System.err( 2928):at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
W/System.err( 2928):at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
W/System.err( 2928):at java.lang.Thread.run(Thread.java:841)
{code}
As you can see the second console.log has the cdvfile protocol with the file
protocol appended to the end. I'm sure this is causing the following error.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (CB-6243) FileEntry.toURL() "cdvfile://localhost/persistent/file://"
[
https://issues.apache.org/jira/browse/CB-6243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Normington updated CB-6243:
-
Description:
When I run something like this:
{code}
window.resolveLocalFileSystemURL('file:///storage/emulated/0/DCIM/Camera/1394726081689.jpg',
function(entry) {
console.log(entry.fullPath);
console.log(entry.toURL());
entry.file(fileSuccess, fail);
});
{code}
The logcat shows this result:
{code}
I/chromium( 3022): [INFO:CONSOLE(28)]
"file:///storage/emulated/0/DCIM/Camera/1394726081689.jpg", source:
file:///android_asset/www/js/pdf.js (28)
I/chromium( 3022): [INFO:CONSOLE(29)]
"cdvfile://localhost/temporary/file://storage/emulated/0/DCIM/Camera/1394726081689.jpg",
source: file:///android_asset/www/js/pdf.js (29)
W/System.err( 2928): java.io.FileNotFoundException: File:
cdvfile://localhost/persistent/file://storage/emulated/0/DCIM/Camera/1394726081689.jpg
does not exist.
W/System.err( 2928):at
org.apache.cordova.file.FileUtils.getFileMetadata(FileUtils.java:953)
W/System.err( 2928):at
org.apache.cordova.file.FileUtils.access$400(FileUtils.java:53)
W/System.err( 2928):at
org.apache.cordova.file.FileUtils$14.run(FileUtils.java:220)
W/System.err( 2928):at
org.apache.cordova.file.FileUtils$23.run(FileUtils.java:325)
W/System.err( 2928):at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
W/System.err( 2928):at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
W/System.err( 2928):at java.lang.Thread.run(Thread.java:841)
{code}
As you can see the second console.log has the cdvfile protocol with the file
protocol appended to the end. I'm sure this is causing the following error.
Seems that the same code runs perfectly on iOS returning the correct URLs:
{code}
[Log] /cdv_photo_001.jpg
[Log] cdvfile://localhost/temporary/cdv_photo_001.jpg
{code}
was:
When I run something like this:
{code}
window.resolveLocalFileSystemURL('file:///storage/emulated/0/DCIM/Camera/1394726081689.jpg',
function(entry) {
console.log(entry.fullPath);
console.log(entry.toURL());
entry.file(fileSuccess, fail);
});
{code}
The logcat shows this result:
{code}
I/chromium( 3022): [INFO:CONSOLE(28)]
"file:///storage/emulated/0/DCIM/Camera/1394726081689.jpg", source:
file:///android_asset/www/js/pdf.js (28)
I/chromium( 3022): [INFO:CONSOLE(29)]
"cdvfile://localhost/temporary/file://storage/emulated/0/DCIM/Camera/1394726081689.jpg",
source: file:///android_asset/www/js/pdf.js (29)
W/System.err( 2928): java.io.FileNotFoundException: File:
cdvfile://localhost/persistent/file://storage/emulated/0/DCIM/Camera/1394726081689.jpg
does not exist.
W/System.err( 2928):at
org.apache.cordova.file.FileUtils.getFileMetadata(FileUtils.java:953)
W/System.err( 2928):at
org.apache.cordova.file.FileUtils.access$400(FileUtils.java:53)
W/System.err( 2928):at
org.apache.cordova.file.FileUtils$14.run(FileUtils.java:220)
W/System.err( 2928):at
org.apache.cordova.file.FileUtils$23.run(FileUtils.java:325)
W/System.err( 2928):at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
W/System.err( 2928):at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
W/System.err( 2928):at java.lang.Thread.run(Thread.java:841)
{code}
As you can see the second console.log has the cdvfile protocol with the file
protocol appended to the end. I'm sure this is causing the following error.
> FileEntry.toURL() "cdvfile://localhost/persistent/file://"
> --
>
> Key: CB-6243
> URL: https://issues.apache.org/jira/browse/CB-6243
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin File
>Affects Versions: 3.4.0
> Environment: Android 4.4 using Genymotion emulator
>Reporter: David Normington
> Labels: android, cdvfile
>
> When I run something like this:
> {code}
> window.resolveLocalFileSystemURL('file:///storage/emulated/0/DCIM/Camera/1394726081689.jpg',
> function(entry) {
> console.log(entry.fullPath);
> console.log(entry.toURL());
> entry.file(fileSuccess, fail);
> });
> {code}
> The logcat shows this result:
> {code}
> I/chromium( 3022): [INFO:CONSOLE(28)]
> "file:///storage/emulated/0/DCIM/Camera/1394726081689.jpg", source:
> file:///android_asset/www/js/pdf.js (28)
> I/chromium( 3022): [INFO:CONSOLE(29)]
> "cdvfile://localhost/temporary/file://storage/emulated/0/DCIM/Camera/1394726081689.jpg",
> source: file:///android_asset/www/js/pdf.js (29)
> W/System.err( 2928): java.io.FileNotFoundException: File:
> cdvfile://localhost/persistent/file://storage/emulated/0/DCIM/Camera/1394726081689.jpg
> does not exist.
> W/System.err( 2928):at
> org.apache.cordova.file.FileUtils.getFileMetadata(F
[jira] [Commented] (CB-6242) [BlackBerry10] resolveLocalFileSystemURL not mapped correctly
[ https://issues.apache.org/jira/browse/CB-6242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13933513#comment-13933513 ] Bryan Higgins commented on CB-6242: --- Also the call to requestAnimationFrame doesn't work on 10.1. > [BlackBerry10] resolveLocalFileSystemURL not mapped correctly > - > > Key: CB-6242 > URL: https://issues.apache.org/jira/browse/CB-6242 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin File >Reporter: Bryan Higgins >Assignee: Bryan Higgins > > resolveLocalFileSystemURI is working correctly, but this has been deprecated > in favour of resolveLocalFileSystemURL -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CB-6244) Plugin development guide command incorrect
Lisa Seacat DeLuca created CB-6244: -- Summary: Plugin development guide command incorrect Key: CB-6244 URL: https://issues.apache.org/jira/browse/CB-6244 Project: Apache Cordova Issue Type: Bug Components: Docs Affects Versions: 3.4.0, 3.5.0 Reporter: Lisa Seacat DeLuca Assignee: Lisa Seacat DeLuca Priority: Minor The plugin development guide says: Then run a command such as the following to test whether iOS dependencies load properly: $ plugman -platform ios /path/to/my/project/www /path/to/my/plugin when testing on a device that command doesn't work. It opens the help for plugman. I believe what it was supposed to say is: $ plugman install -platform ios /path/to/my/project/www /path/to/my/plugin -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CB-6244) Plugin development guide command incorrect
[ https://issues.apache.org/jira/browse/CB-6244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lisa Seacat DeLuca updated CB-6244: --- Description: The plugin development guide says: Then run a command such as the following to test whether iOS dependencies load properly: $ plugman -platform ios /path/to/my/project/www /path/to/my/plugin when testing on a device that command doesn't work. It opens the help for plugman. I believe what it was supposed to say is: $ plugman install --platform ios --project /path/to/my/project/www --plugin /path/to/my/plugin was: The plugin development guide says: Then run a command such as the following to test whether iOS dependencies load properly: $ plugman -platform ios /path/to/my/project/www /path/to/my/plugin when testing on a device that command doesn't work. It opens the help for plugman. I believe what it was supposed to say is: $ plugman install -platform ios /path/to/my/project/www /path/to/my/plugin > Plugin development guide command incorrect > -- > > Key: CB-6244 > URL: https://issues.apache.org/jira/browse/CB-6244 > Project: Apache Cordova > Issue Type: Bug > Components: Docs >Affects Versions: 3.4.0, 3.5.0 >Reporter: Lisa Seacat DeLuca >Assignee: Lisa Seacat DeLuca >Priority: Minor > Original Estimate: 1h > Remaining Estimate: 1h > > The plugin development guide says: > Then run a command such as the following to test whether iOS dependencies > load properly: > $ plugman -platform ios /path/to/my/project/www /path/to/my/plugin > when testing on a device that command doesn't work. It opens the help for > plugman. I believe what it was supposed to say is: > $ plugman install --platform ios --project /path/to/my/project/www --plugin > /path/to/my/plugin -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CB-6244) Plugin development guide command incorrect
[ https://issues.apache.org/jira/browse/CB-6244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lisa Seacat DeLuca updated CB-6244: --- Description: The plugin development guide says: http://cordova.apache.org/docs/en/edge/guide_hybrid_plugins_index.md.html#Plugin%20Development%20Guide Then run a command such as the following to test whether iOS dependencies load properly: $ plugman -platform ios /path/to/my/project/www /path/to/my/plugin when testing on a device that command doesn't work. It opens the help for plugman. I believe what it was supposed to say is: $ plugman install --platform ios --project /path/to/my/project/www --plugin /path/to/my/plugin was: The plugin development guide says: Then run a command such as the following to test whether iOS dependencies load properly: $ plugman -platform ios /path/to/my/project/www /path/to/my/plugin when testing on a device that command doesn't work. It opens the help for plugman. I believe what it was supposed to say is: $ plugman install --platform ios --project /path/to/my/project/www --plugin /path/to/my/plugin > Plugin development guide command incorrect > -- > > Key: CB-6244 > URL: https://issues.apache.org/jira/browse/CB-6244 > Project: Apache Cordova > Issue Type: Bug > Components: Docs >Affects Versions: 3.4.0, 3.5.0 >Reporter: Lisa Seacat DeLuca >Assignee: Lisa Seacat DeLuca >Priority: Minor > Original Estimate: 1h > Remaining Estimate: 1h > > The plugin development guide says: > http://cordova.apache.org/docs/en/edge/guide_hybrid_plugins_index.md.html#Plugin%20Development%20Guide > Then run a command such as the following to test whether iOS dependencies > load properly: > $ plugman -platform ios /path/to/my/project/www /path/to/my/plugin > when testing on a device that command doesn't work. It opens the help for > plugman. I believe what it was supposed to say is: > $ plugman install --platform ios --project /path/to/my/project/www --plugin > /path/to/my/plugin -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6244) Plugin development guide command incorrect
[ https://issues.apache.org/jira/browse/CB-6244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13933673#comment-13933673 ] ASF GitHub Bot commented on CB-6244: GitHub user ldeluca opened a pull request: https://github.com/apache/cordova-docs/pull/195 CB-6244 - Fixed plugman command in docs This works on the windows file system with version 3.4 of Cordova. You can merge this pull request into a Git repository by running: $ git pull https://github.com/ldeluca/cordova-docs patch-7 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-docs/pull/195.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 #195 commit ba395d21dd63bd7d33fd40fda3846fa79b31c5e2 Author: Lisa Seacat DeLuca Date: 2014-03-13T18:11:08Z CB-6244 - Fixed plugman command in docs This works on the windows file system with version 3.4 of Cordova. > Plugin development guide command incorrect > -- > > Key: CB-6244 > URL: https://issues.apache.org/jira/browse/CB-6244 > Project: Apache Cordova > Issue Type: Bug > Components: Docs >Affects Versions: 3.4.0, 3.5.0 >Reporter: Lisa Seacat DeLuca >Assignee: Lisa Seacat DeLuca >Priority: Minor > Original Estimate: 1h > Remaining Estimate: 1h > > The plugin development guide says: > http://cordova.apache.org/docs/en/edge/guide_hybrid_plugins_index.md.html#Plugin%20Development%20Guide > Then run a command such as the following to test whether iOS dependencies > load properly: > $ plugman -platform ios /path/to/my/project/www /path/to/my/plugin > when testing on a device that command doesn't work. It opens the help for > plugman. I believe what it was supposed to say is: > $ plugman install --platform ios --project /path/to/my/project/www --plugin > /path/to/my/plugin -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CB-6245) Tools Release March 14, 2014
Steve Gill created CB-6245: -- Summary: Tools Release March 14, 2014 Key: CB-6245 URL: https://issues.apache.org/jira/browse/CB-6245 Project: Apache Cordova Issue Type: Task Components: CLI, Plugman Reporter: Steve Gill Assignee: Steve Gill Following steps at https://github.com/apache/cordova-coho/blob/master/docs/tools-release-process.md -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6244) Plugin development guide command incorrect
[ https://issues.apache.org/jira/browse/CB-6244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13933812#comment-13933812 ] ASF subversion and git services commented on CB-6244: - Commit 2c5ec964d67fa0456e3e8b48144109a175e758c3 in cordova-docs's branch refs/heads/master from [~ldeluca] [ https://git-wip-us.apache.org/repos/asf?p=cordova-docs.git;h=2c5ec96 ] CB-6244 - Fixed plugman command in docs github: close #195 This works on the windows file system with version 3.4 of Cordova. > Plugin development guide command incorrect > -- > > Key: CB-6244 > URL: https://issues.apache.org/jira/browse/CB-6244 > Project: Apache Cordova > Issue Type: Bug > Components: Docs >Affects Versions: 3.4.0, 3.5.0 >Reporter: Lisa Seacat DeLuca >Assignee: Lisa Seacat DeLuca >Priority: Minor > Original Estimate: 1h > Remaining Estimate: 1h > > The plugin development guide says: > http://cordova.apache.org/docs/en/edge/guide_hybrid_plugins_index.md.html#Plugin%20Development%20Guide > Then run a command such as the following to test whether iOS dependencies > load properly: > $ plugman -platform ios /path/to/my/project/www /path/to/my/plugin > when testing on a device that command doesn't work. It opens the help for > plugman. I believe what it was supposed to say is: > $ plugman install --platform ios --project /path/to/my/project/www --plugin > /path/to/my/plugin -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6244) Plugin development guide command incorrect
[ https://issues.apache.org/jira/browse/CB-6244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13933821#comment-13933821 ] Marcel Kinard commented on CB-6244: --- Pull request merged. > Plugin development guide command incorrect > -- > > Key: CB-6244 > URL: https://issues.apache.org/jira/browse/CB-6244 > Project: Apache Cordova > Issue Type: Bug > Components: Docs >Affects Versions: 3.4.0, 3.5.0 >Reporter: Lisa Seacat DeLuca >Assignee: Lisa Seacat DeLuca >Priority: Minor > Original Estimate: 1h > Remaining Estimate: 1h > > The plugin development guide says: > http://cordova.apache.org/docs/en/edge/guide_hybrid_plugins_index.md.html#Plugin%20Development%20Guide > Then run a command such as the following to test whether iOS dependencies > load properly: > $ plugman -platform ios /path/to/my/project/www /path/to/my/plugin > when testing on a device that command doesn't work. It opens the help for > plugman. I believe what it was supposed to say is: > $ plugman install --platform ios --project /path/to/my/project/www --plugin > /path/to/my/plugin -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CB-6246) Allow for Cordova-Android to use many different types of WebViews
Joe Bowser created CB-6246: -- Summary: Allow for Cordova-Android to use many different types of WebViews Key: CB-6246 URL: https://issues.apache.org/jira/browse/CB-6246 Project: Apache Cordova Issue Type: Bug Components: Android Reporter: Joe Bowser Fix For: 4.0.0 The Android WebView is an externality that may developers don't want to depend on. This has been an ongoing pain point. That being said, we want to keep the web open, therefore instead of working on our own WebView, we should allow an interface for third-party layout engines to be able to be bundled with Cordova, or to be used by Cordova. This includes projects such as Crosswalk and GeckoView. Currently a PoC exists here: https://github.com/infil00p/cordova-android/tree/pluggable_webview -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CB-6246) Allow for Cordova-Android to use many different types of WebViews
[ https://issues.apache.org/jira/browse/CB-6246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser reassigned CB-6246: -- Assignee: Joe Bowser > Allow for Cordova-Android to use many different types of WebViews > - > > Key: CB-6246 > URL: https://issues.apache.org/jira/browse/CB-6246 > Project: Apache Cordova > Issue Type: Bug > Components: Android >Reporter: Joe Bowser >Assignee: Joe Bowser > Labels: Android > Fix For: 4.0.0 > > > The Android WebView is an externality that may developers don't want to > depend on. This has been an ongoing pain point. That being said, we want to > keep the web open, therefore instead of working on our own WebView, we should > allow an interface for third-party layout engines to be able to be bundled > with Cordova, or to be used by Cordova. > This includes projects such as Crosswalk and GeckoView. > Currently a PoC exists here: > https://github.com/infil00p/cordova-android/tree/pluggable_webview -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CB-6246) Allow for Cordova-Android to use many different types of WebViews
[ https://issues.apache.org/jira/browse/CB-6246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser updated CB-6246: --- Issue Type: New Feature (was: Bug) > Allow for Cordova-Android to use many different types of WebViews > - > > Key: CB-6246 > URL: https://issues.apache.org/jira/browse/CB-6246 > Project: Apache Cordova > Issue Type: New Feature > Components: Android >Reporter: Joe Bowser >Assignee: Joe Bowser > Labels: Android > Fix For: 4.0.0 > > > The Android WebView is an externality that may developers don't want to > depend on. This has been an ongoing pain point. That being said, we want to > keep the web open, therefore instead of working on our own WebView, we should > allow an interface for third-party layout engines to be able to be bundled > with Cordova, or to be used by Cordova. > This includes projects such as Crosswalk and GeckoView. > Currently a PoC exists here: > https://github.com/infil00p/cordova-android/tree/pluggable_webview -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CB-3990) Implement optional GeckoView upon ./bin/create
[ https://issues.apache.org/jira/browse/CB-3990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser updated CB-3990: --- Issue Type: Sub-task (was: Improvement) Parent: CB-6246 > Implement optional GeckoView upon ./bin/create > -- > > Key: CB-3990 > URL: https://issues.apache.org/jira/browse/CB-3990 > Project: Apache Cordova > Issue Type: Sub-task > Components: Android >Reporter: Brian LeRoux >Assignee: Joe Bowser >Priority: Minor > > Add --use-gecko flag to ./bin/create > Relevant to our interests from Mozilla's buzilla: > * Bug 880107 is the tracking bug for the work. > * Bug 880119 , bug 880121 and bug 880123 for discussion of improving the > APIs. > * bug 880118 prebuilt binaries -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CB-3990) Implement optional GeckoView as a pluggable WebView
[ https://issues.apache.org/jira/browse/CB-3990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser updated CB-3990: --- Summary: Implement optional GeckoView as a pluggable WebView (was: Implement optional GeckoView upon ./bin/create) > Implement optional GeckoView as a pluggable WebView > --- > > Key: CB-3990 > URL: https://issues.apache.org/jira/browse/CB-3990 > Project: Apache Cordova > Issue Type: Sub-task > Components: Android >Reporter: Brian LeRoux >Assignee: Joe Bowser >Priority: Minor > > Add --use-gecko flag to ./bin/create > Relevant to our interests from Mozilla's buzilla: > * Bug 880107 is the tracking bug for the work. > * Bug 880119 , bug 880121 and bug 880123 for discussion of improving the > APIs. > * bug 880118 prebuilt binaries -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CB-6247) Implement Crosswalk as a pluggable WebView
Joe Bowser created CB-6247: -- Summary: Implement Crosswalk as a pluggable WebView Key: CB-6247 URL: https://issues.apache.org/jira/browse/CB-6247 Project: Apache Cordova Issue Type: Sub-task Reporter: Joe Bowser Assignee: Joe Bowser Fix For: 4.0.0 This is already done: https://github.com/infil00p/cordova-android/tree/pluggable_webview -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CB-6219) org.apache.cordova.keyboard@0.1.2 on iOS 7.1 caused keyboard ugly without background
[ https://issues.apache.org/jira/browse/CB-6219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shazron Abdullah resolved CB-6219. -- Resolution: Fixed > org.apache.cordova.keyboard@0.1.2 on iOS 7.1 caused keyboard ugly without > background > > > Key: CB-6219 > URL: https://issues.apache.org/jira/browse/CB-6219 > Project: Apache Cordova > Issue Type: Bug > Components: Plugins > Environment: iOS 7.1 >Reporter: 2k13yr >Priority: Critical > Labels: ios, ios7.1, javascript, keyboard-plugin > Attachments: Screen Shot 2014-03-12 at 0.46.24.png, Screen Shot > 2014-03-12 at 0.49.11.png > > > Only single line JS Code: > Keyboard.hideFormAccessoryBar(true); > caused keyboard ugly without background on iOS 7.1. > Normally keyboard on iOS 7.0, but the accessory bar is not completely hidden. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CB-6219) org.apache.cordova.keyboard@0.1.2 on iOS 7.1 caused keyboard ugly without background
[ https://issues.apache.org/jira/browse/CB-6219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shazron Abdullah reassigned CB-6219: Assignee: Shazron Abdullah > org.apache.cordova.keyboard@0.1.2 on iOS 7.1 caused keyboard ugly without > background > > > Key: CB-6219 > URL: https://issues.apache.org/jira/browse/CB-6219 > Project: Apache Cordova > Issue Type: Bug > Components: Plugins > Environment: iOS 7.1 >Reporter: 2k13yr >Assignee: Shazron Abdullah >Priority: Critical > Labels: ios, ios7.1, javascript, keyboard-plugin > Attachments: Screen Shot 2014-03-12 at 0.46.24.png, Screen Shot > 2014-03-12 at 0.49.11.png > > > Only single line JS Code: > Keyboard.hideFormAccessoryBar(true); > caused keyboard ugly without background on iOS 7.1. > Normally keyboard on iOS 7.0, but the accessory bar is not completely hidden. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6219) org.apache.cordova.keyboard@0.1.2 on iOS 7.1 caused keyboard ugly without background
[ https://issues.apache.org/jira/browse/CB-6219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13933895#comment-13933895 ] ASF subversion and git services commented on CB-6219: - Commit ff26005678d31df746245b2d7a341e56644d10eb in cordova-plugins's branch refs/heads/master from [~ashearer] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugins.git;h=ff26005 ] CB-6219 - Fix by preventing the main keyboard from becoming transparent on iOS 7. (This looked particularly bad on iOS 7.1, where a white background would render the Shift key icons invisible.) Closes #6 > org.apache.cordova.keyboard@0.1.2 on iOS 7.1 caused keyboard ugly without > background > > > Key: CB-6219 > URL: https://issues.apache.org/jira/browse/CB-6219 > Project: Apache Cordova > Issue Type: Bug > Components: Plugins > Environment: iOS 7.1 >Reporter: 2k13yr >Priority: Critical > Labels: ios, ios7.1, javascript, keyboard-plugin > Attachments: Screen Shot 2014-03-12 at 0.46.24.png, Screen Shot > 2014-03-12 at 0.49.11.png > > > Only single line JS Code: > Keyboard.hideFormAccessoryBar(true); > caused keyboard ugly without background on iOS 7.1. > Normally keyboard on iOS 7.0, but the accessory bar is not completely hidden. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6244) Plugin development guide command incorrect
[ https://issues.apache.org/jira/browse/CB-6244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13933898#comment-13933898 ] ASF GitHub Bot commented on CB-6244: Github user asfgit closed the pull request at: https://github.com/apache/cordova-docs/pull/195 > Plugin development guide command incorrect > -- > > Key: CB-6244 > URL: https://issues.apache.org/jira/browse/CB-6244 > Project: Apache Cordova > Issue Type: Bug > Components: Docs >Affects Versions: 3.4.0, 3.5.0 >Reporter: Lisa Seacat DeLuca >Assignee: Lisa Seacat DeLuca >Priority: Minor > Original Estimate: 1h > Remaining Estimate: 1h > > The plugin development guide says: > http://cordova.apache.org/docs/en/edge/guide_hybrid_plugins_index.md.html#Plugin%20Development%20Guide > Then run a command such as the following to test whether iOS dependencies > load properly: > $ plugman -platform ios /path/to/my/project/www /path/to/my/plugin > when testing on a device that command doesn't work. It opens the help for > plugman. I believe what it was supposed to say is: > $ plugman install --platform ios --project /path/to/my/project/www --plugin > /path/to/my/plugin -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-6219) org.apache.cordova.keyboard@0.1.2 on iOS 7.1 caused keyboard ugly without background
[ https://issues.apache.org/jira/browse/CB-6219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13933905#comment-13933905 ] ASF GitHub Bot commented on CB-6219: Github user asfgit closed the pull request at: https://github.com/apache/cordova-plugins/pull/6 > org.apache.cordova.keyboard@0.1.2 on iOS 7.1 caused keyboard ugly without > background > > > Key: CB-6219 > URL: https://issues.apache.org/jira/browse/CB-6219 > Project: Apache Cordova > Issue Type: Bug > Components: Plugins > Environment: iOS 7.1 >Reporter: 2k13yr >Assignee: Shazron Abdullah >Priority: Critical > Labels: ios, ios7.1, javascript, keyboard-plugin > Attachments: Screen Shot 2014-03-12 at 0.46.24.png, Screen Shot > 2014-03-12 at 0.49.11.png > > > Only single line JS Code: > Keyboard.hideFormAccessoryBar(true); > caused keyboard ugly without background on iOS 7.1. > Normally keyboard on iOS 7.0, but the accessory bar is not completely hidden. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CB-5520) Should we add "DEBUG=1" to "Preprocessor Macros"->"Debug" ?
[
https://issues.apache.org/jira/browse/CB-5520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shazron Abdullah updated CB-5520:
-
Labels: core (was: )
> Should we add "DEBUG=1" to "Preprocessor Macros"->"Debug" ?
> ---
>
> Key: CB-5520
> URL: https://issues.apache.org/jira/browse/CB-5520
> Project: Apache Cordova
> Issue Type: Wish
> Components: iOS
>Affects Versions: 3.2.0
>Reporter: glmnbeyond
>Priority: Minor
> Labels: core
>
> I created a helloCordova project via Cordova CLI, and added some debug info
> to native code:
> DLog('This is a debug info');
> But the debug info is never outputted.If I use ALog, the info can be
> outputted, so I think it probably has something to do with the "DEBUG" macro.
> After I added "DEBUG=1" to "Preprocessor Macros", ran the helloCordova
> target, DLog can be outputted.
> So here is my question:
> Should we add "DEBUG=1" to iOS template project->"Build Settings"->
> "Preprocessor Macros" ->"Debug" ?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Assigned] (CB-5520) Should we add "DEBUG=1" to "Preprocessor Macros"->"Debug" ?
[
https://issues.apache.org/jira/browse/CB-5520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shazron Abdullah reassigned CB-5520:
Assignee: Shazron Abdullah
> Should we add "DEBUG=1" to "Preprocessor Macros"->"Debug" ?
> ---
>
> Key: CB-5520
> URL: https://issues.apache.org/jira/browse/CB-5520
> Project: Apache Cordova
> Issue Type: Wish
> Components: iOS
>Affects Versions: 3.2.0
>Reporter: glmnbeyond
>Assignee: Shazron Abdullah
>Priority: Minor
> Labels: core
>
> I created a helloCordova project via Cordova CLI, and added some debug info
> to native code:
> DLog('This is a debug info');
> But the debug info is never outputted.If I use ALog, the info can be
> outputted, so I think it probably has something to do with the "DEBUG" macro.
> After I added "DEBUG=1" to "Preprocessor Macros", ran the helloCordova
> target, DLog can be outputted.
> So here is my question:
> Should we add "DEBUG=1" to iOS template project->"Build Settings"->
> "Preprocessor Macros" ->"Debug" ?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CB-5920) android:installLocation="preferExternal"
[ https://issues.apache.org/jira/browse/CB-5920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13933941#comment-13933941 ] Frederico Costa Galvão commented on CB-5920: I've used *android:installLocation="auto"* for a while now on my cordova app, already on production. It allows the OS to install it on sdcards if there isn't enough space left on internal storage, and also allows users to move it from internal to external or vice-versa as they please. I've had no issues so far with this strategy, and I agree that it should be added as a platfrom specific ** on *config.xml*. Considering this will most surely (according to my experience using it) not need further code changes other than *AndroidManifest.xml* manipulation, I think this is pretty safe and easy to implement (or modify the existing PR). > android:installLocation="preferExternal" > > > Key: CB-5920 > URL: https://issues.apache.org/jira/browse/CB-5920 > Project: Apache Cordova > Issue Type: Improvement > Components: Android, CLI > Environment: Phones with 512 Ram >Reporter: cesine > Labels: patch > > I created a PR on github suggesting to add preferExternal > https://github.com/apache/cordova-android/pull/91#issuecomment-33513325 > for phones with small amounts of internal storage (512MB and even 1GB, > android 2.2 and 2.3 and even some 4.0) the user wont be able to install the > app (or keep it) unless you let them put it on the sdcard instead of the > internal phone storage. Very few cordova apps are the kind of app which > shouldn't be on external storage. > more details: > http://developer.android.com/guide/topics/data/install-location.html#Should -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CB-6248) Error on prepare when Orientation is configured
Frederico Costa Galvão created CB-6248:
--
Summary: Error on prepare when Orientation is configured
Key: CB-6248
URL: https://issues.apache.org/jira/browse/CB-6248
Project: Apache Cordova
Issue Type: Bug
Components: Android, CLI
Affects Versions: 3.4.0
Environment: Xubuntu 13.10 x86_64, cordova 3.4.0-0.1.3
Reporter: Frederico Costa Galvão
Priority: Minor
After creating an empty cordova project (*cordova create bacon com.bacon
Bacon*), running *cordova platform add android*, and adding
{code}
{code}
and then running *cordova prepare*, the following error is shown among the
output.
{code}
[ReferenceError: a is not defined]
{code}
As a second side effect, bigger than just a logged error, the *orientation*
preference isn't working as expected: the *android:screenOrientation* isn't set
according to what's in the *config.xml* (it isn't set at all, by the way).
PS: I've checked case sensitivity, and I've checked all possible values
\[default, landscape, portrait\].
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CB-5838) Android 4.4 - Path returned from Camera plugin FILE_URI is not readable
[
https://issues.apache.org/jira/browse/CB-5838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13934009#comment-13934009
]
Ralph S Theart commented on CB-5838:
this absolutely does not work...need the file
`content://media/external/images/media/`
> Android 4.4 - Path returned from Camera plugin FILE_URI is not readable
> ---
>
> Key: CB-5838
> URL: https://issues.apache.org/jira/browse/CB-5838
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android, Plugin Camera
>Affects Versions: 3.3.0
>Reporter: Lindsey Simon
>Assignee: Andrew Grieve
>
> I'm calling the plugin like so (pasted below). When I take the file uri and
> try to load it into another interface, like the ExifInterface I get the
> following error:
> E/JHEAD ( 6734): can't open
> 'file:///storage/emulated/0/DCIM/Camera/1390266145786.jpg'
> ---
> var cameraOptions = {
> quality: 100,
> destinationType: Camera.DestinationType.FILE_URI,
> sourceType: Camera.PictureSourceType.CAMERA,
> allowEdit: true,
> encodingType: Camera.EncodingType.JPEG,
> targetWidth: 800,
> saveToPhotoAlbum: true
> };
> navigator.camera.getPicture(
> _.bind(this.onPhotoSuccess_, this),
> _.bind(this.onPhotoError_, this),
> cameraOptions);
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CB-5838) Android 4.4 - Path returned from Camera plugin FILE_URI is not readable
[
https://issues.apache.org/jira/browse/CB-5838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13934011#comment-13934011
]
Ralph S Theart commented on CB-5838:
btw when you take a picture a file:/// path is returned when using FILE_URI but
when choose anything from the gallery it gives back uri but not one you can use
normally in a case where you would want to use the extension.
> Android 4.4 - Path returned from Camera plugin FILE_URI is not readable
> ---
>
> Key: CB-5838
> URL: https://issues.apache.org/jira/browse/CB-5838
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android, Plugin Camera
>Affects Versions: 3.3.0
>Reporter: Lindsey Simon
>Assignee: Andrew Grieve
>
> I'm calling the plugin like so (pasted below). When I take the file uri and
> try to load it into another interface, like the ExifInterface I get the
> following error:
> E/JHEAD ( 6734): can't open
> 'file:///storage/emulated/0/DCIM/Camera/1390266145786.jpg'
> ---
> var cameraOptions = {
> quality: 100,
> destinationType: Camera.DestinationType.FILE_URI,
> sourceType: Camera.PictureSourceType.CAMERA,
> allowEdit: true,
> encodingType: Camera.EncodingType.JPEG,
> targetWidth: 800,
> saveToPhotoAlbum: true
> };
> navigator.camera.getPicture(
> _.bind(this.onPhotoSuccess_, this),
> _.bind(this.onPhotoError_, this),
> cameraOptions);
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CB-5920) android:installLocation="preferExternal"
[ https://issues.apache.org/jira/browse/CB-5920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13934018#comment-13934018 ] Joe Bowser commented on CB-5920: [~jsoref] Yes, by choice. There needs to be more to the patch than just adding this to an AndroidManifest.xml > android:installLocation="preferExternal" > > > Key: CB-5920 > URL: https://issues.apache.org/jira/browse/CB-5920 > Project: Apache Cordova > Issue Type: Improvement > Components: Android, CLI > Environment: Phones with 512 Ram >Reporter: cesine > Labels: patch > > I created a PR on github suggesting to add preferExternal > https://github.com/apache/cordova-android/pull/91#issuecomment-33513325 > for phones with small amounts of internal storage (512MB and even 1GB, > android 2.2 and 2.3 and even some 4.0) the user wont be able to install the > app (or keep it) unless you let them put it on the sdcard instead of the > internal phone storage. Very few cordova apps are the kind of app which > shouldn't be on external storage. > more details: > http://developer.android.com/guide/topics/data/install-location.html#Should -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-5705) Android Library Project
[ https://issues.apache.org/jira/browse/CB-5705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13934021#comment-13934021 ] Joe Bowser commented on CB-5705: Hello Are you still interesting in helping fix this? Please let me know. Thanks > Android Library Project > --- > > Key: CB-5705 > URL: https://issues.apache.org/jira/browse/CB-5705 > Project: Apache Cordova > Issue Type: Bug > Components: Android >Reporter: Вячеслав Шабельник > > Importing of Android Library Project into Android build from plugin dont > implemented. So i cant add some sdks into native plugin that use dependencies > as android library project. > Right now i working on jumio plugin for cordova > http://www.jumio.com/netverify/netverify-mobile/ > And jumio sdk require adding their android library project to android build. > According to cordova plugin specs its not implemented. > More info about referencing android library projects to your project you can > get here http://developer.android.com/tools/projects/projects-cmdline.html > To add a reference to a library project, navigate to the /tools/ > directory and use this command: > android update project \ > --target \ > --path path/to/your/project > --library path/to/library_projectA > I already implement cordova hook that do this job for me on after platform > add, and all is brilliant but you have weak link in your build system. In > exec.js file your exec implementation fail and stop build due to buffer > overflow. Error is "Error: stdout maxBuffer exceeded". All that should be > done is adding maxBuffer: 800*1024 option to exec call, also 800 can be > replaced on any other big number. How can i contribute with this and other > fixes to cordova? I saw your repository on github and even forked it. So if i > send you pull requests with fixes do you include them in next releases? -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-5520) Should we add "DEBUG=1" to "Preprocessor Macros"->"Debug" ?
[
https://issues.apache.org/jira/browse/CB-5520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13934042#comment-13934042
]
Shazron Abdullah commented on CB-5520:
--
I'm thinking of adding a .xcconfig file to the default template, so tweaks like
this can be easier (amongst other settings that can be changed)
> Should we add "DEBUG=1" to "Preprocessor Macros"->"Debug" ?
> ---
>
> Key: CB-5520
> URL: https://issues.apache.org/jira/browse/CB-5520
> Project: Apache Cordova
> Issue Type: Wish
> Components: iOS
>Affects Versions: 3.2.0
>Reporter: glmnbeyond
>Assignee: Shazron Abdullah
>Priority: Minor
> Labels: core
>
> I created a helloCordova project via Cordova CLI, and added some debug info
> to native code:
> DLog('This is a debug info');
> But the debug info is never outputted.If I use ALog, the info can be
> outputted, so I think it probably has something to do with the "DEBUG" macro.
> After I added "DEBUG=1" to "Preprocessor Macros", ran the helloCordova
> target, DLog can be outputted.
> So here is my question:
> Should we add "DEBUG=1" to iOS template project->"Build Settings"->
> "Preprocessor Macros" ->"Debug" ?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CB-6238) [CLI][tests] log statements left in test script
[ https://issues.apache.org/jira/browse/CB-6238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13934094#comment-13934094 ] ASF subversion and git services commented on CB-6238: - Commit 55a31889d1ca46a027ebd34eb1abd54f469688c8 in cordova-cli's branch refs/heads/master from [~lorin] [ https://git-wip-us.apache.org/repos/asf?p=cordova-cli.git;h=55a3188 ] [CB-6238] minor fix, removed echo statements from bash hook tests > [CLI][tests] log statements left in test script > --- > > Key: CB-6238 > URL: https://issues.apache.org/jira/browse/CB-6238 > Project: Apache Cordova > Issue Type: Bug > Components: CLI >Affects Versions: 3.4.0 >Reporter: Lorin Beer >Assignee: Lorin Beer >Priority: Minor > Fix For: 3.4.0 > > > $ grep -r "this is script 1 in" . > ./e2e/fixtures/hooks_bat/test/1.bat:ECHO this is script 1 in %~dp0 > ./e2e/fixtures/hooks_sh/test/1.sh:echo "this is script 1 in `pwd`"; > fix: removed statements from stdout > the tests look for the correct firing of scripts -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-5705) Android Library Project
[ https://issues.apache.org/jira/browse/CB-5705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13934121#comment-13934121 ] Вячеслав Шабельник commented on CB-5705: Hi! Yes, ofcourse! I can try. > Android Library Project > --- > > Key: CB-5705 > URL: https://issues.apache.org/jira/browse/CB-5705 > Project: Apache Cordova > Issue Type: Bug > Components: Android >Reporter: Вячеслав Шабельник > > Importing of Android Library Project into Android build from plugin dont > implemented. So i cant add some sdks into native plugin that use dependencies > as android library project. > Right now i working on jumio plugin for cordova > http://www.jumio.com/netverify/netverify-mobile/ > And jumio sdk require adding their android library project to android build. > According to cordova plugin specs its not implemented. > More info about referencing android library projects to your project you can > get here http://developer.android.com/tools/projects/projects-cmdline.html > To add a reference to a library project, navigate to the /tools/ > directory and use this command: > android update project \ > --target \ > --path path/to/your/project > --library path/to/library_projectA > I already implement cordova hook that do this job for me on after platform > add, and all is brilliant but you have weak link in your build system. In > exec.js file your exec implementation fail and stop build due to buffer > overflow. Error is "Error: stdout maxBuffer exceeded". All that should be > done is adding maxBuffer: 800*1024 option to exec call, also 800 can be > replaced on any other big number. How can i contribute with this and other > fixes to cordova? I saw your repository on github and even forked it. So if i > send you pull requests with fixes do you include them in next releases? -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CB-6238) [CLI][tests] log statements left in test script
[ https://issues.apache.org/jira/browse/CB-6238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lorin Beer resolved CB-6238. Resolution: Fixed trivial fix, tracking for documentation > [CLI][tests] log statements left in test script > --- > > Key: CB-6238 > URL: https://issues.apache.org/jira/browse/CB-6238 > Project: Apache Cordova > Issue Type: Bug > Components: CLI >Affects Versions: 3.4.0 >Reporter: Lorin Beer >Assignee: Lorin Beer >Priority: Minor > Fix For: 3.4.0 > > > $ grep -r "this is script 1 in" . > ./e2e/fixtures/hooks_bat/test/1.bat:ECHO this is script 1 in %~dp0 > ./e2e/fixtures/hooks_sh/test/1.sh:echo "this is script 1 in `pwd`"; > fix: removed statements from stdout > the tests look for the correct firing of scripts -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CB-6249) Camera fails to return an actual FILE_URI it always returns content://
Ralph S Theart created CB-6249:
--
Summary: Camera fails to return an actual FILE_URI it always
returns content://
Key: CB-6249
URL: https://issues.apache.org/jira/browse/CB-6249
Project: Apache Cordova
Issue Type: Bug
Components: Plugin Camera, Plugin File
Affects Versions: 3.4.0
Environment: Current Node Version
v0.10.25
Current Cordova CLI Version
3.4.0-0.1.0
Reporter: Ralph S Theart
No matter what I do I can not get a url of file:///... all I get is
{code}
content://media/external/images/media/1357
{code}
Here is my very simple code
{code}
navigator.camera.getPicture(function(imageURI){
console.log('GOT IMAGE: '+imageURI);
window.resolveLocalFileSystemURL(imageURI, function(entry){
console.log(entry.name + " " +entry.fullPath);
}, function(e){
console.log('Some error occured: '+e.code);
});
}, onPhotoFail, {
destinationType: 1,
sourceType: pictureSource,
mediaType : Camera.MediaType.ALLMEDIA,
encodingType: 0,
allowEdit : false,
correctOrientation:true,
saveToPhotoAlbum: false,
quality: 50
});
{code}
I always get content://... for the returned path from camera and even the same
thing when I resolve the url. Can you confirm this bug?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (CB-6250) [CLI] Cordova build doesn't return anything
Lorin Beer created CB-6250: -- Summary: [CLI] Cordova build doesn't return anything Key: CB-6250 URL: https://issues.apache.org/jira/browse/CB-6250 Project: Apache Cordova Issue Type: Bug Components: CLI Reporter: Lorin Beer The CLI Build functionality implicitly calls before build hooks, prepare, compile, and afterbuild hooks. Promises are used to time the events. By not returning a promise, or observing the callback api, projects depending on the cli don't know when to run local code depending on the promises executing. I'd like to see the cli both returning a promise or executing a callback. The behaviour is simple to implement and observed in several major projects. This would prevent subprojects and scripts from being forced to adopt promises. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CB-5809) StatusBar plugin causes viewport drift
[ https://issues.apache.org/jira/browse/CB-5809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shazron Abdullah updated CB-5809: - Component/s: (was: Plugins) (was: iOS) Plugin Statusbar > StatusBar plugin causes viewport drift > -- > > Key: CB-5809 > URL: https://issues.apache.org/jira/browse/CB-5809 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Statusbar > Environment: iOS 7.0 >Reporter: sandstrom > Labels: statusbar-plugin > > When using the Statusbar Plugin (which is awesome btw) to hide/show the > statusbar, it seems like the viewport and/or document is affected such that > anything attached to the bottom (via `position:absolute;`) drifts downwards, > until it's unreachable. > To reproduce: > 1. Attach some div to the bottom via absolute positioning > 2. write `StatusBar.hide(); StatusBar.show();` 5 times in the console > 3. Watch the div drift downwards. > The plugin in question (0.1.3): > https://github.com/apache/cordova-plugins/tree/master/statusbar > Possibly relevant configuration etc: > > > > > Possibly related issues (probably not the same bug though): > https://issues.apache.org/jira/browse/CB-5439 > https://issues.apache.org/jira/browse/CB-4712 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CB-5138) Code review changes for the StatusBar plugin
[ https://issues.apache.org/jira/browse/CB-5138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shazron Abdullah updated CB-5138: - Component/s: (was: Plugins) Plugin Statusbar > Code review changes for the StatusBar plugin > > > Key: CB-5138 > URL: https://issues.apache.org/jira/browse/CB-5138 > Project: Apache Cordova > Issue Type: Improvement > Components: Plugin Statusbar >Affects Versions: Master >Reporter: Shazron Abdullah > Labels: statusbar-plugin > > From Andrew Grieve in the ML: > http://callback-dev.markmail.org/thread/y345lht3ggjmyj5q > - > Looking at the Keyboard & Statusbar plugins, would you be opposed to using: > > instead of: > > Would require a major version bump, but probably it has little usage since > it's new & in labs still? > Thinking here is that since it's not implementing any spec, we should keep > symbols off of window / navigator objects. Would be good to encourage > plugins not to pollute the global namespace I think. > Other points from code-review standpoint: > - Why make StatusBar a function? It has no prototype methods. > - You're calling exec() from the module scope. You should add a to > the to ensure it gets run at start-up. You should also delay > deviceready until it executes. cordova-plugin-device has an example of > this. > - Might be nicer to make the status-bar state a callback with > keepCallback=true so that the native code is agnostic to where the > namespace is mapped. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CB-5482) Add tap listener on status bar
[ https://issues.apache.org/jira/browse/CB-5482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shazron Abdullah updated CB-5482: - Component/s: (was: Plugins) (was: iOS) Plugin Statusbar > Add tap listener on status bar > -- > > Key: CB-5482 > URL: https://issues.apache.org/jira/browse/CB-5482 > Project: Apache Cordova > Issue Type: Improvement > Components: Plugin Statusbar >Affects Versions: 3.1.0 >Reporter: Jacob Weber >Priority: Minor > Labels: statusbar-plugin > > For the statusbar plugin on iOS, it might be nice if a future version > generated a JavaScript event when you tapped on the center of the status bar. > That way our apps could could respond to it by scrolling to the top. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CB-6107) Webview with statusbar plugin is 20px too tall
[ https://issues.apache.org/jira/browse/CB-6107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shazron Abdullah updated CB-6107: - Component/s: (was: Plugins) Plugin Statusbar > Webview with statusbar plugin is 20px too tall > -- > > Key: CB-6107 > URL: https://issues.apache.org/jira/browse/CB-6107 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Statusbar > Environment: iOS 7 iPad 3 >Reporter: Boston Dell-Vandenberg > Labels: statusbar-plugin > > If this is not the place to post issues for Cordova StatusBar plugin, > apologies in advance! > With the plugin installed, the webview is sized 20px too large which is > causing layout issues when I position elements on the bottom of the screen. > For example, on an iPad portrait it is 1044px and on landscape it is 788px. > Removing the plugin seems to bring it back to the correct dimensions of > 1024px x 768px. > The only values I set are StatusBarOverlaysWebView = true and color in > config.xml and the visibility via JS. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CB-5785) Status bar is initially transparent during startup
[
https://issues.apache.org/jira/browse/CB-5785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shazron Abdullah updated CB-5785:
-
Component/s: (was: Plugins)
(was: iOS)
Plugin Statusbar
> Status bar is initially transparent during startup
> --
>
> Key: CB-5785
> URL: https://issues.apache.org/jira/browse/CB-5785
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin Statusbar
>Affects Versions: 3.3.0
>Reporter: Jacob Weber
>Priority: Minor
> Labels: statusbar-plugin
> Attachments: statusbar.mov
>
>
> Not sure if this is a bug, but when you first launch an iOS app with the
> status bar set to not overlay the web view, the status bar is briefly
> transparent, before it gets its background color.
> Create a new project using the CLI, and install the splash screen and status
> bar plugins. Set the following in config.xml:
> {code}
>
> {code}
> When you first run the app, the status bar will be briefly transparent,
> overlaying the top of the splash screen. Then it will become black. See
> attached movie for an example.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (CB-5369) [ios] StatusBar plugin background thread warning
[ https://issues.apache.org/jira/browse/CB-5369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shazron Abdullah updated CB-5369: - Component/s: (was: Plugins) Plugin Statusbar > [ios] StatusBar plugin background thread warning > > > Key: CB-5369 > URL: https://issues.apache.org/jira/browse/CB-5369 > Project: Apache Cordova > Issue Type: Improvement > Components: Plugin Statusbar > Environment: Cordova 3.1.0 with version 0.1.2 of the StatusBar plugin >Reporter: Bas Bosman > Labels: statusbar-plugin > > My project throws the following warning: > THREAD WARNING: ['StatusBar'] took '56.696777' ms. Plugins should use a > background thread. > Can the plugin be modified to use a background thread or are there better > ways to fix this? -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CB-5511) Status bar plugin doesn't affect in-app browser
[ https://issues.apache.org/jira/browse/CB-5511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shazron Abdullah updated CB-5511: - Component/s: (was: Plugins) (was: Plugin InAppBrowser) (was: iOS) Plugin Statusbar > Status bar plugin doesn't affect in-app browser > --- > > Key: CB-5511 > URL: https://issues.apache.org/jira/browse/CB-5511 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Statusbar >Affects Versions: 3.1.0 >Reporter: Jacob Weber >Priority: Minor > Labels: statusbar-plugin > > If you use the status bar plugin on iOS, and set > StatusBarOverlaysWebView=false or StatusBarBackgroundColor, those settings > don't affect the in-app browser. So when you open an in-app browser, the > status bar will return to a transparent overlay. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CB-5849) Statusbar background is at the bottom on iPad in upsidedown portrait mode
[ https://issues.apache.org/jira/browse/CB-5849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shazron Abdullah updated CB-5849: - Component/s: (was: iOS) Plugin Statusbar > Statusbar background is at the bottom on iPad in upsidedown portrait mode > - > > Key: CB-5849 > URL: https://issues.apache.org/jira/browse/CB-5849 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Statusbar >Affects Versions: 3.3.0 >Reporter: Tim B. > Labels: statusbar-plugin > Attachments: Screenshot 2014-01-22 16.29.10.png > > > On the iPad the background of the statusbar is at the bottom of the screen > and not at the top when the app is started while the iPad is rotated 180° > from normal portrait mode (e.g. the Home Button is on top). > This is with StatusBarOverlaysWebView = false > Wanted to add screenshots, but apparently that requires Java ... ?? > Take a look at the attachement, the black bar at the bottom is supposed to be > where the white bar on the top is. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CB-5265) Status Bar Plugin/Camera Plugin. Taking a photo or choosing a photo from library makes the status bar style back to black.
[ https://issues.apache.org/jira/browse/CB-5265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shazron Abdullah updated CB-5265: - Component/s: (was: Plugins) (was: iOS) Plugin Statusbar > Status Bar Plugin/Camera Plugin. Taking a photo or choosing a photo from > library makes the status bar style back to black. > -- > > Key: CB-5265 > URL: https://issues.apache.org/jira/browse/CB-5265 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Statusbar >Affects Versions: 3.1.0 > Environment: iOS 7 >Reporter: Daniel Morgan > Labels: camera, ios7, statusbar-plugin > > We're using a black status bar and the StatusBarStyleLightContent to simulate > the pre-iOS 7 status bar with the status bar plugin. When a user takes a > photo or choose from library the status bar style goes back to black; making > a black status bar with black text. My quick fix is to add in CDVCamera > under navigationController:willShowViewController:animated to set the status > bar style back to white: [[UIApplication sharedApplication] > setStatusBarStyle:UIStatusBarStyleLightContent];, but of course this only > works for me since I want the status bar style to be white everywhere in my > application. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CB-5439) Status Bar Plugin pushes web view too far down when a personal hotspot connection is active while using overlaysWebView(false)
[
https://issues.apache.org/jira/browse/CB-5439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shazron Abdullah updated CB-5439:
-
Component/s: (was: Plugins)
(was: iOS)
Plugin Statusbar
> Status Bar Plugin pushes web view too far down when a personal hotspot
> connection is active while using overlaysWebView(false)
> --
>
> Key: CB-5439
> URL: https://issues.apache.org/jira/browse/CB-5439
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin Statusbar
>Affects Versions: 3.1.0
>Reporter: Sepp Wijnands
>Priority: Minor
> Labels: statusbar-plugin
> Fix For: 3.5.0
>
>
> When a personal hotspot connection is active or a call is in progress, the
> statusbar occupies two rows.
> If StatusBar.overlaysWebView(false) is used, it causes the webview to be
> pushed further down than it should: Exactly 3 rows instead of 2.
> Steps to reproduce the problem:
> # Enable Personal Hotspot or make sure a call is in progress
> # Open/resume Cordova application that uses
> StatusBar.overlaysWebView(false);
> Screenshot depicting the problem:
> https://www.dropbox.com/s/u47sucujs19g2py/Screenshot%202013.11.19%2010.44.00.png
> Screenshot of application when no call/connection is in progress:
> https://www.dropbox.com/s/n2eiyem7a7wfk7j/Screenshot%202013.11.19%2010.44.45.png
> The red line at the top in the above pictures is made using the following (to
> annotate that it really is the web view that is being pushed down):
> {code}
> body {
> border-top: 2px solid red;
> }
> {code}
> Example project:
> https://www.dropbox.com/s/0yzarp1sioamgud/BugStatusBarPushDown.zip
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (CB-5893) Using StatusBar with StatusBarOverlaysWebView = false on iPad creates only 20px wide webview frame
[
https://issues.apache.org/jira/browse/CB-5893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shazron Abdullah updated CB-5893:
-
Component/s: (was: Plugins)
(was: iOS)
Plugin Statusbar
> Using StatusBar with StatusBarOverlaysWebView = false on iPad creates only
> 20px wide webview frame
> --
>
> Key: CB-5893
> URL: https://issues.apache.org/jira/browse/CB-5893
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin Statusbar
>Affects Versions: 3.3.0
> Environment: iOS 7, iPad (2, iPad Mini (retina), iPad Air)
>Reporter: Hans-Gunther Schmidt
> Labels: statusbar-plugin
>
> When using the statusbar plugin (org.apache.cordova.statusbar) in a Cordova
> (and PhoneGap) app built for iOS we experience an issue on iPads: when
> opening the app on an iPad in *Landscape* (left, right) mode, the whole
> webview seems to only be contained in an 20px by viewable
> frame (basically we can only see parts of our header bar).
> How to reproduce:
> {code}
> $ npm install -g cordova
> $ cordova create hello com.example.hello Hello
> $ cd hello
> $ cordova platform add ios
> $ cordova plugin add org.apache.cordova.statusbar
> $ cordova build ios
> {code}
> Then create an iOS build as given below:
> - open {{platforms/ios/Hello.xcodeproj/}} in Xcode
> - adapt {{StatusBarOverlaysWebView}} in {{config.xml}}:
> {code}
>
> {code}
> to
> {code}
>
> {code}
> - set target device to _iPhone_ (= not _Universal_)
> - set target version _7.0_
> - set device orientation to _Portrait_ (= not _Upside Down_, _Landscape left
> | right_)
> - physically turn your connected iPad into either landscape left/right
> position
> - deploy to your iPad
> Happens to us with iPad 2, iPad Air and iPad Mini (retina) with Cordova
> *3.3.1-0.1.2*. We also see this issue when using PhoneGap *3.1.0-0.15.0* and
> *3.3.0-0.19.1*.
> From poking around and adding log messages to {{setStatusBarOverlaysWebView}}
> we do see that the calculated values might be incorrect.
> {code:title=|borderStyle=solid}
> - (void) setStatusBarOverlaysWebView:(BOOL)statusBarOverlaysWebView
> {
> // we only care about the latest iOS version or a change in setting
> if (!IsAtLeastiOSVersion(@"7.0") || statusBarOverlaysWebView ==
> _statusBarOverlaysWebView) {
> return;
> }
> CGRect bounds = [[UIScreen mainScreen] bounds];
>
> if (statusBarOverlaysWebView) {
>
> [_statusBarBackgroundView removeFromSuperview];
> self.webView.frame = bounds;
> } else {
> CGRect statusBarFrame = [UIApplication
> sharedApplication].statusBarFrame;
> [self initializeStatusBarBackgroundView];
> CGRect frame = self.webView.frame;
> if
> (UIDeviceOrientationIsLandscape(self.viewController.interfaceOrientation)) {
> frame.origin.y = statusBarFrame.size.width;
> frame.size.height -= statusBarFrame.size.width;
> } else {
> frame.origin.y = statusBarFrame.size.height;
> frame.size.height -= statusBarFrame.size.height;
> }
>
> NSLog(@"frame | %f | %f | %f | %f |", frame.origin.x,
> frame.origin.y, frame.size.width, frame.size.height);
> self.webView.frame = frame;
> NSLog(@"self.webview.frame | %f | %f | %f | %f |",
> self.webView.frame.origin.x, self.webView.frame.origin.y,
> self.webView.frame.size.width, self.webView.frame.size.height);
> [self.webView.superview addSubview:_statusBarBackgroundView];
> }
>
> _statusBarOverlaysWebView = statusBarOverlaysWebView;
> }
> {code}
> The NSLog statements will print out:
> {code:title=log output|borderStyle=solid}
> [...]
> 2014-01-24 18:17:02.780 HelloCord[7877:60b] frame | 0.00 | 480.00 |
> 320.00 | -20.00 |
> 2014-01-24 18:17:02.783 HelloCord[7877:60b] self.webview.frame | 0.00 |
> 460.00 | 320.00 | 20.00 |
> [...]
> {code}
> This would (and does) translate into a webview frame (when holding the iPad
> back in Portrait mode again):
> - x = 0 (OK)
> - y = 460px (all the way down ... NOT OK)
> - width = 320px (from left to right screen border ... OK)
> - height = 20px (NOT OK)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CB-5920) android:installLocation="preferExternal"
[ https://issues.apache.org/jira/browse/CB-5920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13934220#comment-13934220 ] Frederico Costa Galvão commented on CB-5920: What is it other than *AndroidManifest.xml*? I've used this on a 2.1-2.9 app with no changes to cordova stuff with no issues, so if there's anything needed it didn't affect me until now. > android:installLocation="preferExternal" > > > Key: CB-5920 > URL: https://issues.apache.org/jira/browse/CB-5920 > Project: Apache Cordova > Issue Type: Improvement > Components: Android, CLI > Environment: Phones with 512 Ram >Reporter: cesine > Labels: patch > > I created a PR on github suggesting to add preferExternal > https://github.com/apache/cordova-android/pull/91#issuecomment-33513325 > for phones with small amounts of internal storage (512MB and even 1GB, > android 2.2 and 2.3 and even some 4.0) the user wont be able to install the > app (or keep it) unless you let them put it on the sdcard instead of the > internal phone storage. Very few cordova apps are the kind of app which > shouldn't be on external storage. > more details: > http://developer.android.com/guide/topics/data/install-location.html#Should -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-5814) Android's cordova/emulate command sometimes never exits
[ https://issues.apache.org/jira/browse/CB-5814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13934244#comment-13934244 ] Victor Adrian Sosa Herrera commented on CB-5814: I found this defect in Cordova 3.4 in Windows 7 > Android's cordova/emulate command sometimes never exits > --- > > Key: CB-5814 > URL: https://issues.apache.org/jira/browse/CB-5814 > Project: Apache Cordova > Issue Type: Bug > Components: Android > Environment: Windows >Reporter: Andrew Grieve >Priority: Minor > > Need to confirm whether this happens on *nix as well, but I know it's the > case on Windows. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-1291) Windows 8 Contacts - Find+Create APIs
[ https://issues.apache.org/jira/browse/CB-1291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13934657#comment-13934657 ] ASF subversion and git services commented on CB-1291: - Commit b1ec0bc49ca291c559d8a9b583ee8b192c21ca75 in cordova-plugin-contacts's branch refs/heads/master from [~purplecabbage] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-contacts.git;h=b1ec0bc ] CB-1291 Windows8 added some contact conversion, console.error on save because it is not supported > Windows 8 Contacts - Find+Create APIs > - > > Key: CB-1291 > URL: https://issues.apache.org/jira/browse/CB-1291 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Contacts, Windows 8 >Reporter: Jesse MacFadyen >Assignee: Jesse MacFadyen > > It looks like we will need to approach Contacts on Windows 8 differently. > The goal of the Contacts API is not to have every app become a > ContactProvider, which would result in chaos ... > Windows 8 does not have built in contacts, they are managed internally by the > People app. The People app is a ContactProvider so when you are performing > an operation that requires a contact, you are given the opportunity to select > one or more contacts from the People app, as well as every other app that > publishes the ContactProvider contract. > Searching contacts cannot be achieved given Windows 8 APIs and interaction > with the People app, but the primary use case of picking one or more contacts > to interact with can work. > I think the best approach would be to return a contact object as defined by > PhoneGap APIs, but allow the user to actually do the selection ( via the > picker ) > Here is a good write-up by a Microsoft evangelist about how contacts work on > Windows 8. > http://blogs.msdn.com/b/glengordon/archive/2012/08/28/windows-8-apps-for-the-phonegap-developer-contacts.aspx -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-1291) Windows 8 Contacts - Find+Create APIs
[ https://issues.apache.org/jira/browse/CB-1291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13934656#comment-13934656 ] ASF subversion and git services commented on CB-1291: - Commit 04b96dc9426cc0c2504f0a36ba9acacb4ce52e6a in cordova-plugin-contacts's branch refs/heads/master from [~purplecabbage] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-contacts.git;h=04b96dc ] CB-1291 Windows8 Adding contact picker apis > Windows 8 Contacts - Find+Create APIs > - > > Key: CB-1291 > URL: https://issues.apache.org/jira/browse/CB-1291 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Contacts, Windows 8 >Reporter: Jesse MacFadyen >Assignee: Jesse MacFadyen > > It looks like we will need to approach Contacts on Windows 8 differently. > The goal of the Contacts API is not to have every app become a > ContactProvider, which would result in chaos ... > Windows 8 does not have built in contacts, they are managed internally by the > People app. The People app is a ContactProvider so when you are performing > an operation that requires a contact, you are given the opportunity to select > one or more contacts from the People app, as well as every other app that > publishes the ContactProvider contract. > Searching contacts cannot be achieved given Windows 8 APIs and interaction > with the People app, but the primary use case of picking one or more contacts > to interact with can work. > I think the best approach would be to return a contact object as defined by > PhoneGap APIs, but allow the user to actually do the selection ( via the > picker ) > Here is a good write-up by a Microsoft evangelist about how contacts work on > Windows 8. > http://blogs.msdn.com/b/glengordon/archive/2012/08/28/windows-8-apps-for-the-phonegap-developer-contacts.aspx -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-1291) Windows 8 Contacts - Find+Create APIs
[ https://issues.apache.org/jira/browse/CB-1291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13934658#comment-13934658 ] ASF subversion and git services commented on CB-1291: - Commit 92ebe1aaf95de85d95b319fba11570605eea4706 in cordova-plugin-contacts's branch refs/heads/master from [~purplecabbage] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-contacts.git;h=92ebe1a ] Merge pull request #1 from purplecabbage/CB-1291-Windows8 Cb 1291 windows8 > Windows 8 Contacts - Find+Create APIs > - > > Key: CB-1291 > URL: https://issues.apache.org/jira/browse/CB-1291 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Contacts, Windows 8 >Reporter: Jesse MacFadyen >Assignee: Jesse MacFadyen > > It looks like we will need to approach Contacts on Windows 8 differently. > The goal of the Contacts API is not to have every app become a > ContactProvider, which would result in chaos ... > Windows 8 does not have built in contacts, they are managed internally by the > People app. The People app is a ContactProvider so when you are performing > an operation that requires a contact, you are given the opportunity to select > one or more contacts from the People app, as well as every other app that > publishes the ContactProvider contract. > Searching contacts cannot be achieved given Windows 8 APIs and interaction > with the People app, but the primary use case of picking one or more contacts > to interact with can work. > I think the best approach would be to return a contact object as defined by > PhoneGap APIs, but allow the user to actually do the selection ( via the > picker ) > Here is a good write-up by a Microsoft evangelist about how contacts work on > Windows 8. > http://blogs.msdn.com/b/glengordon/archive/2012/08/28/windows-8-apps-for-the-phonegap-developer-contacts.aspx -- This message was sent by Atlassian JIRA (v6.2#6252)
