[jira] [Commented] (CB-5634) Orientation Preference is ignored in Android, should be parsed by CLI
[ https://issues.apache.org/jira/browse/CB-5634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13887504#comment-13887504 ] Darryl Pogue commented on CB-5634: -- I have a patch to cordova-cli for Android that correctly handles parses the orientation: https://github.com/apache/cordova-cli/pull/112 > Orientation Preference is ignored in Android, should be parsed by CLI > - > > Key: CB-5634 > URL: https://issues.apache.org/jira/browse/CB-5634 > Project: Apache Cordova > Issue Type: Bug > Components: Amazon FireOS, Android, CLI, Docs, iOS >Reporter: Joe Bowser > > The docs say that an Orientation preference is supposed to work across all > platforms. However, Android's activities can only be locked to an > orientation by modifying the AndroidManifest.xml. > To get past this, we either change the docs, or we support this in the CLI. > I feel that adding an XML parser to the scripts is complete overkill, since > we don't have any tests for our platform scripts, and I personally think > they're a giant pile of technical debt. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (CB-6015) FileTransfer error: Read-Only filesystem
Darryl Pogue created CB-6015:
Summary: FileTransfer error: Read-Only filesystem
Key: CB-6015
URL: https://issues.apache.org/jira/browse/CB-6015
Project: Apache Cordova
Issue Type: Bug
Components: Android, Plugin File, Plugin File Transfer
Affects Versions: 3.3.0
Reporter: Darryl Pogue
Using the FileTransfer plugin to write to a FileEntry returned from the File
plugin results in an error.
{code}
D/FileTransfer(12423): download http://example.com/image.jpeg to //avatar.jpeg
E/FileTransfer(12423):
{"target":"\/\/avatar.jpeg","source":"http:\/\/example.com\/image.jpeg","http_status":0,"code":1}
E/FileTransfer(12423): java.io.FileNotFoundException: /avatar.jpeg: open
failed: EROFS (Read-only file system)
E/FileTransfer(12423): at libcore.io.IoBridge.open(IoBridge.java:409)
E/FileTransfer(12423): at
java.io.FileOutputStream.(FileOutputStream.java:88)
E/FileTransfer(12423): at
org.apache.cordova.CordovaResourceApi.openOutputStream(CordovaResourceApi.java:293)
E/FileTransfer(12423): at
org.apache.cordova.CordovaResourceApi.openOutputStream(CordovaResourceApi.java:274)
E/FileTransfer(12423): at
org.apache.cordova.filetransfer.FileTransfer$4.run(FileTransfer.java:708)
E/FileTransfer(12423): at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1080)
E/FileTransfer(12423): at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:573)
E/FileTransfer(12423): at java.lang.Thread.run(Thread.java:841)
E/FileTransfer(12423): Caused by: libcore.io.ErrnoException: open failed: EROFS
(Read-only file system)
E/FileTransfer(12423): at libcore.io.Posix.open(Native Method)
E/FileTransfer(12423): at libcore.io.BlockGuardOs.open(BlockGuardOs.java:110)
E/FileTransfer(12423): at libcore.io.IoBridge.open(IoBridge.java:393)
E/FileTransfer(12423): ... 7 more
{code}
This worked correctly before upgrading the file plugin.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Resolved] (CB-6015) FileTransfer error: Read-Only filesystem
[
https://issues.apache.org/jira/browse/CB-6015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darryl Pogue resolved CB-6015.
--
Resolution: Not A Problem
Fix Version/s: 3.3.0
> FileTransfer error: Read-Only filesystem
>
>
> Key: CB-6015
> URL: https://issues.apache.org/jira/browse/CB-6015
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android, Plugin File, Plugin File Transfer
>Affects Versions: 3.3.0
>Reporter: Darryl Pogue
>Assignee: Ian Clelland
> Fix For: 3.3.0
>
>
> Using the FileTransfer plugin to write to a FileEntry returned from the File
> plugin results in an error.
> {code}
> D/FileTransfer(12423): download http://example.com/image.jpeg to //avatar.jpeg
> E/FileTransfer(12423):
> {"target":"\/\/avatar.jpeg","source":"http:\/\/example.com\/image.jpeg","http_status":0,"code":1}
> E/FileTransfer(12423): java.io.FileNotFoundException: /avatar.jpeg: open
> failed: EROFS (Read-only file system)
> E/FileTransfer(12423):at libcore.io.IoBridge.open(IoBridge.java:409)
> E/FileTransfer(12423):at
> java.io.FileOutputStream.(FileOutputStream.java:88)
> E/FileTransfer(12423):at
> org.apache.cordova.CordovaResourceApi.openOutputStream(CordovaResourceApi.java:293)
> E/FileTransfer(12423):at
> org.apache.cordova.CordovaResourceApi.openOutputStream(CordovaResourceApi.java:274)
> E/FileTransfer(12423):at
> org.apache.cordova.filetransfer.FileTransfer$4.run(FileTransfer.java:708)
> E/FileTransfer(12423):at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1080)
> E/FileTransfer(12423):at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:573)
> E/FileTransfer(12423):at java.lang.Thread.run(Thread.java:841)
> E/FileTransfer(12423): Caused by: libcore.io.ErrnoException: open failed:
> EROFS (Read-only file system)
> E/FileTransfer(12423):at libcore.io.Posix.open(Native Method)
> E/FileTransfer(12423):at
> libcore.io.BlockGuardOs.open(BlockGuardOs.java:110)
> E/FileTransfer(12423):at libcore.io.IoBridge.open(IoBridge.java:393)
> E/FileTransfer(12423):... 7 more
> {code}
> This worked correctly before upgrading the file plugin.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (CB-6015) FileTransfer error: Read-Only filesystem
[
https://issues.apache.org/jira/browse/CB-6015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899358#comment-13899358
]
Darryl Pogue commented on CB-6015:
--
Yep, {{fullPath}} vs {{toURL()}} was the issue. Thanks!
> FileTransfer error: Read-Only filesystem
>
>
> Key: CB-6015
> URL: https://issues.apache.org/jira/browse/CB-6015
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android, Plugin File, Plugin File Transfer
>Affects Versions: 3.3.0
>Reporter: Darryl Pogue
>Assignee: Ian Clelland
>
> Using the FileTransfer plugin to write to a FileEntry returned from the File
> plugin results in an error.
> {code}
> D/FileTransfer(12423): download http://example.com/image.jpeg to //avatar.jpeg
> E/FileTransfer(12423):
> {"target":"\/\/avatar.jpeg","source":"http:\/\/example.com\/image.jpeg","http_status":0,"code":1}
> E/FileTransfer(12423): java.io.FileNotFoundException: /avatar.jpeg: open
> failed: EROFS (Read-only file system)
> E/FileTransfer(12423):at libcore.io.IoBridge.open(IoBridge.java:409)
> E/FileTransfer(12423):at
> java.io.FileOutputStream.(FileOutputStream.java:88)
> E/FileTransfer(12423):at
> org.apache.cordova.CordovaResourceApi.openOutputStream(CordovaResourceApi.java:293)
> E/FileTransfer(12423):at
> org.apache.cordova.CordovaResourceApi.openOutputStream(CordovaResourceApi.java:274)
> E/FileTransfer(12423):at
> org.apache.cordova.filetransfer.FileTransfer$4.run(FileTransfer.java:708)
> E/FileTransfer(12423):at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1080)
> E/FileTransfer(12423):at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:573)
> E/FileTransfer(12423):at java.lang.Thread.run(Thread.java:841)
> E/FileTransfer(12423): Caused by: libcore.io.ErrnoException: open failed:
> EROFS (Read-only file system)
> E/FileTransfer(12423):at libcore.io.Posix.open(Native Method)
> E/FileTransfer(12423):at
> libcore.io.BlockGuardOs.open(BlockGuardOs.java:110)
> E/FileTransfer(12423):at libcore.io.IoBridge.open(IoBridge.java:393)
> E/FileTransfer(12423):... 7 more
> {code}
> This worked correctly before upgrading the file plugin.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Created] (CB-6033) Android 4.4 update loses LocalStorage data
Darryl Pogue created CB-6033: Summary: Android 4.4 update loses LocalStorage data Key: CB-6033 URL: https://issues.apache.org/jira/browse/CB-6033 Project: Apache Cordova Issue Type: Bug Components: Android Reporter: Darryl Pogue Priority: Critical This appears to be a result of the switch from old WebView to the new Chrome-powered WebView. If an app is installed in 4.3 and saves data to LocalStorage (and possibly to WebSQL) and then the device is updated to 4.4, that data appears to be lost. Some threads regarding the problem: http://www.sencha.com/forum/showthread.php?278158-localStorage-cleared-when-upgrading-to-KitKat-(Android-4.4) https://groups.google.com/forum/#!msg/phonegap/rNizMKW5GaA/g1XBBco2otMJ -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (CB-6090) CLI should not error on build command for firefoxos
[ https://issues.apache.org/jira/browse/CB-6090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010776#comment-14010776 ] Darryl Pogue commented on CB-6090: -- This issue is resolved in Cordova FirefoxOS 3.5.0. > CLI should not error on build command for firefoxos > --- > > Key: CB-6090 > URL: https://issues.apache.org/jira/browse/CB-6090 > Project: Apache Cordova > Issue Type: Bug > Components: CLI, FirefoxOS >Affects Versions: 3.4.0 > Environment: osx > $ cordova -v > 3.4.0-0.1.0 >Reporter: Carlos Santana > > cordova should not error when running 'cordova build firefoxos" > firefox platform already handle with a nice message that the command is not > applicable for other commands like "emulate" and "run" > same should be done for build > recreate: > (master)$ cordova create todd-firefoxos com.example.todd TODD > Creating a new cordova project with name "TODD" and id "com.example.todd" at > location > "/Users/csantana23/Documents/SWG/git/csantanapr/triangle-open-data-day/hybridApp/todd-firefoxos" > (master)$ cd todd-firefoxos/ > (master)$ cordova platform add firefoxos > Creating firefoxos project... > Creating Firefox OS project > Project Path > ../../../../../../../git/csantanapr/triangle-open-data-day/hybridApp/todd-firefoxos/platforms/firefoxos > Package Name com.example.todd > Project Name TODD > Generating config.xml from defaults for platform "firefoxos" > Preparing firefoxos project > (master)$ cordova build > Generating config.xml from defaults for platform "firefoxos" > Preparing firefoxos project > Running command: > /Users/csantana23/git/csantanapr/triangle-open-data-day/hybridApp/todd-firefoxos/platforms/firefoxos/cordova/build > args=[] > execvp(): No such file or directory > Error: > /Users/csantana23/git/csantanapr/triangle-open-data-day/hybridApp/todd-firefoxos/platforms/firefoxos/cordova/build: > Command failed with exit code ENOENT > at ChildProcess.whenDone > (/Users/csantana23/.nvm/v0.10.24/lib/node_modules/cordova/src/superspawn.js:112:23) > at ChildProcess.EventEmitter.emit (events.js:95:17) > at Process.ChildProcess._handle.onexit (child_process.js:787:12) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-5751) FirefoxOS build issue
[ https://issues.apache.org/jira/browse/CB-5751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010779#comment-14010779 ] Darryl Pogue commented on CB-5751: -- This issue should be resolved in Cordova FirefoxOS 3.5.0. > FirefoxOS build issue > - > > Key: CB-5751 > URL: https://issues.apache.org/jira/browse/CB-5751 > Project: Apache Cordova > Issue Type: Bug > Components: CLI, FirefoxOS >Affects Versions: 3.3.0 > Environment: Windows 7 amd64 > Cordova 3.3.1-0.1.2 > nodejs v0.10.24 >Reporter: Vincenzo >Assignee: Gert-Jan Braas > Fix For: 3.6.0 > > > After typing > cordova platform add firefoxos > and > cordova build > I read this error: > C:\Users\Utente\AppData\Roaming\npm\node_modules\cordova\node_modules\q\q.js:126 > throw e; > ^ > Error: An error occurred while building the firefoxos > project."c:\Linkpass\platf > orms\firefoxos\cordova\build" non ´┐¢ riconosciuto come comando interno o > estern > o, > un programma eseguibile o un file batch. > at ChildProcess. > (C:\Users\Utente\AppData\Roaming\npm\node_module > s\cordova\src\compile.js:65:22) > at ChildProcess.EventEmitter.emit (events.js:98:17) > at maybeClose (child_process.js:735:16) > at Socket. (child_process.js:948:11) > at Socket.EventEmitter.emit (events.js:95:17) > at Pipe.close (net.js:466:12) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-4556) Add a ./cordova/clean project-level script
[ https://issues.apache.org/jira/browse/CB-4556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010783#comment-14010783 ] Darryl Pogue commented on CB-4556: -- This script exists in Cordova FirefoxOS 3.5.0, but does not have a corresponding .bat file. > Add a ./cordova/clean project-level script > -- > > Key: CB-4556 > URL: https://issues.apache.org/jira/browse/CB-4556 > Project: Apache Cordova > Issue Type: Sub-task > Components: FirefoxOS >Reporter: Steve Gill > > This script should delete any build artifacts that are create from running an > app compilation. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CB-5711) Keyboard plugin w/ shrinkView breaks when switching between different keyboards
[
https://issues.apache.org/jira/browse/CB-5711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14035904#comment-14035904
]
Darryl Pogue commented on CB-5711:
--
Should be fixed in master by
https://git-wip-us.apache.org/repos/asf?p=cordova-plugins.git;a=commit;h=34912f80900b9d23bdf09997a19dd9dee21aa86e
> Keyboard plugin w/ shrinkView breaks when switching between different
> keyboards
> ---
>
> Key: CB-5711
> URL: https://issues.apache.org/jira/browse/CB-5711
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin Keyboard
>Affects Versions: 3.2.0
>Reporter: Stuart Parmenter
> Labels: keyboard-plugin
>
> If you have an followed by an or an
> they all show different keyboards and fire
> UIKeyboardWillShowNotification without firing UIKeyboardWillHideNotification.
> This causes the shrink code to happen multiple times.
> The easiest fix is to add a check in shrinkViewKeyboardWillShow:
> if (self.keyboardIsVisible) {
> return;
> }
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (CB-6974) Keyboard causes input focus issue
Darryl Pogue created CB-6974:
Summary: Keyboard causes input focus issue
Key: CB-6974
URL: https://issues.apache.org/jira/browse/CB-6974
Project: Apache Cordova
Issue Type: Bug
Components: Plugin Keyboard
Affects Versions: 3.5.0
Environment: iOS 6.1
Reporter: Darryl Pogue
I've confirmed that this issue is caused by the keyboard plugin, because it
does not happen when the keyboard plugin is disabled.
If there is an input on the lower half of the page, when it is tapped, the
keyboard will slide up, covering the input and not putting it in focus.
In my config file I have the following:
{code:xml|title=config.xml}
{code}
This appears to only happen when the input is on a page that is absolutely
positioned.
The best reference I can find about the issue is
http://www.telerik.com/forums/click-on-input-levels-up-the-footer-on-the-keyboard-whitout-change-the-view-!-
but the suggested change of setting the body height on deviceReady didn't work
for me.
It does not appear to be related to the status bar (as potentially stated in
that thread). Removing the status bar plugin did not fix the problem.
My guess is that it's related to hiding the accessory bar and intercepting the
keyboard opening in Objective C, but I don't know enough about ObjC to know
what would cause the focus to be lost :(
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (CB-6974) Keyboard causes input focus issue
[
https://issues.apache.org/jira/browse/CB-6974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14036384#comment-14036384
]
Darryl Pogue commented on CB-6974:
--
This only happens if {{KeyboardShrinksView}} is true in config.xml.
> Keyboard causes input focus issue
> -
>
> Key: CB-6974
> URL: https://issues.apache.org/jira/browse/CB-6974
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin Keyboard
>Affects Versions: 3.5.0
> Environment: iOS 6.1
>Reporter: Darryl Pogue
> Labels: iOS
>
> I've confirmed that this issue is caused by the keyboard plugin, because it
> does not happen when the keyboard plugin is disabled.
> If there is an input on the lower half of the page, when it is tapped, the
> keyboard will slide up, covering the input and not putting it in focus.
> In my config file I have the following:
> {code:xml|title=config.xml}
>
>
> />
> {code}
> This appears to only happen when the input is on a page that is absolutely
> positioned.
> The best reference I can find about the issue is
> http://www.telerik.com/forums/click-on-input-levels-up-the-footer-on-the-keyboard-whitout-change-the-view-!-
> but the suggested change of setting the body height on deviceReady didn't
> work for me.
> It does not appear to be related to the status bar (as potentially stated in
> that thread). Removing the status bar plugin did not fix the problem.
> My guess is that it's related to hiding the accessory bar and intercepting
> the keyboard opening in Objective C, but I don't know enough about ObjC to
> know what would cause the focus to be lost :(
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (CB-9525) Dependent plugins not restored with versions from config.xml
Darryl Pogue created CB-9525:
Summary: Dependent plugins not restored with versions from
config.xml
Key: CB-9525
URL: https://issues.apache.org/jira/browse/CB-9525
Project: Apache Cordova
Issue Type: Bug
Components: CordovaLib
Affects Versions: 5.2.0
Environment: OSX
Reporter: Darryl Pogue
When I have a config.xml that uses a custom git branch of the
cordova-plugin-file and the npm version of cordova-plugin-file-transfer, the
npm version of cordova-plugin-file is installed before the git branch. This
causes the app to use the npm version rather than the git branch as specified
in config.xml.
Test case:
Create a new cordova project, replace the config.xml with the following, run
cordova prepare.
{code:xml}
http://www.w3.org/ns/widgets";
xmlns:cdv="http://cordova.apache.org/ns/1.0";>
HelloCordova
A sample Apache Cordova application that responds to the deviceready
event.
http://cordova.io";>
Apache Cordova Team
http://*/*"; />
https://*/*"; />
mailto:*"; />
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-9693) Spaces in project name cause index.html to fail to load in cordova-ios 4.0.0-dev
Darryl Pogue created CB-9693: Summary: Spaces in project name cause index.html to fail to load in cordova-ios 4.0.0-dev Key: CB-9693 URL: https://issues.apache.org/jira/browse/CB-9693 Project: Apache Cordova Issue Type: Bug Components: iOS Affects Versions: Master Reporter: Darryl Pogue If the project name in config.xml has a space in it, when building with cordova-ios@4.0.0-dev it will succeed but fail to load the www/index.html file. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-9693) Spaces in project name cause index.html to fail to load in cordova-ios 4.0.0-dev
[ https://issues.apache.org/jira/browse/CB-9693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darryl Pogue updated CB-9693: - Description: If the project name in config.xml has a space in it, when building with cordova-ios@4.0.0-dev it will succeed but fail to load the www/index.html file. This works correctly in cordova-ios@3.9.1 was:If the project name in config.xml has a space in it, when building with cordova-ios@4.0.0-dev it will succeed but fail to load the www/index.html file. > Spaces in project name cause index.html to fail to load in cordova-ios > 4.0.0-dev > > > Key: CB-9693 > URL: https://issues.apache.org/jira/browse/CB-9693 > Project: Apache Cordova > Issue Type: Bug > Components: iOS >Affects Versions: Master >Reporter: Darryl Pogue > > If the project name in config.xml has a space in it, when building with > cordova-ios@4.0.0-dev it will succeed but fail to load the www/index.html > file. > This works correctly in cordova-ios@3.9.1 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-10239) Installing platforms from scoped npm packages
Darryl Pogue created CB-10239:
-
Summary: Installing platforms from scoped npm packages
Key: CB-10239
URL: https://issues.apache.org/jira/browse/CB-10239
Project: Apache Cordova
Issue Type: Improvement
Components: CordovaLib
Affects Versions: 3.5.0
Reporter: Darryl Pogue
I have a bugfix branch for a platform, and while waiting for it to be merged
and released, I published my fork of that platform to a scoped package on npm
(i.e., @dpogue/cordova-android).
In config.xml, there does not appear to be a way to specify that {{cordova
prepare}} should restore that scoped package instead of the canonical Apache
one.
\\
Attempt #1:
{code:xml}
{code}
results in a warning being printed about a null or unrecognized platform.
\\
Attempt #2:
{code:xml}
{code}
results in pulling the Apache version from npm, ignoring my scoped package.
A workaround for now is to use a git URL, but the advantage of npm is that it
can download a tarball without the network cost of doing a full git clone.
\\
Also worth noting that scoped npm packages are supported with plugins:
{code:xml}
{code}
works as intended.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-2606) Add support for elements in config.xml
[
https://issues.apache.org/jira/browse/CB-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13593067#comment-13593067
]
Darryl Pogue commented on CB-2606:
--
Do the icons need to live under {{www}}?
It seems a bit wasteful to include all the icons for all the platforms in each
platform's binary, while the actual icon used by the platform is probably
duplicated somewhere else by the build process.
I know the savings are relatively small, but on a project I just generated with
the CLI tools the {{www/res/}} directory totals 6.8 MB (containing both icons
and splash screens).
> Add support for elements in config.xml
> -
>
> Key: CB-2606
> URL: https://issues.apache.org/jira/browse/CB-2606
> Project: Apache Cordova
> Issue Type: Sub-task
> Components: Docs
>Reporter: Filip Maj
>Assignee: Filip Maj
> Fix For: 2.6.0
>
>
> This feature would add support for specifying the application icon by
> changing values inside the {{config.xml}} document.
> Relevant details for Cordova:
> - {{}} elements _may_ have {{width}} and {{height}} attributes
> representing the preferred size of the icon in CSS pixels.
> - {{}} elements _must_ have a {{src}} attribute, which contains a path
> string relative to the {{www/}} folder (or equivalent) in the platform.
> See [the Widget Spec's section on
> icons|http://www.w3.org/TR/widgets/#the-icon-element-and-its-attributes] for
> specifics.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-2606) Add support for elements in config.xml
[
https://issues.apache.org/jira/browse/CB-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13593846#comment-13593846
]
Darryl Pogue commented on CB-2606:
--
The project structure from the CLI tools right now is
{code}[projectname]
|- platforms/
|- plugins/
`- www/
{code}
It seems like having a {{res/}} folder there at the top level (instead of under
{{www/}} would allow the icons to be easily referenced, but not bundled with
the app.
I guess you could reference them as {{"../res/"}} in config.xml, but it's not
clear if the config.xml is read before copying to the platform (where it would
work) or after (where {{../res/}} wouldn't exist).
> Add support for elements in config.xml
> -
>
> Key: CB-2606
> URL: https://issues.apache.org/jira/browse/CB-2606
> Project: Apache Cordova
> Issue Type: Sub-task
> Components: Docs
>Reporter: Filip Maj
>Assignee: Filip Maj
> Fix For: 2.6.0
>
>
> This feature would add support for specifying the application icon by
> changing values inside the {{config.xml}} document.
> Relevant details for Cordova:
> - {{}} elements _may_ have {{width}} and {{height}} attributes
> representing the preferred size of the icon in CSS pixels.
> - {{}} elements _must_ have a {{src}} attribute, which contains a path
> string relative to the {{www/}} folder (or equivalent) in the platform.
> See [the Widget Spec's section on
> icons|http://www.w3.org/TR/widgets/#the-icon-element-and-its-attributes] for
> specifics.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CB-7598) Support 9-patch splashscreen images for Android
Darryl Pogue created CB-7598: Summary: Support 9-patch splashscreen images for Android Key: CB-7598 URL: https://issues.apache.org/jira/browse/CB-7598 Project: Apache Cordova Issue Type: Bug Components: Android, CLI, CordovaLib Affects Versions: 3.5.0 Reporter: Darryl Pogue Priority: Minor If a splashscreen image for Android is specified in config.xml and ends with `.9.png`, it is a 9-patch image and should retain that extension when copied into the platforms/android directory. Currently the file will be renamed to `screen.png` when it should be `screen.9.png`. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CB-7598) Support 9-patch splashscreen images for Android
[
https://issues.apache.org/jira/browse/CB-7598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darryl Pogue updated CB-7598:
-
Description:
If a splashscreen image for Android is specified in config.xml and ends with
{{.9.png}}, it is a 9-patch image and should retain that extension when copied
into the platforms/android directory.
Currently the file will be renamed to {{screen.png}} when it should be
{{screen.9.png}}.
was:
If a splashscreen image for Android is specified in config.xml and ends with
`.9.png`, it is a 9-patch image and should retain that extension when copied
into the platforms/android directory.
Currently the file will be renamed to `screen.png` when it should be
`screen.9.png`.
> Support 9-patch splashscreen images for Android
> ---
>
> Key: CB-7598
> URL: https://issues.apache.org/jira/browse/CB-7598
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android, CLI, CordovaLib
>Affects Versions: 3.5.0
>Reporter: Darryl Pogue
>Priority: Minor
>
> If a splashscreen image for Android is specified in config.xml and ends with
> {{.9.png}}, it is a 9-patch image and should retain that extension when
> copied into the platforms/android directory.
> Currently the file will be renamed to {{screen.png}} when it should be
> {{screen.9.png}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CB-7836) Control output .apk filename
[
https://issues.apache.org/jira/browse/CB-7836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14178590#comment-14178590
]
Darryl Pogue commented on CB-7836:
--
Appears to be a side-effect (or intended result?) of CB-6511
> Control output .apk filename
>
>
> Key: CB-7836
> URL: https://issues.apache.org/jira/browse/CB-7836
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Affects Versions: Master
> Environment: Mac, Linux, whatever
>Reporter: Filip Maj
>Priority: Minor
>
> ohai cordova :D
> I go to create a cordova-android project with: {{cordova create hello
> com.example.hello HelloWorld}}.
> My expectation is that the final output of the .apk filename will be
> {{HelloWorld.apk}}.
> It always comes out as {{CordovaApp.apk}}.
> Pretty sure I used to be able to control the output file name in a previous
> cordova version.
> Can haz that back plz?
> [Here|https://gist.github.com/sebv/9854f5443e2095ade2b6]'s a gist of project
> creation output for details.
> P.S. y'all are awesome
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-8183) Browserify generates bad cordova.js with multi-platform build
Darryl Pogue created CB-8183:
Summary: Browserify generates bad cordova.js with multi-platform
build
Key: CB-8183
URL: https://issues.apache.org/jira/browse/CB-8183
Project: Apache Cordova
Issue Type: Bug
Components: CLI, CordovaJS, CordovaLib
Reporter: Darryl Pogue
I was trying out the browserify flag today, and overall I love the idea. I
found one issue when building for multiple platforms:
{code}
cordova platform add ios android
cordova build --browserify
{code}
The Android build was fine, but the iOS build was throwing up prompt boxes. My
guess is that browserify generated a cordova.js for Android and then used the
same file for iOS, so the Android bridge/exec code was getting run on iOS and
failing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-8183) Browserify generates bad cordova.js with multi-platform build
[
https://issues.apache.org/jira/browse/CB-8183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14266532#comment-14266532
]
Darryl Pogue commented on CB-8183:
--
I just tested this a bit more. It seems to work properly unless you add
platforms with the --usegit flag.
My exact steps:
{code}
cordova create browserifytest
cd ./browserifytest
cordova platform add android@4.0.x ios --usegit
cordova build --browserify
open ./platforms/ios/HelloCordova.xcodeproj
{code}
Build the Xcode Project and run in the simulator and I see prompts.
> Browserify generates bad cordova.js with multi-platform build
> -
>
> Key: CB-8183
> URL: https://issues.apache.org/jira/browse/CB-8183
> Project: Apache Cordova
> Issue Type: Bug
> Components: CLI, CordovaJS, CordovaLib
>Reporter: Darryl Pogue
>Assignee: Steve Gill
>
> I was trying out the browserify flag today, and overall I love the idea. I
> found one issue when building for multiple platforms:
> {code}
> cordova platform add ios android
> cordova build --browserify
> {code}
> The Android build was fine, but the iOS build was throwing up prompt boxes.
> My guess is that browserify generated a cordova.js for Android and then used
> the same file for iOS, so the Android bridge/exec code was getting run on iOS
> and failing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-12756) Cordova@7 does not prompt for password when installing from private git repo
Darryl Pogue created CB-12756:
-
Summary: Cordova@7 does not prompt for password when installing
from private git repo
Key: CB-12756
URL: https://issues.apache.org/jira/browse/CB-12756
Project: Apache Cordova
Issue Type: Bug
Components: cordova-cli
Reporter: Darryl Pogue
Priority: Minor
When installing a plugin from a private git repo, Cordova 7 does not prompt for
a passphrase for git. The plugin fails to install.
{code}
Discovered plugin "private-cordova-plugin" in config.xml. Adding it to the
project
Failed to restore plugin "private-cordova-plugin" from config.xml. You might
need to try adding it again. Error: Failed to fetch plugin
private-cordova-plugin@dpogue/private-cordova-plugin via registry.
Probably this is either a connection problem, or plugin spec is incorrect.
Check your connection and plugin name/version/URL.
Failed to get absolute path to installed module
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-12757) Cordova@7 saves wrong spec in config.xml for git plugins
Darryl Pogue created CB-12757:
-
Summary: Cordova@7 saves wrong spec in config.xml for git plugins
Key: CB-12757
URL: https://issues.apache.org/jira/browse/CB-12757
Project: Apache Cordova
Issue Type: Bug
Components: CLI
Reporter: Darryl Pogue
Priority: Minor
(This possibly existed in earlier versions, I never used on the {{--save}} flag
so I'm not sure...)
{code}
cordova plugin add cordova-plugin-ayogo-push@AyogoHealth/cordova-plugin-push
{code}
It saves the github repo properly into package.json, but in config.xml it sets
the spec to the version number. This will fail to restore (from config.xml)
because the plugin isn't published to the npm registry.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-12717) Statusbar - [SUNSET | KEEP | INTEGRATE]
[
https://issues.apache.org/jira/browse/CB-12717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16020525#comment-16020525
]
Darryl Pogue commented on CB-12717:
---
Ideally, the status bar colour could be pulled from the {{}} tag of the page, as per spec:
https://html.spec.whatwg.org/multipage/semantics.html#meta-theme-color
> Statusbar - [SUNSET | KEEP | INTEGRATE]
> ---
>
> Key: CB-12717
> URL: https://issues.apache.org/jira/browse/CB-12717
> Project: Apache Cordova
> Issue Type: Sub-task
> Components: cordova-plugin-statusbar
>Reporter: Shazron Abdullah
>
> See parent issue.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-12316) Rename Entitlements-Debug.plist and Entitlements-Release.plist to have a .entitlements extension instead
[
https://issues.apache.org/jira/browse/CB-12316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16021572#comment-16021572
]
Darryl Pogue commented on CB-12316:
---
Could we add a build step that copies
{{Entitlements-Debug.plist}}/{{Entitlements-Release.plist}} (or whatever we
rename it to) to {{PROJECTNAME.entitlements}}? I keep running into build issues
with push notifications because Xcode complains about aps-environment
entitlements missing (despite them being in the Entitlements.plist files)
> Rename Entitlements-Debug.plist and Entitlements-Release.plist to have a
> .entitlements extension instead
>
>
> Key: CB-12316
> URL: https://issues.apache.org/jira/browse/CB-12316
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-ios
>Reporter: Shazron Abdullah
>Assignee: Shazron Abdullah
> Fix For: cordova-ios@4.4.1
>
>
> This would go in a minor update of cordova-ios.
> See:
> https://issues.apache.org/jira/browse/CB-11854?focusedCommentId=15770323&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15770323
> Not sure if it will be worth it.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-12703) Push Notification not working via cordova cli
[
https://issues.apache.org/jira/browse/CB-12703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16021578#comment-16021578
]
Darryl Pogue commented on CB-12703:
---
I suspect this is caused by the same Entitlements plist extension issues
discussed in CB-12316 and CB-12456
> Push Notification not working via cordova cli
> -
>
> Key: CB-12703
> URL: https://issues.apache.org/jira/browse/CB-12703
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-cli, cordova-ios
>Affects Versions: 6.5.0
> Environment: iPhone
>Reporter: Hiren
>Priority: Minor
>
> Facing an issue when creating an iOS build with the below command.
> {noformat}
> cordova build ios --release --device --buildConfig
> {noformat}
> When generating the build with the above command the ipa gets created
> successfully and user is also able to install and use the app. But we do not
> get any push notifications. We are using Firebase to manage our push
> notification and sending it from firebase console. Here i can see that the
> app generates a devices token but sending a notification on this token does
> not trigger any message on the mobile.
> But notification works when we create a build using Xcode. We generate the
> build by first running,
> {noformat}
> cordova prepare ios
> {noformat}
> Then using the Archive option from Product menu in Xcode.
> I believe that the APN entitle file is not getting set to production. We are
> creating an app using enterprise certificate.
> This is creating an issue when running Jenkins CI. My build gets created but
> I loose the push notification functionality. Hence i have to release ios
> builds manually from my system.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-12886) white area where status bar is in iOS 11
[
https://issues.apache.org/jira/browse/CB-12886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16037944#comment-16037944
]
Darryl Pogue commented on CB-12886:
---
The pure-HTML way to fix this is to add {{viewport-fit=cover}} to the {{meta
viewport}} tag.
> white area where status bar is in iOS 11
>
>
> Key: CB-12886
> URL: https://issues.apache.org/jira/browse/CB-12886
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-ios
> Environment: iOS 11 beta 1
>Reporter: Shazron Abdullah
> Labels: ios11
> Fix For: cordova-ios@4.4.1
>
> Attachments: ios11.png
>
>
> See attached screenshot. Using WKWebView plugin, new app.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-12886) white area where status bar is in iOS 11
[
https://issues.apache.org/jira/browse/CB-12886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16071835#comment-16071835
]
Darryl Pogue commented on CB-12886:
---
That {{viewport-fit}} thing doesn't work in the latest iOS 11 beta, so the
better way (that works on both WKWebView and UIWebView) is to set {code}
[[webView scrollView] setContentInsetAdjustmentBehavior:
UIScrollViewContentInsetAdjustmentNever];
{code}
> white area where status bar is in iOS 11
>
>
> Key: CB-12886
> URL: https://issues.apache.org/jira/browse/CB-12886
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-ios
> Environment: iOS 11 beta 1
>Reporter: Shazron Abdullah
> Labels: ios11
> Fix For: cordova-ios@5.0.0
>
> Attachments: ios11.png
>
>
> See attached screenshot. Using WKWebView plugin, new app.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-12886) white area where status bar is in iOS 11
[ https://issues.apache.org/jira/browse/CB-12886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16074168#comment-16074168 ] Darryl Pogue commented on CB-12886: --- See also https://github.com/WebKit/webkit/commit/52ec9f74f64da8fde4b21783b0b457d30897e3db (unreleased in a beta so far) > white area where status bar is in iOS 11 > > > Key: CB-12886 > URL: https://issues.apache.org/jira/browse/CB-12886 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-ios > Environment: iOS 11 beta 1 >Reporter: Shazron Abdullah > Labels: ios11 > Fix For: cordova-ios@5.0.0 > > Attachments: ios11.png > > > See attached screenshot. Using WKWebView plugin, new app. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-12886) white area where status bar is in iOS 11
[
https://issues.apache.org/jira/browse/CB-12886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16097762#comment-16097762
]
Darryl Pogue commented on CB-12886:
---
I think iOS 11 beta 4 will restore the {{viewportFit=cover}} behaviour, so we
should wait for that to decide.
I hear
[rumours|https://9to5mac.files.wordpress.com/2017/06/iphone-8-ios-11.jpg] that
this behaviour might be due to status bar changes in iOS 11 where part of the
phone frame extends into the status bar area, leading to an irregularly shaped
top edge, and this "safe area" behaviour is to ensure that content doesn't get
hidden behind a non-visible area.
> white area where status bar is in iOS 11
>
>
> Key: CB-12886
> URL: https://issues.apache.org/jira/browse/CB-12886
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-ios
> Environment: iOS 11 beta 1
>Reporter: Shazron Abdullah
> Labels: backlog, ios11
> Fix For: cordova-ios@5.0.0
>
> Attachments: ios11.png
>
>
> See attached screenshot. Using WKWebView plugin, new app.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-12886) white area where status bar is in iOS 11
[
https://issues.apache.org/jira/browse/CB-12886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16099158#comment-16099158
]
Darryl Pogue commented on CB-12886:
---
Just testing in iOS11b4, it appears that {{viewport-fit=cover}} works in both
WKWebView and UIWebView now.
> white area where status bar is in iOS 11
>
>
> Key: CB-12886
> URL: https://issues.apache.org/jira/browse/CB-12886
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-ios
> Environment: iOS 11 beta 1
>Reporter: Shazron Abdullah
> Labels: backlog, ios11
> Fix For: cordova-ios@5.0.0
>
> Attachments: ios11.png
>
>
> See attached screenshot. Using WKWebView plugin, new app.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-12070) edit-config doesn't work with plist files
[
https://issues.apache.org/jira/browse/CB-12070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darryl Pogue resolved CB-12070.
---
Resolution: Fixed
Thanks Julio! Not sure when this got fixed, but my example does appear to work
with latest CLI (7.0.1) and latest Cordova-iOS (4.4.0)
> edit-config doesn't work with plist files
> -
>
> Key: CB-12070
> URL: https://issues.apache.org/jira/browse/CB-12070
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-lib
>Reporter: Darryl Pogue
> Fix For: cordova-lib@6.4.1
>
>
> Trying to use the {{edit-config}} tag in config.xml to add to the iOS
> Info.plist file:
> {code} mode="merge">
>
> foo
>
> {code}
> It's giving me an error in xml_helpers.js:
> {code}Error: TypeError: doc.find is not a function
> at Object.resolveParent
> (/Users/dpogue/Coding/cordova-app/node_modules/cordova-common/src/util/xml-helpers.js:210:26)
> at
> /Users/dpogue/Coding/cordova-app/node_modules/cordova-common/src/ConfigChanges/ConfigChanges.js:464:53
> at Array.forEach (native)
> at is_conflicting
> (/Users/dpogue/Coding/cordova-app/node_modules/cordova-common/src/ConfigChanges/ConfigChanges.js:456:17)
> at PlatformMunger.add_config_changes
> (/Users/dpogue/Coding/cordova-app/node_modules/cordova-common/src/ConfigChanges/ConfigChanges.js:204:33)
> at
> /Users/dpogue/Coding/cordova-app/node_modules/cordova-lib/src/cordova/prepare.js:127:24
> at _fulfilled
> (/Users/dpogue/Coding/cordova-app/platforms/ios/cordova/node_modules/q/q.js:834:54)
> at self.promiseDispatch.done
> (/Users/dpogue/Coding/cordova-app/platforms/ios/cordova/node_modules/q/q.js:863:30)
> at Promise.promise.promiseDispatch
> (/Users/dpogue/Coding/cordova-app/platforms/ios/cordova/node_modules/q/q.js:796:13)
> at
> /Users/dpogue/Coding/cordova-app/platforms/ios/cordova/node_modules/q/q.js:604:44{code}
> This seems to happen because plist files are turned into JS objects when they
> are parsed, rather than XML documents like AndroidManifest.xml or config.xml.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-12668) support arbitrary creation of resources in the Asset Catalog
[
https://issues.apache.org/jira/browse/CB-12668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16154428#comment-16154428
]
Darryl Pogue commented on CB-12668:
---
{{}} is supported in config.xml now, which should allow copying
the resource files into the right spots. We might need to add some special
handling if the target path contains xcassets to update the asset catalogue.
> support arbitrary creation of resources in the Asset Catalog
>
>
> Key: CB-12668
> URL: https://issues.apache.org/jira/browse/CB-12668
> Project: Apache Cordova
> Issue Type: New Feature
> Components: cordova-ios
>Affects Versions: 3.6.4
>Reporter: Josh Sharpe
>Priority: Critical
> Labels: backlog, cordova-ios
> Fix For: cordova-ios@4.5.1
>
>
> A handful of plugins* recommend the use of an image/asset out of the Asset
> Catalog. It would be great if we could create those just by setting tags in
> config.xml, similar to and that then generate the resource in
> Xcode.
> My specific use case is to add a "back" image to be used by
> 'cordova-plugin-themeablebrowser'. I can do this manually by:
> - opening xCode
> - Click on Project -> Resources -> Image.xcassets
> - Click '+' in the bottom task bar -> New Image Set
> - Rename the new Set 'back'
> - Manually drag and drop 3 images into xcode
> To be clear - I'm not asking that cordova produce different sized images as I
> believe that's out of scope. I just need it to build the new resource in
> xcode referencing certain files on disk with tags like:
> {code}
>
>
>
>
>
> {code}
> * Example plugins:
> https://github.com/arnesson/cordova-plugin-firebase
> https://github.codifferent m/phonegap/phonegap-plugin-push
> https://github.com/initialxy/cordova-plugin-themeablebrowser
> **Bonus!**
> It'd be extra great, since I'm sure some folks want this, if cordova could
> add sound files to be used by firebase/push plugins that can leverage those
> if they exist, but I'm not sure how those get set up in xcode such that
> phonegap-plugin-push can use them.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-13252) Nightly causing npm symbolic link loop issues
Darryl Pogue created CB-13252:
-
Summary: Nightly causing npm symbolic link loop issues
Key: CB-13252
URL: https://issues.apache.org/jira/browse/CB-13252
Project: Apache Cordova
Issue Type: Bug
Components: cordova-fetch
Affects Versions: 7.0.2
Reporter: Darryl Pogue
Reproducible test case: https://github.com/dpogue/cordova-eloop (running with
npm 5.4.0)
Cordova prepare somehow decides to update the package.json to point a plugin at
{{file:node_modules/cordova-plugin-}}, leading to npm trying to
install from a folder into the same folder and throwing ELOOP errors.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-13252) Nightly causing npm symbolic link loop issues
[
https://issues.apache.org/jira/browse/CB-13252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darryl Pogue updated CB-13252:
--
Attachment: cordova.log
I've been able to reproduce it on both macOS and Linux. Running node v8.4.0 on
both, with npm@5.4.0.
Attached is the output of cordova prepare -d (on Linux) when encountering this
problem.
> Nightly causing npm symbolic link loop issues
> -
>
> Key: CB-13252
> URL: https://issues.apache.org/jira/browse/CB-13252
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-fetch
>Affects Versions: 7.0.2
>Reporter: Darryl Pogue
> Labels: tools-next
> Attachments: cordova.log
>
>
> Reproducible test case: https://github.com/dpogue/cordova-eloop (running with
> npm 5.4.0)
> Cordova prepare somehow decides to update the package.json to point a plugin
> at {{file:node_modules/cordova-plugin-}}, leading to npm trying to
> install from a folder into the same folder and throwing ELOOP errors.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13252) Nightly causing npm symbolic link loop issues
[
https://issues.apache.org/jira/browse/CB-13252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16157435#comment-16157435
]
Darryl Pogue commented on CB-13252:
---
I was curious if this might be a known npm issue, but it doesn't look like it.
Although I did find an issue filed against npm from someone that seems to be
running into the same problem: https://github.com/npm/npm/issues/17884
> Nightly causing npm symbolic link loop issues
> -
>
> Key: CB-13252
> URL: https://issues.apache.org/jira/browse/CB-13252
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-fetch
>Affects Versions: 7.0.2
>Reporter: Darryl Pogue
> Labels: tools-next
> Attachments: cordova.log
>
>
> Reproducible test case: https://github.com/dpogue/cordova-eloop (running with
> npm 5.4.0)
> Cordova prepare somehow decides to update the package.json to point a plugin
> at {{file:node_modules/cordova-plugin-}}, leading to npm trying to
> install from a folder into the same folder and throwing ELOOP errors.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-12886) white area where status bar is in iOS 11
[ https://issues.apache.org/jira/browse/CB-12886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16160212#comment-16160212 ] Darryl Pogue commented on CB-12886: --- I can confirm if I load [this example|https://gist.github.com/dpogue/d3b9722904c68cd2e3ba349d551cad36] in a cordova app with cordova-plugin-wkwebview-engine, there's a gap at the bottom :( > white area where status bar is in iOS 11 > > > Key: CB-12886 > URL: https://issues.apache.org/jira/browse/CB-12886 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-ios > Environment: iOS 11 beta 1 >Reporter: Shazron Abdullah > Labels: backlog, ios11 > Fix For: cordova-ios@5.0.0 > > Attachments: ios11.png, screenshot-1.png > > > See attached screenshot. Using WKWebView plugin, new app. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-12886) white area where status bar is in iOS 11
[ https://issues.apache.org/jira/browse/CB-12886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16160225#comment-16160225 ] Darryl Pogue commented on CB-12886: --- Some more details: It appears that the WKWebView instance is correctly sized to 568px tall. It's internal scroll view has a frame height of 568 but a content height of only 548 (leaving a 20px gap at the bottom). I tried changing where the WKWebView was initialized with bounds, but that didn't seem to have any effect. > white area where status bar is in iOS 11 > > > Key: CB-12886 > URL: https://issues.apache.org/jira/browse/CB-12886 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-ios > Environment: iOS 11 beta 1 >Reporter: Shazron Abdullah > Labels: backlog, ios11 > Fix For: cordova-ios@5.0.0 > > Attachments: ios11.png, screenshot-1.png > > > See attached screenshot. Using WKWebView plugin, new app. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-12886) white area where status bar is in iOS 11
[
https://issues.apache.org/jira/browse/CB-12886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16160228#comment-16160228
]
Darryl Pogue commented on CB-12886:
---
I don't think it's an iOS bug, I strongly believe it has something to do with
the new safe area insets. Note that it does *not* happen in my [test
app|https://github.com/dpogue/WKScrollTest] using WKWebView directly without
Cordova.
I reproduced it in Cordova with both {{position: fixed}} and {{position:
absolute}} elements having {{bottom: 0}}.
> white area where status bar is in iOS 11
>
>
> Key: CB-12886
> URL: https://issues.apache.org/jira/browse/CB-12886
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-ios
> Environment: iOS 11 beta 1
>Reporter: Shazron Abdullah
> Labels: backlog, ios11
> Fix For: cordova-ios@5.0.0
>
> Attachments: ios11.png, screenshot-1.png
>
>
> See attached screenshot. Using WKWebView plugin, new app.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-12886) white area where status bar is in iOS 11
[
https://issues.apache.org/jira/browse/CB-12886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16160663#comment-16160663
]
Darryl Pogue commented on CB-12886:
---
In theory, with jcesarmobile's plugin, the {{viewport-fit=cover}} isn't needed,
since the safe area adjustments are disabled entirely.
Ideally though, there should be a way to fix this without disabling that
entirely. I couldn't find any obvious difference between Cordova's
(gap-inducing) WKWebView setup and [my (working) direct
WKWebView|https://github.com/dpogue/WKScrollTest] setup. I definitely don't
turn off the content inset adjustment.
> white area where status bar is in iOS 11
>
>
> Key: CB-12886
> URL: https://issues.apache.org/jira/browse/CB-12886
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-ios
> Environment: iOS 11 beta 1
>Reporter: Shazron Abdullah
> Labels: backlog, ios11
> Fix For: cordova-ios@5.0.0
>
> Attachments: ios11.png, screenshot-1.png, screenshot-2.png
>
>
> See attached screenshot. Using WKWebView plugin, new app.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-12886) white area where status bar is in iOS 11
[
https://issues.apache.org/jira/browse/CB-12886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16161559#comment-16161559
]
Darryl Pogue commented on CB-12886:
---
[~stripathix] The {{allow-navigation}} is definitely not needed in this
example, and the other lines are added automatically when installing
cordova-plugin-wkwebview-engine.
Note that this issue is referring to the _Cordova_ WKWebView plugin.
*Issues involving the Ionic WKWebView plugin should be filed against Ionic.*
> white area where status bar is in iOS 11
>
>
> Key: CB-12886
> URL: https://issues.apache.org/jira/browse/CB-12886
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-ios
> Environment: iOS 11 beta 1
>Reporter: Shazron Abdullah
> Labels: backlog, ios11
> Fix For: cordova-ios@5.0.0
>
> Attachments: ios11.png, screenshot-1.png, screenshot-2.png
>
>
> See attached screenshot. Using WKWebView plugin, new app.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13273) Webview is sized incorrectly on iPhone X (Simulator)
[
https://issues.apache.org/jira/browse/CB-13273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16167397#comment-16167397
]
Darryl Pogue commented on CB-13273:
---
This is actually unrelated to the viewport-fit stuff.
In order for apps to opt-in to the full screen height without letterboxing,
they must use a LaunchStoryboard instead of splash screen launch images (the
same applies to certain iPads too, but I guess nobody really cared about them).
LaunchStoryboards are supported by Cordova in newer versions:
https://cordova.apache.org/docs/en/latest/reference/cordova-plugin-splashscreen/index.html#launch-storyboard-images
> Webview is sized incorrectly on iPhone X (Simulator)
>
>
> Key: CB-13273
> URL: https://issues.apache.org/jira/browse/CB-13273
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-ios
>Affects Versions: cordova-ios 4.5.0
> Environment: Xcode 9.0 (9A235)
> Simulator 10.0 (SimulatorApp-829.6) - iPhone X
>Reporter: Dave Alden
>Assignee: Shazron Abdullah
> Labels: iPhoneX, ios11
> Attachments: Simulator Screen Shot - iPhone X - 2017-09-14 at
> 15.52.54.png, webview-test.zip
>
>
> New app with cordova-ios@4.5.0 (using default UIWebView) running on iPhone X
> Simulator does not size correctly, leaving black areas above and below the
> app content and white bars between the black areas and app content.
> Adding cordova-plugin-wkwebview-engine so Cordova uses WKWebView, white bars
> go away, but the black areas remain:
> !https://cdn.pbrd.co/images/GKeaEPg.png|height=640!
> !https://cdn.pbrd.co/images/GKeaWwK.png|height=640!
> Setting
> {code:html}viewport-fit=cover{code}
> fixes the white bar issue with UIWebView, as outlined here
> [http://stephenradford.me/removing-the-white-bars-in-safari-on-iphone-x/],
> but the black areas remain:
> [^Simulator Screen Shot - iPhone X - 2017-09-14 at 15.52.54.png]
> Probably need some some tweaking of Launch Images in cordova-ios to get rid
> of those black areas.
> Attached Cordova project illustrates the issue.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13273) Webview is sized incorrectly on iPhone X (Simulator)
[
https://issues.apache.org/jira/browse/CB-13273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16171995#comment-16171995
]
Darryl Pogue commented on CB-13273:
---
I can reproduce this with a plain UIWebView loading the test page. Sounds like
we need to file bug reports with Apple.
It does work in WKWebView, and it looks like the fix might have been
https://github.com/WebKit/webkit/commit/4ab234a9e72f1dadc3540a82507065af9e91addb
> Webview is sized incorrectly on iPhone X (Simulator)
>
>
> Key: CB-13273
> URL: https://issues.apache.org/jira/browse/CB-13273
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-ios
>Affects Versions: cordova-ios 4.5.0
> Environment: Xcode 9.0 (9A235)
> Simulator 10.0 (SimulatorApp-829.6) - iPhone X
>Reporter: Dave Alden
>Assignee: Shazron Abdullah
> Labels: iPhoneX, ios11
> Attachments: fig1.png, fig2.png, Simulator Screen Shot - iPhone X -
> 2017-09-14 at 15.52.54.png, Simulator Screen Shot - iPhone X - 2017-09-15 at
> 09.20.48.png, Simulator Screen Shot - iPhone X - 2017-09-19 at 11.29.00.png,
> webview-test.zip
>
>
> New app with cordova-ios@4.5.0 (using default UIWebView) running on iPhone X
> Simulator does not size correctly, leaving black areas above and below the
> app content and white bars between the black areas and app content.
> Adding cordova-plugin-wkwebview-engine so Cordova uses WKWebView, white bars
> go away, but the black areas remain:
> !https://cdn.pbrd.co/images/GKeaEPg.png|height=640!
> !https://cdn.pbrd.co/images/GKeaWwK.png|height=640!
> Setting
> {code:html}viewport-fit=cover{code}
> fixes the white bar issue with UIWebView, as outlined here
> [http://stephenradford.me/removing-the-white-bars-in-safari-on-iphone-x/],
> but the black areas remain:
> [^Simulator Screen Shot - iPhone X - 2017-09-14 at 15.52.54.png]
> Attached Cordova project illustrates the issue.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Comment Edited] (CB-13273) Webview is sized incorrectly on iPhone X (Simulator)
[
https://issues.apache.org/jira/browse/CB-13273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16171995#comment-16171995
]
Darryl Pogue edited comment on CB-13273 at 9/19/17 4:42 PM:
I can reproduce this with a plain UIWebView loading the test page. Sounds like
we need to file bug reports with Apple.
My Radar report: http://www.openradar.me/radar?id=5035192880201728
It does work in WKWebView, and it looks like the fix might have been
https://github.com/WebKit/webkit/commit/4ab234a9e72f1dadc3540a82507065af9e91addb
was (Author: dpogue):
I can reproduce this with a plain UIWebView loading the test page. Sounds like
we need to file bug reports with Apple.
It does work in WKWebView, and it looks like the fix might have been
https://github.com/WebKit/webkit/commit/4ab234a9e72f1dadc3540a82507065af9e91addb
> Webview is sized incorrectly on iPhone X (Simulator)
>
>
> Key: CB-13273
> URL: https://issues.apache.org/jira/browse/CB-13273
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-ios
>Affects Versions: cordova-ios 4.5.0
> Environment: Xcode 9.0 (9A235)
> Simulator 10.0 (SimulatorApp-829.6) - iPhone X
>Reporter: Dave Alden
>Assignee: Shazron Abdullah
> Labels: iPhoneX, ios11
> Attachments: fig1.png, fig2.png, Simulator Screen Shot - iPhone X -
> 2017-09-14 at 15.52.54.png, Simulator Screen Shot - iPhone X - 2017-09-15 at
> 09.20.48.png, Simulator Screen Shot - iPhone X - 2017-09-19 at 11.29.00.png,
> webview-test.zip
>
>
> New app with cordova-ios@4.5.0 (using default UIWebView) running on iPhone X
> Simulator does not size correctly, leaving black areas above and below the
> app content and white bars between the black areas and app content.
> Adding cordova-plugin-wkwebview-engine so Cordova uses WKWebView, white bars
> go away, but the black areas remain:
> !https://cdn.pbrd.co/images/GKeaEPg.png|height=640!
> !https://cdn.pbrd.co/images/GKeaWwK.png|height=640!
> Setting
> {code:html}viewport-fit=cover{code}
> fixes the white bar issue with UIWebView, as outlined here
> [http://stephenradford.me/removing-the-white-bars-in-safari-on-iphone-x/],
> but the black areas remain:
> [^Simulator Screen Shot - iPhone X - 2017-09-14 at 15.52.54.png]
> Attached Cordova project illustrates the issue.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-10986) Unable to install plugin with cordova-cli@6.1.0
Darryl Pogue created CB-10986:
-
Summary: Unable to install plugin with cordova-cli@6.1.0
Key: CB-10986
URL: https://issues.apache.org/jira/browse/CB-10986
Project: Apache Cordova
Issue Type: Bug
Components: CLI
Affects Versions: 6.1.0
Reporter: Darryl Pogue
{code}
$ cordova create MyProject
$ cd ./MyProject
$ cordova platform add android
$ cordova plugin add @dpogue/cordova-plugin-crosswalk-webview
Error: Cannot find plugin.xml for plugin 'plugins'. Please try adding it again.
{code}
This works as expected with cordova@6.0.0.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10986) Unable to install plugin with cordova-cli@6.1.0
[
https://issues.apache.org/jira/browse/CB-10986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216656#comment-15216656
]
Darryl Pogue commented on CB-10986:
---
This seems to only affect plugins that are scoped npm packages
> Unable to install plugin with cordova-cli@6.1.0
> ---
>
> Key: CB-10986
> URL: https://issues.apache.org/jira/browse/CB-10986
> Project: Apache Cordova
> Issue Type: Bug
> Components: CLI
>Affects Versions: 6.1.0
>Reporter: Darryl Pogue
>
> {code}
> $ cordova create MyProject
> $ cd ./MyProject
> $ cordova platform add android
> $ cordova plugin add @dpogue/cordova-plugin-crosswalk-webview
> Error: Cannot find plugin.xml for plugin 'plugins'. Please try adding it
> again.
> {code}
> This works as expected with cordova@6.0.0.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10986) Unable to install plugin with cordova-cli@6.1.0
[
https://issues.apache.org/jira/browse/CB-10986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15224899#comment-15224899
]
Darryl Pogue commented on CB-10986:
---
Could we use npm's package/version parsing code instead of our own?
https://www.npmjs.com/package/npm-package-arg is the module they use
Maybe this has to wait for cordova-fetch, but if it can be fixed sooner that
would be great. This is blocking us from being able to update our cordova
tooling :(
> Unable to install plugin with cordova-cli@6.1.0
> ---
>
> Key: CB-10986
> URL: https://issues.apache.org/jira/browse/CB-10986
> Project: Apache Cordova
> Issue Type: Bug
> Components: CordovaLib
>Affects Versions: 6.1.0
>Reporter: Darryl Pogue
> Labels: regression, reproduced, triaged
>
> {code}
> $ cordova create MyProject
> $ cd ./MyProject
> $ cordova platform add android
> $ cordova plugin add @dpogue/cordova-plugin-crosswalk-webview
> Error: Cannot find plugin.xml for plugin 'plugins'. Please try adding it
> again.
> {code}
> This works as expected with cordova@6.0.0.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-11180) Ignore plugin mapper when a git spec is specified
Darryl Pogue created CB-11180:
-
Summary: Ignore plugin mapper when a git spec is specified
Key: CB-11180
URL: https://issues.apache.org/jira/browse/CB-11180
Project: Apache Cordova
Issue Type: Bug
Components: CordovaLib
Affects Versions: 6.0.0
Reporter: Darryl Pogue
Priority: Minor
We had a project with this in the config.xml:
{code}
https://github.com/Telerik-Verified-Plugins/ScreenOrientation.git"; />
{code}
However, the cordova plugin mapper has an entry for
{{net.yoik.cordova.plugins.screenorientation}} that was telling it to fetch
from npm.
The cordova prepare output said it was being fetched from npm, but there was a
folder in ./plugins/ with the old ID and then it said that it failed to install
for iOS because it was already installed for Android, and also said that it was
fetching from npm again.
The best solution is probably to avoid going through the plugin mapper if a
spec is a git reference (or maybe if there's a spec at all?)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11009) Use xcode 0.8.4 in cordova-lib
[ https://issues.apache.org/jira/browse/CB-11009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15274892#comment-15274892 ] Darryl Pogue commented on CB-11009: --- The Xcode dependency is updated as part of CB-11200. > Use xcode 0.8.4 in cordova-lib > -- > > Key: CB-11009 > URL: https://issues.apache.org/jira/browse/CB-11009 > Project: Apache Cordova > Issue Type: Bug > Components: CordovaLib >Reporter: Shazron Abdullah >Assignee: Shazron Abdullah > Labels: triaged > > This is to fix CB-10156 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-11245) Swift plugins need additional build settings
Darryl Pogue created CB-11245:
-
Summary: Swift plugins need additional build settings
Key: CB-11245
URL: https://issues.apache.org/jira/browse/CB-11245
Project: Apache Cordova
Issue Type: Bug
Components: iOS
Reporter: Darryl Pogue
Priority: Minor
Plugins written in Swift require some additional build settings in order to
work properly (and not crash the app immediately).
In particular, {{EMBEDDED_CONTENT_CONTAINS_SWIFT = "YES"}} and
{{LD_RUNPATH_SEARCH_PATHS = "@executable_path/Frameworks"}} are required.
This could be handled in a general way by allowing plugins to add their own
options to .xcconfig (but could result in duplication), or for this specific
case it is probably enough to set these if any plugins contain .swift files.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-11252) Cordova-fetch fails to restore scoped plugins on prepare
Darryl Pogue created CB-11252:
-
Summary: Cordova-fetch fails to restore scoped plugins on prepare
Key: CB-11252
URL: https://issues.apache.org/jira/browse/CB-11252
Project: Apache Cordova
Issue Type: Bug
Components: cordova-fetch
Reporter: Darryl Pogue
Assignee: Steve Gill
With {code}{code} in my config.xml, I get the following when running {{cordova prepare
--fetch --verbose}}:
{code}
Executing "after_prepare" hook for all plugins.
Discovered plugin "@dpogue/cordova-plugin-wkwebview-engine" in config.xml.
Installing to the project
Executing "before_plugin_add" hook for all plugins.
Calling plugman.fetch on plugin "@dpogue/cordova-plugin-wkwebview-engine@~1.0.1"
Failed to restore plugin @dpogue/cordova-plugin-wkwebview-engine from
config.xml. You might want to reinstall it again. Error: Cannot find plugin.xml
for plugin 'node_modules'. Please try adding it again.
Discovered plugin "@dpogue/cordova-plugin-crosswalk-webview" in config.xml.
Installing to the project
Executing "before_plugin_add" hook for all plugins.
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Assigned] (CB-11311) cordova-plugin-wkwebview-engine not working with --browserify flag
[
https://issues.apache.org/jira/browse/CB-11311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darryl Pogue reassigned CB-11311:
-
Assignee: Darryl Pogue
> cordova-plugin-wkwebview-engine not working with --browserify flag
> --
>
> Key: CB-11311
> URL: https://issues.apache.org/jira/browse/CB-11311
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin WKWebViewEngine
>Affects Versions: 4.1.1
> Environment: OS X 10.11
> Cordova CLI 6.1.1
> Cordova iOS 4.1.1
> cordova-plugin-wkwebview-engine 1.0.3
>Reporter: Wilson Yang
>Assignee: Darryl Pogue
>
> The code below for replace the exec bridge is not compatible with browserify
> {code:javascript}
> // unregister the old bridge
> cordova.define.remove('cordova/exec');
> // redefine bridge to our new bridge
> cordova.define("cordova/exec", function(require, exports, module) {
> module.exports = execProxy;
> });
> {code}
> After using browserify flag, all scripts for www will be packed into
> cordova.js as single file. At the same time, the `cordova.define` become
> undefined.
> {code}
> TypeError: undefined is not an object (evaluating 'cordova.define.remove')
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-11311) cordova-plugin-wkwebview-engine not working with --browserify flag
[
https://issues.apache.org/jira/browse/CB-11311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darryl Pogue updated CB-11311:
--
Assignee: (was: Darryl Pogue)
> cordova-plugin-wkwebview-engine not working with --browserify flag
> --
>
> Key: CB-11311
> URL: https://issues.apache.org/jira/browse/CB-11311
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin WKWebViewEngine
>Affects Versions: 4.1.1
> Environment: OS X 10.11
> Cordova CLI 6.1.1
> Cordova iOS 4.1.1
> cordova-plugin-wkwebview-engine 1.0.3
>Reporter: Wilson Yang
>
> The code below for replace the exec bridge is not compatible with browserify
> {code:javascript}
> // unregister the old bridge
> cordova.define.remove('cordova/exec');
> // redefine bridge to our new bridge
> cordova.define("cordova/exec", function(require, exports, module) {
> module.exports = execProxy;
> });
> {code}
> After using browserify flag, all scripts for www will be packed into
> cordova.js as single file. At the same time, the `cordova.define` become
> undefined.
> {code}
> TypeError: undefined is not an object (evaluating 'cordova.define.remove')
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11315) WkWebview + DisallowOverscroll breaks fixed positioned elements
[ https://issues.apache.org/jira/browse/CB-11315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15313261#comment-15313261 ] Darryl Pogue commented on CB-11315: --- This isn't a Cordova bug, I've submitted it to WebKit: https://bugs.webkit.org/show_bug.cgi?id=158325 > WkWebview + DisallowOverscroll breaks fixed positioned elements > --- > > Key: CB-11315 > URL: https://issues.apache.org/jira/browse/CB-11315 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin WKWebViewEngine >Reporter: Bjorn Rombaut > Labels: DisallowOverscroll, ios, wkwebview-1.0.2 > Attachments: IMG_0656.PNG, wkwebview-disallowoverscroll-issue.zip > > > Hi! > When using both the DisallowOverscroll property and WkWebview, there seems to > be an issue when scrolling and repainting fixed elements. > When you scroll to the end of the page (where it would bounce if you don't > set the DisallowOverscroll), fixed positioned elements seem to bounce but > never return to their original position. Visually there is no issue but when > you try to click something inside the fixed element (for example a button > inside a fixed footer) the click action will not be triggered. Also when you > hover the node in the Safari Debug Tools it thinks the element is displayed > somewhere else. > I've attached a screenshot and some code to make it a bit more clear. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-10419) cordova-plugin-file 4.0.0 error with browserify workflow
Darryl Pogue created CB-10419:
-
Summary: cordova-plugin-file 4.0.0 error with browserify workflow
Key: CB-10419
URL: https://issues.apache.org/jira/browse/CB-10419
Project: Apache Cordova
Issue Type: Bug
Components: CLI, Plugin File
Affects Versions: 3.5.0
Reporter: Darryl Pogue
We’ve recently started getting an error with aliasify and the file plugin when
building with a --browserify workflow.
{code}
events.js:72
throw er; // Unhandled 'error' event
^
SyntaxError: 'return' outside of function (31:4) (while aliasify was processing
/projects/plugins/cordova-plugin-file/www/requestFileSystem.js) while parsing
file: /project/plugins/cordova-plugin-file/www/requestFileSystem.js
{code}
This started when the File plugin v4.0.0 was released. It's caused by a return
statement outside of a function:
https://github.com/apache/cordova-plugin-file/blob/77c63ef181313eba51652e1026cc730fc79ab9f2/www/requestFileSystem.js#L31
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10419) cordova-plugin-file 4.0.0 error with browserify workflow
[
https://issues.apache.org/jira/browse/CB-10419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15115801#comment-15115801
]
Darryl Pogue commented on CB-10419:
---
This reproduces it for me:
{code}
cordova create testapp
cd ./testapp
cordova platform add android --save
cordova plugin add cordova-plugin-file-transfer --save
cordova build --browserify --verbose
{code}
> cordova-plugin-file 4.0.0 error with browserify workflow
>
>
> Key: CB-10419
> URL: https://issues.apache.org/jira/browse/CB-10419
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin File
>Affects Versions: 3.5.0
>Reporter: Darryl Pogue
> Labels: regression, triaged
>
> We’ve recently started getting an error with aliasify and the file plugin
> when building with a --browserify workflow.
> {code}
> events.js:72
> throw er; // Unhandled 'error' event
> ^
> SyntaxError: 'return' outside of function (31:4) (while aliasify was
> processing /projects/plugins/cordova-plugin-file/www/requestFileSystem.js)
> while parsing file:
> /project/plugins/cordova-plugin-file/www/requestFileSystem.js
> {code}
> This started when the File plugin v4.0.0 was released. It's caused by a
> return statement outside of a function:
> https://github.com/apache/cordova-plugin-file/blob/77c63ef181313eba51652e1026cc730fc79ab9f2/www/requestFileSystem.js#L31
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-11589) Missing plugins in PlatformJson after restore
Darryl Pogue created CB-11589:
-
Summary: Missing plugins in PlatformJson after restore
Key: CB-11589
URL: https://issues.apache.org/jira/browse/CB-11589
Project: Apache Cordova
Issue Type: Bug
Components: CordovaLib
Affects Versions: 6.2.0
Reporter: Darryl Pogue
My project has both Android and iOS platforms, and sometimes when I run
{{cordova prepare}} it installs everything properly for Android, and installs
the plugin files for iOS but leaves the ios.json file mostly empty.
It turns out we're incredibly inefficient with restoring platforms and plugins.
The entire process looks something like this:
{code}
Cordova Prepare
restore Android
Android install new plugins
Android prepare
restore iOS
iOS install new plugins
iOS prepare
prepare Android
prepare iOS
restore Plugins
add plugin
add plugin
...
{code}
Rather than preparing when we add the platform and then preparing again after
all the platforms are added, it would be ideal to add the platforms and then do
a single prepare at the end.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-11777) Plugins superseding config.xml
Darryl Pogue created CB-11777:
-
Summary: Plugins superseding config.xml
Key: CB-11777
URL: https://issues.apache.org/jira/browse/CB-11777
Project: Apache Cordova
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: CordovaLib
Affects Versions: 3.5.0
Reporter: Darryl Pogue
Assignee: Vladimir Kotikov
The ongoing saga of CB-11589 and CB-11698...
When running {{cordova prepare}} to restore platforms and plugins, the platform
has prepare called before the plugins are restored. This leads to the top-level
config.xml data being copied into the platform at prepare time, and then plugin
config being appended when they are later restored.
In my case, this was causing the Crosswalk version defined in my top-level
config.xml to be overwritten by an undefined version when the plugin was
installed. A workaround is to run {{cordova prepare}} a second time.
A better fix is probably to restore the platforms, restore the plugins, and
then run prepare after everything has been restored.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-11860) Cordova-iOS cannot package distributions apps with Xcode 8
Darryl Pogue created CB-11860:
-
Summary: Cordova-iOS cannot package distributions apps with Xcode 8
Key: CB-11860
URL: https://issues.apache.org/jira/browse/CB-11860
Project: Apache Cordova
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: iOS
Affects Versions: 4.3.0
Reporter: Darryl Pogue
Assignee: Darryl Pogue
See mailing list thread:
https://lists.apache.org/thread.html/85a715681471c774821d76a90ec288943eca1a4bb0a267ba299d2eb3@%3Cdev.cordova.apache.org%3E
{quote}My proposal is for cordova-ios to drop support for Xcode 6 with the xcrun
packaging, and start using xcodebuild for archiving and generating the IPA.
I suppose that would have to wait for a major version bump of cordova-ios,
unless we detected the Xcode version and kept the old code around
conditionally.
As part of packaging, we would need to generate a exportOptions.plist file,
indicating what type of build to package (development, enterprise, ad-hoc,
or app-store). I'd suggest we add a "packageType" or "buildType" field to
build.json for specifying this value (with a default of development).{quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11792) Add Cocoapods .xcconfig includes to build.xcconfig files in template, modify create script
[ https://issues.apache.org/jira/browse/CB-11792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15497096#comment-15497096 ] Darryl Pogue commented on CB-11792: --- That sounds good to me > Add Cocoapods .xcconfig includes to build.xcconfig files in template, modify > create script > -- > > Key: CB-11792 > URL: https://issues.apache.org/jira/browse/CB-11792 > Project: Apache Cordova > Issue Type: Sub-task > Security Level: Public(Anyone can view this level - this is the > default.) > Components: iOS >Reporter: Shazron Abdullah >Assignee: Shazron Abdullah > > 1. The platforms/ios/cordova/build-debug.xcconfig file needs to add this > reference at the end: #include "Pods/Target Support > Files/Pods-PROJECTNAME/Pods-PROJECTNAME.debug.xcconfig" > 2. The platforms/ios/cordova/build-release.xcconfig file needs to add this > reference at the end: #include "Pods/Target Support > Files/Pods-PROJECTNAME/Pods-PROJECTNAME.debug.xcconfig" > 3. The create script should replace PROJECTNAME with the correct project name -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-10885) `LD_RUNPATH_SEARCH_PATHS = "@executable_path/Frameworks"` missing from iOS `release` builds
[ https://issues.apache.org/jira/browse/CB-10885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darryl Pogue resolved CB-10885. --- Resolution: Fixed This was fixed with https://github.com/apache/cordova-ios/commit/f74e2de6ac6e33981edb2e331d6953d20ae5f4de and should be released as part of cordova-ios@4.3.0 > `LD_RUNPATH_SEARCH_PATHS = "@executable_path/Frameworks"` missing from iOS > `release` builds > --- > > Key: CB-10885 > URL: https://issues.apache.org/jira/browse/CB-10885 > Project: Apache Cordova > Issue Type: Bug > Components: iOS >Affects Versions: 4.0.0, 4.1.0 >Reporter: Martijn Walraven > Labels: triaged > > With Cordova iOS 4.0 and higher, the Xcode project only sets > `LD_RUNPATH_SEARCH_PATHS = "@executable_path/Frameworks"` for `debug` and not > for `release` builds. This means the app won't be able to find embedded > frameworks at run time. One consequence is that apps with plugins written in > Swift will fail because these depend on the Swift core library: > ``` > dyld: Library not loaded: @rpath/libswiftCore.dylib > Referenced from: > /var/mobile/Containers/Bundle/Application/B862070D-86B6-4CCB-A484-1A53FBFDB59B/mobileapp.app/mobileapp > Reason: image not found > ``` > It seems the issue results from the changes made in [this > commit](https://github.com/apache/cordova-ios/commit/2a54fc1b0cd92887fd47af8ef3dfb9de805cc188), > where build settings were split-off from `.pbxproj` to `.xcconfig` files. > This removed `LD_RUNPATH_SEARCH_PATHS` from the `release` but not the `debug` > configuration. > As a workaround, I now set `LD_RUNPATH_SEARCH_PATHS` in > `build-extras.xcconfig`, but this should obviously be fixed in the platform > itself. > Should this be added back to `.pbxproj`? Or should it be moved to > `build.xcconfig`? -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11245) Swift plugins need additional build settings
[
https://issues.apache.org/jira/browse/CB-11245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15547148#comment-15547148
]
Darryl Pogue commented on CB-11245:
---
CB-11831 improves the amount of edits needed, but CB-11952 would definitely
allow setting all the flags we need.
For reference, this is the hook that I currently run in a Swift plugin with
Xcode 8: https://gist.github.com/dpogue/fd4025c72c97c91556815b54a637d57d
> Swift plugins need additional build settings
>
>
> Key: CB-11245
> URL: https://issues.apache.org/jira/browse/CB-11245
> Project: Apache Cordova
> Issue Type: Bug
> Components: iOS
>Reporter: Darryl Pogue
>Assignee: Shazron Abdullah
>Priority: Minor
> Labels: cordova-ios-5.0.x, triaged
>
> Plugins written in Swift require some additional build settings in order to
> work properly (and not crash the app immediately).
> In particular, {{EMBEDDED_CONTENT_CONTAINS_SWIFT = "YES"}} and
> {{LD_RUNPATH_SEARCH_PATHS = "@executable_path/Frameworks"}} are required.
> This could be handled in a general way by allowing plugins to add their own
> options to .xcconfig (but could result in duplication), or for this specific
> case it is probably enough to set these if any plugins contain .swift files.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11803) Plugin features don't get written to iOS-specific config.xml
[
https://issues.apache.org/jira/browse/CB-11803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15556551#comment-15556551
]
Darryl Pogue commented on CB-11803:
---
Ugh, this is one of the reasons that I want to separate prepare and restore,
because there are all these cases that aren't captured in tests or
documentation anywhere and trying to fix anything results in breaking
expectations.
However, I thought this particular case was already fixed by CB-11698?
> Plugin features don't get written to iOS-specific config.xml
>
>
> Key: CB-11803
> URL: https://issues.apache.org/jira/browse/CB-11803
> Project: Apache Cordova
> Issue Type: Bug
> Components: CLI, iOS, Plugins
>Affects Versions: 6.3.1
>Reporter: Matus Koprda
>Priority: Critical
>
> When running `cordova prepare` or `cordova platform add ios` after adding
> plugins, the platform-specific config.xml file for iOS
> (`platforms/ios/NAME/config.xml`) doesn't have `` tags, which
> effectively prevents any installed plugin from working.
> The tags *do* get added when installing plugins *after* the iOS platform was
> created.
> How to reproduce - this creates a working config.xml:
> {code}
> cordova create test
> cd test
> cordova platform add ios
> cordova plugin add cordova-plugin-device --save
> {code}
> This creates a broken config.xml (resulting in `Plugin 'Device' not found, or
> is not a CDVPlugin.` error when running on a an iPhone):
> {code}
> cordova create test
> cd test
> cordova plugin add cordova-plugin-device --save
> cordova platform add ios
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-12002) Support LSApplicationQueriesSchemes
Darryl Pogue created CB-12002:
-
Summary: Support LSApplicationQueriesSchemes
Key: CB-12002
URL: https://issues.apache.org/jira/browse/CB-12002
Project: Apache Cordova
Issue Type: Bug
Components: iOS
Reporter: Darryl Pogue
Assignee: Darryl Pogue
For apps to launch other apps via their custom URL schemes, they need to be
whitelisted in LSApplicationQueriesSchemes. We should be able to use the
(currently unused by iOS) {{}} tags in config.xml to configure
this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-12070) edit-config doesn't work with plist files
Darryl Pogue created CB-12070:
-
Summary: edit-config doesn't work with plist files
Key: CB-12070
URL: https://issues.apache.org/jira/browse/CB-12070
Project: Apache Cordova
Issue Type: Bug
Components: CordovaLib
Reporter: Darryl Pogue
Trying to use the {{edit-config}} tag in config.xml to add to the iOS
Info.plist file:
{code}
foo
{code}
It's giving me an error in xml_helpers.js:
{code}Error: TypeError: doc.find is not a function
at Object.resolveParent
(/Users/dpogue/Coding/cordova-app/node_modules/cordova-common/src/util/xml-helpers.js:210:26)
at
/Users/dpogue/Coding/cordova-app/node_modules/cordova-common/src/ConfigChanges/ConfigChanges.js:464:53
at Array.forEach (native)
at is_conflicting
(/Users/dpogue/Coding/cordova-app/node_modules/cordova-common/src/ConfigChanges/ConfigChanges.js:456:17)
at PlatformMunger.add_config_changes
(/Users/dpogue/Coding/cordova-app/node_modules/cordova-common/src/ConfigChanges/ConfigChanges.js:204:33)
at
/Users/dpogue/Coding/cordova-app/node_modules/cordova-lib/src/cordova/prepare.js:127:24
at _fulfilled
(/Users/dpogue/Coding/cordova-app/platforms/ios/cordova/node_modules/q/q.js:834:54)
at self.promiseDispatch.done
(/Users/dpogue/Coding/cordova-app/platforms/ios/cordova/node_modules/q/q.js:863:30)
at Promise.promise.promiseDispatch
(/Users/dpogue/Coding/cordova-app/platforms/ios/cordova/node_modules/q/q.js:796:13)
at
/Users/dpogue/Coding/cordova-app/platforms/ios/cordova/node_modules/q/q.js:604:44{code}
This seems to happen because plist files are turned into JS objects when they
are parsed, rather than XML documents like AndroidManifest.xml or config.xml.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Assigned] (CB-12077) Custom app icons and splash screens not working in cordova-android v6.0.0
[ https://issues.apache.org/jira/browse/CB-12077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darryl Pogue reassigned CB-12077: - Assignee: Darryl Pogue > Custom app icons and splash screens not working in cordova-android v6.0.0 > - > > Key: CB-12077 > URL: https://issues.apache.org/jira/browse/CB-12077 > Project: Apache Cordova > Issue Type: Bug > Environment: cordova v6.4.0, cordova-android v6.0.0, > cordova-plugin-splashscreen@4.0.0 >Reporter: Graeme Mawson >Assignee: Darryl Pogue >Priority: Critical > > With the latest cordova-android v6.0.0 release, which is pinned to cordova > v6.4.0, custom app icons and splash screens no longer work. > It appears as though the custom app icons and splash screens are copied into > the ./res folder and not into the ./platforms/android/res folder. > Others have mentioned the same bug - please refer to the comments at the > bottom of your blog post announcement of the cordova-android v6.0.0 release > (http://cordova.apache.org/announcements/2016/10/24/android-release.html). > My config.xml file refers to the app icons & splash screens as follows: > > > > > > > > > density="land-ldpi"/> > density="land-mdpi"/> > density="land-hdpi"/> > density="land-xhdpi"/> > density="land-xxhdpi"/> > density="land-xxxhdpi"/> > density="port-hdpi"/> > density="port-ldpi"/> > density="port-mdpi"/> > density="port-xhdpi"/> > density="port-xxhdpi"/> > density="port-xxxhdpi"/> > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-13523) Add build config option to enable Xcode automatic provisioning
Darryl Pogue created CB-13523: - Summary: Add build config option to enable Xcode automatic provisioning Key: CB-13523 URL: https://issues.apache.org/jira/browse/CB-13523 Project: Apache Cordova Issue Type: Improvement Components: cordova-ios Environment: Xcode 9 Cordova-iOS 4.5.3 Reporter: Darryl Pogue Assignee: Darryl Pogue Xcode 9 made more changes to how provisioning works for apps, particularly around manual vs automatic signing. The changes required to support manual signing of release builds was implemented as part of CB-13315. In order for automatic signing to work, we need to pass an additional flag to xcodebuild to allow Xcode to manage automatically updating provisioning profiles as needed. I want to keep this being a build config option because many people may not want to grant Xcode such power by default. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13523) Add build config option to enable Xcode automatic provisioning
[ https://issues.apache.org/jira/browse/CB-13523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16235778#comment-16235778 ] Darryl Pogue commented on CB-13523: --- The buildFlags are only passed to xcodebuild during the building/archiving step, not during the export step that generates the final .ipa file (and I suspect it might be invalid to specify most of the buildFlags during an export) > Add build config option to enable Xcode automatic provisioning > -- > > Key: CB-13523 > URL: https://issues.apache.org/jira/browse/CB-13523 > Project: Apache Cordova > Issue Type: Improvement > Components: cordova-ios > Environment: Xcode 9 > Cordova-iOS 4.5.3 >Reporter: Darryl Pogue >Assignee: Darryl Pogue >Priority: Major > > Xcode 9 made more changes to how provisioning works for apps, particularly > around manual vs automatic signing. > The changes required to support manual signing of release builds was > implemented as part of CB-13315. > In order for automatic signing to work, we need to pass an additional flag to > xcodebuild to allow Xcode to manage automatically updating provisioning > profiles as needed. I want to keep this being a build config option because > many people may not want to grant Xcode such power by default. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-13532) Cordova fails to find platform/plugin versions in package.json devDependencies
Darryl Pogue created CB-13532:
-
Summary: Cordova fails to find platform/plugin versions in
package.json devDependencies
Key: CB-13532
URL: https://issues.apache.org/jira/browse/CB-13532
Project: Apache Cordova
Issue Type: Bug
Components: cordova-lib
Reporter: Darryl Pogue
Priority: Major
Cordova only looks at the {{dependencies}} section of package.json, and ignores
anything specified in {{devDependencies}}. This results in the default pinned
versions for platforms/plugins being used.
Code in question:
https://github.com/apache/cordova-lib/blob/da8ebf6cb81dd84c22e24fdf0baff9837a544b2d/src/cordova/platform/addHelper.js#L109-L113
This is wrong because Cordova (and its related bits) is not a dependency of my
application code, it is a build tool that belongs in devDependencies.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13254) node 4 with cordova-cli causes platform add issues
[
https://issues.apache.org/jira/browse/CB-13254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16237107#comment-16237107
]
Darryl Pogue commented on CB-13254:
---
npm@2 is a dependency of cordova-lib, so even having npm@3 installed globally
won't necessarily result in cordova using npm@3.
> node 4 with cordova-cli causes platform add issues
> --
>
> Key: CB-13254
> URL: https://issues.apache.org/jira/browse/CB-13254
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-cli
>Reporter: Shazron Abdullah
>Priority: Major
> Labels: tools-next
>
> From [~jcesarmobile] in dev@:
> {code}
> I'm trying to do cordova platform add
> https://github.com/apache/cordova-ios#4.5.0 and getting this error
> Using CLI 7.0.1:
> cordova platform add https://github.com/apache/cordova-ios#4.5.0
> Using cordova-fetch for https://github.com/apache/cordova-ios#4.5.0
> Adding ios project...
> Using this version of Cordova with older version of cordova-ios is
> deprecated. Upgrade to cordova-ios@4.0.0 or newer.
> Error: Your ios platform does not have Api.js
> Using nightly CLI:
> cordova platform add https://github.com/apache/cordova-ios#4.5.0
> Warning: using prerelease version 7.0.2-nightly.2017.9.7.596da5df
> (cordova-lib@7.0.2-nightly.2017.9.7.6f5be6a7)
> Using cordova-fetch for https://github.com/apache/cordova-ios#4.5.0
> Adding ios project...
> Unable to load PlatformApi from platform. Error: Cannot find module 'unorm'
> Error: Uncaught, unspecified "error" event. (The platform "ios" does not
> appear to be a valid cordova platform. It is missing API.js. ios not
> supported.)
> node -v
> v4.4.7
> npm -v
> 2.15.8
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-12886) white area where status bar is in iOS 11
[ https://issues.apache.org/jira/browse/CB-12886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16252631#comment-16252631 ] Darryl Pogue commented on CB-12886: --- bq. As far as I remember, that didn't happen on a regular WKWebView, just on the plugin. That's correct. It only happens with the Cordova WKWebView plugin, it does not happen with a native project using WKWebView. > white area where status bar is in iOS 11 > > > Key: CB-12886 > URL: https://issues.apache.org/jira/browse/CB-12886 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-ios > Environment: iOS 11 beta 1 >Reporter: Shazron Abdullah > Labels: backlog, ios11 > Fix For: cordova-ios@5.0.0 > > Attachments: ios11.png, screenshot-1.png, screenshot-2.png, > screenshot-3.png, screenshot-4.png, screenshot-5.png, screenshot-6.png > > > See attached screenshot. Using WKWebView plugin, new app. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Comment Edited] (CB-12886) white area where status bar is in iOS 11
[
https://issues.apache.org/jira/browse/CB-12886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16252631#comment-16252631
]
Darryl Pogue edited comment on CB-12886 at 11/14/17 10:51 PM:
--
bq. As far as I remember, that didn't happen on a regular WKWebView, just on
the plugin.
That's correct. It only happens with the Cordova WKWebView plugin, it does not
happen with a native project using WKWebView.
[~Jespertheend] That second radar is closed because using
{{viewport-fit=cover}} works in a native WKWebView.
was (Author: dpogue):
bq. As far as I remember, that didn't happen on a regular WKWebView, just on
the plugin.
That's correct. It only happens with the Cordova WKWebView plugin, it does not
happen with a native project using WKWebView.
> white area where status bar is in iOS 11
>
>
> Key: CB-12886
> URL: https://issues.apache.org/jira/browse/CB-12886
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-ios
> Environment: iOS 11 beta 1
>Reporter: Shazron Abdullah
> Labels: backlog, ios11
> Fix For: cordova-ios@5.0.0
>
> Attachments: ios11.png, screenshot-1.png, screenshot-2.png,
> screenshot-3.png, screenshot-4.png, screenshot-5.png, screenshot-6.png
>
>
> See attached screenshot. Using WKWebView plugin, new app.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-12886) white area where status bar is in iOS 11
[ https://issues.apache.org/jira/browse/CB-12886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253078#comment-16253078 ] Darryl Pogue commented on CB-12886: --- I have a suspicion that this is due to Cordova using a .xib for the main app layout, rather than a .storyboard > white area where status bar is in iOS 11 > > > Key: CB-12886 > URL: https://issues.apache.org/jira/browse/CB-12886 > Project: Apache Cordova > Issue Type: Bug > Components: cordova-ios > Environment: iOS 11 beta 1 >Reporter: Shazron Abdullah > Labels: backlog, ios11 > Fix For: cordova-ios@5.0.0 > > Attachments: ios11.png, screenshot-1.png, screenshot-2.png, > screenshot-3.png, screenshot-4.png, screenshot-5.png, screenshot-6.png > > > See attached screenshot. Using WKWebView plugin, new app. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-13610) Android default image assets are not compressed
Darryl Pogue created CB-13610: - Summary: Android default image assets are not compressed Key: CB-13610 URL: https://issues.apache.org/jira/browse/CB-13610 Project: Apache Cordova Issue Type: Bug Reporter: Darryl Pogue Assignee: Darryl Pogue The default splash screen and app icon images in Cordova-Android account for 7MB, and get bundled into the apk with minimal compression. Running them through pngquant and zopflipng results in assets that are only 1.7MB, which is a savings of 75% -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Updated] (CB-13610) Android default image assets are not compressed
[ https://issues.apache.org/jira/browse/CB-13610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darryl Pogue updated CB-13610: -- Priority: Minor (was: Major) > Android default image assets are not compressed > --- > > Key: CB-13610 > URL: https://issues.apache.org/jira/browse/CB-13610 > Project: Apache Cordova > Issue Type: Bug >Reporter: Darryl Pogue >Assignee: Darryl Pogue >Priority: Minor > > The default splash screen and app icon images in Cordova-Android account for > 7MB, and get bundled into the apk with minimal compression. > Running them through pngquant and zopflipng results in assets that are only > 1.7MB, which is a savings of 75% -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-13610) Android default image assets are not compressed
[ https://issues.apache.org/jira/browse/CB-13610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darryl Pogue resolved CB-13610. --- Resolution: Fixed Fix Version/s: cordova-android@7.0.0 > Android default image assets are not compressed > --- > > Key: CB-13610 > URL: https://issues.apache.org/jira/browse/CB-13610 > Project: Apache Cordova > Issue Type: Bug >Reporter: Darryl Pogue >Assignee: Darryl Pogue >Priority: Minor > Fix For: cordova-android@7.0.0 > > > The default splash screen and app icon images in Cordova-Android account for > 7MB, and get bundled into the apk with minimal compression. > Running them through pngquant and zopflipng results in assets that are only > 1.7MB, which is a savings of 75% -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-13525) cordova build doesn't pass build flag "-allowProvisioningUpdates" to xcodebuild
[
https://issues.apache.org/jira/browse/CB-13525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darryl Pogue resolved CB-13525.
---
Resolution: Fixed
Fix Version/s: cordova-ios@4.5.4
This should be fixed in cordova-ios 4.5.4, but in a slightly different way.
Rather than using build flags, we added a {{automaticProvisioning}} boolean
field to build.json. Docs change is pending, but you can read about it here:
https://github.com/apache/cordova-docs/pull/762/files?short_path=f22acfe#diff-f22acfe9e3ac5b3385cf807e058ccd72
> cordova build doesn't pass build flag "-allowProvisioningUpdates" to
> xcodebuild
> ---
>
> Key: CB-13525
> URL: https://issues.apache.org/jira/browse/CB-13525
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-ios
> Environment: cordova 7.1.0
> cordova iOS 4.5.3
> Xcode 9.1.0
>Reporter: Michael Schmidt
>Assignee: Suraj Pindoria
>Priority: Critical
> Fix For: cordova-ios@4.5.4
>
>
> build.json:
> {code}
> "ios": {
> "debug": {
> ...
> "buildFlag": [
> "-allowProvisioningUpdates"
> ]
> },
> "release": {
> ...
> "buildFlag": [
> "-allowProvisioningUpdates"
> ]
> }
> },
> {code}
> when running the following command:
> {code}
> cordova build ios --release --device --buildConfig="build.json" --verbose
> {code}
> cordova build shows that the build flag is detected:
> {code}
> Adding xcodebuildArg: -allowProvisioningUpdates
> {code}
> BUT it doesn't pass on the build flag to xcodebuild - as shown in the
> argument list to xcodebuild on an error:
> {code}
> Error: Error code 70 for command: xcodebuild with args:
> -exportArchive,-archivePath,DemoApp.xcarchive,-exportOptionsPlist,/demo/platforms/ios/exportOptions.plist,-exportPath,/demo/platforms/ios/build/device
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-13523) Add build config option to enable Xcode automatic provisioning
[ https://issues.apache.org/jira/browse/CB-13523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darryl Pogue resolved CB-13523. --- Resolution: Fixed Fix Version/s: cordova-ios@4.5.4 > Add build config option to enable Xcode automatic provisioning > -- > > Key: CB-13523 > URL: https://issues.apache.org/jira/browse/CB-13523 > Project: Apache Cordova > Issue Type: Improvement > Components: cordova-ios > Environment: Xcode 9 > Cordova-iOS 4.5.3 >Reporter: Darryl Pogue >Assignee: Darryl Pogue > Fix For: cordova-ios@4.5.4 > > > Xcode 9 made more changes to how provisioning works for apps, particularly > around manual vs automatic signing. > The changes required to support manual signing of release builds was > implemented as part of CB-13315. > In order for automatic signing to work, we need to pass an additional flag to > xcodebuild to allow Xcode to manage automatically updating provisioning > profiles as needed. I want to keep this being a build config option because > many people may not want to grant Xcode such power by default. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Closed] (CB-13298) npm WARN deprecated node-uuid@1.4.8: Use uuid module instead
[
https://issues.apache.org/jira/browse/CB-13298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darryl Pogue closed CB-13298.
-
Resolution: Duplicate
Seeing as this is caused by the npm2 dependency, I'm going to mark this as a
duplicate of CB-9626 which tracks removing that dependency entirely.
> npm WARN deprecated node-uuid@1.4.8: Use uuid module instead
>
>
> Key: CB-13298
> URL: https://issues.apache.org/jira/browse/CB-13298
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-common
>Affects Versions: 7.0.1
> Environment: NPM 5.4.0
>Reporter: Shad Sterling
>Priority: Minor
> Labels: beginner, dependencies, deprecation, easyfix,
> reproduced, triaged
>
> Running `npm install` with Cordova as a dependency raises this warning
> message:
> {code}
> npm WARN deprecated node-uuid@1.4.8: Use uuid module instead
> {code}
> `npm ls node-uuid` shows that Cordova depends on `node-uuid` in two places:
> {code}
> └─┬ cordova@7.0.1
> ├─┬ cordova-lib@7.0.1
> │ └─┬ npm@2.15.12
> │ └─┬ request@2.74.0
> │ └── node-uuid@1.4.7
> └─┬ insight@0.8.2
> └── node-uuid@1.4.8
> {code}
> The dependencies on `insight` and`npm` should be updated.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-13025) Remove use of React in plugins.cordova.io
[ https://issues.apache.org/jira/browse/CB-13025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darryl Pogue resolved CB-13025. --- Resolution: Fixed > Remove use of React in plugins.cordova.io > - > > Key: CB-13025 > URL: https://issues.apache.org/jira/browse/CB-13025 > Project: Apache Cordova > Issue Type: Task > Components: cordova-docs >Reporter: Shazron Abdullah >Assignee: Tommy-Carlos Williams >Priority: Critical > > plugins.cordova.io uses React. See if you can use Preact as a drop-in. > This only affects the website, which we don't "release". > Apache projects can't use React per LEGAL-303 as covered here and sent to the > PMCs: > https://issues.apache.org/jira/browse/LEGAL-303?focusedCommentId=16088663&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16088663 > Aug 31 2017 deadline plus NOTICE addition requirements (an email to the PMC > should already be sent with details). > However, we don't explicitly "include" React, it is a node.js dependency and > is installed at runtime: > https://github.com/apache/cordova-docs/blob/03b67269efe58ebd1cf12042ec9616bd1d05ea25/package.json#L47 > Even so, the advisory is that we can't even *use* React so we should remove > it accordingly. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-13001) NPM Installation loop with package-lock.json and cordova-plugin-device
[
https://issues.apache.org/jira/browse/CB-13001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darryl Pogue resolved CB-13001.
---
Resolution: Fixed
Fix Version/s: cordova@7.1.0
This should be fixed with the latest version of the Cordova tools
> NPM Installation loop with package-lock.json and cordova-plugin-device
> --
>
> Key: CB-13001
> URL: https://issues.apache.org/jira/browse/CB-13001
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-plugin-device
>Affects Versions: 1.1.0, 7.0.0, 1.1.3, 1.1.1, 7.0.2, cordova@7.0.0, 7.0.1
> Environment: Docker environment on bitrise.io & Windows 10 64-bit
> with nodejs 6.9.1 and NPM 5.0.4
>Reporter: Paedly
> Fix For: cordova@7.1.0
>
>
> If this lines are in the {{package-lock.json}} I get a symlink loop on my
> linux docker environment.
> {code:javascript}"cordova-plugin-device": {
> "version": "1.1.6",
> "resolved":
> "https://registry.npmjs.org/cordova-plugin-device/-/cordova-plugin-device-1.1.6.tgz";,
> "integrity": "sha1-LSF2TK18m4AVI+TgmjDgJLJJM0s="
> },{code}
> Here is the {{package.json}}:
> {code:javascript}{
> "version": "0.0.1",
> "author": "Ionic Framework",
> "homepage": "http://ionicframework.com/";,
> "private": true,
> "dependencies": {
> "cordova-plugin-device": "^1.1.6"
> },
> "devDependencies": {
> "@ionic/cli-plugin-cordova": "1.4.0",
> "@ionic/cli-plugin-ionic-angular": "1.3.1",
> "typescript": "2.3.4"
> },
> "cordova": {
> "plugins": {
> "cordova-plugin-device": {}
> },
> "platforms": [
> "android",
> "ios"
> ]
> }
> }{code}
> *And this is the error.*
> {code}Error: npm: Command failed with exit code 216 Error output:
> npm ERR! path
> /bitrise/src/node_modules/cordova-plugin-device/package.json
> npm ERR! code ELOOP
> npm ERR! errno -40
> npm ERR! syscall open
> npm ERR! ELOOP: too many symbolic links encountered, open
> '/bitrise/src/node_modules/cordova-plugin-device/package.json'{code}
> Don't know what the problem is with this {{package-lock.json}} entry.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-9525) Dependent plugins not restored with versions from config.xml
[
https://issues.apache.org/jira/browse/CB-9525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darryl Pogue resolved CB-9525.
--
Resolution: Fixed
> Dependent plugins not restored with versions from config.xml
>
>
> Key: CB-9525
> URL: https://issues.apache.org/jira/browse/CB-9525
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-lib
>Affects Versions: 5.2.0
> Environment: OSX
>Reporter: Darryl Pogue
>
> When I have a config.xml that uses a custom git branch of the
> cordova-plugin-file and the npm version of cordova-plugin-file-transfer, the
> npm version of cordova-plugin-file is installed before the git branch. This
> causes the app to use the npm version rather than the git branch as specified
> in config.xml.
> Test case:
> Create a new cordova project, replace the config.xml with the following, run
> cordova prepare.
> {code:xml}
>
> xmlns="http://www.w3.org/ns/widgets";
> xmlns:cdv="http://cordova.apache.org/ns/1.0";>
> HelloCordova
>
> A sample Apache Cordova application that responds to the deviceready
> event.
>
> http://cordova.io";>
> Apache Cordova Team
>
>
>
>
> http://*/*"; />
> https://*/*"; />
>
>
> mailto:*"; />
>
>
>
>
>
>
>
>
>
> spec="git://github.com/apache/cordova-plugin-file.git" />
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-11180) Ignore plugin mapper when a git spec is specified
[
https://issues.apache.org/jira/browse/CB-11180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darryl Pogue resolved CB-11180.
---
Resolution: Fixed
> Ignore plugin mapper when a git spec is specified
> -
>
> Key: CB-11180
> URL: https://issues.apache.org/jira/browse/CB-11180
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-lib
>Affects Versions: 6.0.0
>Reporter: Darryl Pogue
>Priority: Minor
> Labels: triaged
>
> We had a project with this in the config.xml:
> {code}
> spec="https://github.com/Telerik-Verified-Plugins/ScreenOrientation.git"; />
> {code}
> However, the cordova plugin mapper has an entry for
> {{net.yoik.cordova.plugins.screenorientation}} that was telling it to fetch
> from npm.
> The cordova prepare output said it was being fetched from npm, but there was
> a folder in ./plugins/ with the old ID and then it said that it failed to
> install for iOS because it was already installed for Android, and also said
> that it was fetching from npm again.
> The best solution is probably to avoid going through the plugin mapper if a
> spec is a git reference (or maybe if there's a spec at all?)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-13615) Release signing with build.json not working
Darryl Pogue created CB-13615:
-
Summary: Release signing with build.json not working
Key: CB-13615
URL: https://issues.apache.org/jira/browse/CB-13615
Project: Apache Cordova
Issue Type: Bug
Components: cordova-android
Reporter: Darryl Pogue
Assignee: Joe Bowser
With cordova-android master, I'm not setting signed release builds.
I'm specifying the keystore and passwords in my build.json file.
The output of {{cordova build android --device --release}} is as follows:
{code}
ANDROID_HOME=/usr/local/Caskroom/android-sdk/25.2.3
JAVA_HOME=/Library/Java/JavaVirtualMachines/jdk1.8.0_112.jdk/Contents/Home
Reading build config file: .../build.json
Reading the keystore from: ../correct.keystore
studio
Starting a Gradle Daemon (subsequent builds will be faster)
:wrapper
BUILD SUCCESSFUL in 4s
1 actionable task: 1 executed
Subproject Path: CordovaLib
Subproject Path: app
Starting a Gradle Daemon (subsequent builds will be faster)
publishNonDefault is deprecated and has no effect anymore. All variants are now
published.
Download
https://repo1.maven.org/maven2/com/google/j2objc/j2objc-annotations/1.1/j2objc-annotations-1.1.jar
The Task.leftShift(Closure) method has been deprecated and is scheduled to be
removed in Gradle 5.0. Please use Task.doLast(Action) instead.
at
build_mwups4l6vzpjxql6irnsfnd4.run(.../platforms/android/app/build.gradle:143)
:CordovaLib:preBuild UP-TO-DATE
:CordovaLib:preReleaseBuild UP-TO-DATE
:CordovaLib:compileReleaseAidl
:CordovaLib:compileReleaseRenderscript
:CordovaLib:checkReleaseManifest
:CordovaLib:generateReleaseBuildConfig
:CordovaLib:prepareLintJar
:CordovaLib:generateReleaseResValues
:CordovaLib:generateReleaseResources
:CordovaLib:packageReleaseResources
:CordovaLib:platformAttrExtractor
:CordovaLib:processReleaseManifest
:CordovaLib:javaPreCompileRelease
:CordovaLib:processReleaseJavaRes NO-SOURCE
:app:preBuild UP-TO-DATE
:app:preReleaseBuild
:app:compileReleaseAidl
:CordovaLib:packageReleaseRenderscript NO-SOURCE
:app:compileReleaseRenderscript
:app:checkReleaseManifest
:app:generateReleaseBuildConfig
:app:prepareLintJar
:app:generateReleaseResValues
:app:generateReleaseResources
:app:mergeReleaseResources
:app:createReleaseCompatibleScreenManifests
:app:processReleaseManifest
:app:splitsDiscoveryTaskRelease
:app:compileReleaseNdk NO-SOURCE
:CordovaLib:mergeReleaseShaders
:CordovaLib:compileReleaseShaders
:CordovaLib:generateReleaseAssets
:CordovaLib:mergeReleaseAssets
:app:mergeReleaseShaders
:app:compileReleaseShaders
:app:generateReleaseAssets
:app:mergeReleaseAssets
:app:extractTryWithResourcesSupportJarRelease
:CordovaLib:compileReleaseNdk NO-SOURCE
:CordovaLib:mergeReleaseJniLibFolders
:CordovaLib:transformNativeLibsWithMergeJniLibsForRelease
:CordovaLib:transformNativeLibsWithIntermediateJniLibsForRelease
:app:mergeReleaseJniLibFolders
:app:processReleaseJavaRes NO-SOURCE
:CordovaLib:processReleaseResources
:CordovaLib:generateReleaseSources
:CordovaLib:compileReleaseJavaWithJavacNote: Some input files use or override a
deprecated API.
Note: Recompile with -Xlint:deprecation for details.
:CordovaLib:transformClassesAndResourcesWithPrepareIntermediateJarsForRelease
:app:processReleaseResources
:app:generateReleaseSources
:app:javaPreCompileRelease
:app:compileReleaseJavaWithJavac
:app:compileReleaseSources
:app:transformClassesWithStackFramesFixerForRelease
:app:transformClassesWithDesugarForRelease
:app:transformClassesWithPreDexForRelease
:app:transformDexWithDexForRelease
:app:transformNativeLibsWithMergeJniLibsForRelease
:app:transformResourcesWithMergeJavaResForRelease
:app:packageRelease
:app:lintVitalRelease
:app:assembleRelease
:app:cdvBuildRelease
BUILD SUCCESSFUL in 34s
46 actionable tasks: 46 executed
Built the following apk(s):
.../platforms/android/app/build/outputs/apk/release/android-release-unsigned.apk
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13298) npm WARN deprecated node-uuid@1.4.8: Use uuid module instead
[
https://issues.apache.org/jira/browse/CB-13298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16297465#comment-16297465
]
Darryl Pogue commented on CB-13298:
---
`insight` was updated (along with the removal of the `npm` dependency) in
Cordova 8.
> npm WARN deprecated node-uuid@1.4.8: Use uuid module instead
>
>
> Key: CB-13298
> URL: https://issues.apache.org/jira/browse/CB-13298
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-common
>Affects Versions: 7.0.1
> Environment: NPM 5.4.0
>Reporter: Shad Sterling
>Priority: Minor
> Labels: beginner, dependencies, deprecation, easyfix,
> reproduced, triaged
>
> Running `npm install` with Cordova as a dependency raises this warning
> message:
> {code}
> npm WARN deprecated node-uuid@1.4.8: Use uuid module instead
> {code}
> `npm ls node-uuid` shows that Cordova depends on `node-uuid` in two places:
> {code}
> └─┬ cordova@7.0.1
> ├─┬ cordova-lib@7.0.1
> │ └─┬ npm@2.15.12
> │ └─┬ request@2.74.0
> │ └── node-uuid@1.4.7
> └─┬ insight@0.8.2
> └── node-uuid@1.4.8
> {code}
> The dependencies on `insight` and`npm` should be updated.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Resolved] (CB-9626) Cordova-Lib requires NPM as a dependency
[ https://issues.apache.org/jira/browse/CB-9626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darryl Pogue resolved CB-9626. -- Resolution: Fixed Fix Version/s: cordova@8.0.0 The npm@2 dependency has been removed in Cordova 8 > Cordova-Lib requires NPM as a dependency > > > Key: CB-9626 > URL: https://issues.apache.org/jira/browse/CB-9626 > Project: Apache Cordova > Issue Type: Wish > Components: cordova-lib >Reporter: Robert Baker > Labels: backlog, tools-next > Fix For: cordova@8.0.0 > > > cordova-create is installing NPM 2.x in my node modules folder. > There should be a way around this, it should use the same version I'm already > using. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13298) npm WARN deprecated node-uuid@1.4.8: Use uuid module instead
[
https://issues.apache.org/jira/browse/CB-13298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16297877#comment-16297877
]
Darryl Pogue commented on CB-13298:
---
It's not possible to do that: Removing the npm dependency is a breaking change,
so it requires a major version bump (as per semver, which Cordova follows)
> npm WARN deprecated node-uuid@1.4.8: Use uuid module instead
>
>
> Key: CB-13298
> URL: https://issues.apache.org/jira/browse/CB-13298
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-common
>Affects Versions: 7.0.1
> Environment: NPM 5.4.0
>Reporter: Shad Sterling
>Priority: Minor
> Labels: beginner, dependencies, deprecation, easyfix,
> reproduced, triaged
>
> Running `npm install` with Cordova as a dependency raises this warning
> message:
> {code}
> npm WARN deprecated node-uuid@1.4.8: Use uuid module instead
> {code}
> `npm ls node-uuid` shows that Cordova depends on `node-uuid` in two places:
> {code}
> └─┬ cordova@7.0.1
> ├─┬ cordova-lib@7.0.1
> │ └─┬ npm@2.15.12
> │ └─┬ request@2.74.0
> │ └── node-uuid@1.4.7
> └─┬ insight@0.8.2
> └── node-uuid@1.4.8
> {code}
> The dependencies on `insight` and`npm` should be updated.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-13797) Fetch failing to install plugin dependencies
Darryl Pogue created CB-13797:
-
Summary: Fetch failing to install plugin dependencies
Key: CB-13797
URL: https://issues.apache.org/jira/browse/CB-13797
Project: Apache Cordova
Issue Type: Bug
Components: cordova-fetch
Environment: cordova@8.0.0
cordova-common@2.2.1
cordova-lib@8.0.0
cordova-fetch@1.3.0
npm@5.6.0
node@9.4.0
Reporter: Darryl Pogue
I'm currently unable to install Microsoft's cordova-plugin-code-push due to
some incredibly confusing errors when installing the plugin dependencies.
The plugin [lists 3
dependencies|https://github.com/Microsoft/cordova-plugin-code-push/blob/e828a5eacd42dcd81bacf121a3e62735c3500227/plugin.xml#L10-L12]
in plugin.xml.
Cordova successfully installs the first (code-push) dependency.
Cordova attempts to install the second (cordova-plugin-device) dependency. It
appears that the npm install is successful.
At the end of the npm install, cordova-fetch [attempts to
discover|https://github.com/apache/cordova-fetch/blob/master/index.js#L100]
what was just installed. Rather than finding "cordova-plugin-device", it finds
"code-push" for a second time.
Then it fails with the following confusing error message:
{noformat}
Failed to install 'cordova-plugin-code-push': Error: Expected plugin to have ID
"cordova-plugin-dialogs" but got "code-push".{noformat}
The full verbose output from {{cordova prepare}} is below:
{noformat}
Discovered plugin "cordova-plugin-code-push" in config.xml. Adding it to the
project
No scripts found for hook "before_plugin_add".
Calling plugman.fetch on plugin "cordova-plugin-code-push@^1.11.2"
Running command: npm install cordova-plugin-code-push@^1.11.2 --production
--no-save
Command finished with error code 0: npm
install,cordova-plugin-code-push@^1.11.2,--production,--no-save
Copying plugin "/PROJECT/node_modules/cordova-plugin-code-push" =>
"/PROJECT/plugins/cordova-plugin-code-push"
Calling plugman.install on plugin "/PROJECT/plugins/cordova-plugin-code-push"
for platform "android
Installing "cordova-plugin-code-push" for android
Running command: /PROJECT/platforms/android/cordova/version
Command finished with error code 0: /PROJECT/platforms/android/cordova/version
Dependencies detected, iterating through them...
Requesting plugin "code-push@2.0.4".
Plugin dependency "code-push" not fetched, retrieving then installing.
Running command: npm install code-push@2.0.4 --production --no-save
Command finished with error code 0: npm
install,code-push@2.0.4,--production,--no-save
Copying plugin "/PROJECT/node_modules/code-push" => "/PROJECT/plugins/code-push"
Installing "code-push" for android
Finding scripts for "before_plugin_install" hook from plugin code-push on
android platform only.
No scripts found for hook "before_plugin_install".
Install start for "code-push" on android.
Beginning processing of action stack for android project...
Action stack processing complete.
Install complete for code-push on android.
Finding scripts for "after_plugin_install" hook from plugin code-push on
android platform only.
No scripts found for hook "after_plugin_install".
Requesting plugin "cordova-plugin-dialogs@>=1.1.1".
Plugin dependency "cordova-plugin-dialogs" not fetched, retrieving then
installing.
Running command: npm install cordova-plugin-dialogs@>=1.1.1 --production
--no-save
Command finished with error code 0: npm
install,cordova-plugin-dialogs@>=1.1.1,--production,--no-save
Copying plugin "/PROJECT/node_modules/code-push" => "/PROJECT/plugins/code-push"
Failed to install 'cordova-plugin-code-push': Error: Expected plugin to have ID
"cordova-plugin-dialogs" but got "code-push".
at checkID (/PROJECT/node_modules/cordova-lib/src/plugman/fetch.js:215:15)
at /PROJECT/node_modules/cordova-lib/src/plugman/fetch.js:199:9
at _fulfilled (/PROJECT/node_modules/cordova-lib/node_modules/q/q.js:787:54)
at self.promiseDispatch.done
(/PROJECT/node_modules/cordova-lib/node_modules/q/q.js:816:30)
at Promise.promise.promiseDispatch
(/PROJECT/node_modules/cordova-lib/node_modules/q/q.js:749:13)
at /PROJECT/node_modules/cordova-lib/node_modules/q/q.js:557:44
at flush (/PROJECT/node_modules/cordova-lib/node_modules/q/q.js:108:17)
at process._tickCallback (internal/process/next_tick.js:150:11)
Failed to restore plugin "cordova-plugin-code-push" from config.xml. You might
need to try adding it again. Error: Error: Expected plugin to have ID
"cordova-plugin-dialogs" but got "code-push".{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13797) Fetch failing to install plugin dependencies
[
https://issues.apache.org/jira/browse/CB-13797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16361808#comment-16361808
]
Darryl Pogue commented on CB-13797:
---
After your comment, I thought maybe one of my tools was to blame, but it turns
out I can still reproduce this even with cordova from npm.
I put together a test case here: https://github.com/dpogue/cb-13797
> Fetch failing to install plugin dependencies
>
>
> Key: CB-13797
> URL: https://issues.apache.org/jira/browse/CB-13797
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-fetch
> Environment: cordova@8.0.0
> cordova-common@2.2.1
> cordova-lib@8.0.0
> cordova-fetch@1.3.0
> npm@5.6.0
> node@9.4.0
>
>Reporter: Darryl Pogue
>Priority: Critical
>
> I'm currently unable to install Microsoft's cordova-plugin-code-push due to
> some incredibly confusing errors when installing the plugin dependencies.
> The plugin [lists 3
> dependencies|https://github.com/Microsoft/cordova-plugin-code-push/blob/e828a5eacd42dcd81bacf121a3e62735c3500227/plugin.xml#L10-L12]
> in plugin.xml.
> Cordova successfully installs the first (code-push) dependency.
> Cordova attempts to install the second (cordova-plugin-device) dependency. It
> appears that the npm install is successful.
> At the end of the npm install, cordova-fetch [attempts to
> discover|https://github.com/apache/cordova-fetch/blob/master/index.js#L100]
> what was just installed. Rather than finding "cordova-plugin-device", it
> finds "code-push" for a second time.
> Then it fails with the following confusing error message:
> {noformat}
> Failed to install 'cordova-plugin-code-push': Error: Expected plugin to have
> ID "cordova-plugin-dialogs" but got "code-push".{noformat}
> The full verbose output from {{cordova prepare}} is below:
> {noformat}
> Discovered plugin "cordova-plugin-code-push" in config.xml. Adding it to the
> project
> No scripts found for hook "before_plugin_add".
> Calling plugman.fetch on plugin "cordova-plugin-code-push@^1.11.2"
> Running command: npm install cordova-plugin-code-push@^1.11.2 --production
> --no-save
> Command finished with error code 0: npm
> install,cordova-plugin-code-push@^1.11.2,--production,--no-save
> Copying plugin "/PROJECT/node_modules/cordova-plugin-code-push" =>
> "/PROJECT/plugins/cordova-plugin-code-push"
> Calling plugman.install on plugin "/PROJECT/plugins/cordova-plugin-code-push"
> for platform "android
> Installing "cordova-plugin-code-push" for android
> Running command: /PROJECT/platforms/android/cordova/version
> Command finished with error code 0:
> /PROJECT/platforms/android/cordova/version
> Dependencies detected, iterating through them...
> Requesting plugin "code-push@2.0.4".
> Plugin dependency "code-push" not fetched, retrieving then installing.
> Running command: npm install code-push@2.0.4 --production --no-save
> Command finished with error code 0: npm
> install,code-push@2.0.4,--production,--no-save
> Copying plugin "/PROJECT/node_modules/code-push" =>
> "/PROJECT/plugins/code-push"
> Installing "code-push" for android
> Finding scripts for "before_plugin_install" hook from plugin code-push on
> android platform only.
> No scripts found for hook "before_plugin_install".
> Install start for "code-push" on android.
> Beginning processing of action stack for android project...
> Action stack processing complete.
> Install complete for code-push on android.
> Finding scripts for "after_plugin_install" hook from plugin code-push on
> android platform only.
> No scripts found for hook "after_plugin_install".
> Requesting plugin "cordova-plugin-dialogs@>=1.1.1".
> Plugin dependency "cordova-plugin-dialogs" not fetched, retrieving then
> installing.
> Running command: npm install cordova-plugin-dialogs@>=1.1.1 --production
> --no-save
> Command finished with error code 0: npm
> install,cordova-plugin-dialogs@>=1.1.1,--production,--no-save
> Copying plugin "/PROJECT/node_modules/code-push" =>
> "/PROJECT/plugins/code-push"
> Failed to install 'cordova-plugin-code-push': Error: Expected plugin to have
> ID "cordova-plugin-dialogs" but got "code-push".
> at checkID (/PROJECT/node_modules/cordova-lib/src/plugman/fetch.js:215:15)
> at /PROJECT/node_modules/cordova-lib/src/plugman/fetch.js:199:9
> at _fulfilled (/PROJECT/node_modules/cordova-lib/node_modules/q/q.js:787:54)
> at self.promiseDispatch.done
> (/PROJECT/node_modules/cordova-lib/node_modules/q/q.js:816:30)
> at Promise.promise.promiseDispatch
> (/PROJECT/node_modules/cordova-lib/node_modules/q/q.js:749:13)
> at /PROJECT/node_modules/cordova-lib/node_modules/q/q.js:557:44
> at flush (/PROJECT/node_modules/cordova-lib/node_modules/q/q.js:108:17)
> at process._tickCallback (internal/process/next_tick.js:150:11)
> Failed to restore pl
[jira] [Commented] (CB-12013) input caret position wrong when scaling iframe
[ https://issues.apache.org/jira/browse/CB-12013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15664951#comment-15664951 ] Darryl Pogue commented on CB-12013: --- This is a Safari problem, not a Cordova problem. It's probably the same cause as https://bugs.webkit.org/show_bug.cgi?id=138201 > input caret position wrong when scaling iframe > -- > > Key: CB-12013 > URL: https://issues.apache.org/jira/browse/CB-12013 > Project: Apache Cordova > Issue Type: Bug > Components: iOS >Affects Versions: 3.5.0 > Environment: iOS 10 on iPad 3 >Reporter: Pieter Biesemans >Priority: Critical > > When loading content through an iframe that is scaled or embedded in a scaled > page (through css transfrom:scale()) the caret position of the input is wrong. > We loaded a simple form through an iframe. This form is part of a > presentation, which is scaled down or up to fit the screen. When selecting an > input to input some data (be it a text input, number input, contenteditable > div, ...) the OS treats the input as if it is in the location it was before > the scaling was applied. > The issue is only present when running in Cordova. We cannot replicate it > running the same code in Safari or Chrome on the same device. > Screenshot (when selecting the textarea): http://imgur.com/JllMQmg -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-12013) input caret position wrong when scaling iframe
[ https://issues.apache.org/jira/browse/CB-12013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15666490#comment-15666490 ] Darryl Pogue commented on CB-12013: --- Have you tested with the WKWebView plugin? Safari on iOS effectively uses WKWebView now, while Cordova by default uses the older (but more reliable) UIWebView. > input caret position wrong when scaling iframe > -- > > Key: CB-12013 > URL: https://issues.apache.org/jira/browse/CB-12013 > Project: Apache Cordova > Issue Type: Bug > Components: iOS >Affects Versions: 3.5.0 > Environment: iOS 10 on iPad 3 >Reporter: Pieter Biesemans >Priority: Critical > > When loading content through an iframe that is scaled or embedded in a scaled > page (through css transfrom:scale()) the caret position of the input is wrong. > We loaded a simple form through an iframe. This form is part of a > presentation, which is scaled down or up to fit the screen. When selecting an > input to input some data (be it a text input, number input, contenteditable > div, ...) the OS treats the input as if it is in the location it was before > the scaling was applied. > The issue is only present when running in Cordova. We cannot replicate it > running the same code in Safari or Chrome on the same device. > Screenshot (when selecting the textarea): http://imgur.com/JllMQmg -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-12473) [iOS] Building for simulator clobbers device builds
Darryl Pogue created CB-12473:
-
Summary: [iOS] Building for simulator clobbers device builds
Key: CB-12473
URL: https://issues.apache.org/jira/browse/CB-12473
Project: Apache Cordova
Issue Type: Bug
Components: iOS
Reporter: Darryl Pogue
Assignee: Darryl Pogue
Priority: Minor
When building for the iOS Simulator, the build step deletes
{{project_path/build/device}} when it should be deleting
{{project_path/build/emulator}}. This means you cannot build for device and
then for simulator without clobbering the device builds.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Assigned] (CB-12656) Add docs for support in config.xml
[ https://issues.apache.org/jira/browse/CB-12656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darryl Pogue reassigned CB-12656: - Assignee: Darryl Pogue > Add docs for support in config.xml > -- > > Key: CB-12656 > URL: https://issues.apache.org/jira/browse/CB-12656 > Project: Apache Cordova > Issue Type: Sub-task > Components: Docs >Reporter: Shazron Abdullah >Assignee: Darryl Pogue > > Should be copy paste from plugin.xml > Right now there is support in cordova-android@6.2.1 and possibly > cordova-ios@4.4.0 > Presumably this feature was added in cordova@6.5.0 CLI release -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-13767) Huge performance issues moving from cordova 6.5 to 8 due to cordova-fetch
[
https://issues.apache.org/jira/browse/CB-13767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16408560#comment-16408560
]
Darryl Pogue commented on CB-13767:
---
One of the reasons it is slow is that it appears to always fetch from npm, even
when the plugin or platform has already been installed to node_modules by way
of a normal {{npm install}}. It doesn't attempt to find that existing copy, but
reinstalls it every time. It does the same for any dependencies of those
platforms & plugins.
> Huge performance issues moving from cordova 6.5 to 8 due to cordova-fetch
> -
>
> Key: CB-13767
> URL: https://issues.apache.org/jira/browse/CB-13767
> Project: Apache Cordova
> Issue Type: Bug
>Reporter: Andrew Crites
>Priority: Major
>
> This is for a project with a wide variety of plugins ... about 25. This may
> be above average, but not extreme. I've updated the project from cordova 6.5
> to cordova 8. Cordova 8 always uses {{cordova-fetch}} to install plugins, so
> I can't opt out. Before, I was not using {{cordova-fetch}}.
> {code}
> $ time npx cordova@6.5 platform add ios
> 23.85s user 9.26s system 130% cpu 25.414 total
> $ time npx cordova@8 platform add ios --nosave
> 402.44s user 61.94s system 119% cpu 6:28.09 total
> {code}
> That takes over 15 times longer. {{--nosave}} was used since this is the
> default behavior for 6.5.
> For subsequent installations using {{--save}} (or default) the performance is
> still like this.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-14063) Remove Node 4 from CI
Darryl Pogue created CB-14063: - Summary: Remove Node 4 from CI Key: CB-14063 URL: https://issues.apache.org/jira/browse/CB-14063 Project: Apache Cordova Issue Type: Task Reporter: Darryl Pogue Assignee: Darryl Pogue After April 30th, 2018, Node 4.x is deprecated and we no longer officially support it. Ref: https://cordova.apache.org/news/2016/10/01/0.x-4.x-deprecation-timeline.html -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-14064) Remove Node 4 from CI - cordova-common
Darryl Pogue created CB-14064: - Summary: Remove Node 4 from CI - cordova-common Key: CB-14064 URL: https://issues.apache.org/jira/browse/CB-14064 Project: Apache Cordova Issue Type: Sub-task Components: cordova-common Reporter: Darryl Pogue Assignee: Darryl Pogue -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-14065) Remove Node 4 from CI - cordova-lib
Darryl Pogue created CB-14065: - Summary: Remove Node 4 from CI - cordova-lib Key: CB-14065 URL: https://issues.apache.org/jira/browse/CB-14065 Project: Apache Cordova Issue Type: Sub-task Components: cordova-lib Reporter: Darryl Pogue Assignee: Darryl Pogue -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-14066) Remove Node 4 from CI - cordova-fetch
Darryl Pogue created CB-14066: - Summary: Remove Node 4 from CI - cordova-fetch Key: CB-14066 URL: https://issues.apache.org/jira/browse/CB-14066 Project: Apache Cordova Issue Type: Sub-task Components: cordova-fetch Reporter: Darryl Pogue Assignee: Darryl Pogue -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-14067) Remove Node 4 from CI - cordova-create
Darryl Pogue created CB-14067: - Summary: Remove Node 4 from CI - cordova-create Key: CB-14067 URL: https://issues.apache.org/jira/browse/CB-14067 Project: Apache Cordova Issue Type: Sub-task Components: cordova-create Reporter: Darryl Pogue Assignee: Darryl Pogue -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
