[jira] [Commented] (CB-7818) CLI builds ignore Distribution certificates
[ https://issues.apache.org/jira/browse/CB-7818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14176629#comment-14176629 ] ASF GitHub Bot commented on CB-7818: Github user SidneyS commented on the pull request: https://github.com/apache/cordova-ios/pull/114#issuecomment-59688070 Thanks @shazron, just pushed the new version. We also use a custom build system which is regexing/patching build.xcconfig on runtime (..). I amended the commit, choice of xcconfig it is now solved via inheritance from build.xcconfig. build-debug.xcconfig is empty but can by extended as users see fit, as it overrides build.xcconfig per default. build-release.xcconfig always overrides build.xcconfig when used. Also added ASF comment section and some documentation. CLI builds ignore Distribution certificates --- Key: CB-7818 URL: https://issues.apache.org/jira/browse/CB-7818 Project: Apache Cordova Issue Type: Bug Components: iOS Affects Versions: 3.5.0 Reporter: SidneyS Fix For: Master Hi, currently, cordova build --release --device yields in device builds using a default iOS Development-type Signing Identity. Intuitively, using release in conjunction with device should try to leverage a local iOS Distribution-type identity to enable CLI adhoc/inhouse-builds without patching xcconfig/xcodeproject files on runtime, or re-signing the created binary after using the default build process. -- 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-6911) [CordovaJS][iOS 8] - deprecated attempt to access property errors when accessing anything off window.navigator
[ https://issues.apache.org/jira/browse/CB-6911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14176658#comment-14176658 ] Fabian Diehl commented on CB-6911: -- [~andrew] make sure you use the latest version of the geolocation plugin (0.3.10)! I had the same problem in an earlier state of this bug report and I had to update to the dev version to get it working. 0.3.10 works for me, tested this morning. [CordovaJS][iOS 8] - deprecated attempt to access property errors when accessing anything off window.navigator Key: CB-6911 URL: https://issues.apache.org/jira/browse/CB-6911 Project: Apache Cordova Issue Type: Sub-task Components: CordovaJS Environment: iOS 8 beta 5 (device) Reporter: Jeff Schilling Assignee: Shazron Abdullah Fix For: 3.7.0 Attachments: Screen Shot 2014-09-01 at 9.03.30 pm.png, Screen Shot 2014-09-04 at 9.30.58 pm.png references to window.navigator.* (platform, geolocation) etc fail with Deprecated attempt to access property 'geolocation' on a non-Navigator object. -- 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-7759) Application slows down after moving device time backwards on Samsung devices with android
[ https://issues.apache.org/jira/browse/CB-7759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14176743#comment-14176743 ] Matus Pleva commented on CB-7759: - Every time when somebody changes time in system settings. Even 1 minute back will slow application down. Application slows down after moving device time backwards on Samsung devices with android - Key: CB-7759 URL: https://issues.apache.org/jira/browse/CB-7759 Project: Apache Cordova Issue Type: Bug Components: Android Affects Versions: 3.2.0, 3.5.0 Environment: Samsung devices with android such as Samsung Galaxy Ace (android 2.3.3), Samsung Galaxy SIII mini (android 4.2.2) Reporter: Matus Pleva Priority: Minor Labels: android, freeze, samsung, timemove When device time is moved backwards, application GUI slows down, javascript timers stop working, css animations don't work too. After a while everything start working again. It seems that recovery time depends on how much the time is moved. (1min backwards - recovery about 2min). I tested it also on Nexus 4 and Nexus 7 (both android 4.4.4) but here the problem doesn't occur. This issue can be easily reproduced by creating new cordova project (sample application with device ready indicator). When time is moved back, css animation on green box stops. You can add js timer there and again it stops. -- 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-7780) iPhone app on iPad (iOS 8)
[ https://issues.apache.org/jira/browse/CB-7780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14176760#comment-14176760 ] Tom Bell commented on CB-7780: -- I would like to add this is only an issue when the iPhone app is locked to portrait in the properties, and the device is landscape when the application is launched. When the device is portrait there is no issue. iPhone app on iPad (iOS 8) -- Key: CB-7780 URL: https://issues.apache.org/jira/browse/CB-7780 Project: Apache Cordova Issue Type: Bug Components: iOS Affects Versions: 3.6.3 Reporter: Tom Bell When running an iPhone only, portrait only app on an iPad running iOS 8, the viewport is pretty messed up. I've tested this using a blank Cordova project from scratch. Removing the `height` and `width` options from the viewport. The viewport seems to resize to half the screen width, when viewing in landscape. It should keep the normal portrait viewport and be portrait. -- 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-7633) [iOS 8][SplashScreen] Add support for iPhone 6 and iPhone 6 Plus resolutions
[ https://issues.apache.org/jira/browse/CB-7633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14176857#comment-14176857 ] Angus Bremner commented on CB-7633: --- Can anyone explain in what capacity does this now support the iPhone 6? I tried creating a new project from scratch using Cordova 4.0 and the latest version of this plugin still causes the app to launch the iPhone 5 splash image and scale up on iPhone 6. When adding the iOS platform, It would be good if Cordova could generate the default splash files under Resources/splash for iPhone 6, so it's an easy matter of replacing these files without having to figure out the correct file names. I've noticed that if selecting MainViewController as the Launch Screen File, this will display the correct resolution - but the splash is blank to start then we get a flicker of the actual iPhone 6 splash before it's ready. For now I am using a LaunchImage asset, but this also has a delay of 1 - 2 seconds after showing the splash before device ready. Any advice appreciated. [iOS 8][SplashScreen] Add support for iPhone 6 and iPhone 6 Plus resolutions Key: CB-7633 URL: https://issues.apache.org/jira/browse/CB-7633 Project: Apache Cordova Issue Type: Sub-task Components: Plugin SplashScreen Reporter: Shazron Abdullah Assignee: Shazron Abdullah See https://github.com/apache/cordova-plugin-splashscreen/pull/26 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Comment Edited] (CB-7633) [iOS 8][SplashScreen] Add support for iPhone 6 and iPhone 6 Plus resolutions
[ https://issues.apache.org/jira/browse/CB-7633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14176857#comment-14176857 ] Angus Bremner edited comment on CB-7633 at 10/20/14 12:15 PM: -- Can anyone explain in what capacity does this now support the iPhone 6? I tried creating a new project from scratch using Cordova 4.0 and the latest version of this plugin still causes the app to launch the iPhone 5 splash image and scale up on iPhone 6. When adding the iOS platform, It would be good if Cordova could generate the default splash files under Resources/splash for iPhone 6, so it's an easy matter of replacing these files without having to figure out the correct file names. I've noticed that if selecting MainViewController as the Launch Screen File, this will display the correct resolution - but the splash is blank to start then we get a brief flicker of the actual iPhone 6 splash before it's ready. If I use a LaunchImage asset, I get the reverse problem of the splash to start and then a delay of blank before device ready. Any advice appreciated. was (Author: abremner): Can anyone explain in what capacity does this now support the iPhone 6? I tried creating a new project from scratch using Cordova 4.0 and the latest version of this plugin still causes the app to launch the iPhone 5 splash image and scale up on iPhone 6. When adding the iOS platform, It would be good if Cordova could generate the default splash files under Resources/splash for iPhone 6, so it's an easy matter of replacing these files without having to figure out the correct file names. I've noticed that if selecting MainViewController as the Launch Screen File, this will display the correct resolution - but the splash is blank to start then we get a flicker of the actual iPhone 6 splash before it's ready. For now I am using a LaunchImage asset, but this also has a delay of 1 - 2 seconds after showing the splash before device ready. Any advice appreciated. [iOS 8][SplashScreen] Add support for iPhone 6 and iPhone 6 Plus resolutions Key: CB-7633 URL: https://issues.apache.org/jira/browse/CB-7633 Project: Apache Cordova Issue Type: Sub-task Components: Plugin SplashScreen Reporter: Shazron Abdullah Assignee: Shazron Abdullah See https://github.com/apache/cordova-plugin-splashscreen/pull/26 -- 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] [Reopened] (CB-6761) Calling a function the first time no callbacks are being executed
[
https://issues.apache.org/jira/browse/CB-6761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Grieve reopened CB-6761:
---
Calling a function the first time no callbacks are being executed
-
Key: CB-6761
URL: https://issues.apache.org/jira/browse/CB-6761
Project: Apache Cordova
Issue Type: Bug
Components: Android, CordovaJS
Affects Versions: 3.5.0
Environment: Nexus 5, Android 4.4.2
Reporter: Roy Ackermann
Assignee: Andrew Grieve
Priority: Blocker
Labels: bridge, callback, function
Attachments: sidemenu.tar.gz
Using different functions the same error occurs. Calling a function the first
time no callbacks are being executed. There is no error in the log. Using the
same function again for a second call, everything works fine. Now the first
call is being executed as well and I receive the callback from the first
excution.
It looks like something is wainting. It is odd that the second call works and
executes the first call as well.
I found this bug on this calls:
- window.requestFileSystem(LocalFileSystem.PERSISTENT, 3097152, gotFS, fail);
- navigator.camera.getPicture(onSuccessCapturePhoto, onFailCamera, {
targetWidth: 1200, targetHeight: 1200, quality: 55, destinationType:
Camera.DestinationType.FILE_URI, saveToPhotoAlbum: true,
correctOrientation:true});
- navigator.camera.getPicture(onSuccessGetPhoto, onFailCamera, { targetWidth:
1000,targetHeight: 1000, quality: 65, destinationType:
Camera.DestinationType.FILE_URI , saveToPhotoAlbum: false , sourceType:
Camera.PictureSourceType.SAVEDPHOTOALBUM, correctOrientation:true});
--
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-3325) Add PDF support to the InAppBrowser within Android
[ https://issues.apache.org/jira/browse/CB-3325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14176881#comment-14176881 ] Andrew Grieve commented on CB-3325: --- You might try: http://mozilla.github.io/pdf.js Add PDF support to the InAppBrowser within Android -- Key: CB-3325 URL: https://issues.apache.org/jira/browse/CB-3325 Project: Apache Cordova Issue Type: Improvement Components: Android Affects Versions: 2.6.0 Environment: Windows 7, Eclipse v3.8.0 Reporter: Kelvin Dart Priority: Minor Fix For: Master When I was making use of the ChildBrowser for both iOS and Android, I wrote an extra bit of code to enable PDF support for the Android version (which started up the installed PDF application if there was one). I also understand that the Android WebView doesn't natively support viewing a PDF document which is why it doesn't fully behave like the iOS version - but is it possible to either: 1) write similar code which, if the opened URL is directed to a PDF file, then it opens the native PDF reader or; 2) integrate a PDF view into the InAppBrowser which opens a PDF document much like InAppBrowser does on iOS. (1) is what I currently have working at the moment and would probably be easiest. (2) is what would be very good but I expect more difficult to achieve. -- 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-7759) Application slows down after moving device time backwards on Samsung devices with android
[ https://issues.apache.org/jira/browse/CB-7759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14176890#comment-14176890 ] Joe Bowser commented on CB-7759: Right, and how often would the average user even change the time? Most phones get the time from the cell phone network. Application slows down after moving device time backwards on Samsung devices with android - Key: CB-7759 URL: https://issues.apache.org/jira/browse/CB-7759 Project: Apache Cordova Issue Type: Bug Components: Android Affects Versions: 3.2.0, 3.5.0 Environment: Samsung devices with android such as Samsung Galaxy Ace (android 2.3.3), Samsung Galaxy SIII mini (android 4.2.2) Reporter: Matus Pleva Priority: Minor Labels: android, freeze, samsung, timemove When device time is moved backwards, application GUI slows down, javascript timers stop working, css animations don't work too. After a while everything start working again. It seems that recovery time depends on how much the time is moved. (1min backwards - recovery about 2min). I tested it also on Nexus 4 and Nexus 7 (both android 4.4.4) but here the problem doesn't occur. This issue can be easily reproduced by creating new cordova project (sample application with device ready indicator). When time is moved back, css animation on green box stops. You can add js timer there and again it stops. -- 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-7759) Application slows down after moving device time backwards on Samsung devices with android
[ https://issues.apache.org/jira/browse/CB-7759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14176897#comment-14176897 ] Matus Pleva commented on CB-7759: - In our case it could be quite often. We are developing application where we measure employee working time. User could change it to have more working hours and bigger reward. So we have to somehow handle time moves, but it is not possible when application stops working. Application slows down after moving device time backwards on Samsung devices with android - Key: CB-7759 URL: https://issues.apache.org/jira/browse/CB-7759 Project: Apache Cordova Issue Type: Bug Components: Android Affects Versions: 3.2.0, 3.5.0 Environment: Samsung devices with android such as Samsung Galaxy Ace (android 2.3.3), Samsung Galaxy SIII mini (android 4.2.2) Reporter: Matus Pleva Priority: Minor Labels: android, freeze, samsung, timemove When device time is moved backwards, application GUI slows down, javascript timers stop working, css animations don't work too. After a while everything start working again. It seems that recovery time depends on how much the time is moved. (1min backwards - recovery about 2min). I tested it also on Nexus 4 and Nexus 7 (both android 4.4.4) but here the problem doesn't occur. This issue can be easily reproduced by creating new cordova project (sample application with device ready indicator). When time is moved back, css animation on green box stops. You can add js timer there and again it stops. -- 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-7822) Too many / wrong permissions for Device Orientation plugin
[ https://issues.apache.org/jira/browse/CB-7822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Tuttle updated CB-7822: Summary: Too many / wrong permissions for Device Orientation plugin (was: Too many / wrong permissions for ) Too many / wrong permissions for Device Orientation plugin -- Key: CB-7822 URL: https://issues.apache.org/jira/browse/CB-7822 Project: Apache Cordova Issue Type: Bug Components: Plugin Device Orientation Reporter: Adam Tuttle Priority: Minor It seems intuitively incorrect that the Device Orientation plugin needs to request the permissions ACCESS_COARSE_LOCATION and ACCESS_FINE_LOCATION. I did a little bit of research and haven't found anything conclusive one way or the other. I just know that I need this information to make my app look good, but now my users could think that I'm watching their GPS for no reason. This was the best information I was able to find on getting orientation, but I don't see any discussion on the necessary permissions. http://stackoverflow.com/questions/2795833/check-orientation-on-android-phone I wish I had a better idea of whether or not this is a bug or a feature of the way android permissions are provisioned, but this is the best I can do at the moment. Can someone please look into 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-7822) Too many / wrong permissions for
Adam Tuttle created CB-7822: --- Summary: Too many / wrong permissions for Key: CB-7822 URL: https://issues.apache.org/jira/browse/CB-7822 Project: Apache Cordova Issue Type: Bug Components: Plugin Device Orientation Reporter: Adam Tuttle Priority: Minor It seems intuitively incorrect that the Device Orientation plugin needs to request the permissions ACCESS_COARSE_LOCATION and ACCESS_FINE_LOCATION. I did a little bit of research and haven't found anything conclusive one way or the other. I just know that I need this information to make my app look good, but now my users could think that I'm watching their GPS for no reason. This was the best information I was able to find on getting orientation, but I don't see any discussion on the necessary permissions. http://stackoverflow.com/questions/2795833/check-orientation-on-android-phone I wish I had a better idea of whether or not this is a bug or a feature of the way android permissions are provisioned, but this is the best I can do at the moment. Can someone please look into 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] [Commented] (CB-7487) Writing a file doesn't show up on android MTP
[ https://issues.apache.org/jira/browse/CB-7487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14176936#comment-14176936 ] ASF GitHub Bot commented on CB-7487: Github user dpeacock closed the pull request at: https://github.com/apache/cordova-plugin-file/pull/81 Writing a file doesn't show up on android MTP - Key: CB-7487 URL: https://issues.apache.org/jira/browse/CB-7487 Project: Apache Cordova Issue Type: Bug Components: Android, Plugin File Affects Versions: 3.4.0 Environment: Nexus 5 and Windows 7 Reporter: David Peacock Assignee: Ian Clelland Using the file plug-in to write out a file works, but when you use MTP to view the file when connected to USB on Windows the file doesn't show up. The file shows up on the device or through adb. Rebooting the device or using things to refresh the MTP will have the file appear. This was tested on multiple Nexus 5 devices on multiple Windows 7 machines. Cordova should be broadcasting ACTION_MEDIA_SCANNER_SCAN_FILE on the file to have it appear immediately. I will be submitting a pull request on the file plug-in for a fix I've tested and confirmed that resolves this issue. -- 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-7487) Writing a file doesn't show up on android MTP
[ https://issues.apache.org/jira/browse/CB-7487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14176954#comment-14176954 ] Joe Bowser commented on CB-7487: Can we get this code shared with Camera somehow? Writing a file doesn't show up on android MTP - Key: CB-7487 URL: https://issues.apache.org/jira/browse/CB-7487 Project: Apache Cordova Issue Type: Bug Components: Android, Plugin File Affects Versions: 3.4.0 Environment: Nexus 5 and Windows 7 Reporter: David Peacock Assignee: Ian Clelland Using the file plug-in to write out a file works, but when you use MTP to view the file when connected to USB on Windows the file doesn't show up. The file shows up on the device or through adb. Rebooting the device or using things to refresh the MTP will have the file appear. This was tested on multiple Nexus 5 devices on multiple Windows 7 machines. Cordova should be broadcasting ACTION_MEDIA_SCANNER_SCAN_FILE on the file to have it appear immediately. I will be submitting a pull request on the file plug-in for a fix I've tested and confirmed that resolves this issue. -- 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-7487) Writing a file doesn't show up on android MTP
[ https://issues.apache.org/jira/browse/CB-7487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14176967#comment-14176967 ] Ian Clelland commented on CB-7487: -- Certainly; it should probably be a separate (related) issue, though. Writing a file doesn't show up on android MTP - Key: CB-7487 URL: https://issues.apache.org/jira/browse/CB-7487 Project: Apache Cordova Issue Type: Bug Components: Android, Plugin File Affects Versions: 3.4.0 Environment: Nexus 5 and Windows 7 Reporter: David Peacock Assignee: Ian Clelland Using the file plug-in to write out a file works, but when you use MTP to view the file when connected to USB on Windows the file doesn't show up. The file shows up on the device or through adb. Rebooting the device or using things to refresh the MTP will have the file appear. This was tested on multiple Nexus 5 devices on multiple Windows 7 machines. Cordova should be broadcasting ACTION_MEDIA_SCANNER_SCAN_FILE on the file to have it appear immediately. I will be submitting a pull request on the file plug-in for a fix I've tested and confirmed that resolves this issue. -- 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-7700) Translations for October
[ https://issues.apache.org/jira/browse/CB-7700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14177009#comment-14177009 ] ASF GitHub Bot commented on CB-7700: GitHub user sosahvictor opened a pull request: https://github.com/apache/cordova-plugin-globalization/pull/29 CB-7700 cordova-plugin-globalization documentation translation CB-7700 cordova-plugin-globalization documentation translation: cordova-plugin-globalization You can merge this pull request into a Git repository by running: $ git pull https://github.com/sosahvictor/cordova-plugin-globalization CB-7700cordova-plugin-globalization Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-plugin-globalization/pull/29.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #29 commit 382010bc21fca40a2f3709ad133102ad81503663 Author: Victor Sosa victo...@mx1.ibm.com Date: 2014-10-20T15:38:34Z CB-7700 cordova-plugin-globalization documentation translation: cordova-plugin-globalization Translations for October Key: CB-7700 URL: https://issues.apache.org/jira/browse/CB-7700 Project: Apache Cordova Issue Type: Improvement Components: Translation Reporter: Victor Adrian Sosa Herrera Assignee: Lisa Seacat DeLuca Priority: Minor -- 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-7700) Translations for October
[ https://issues.apache.org/jira/browse/CB-7700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14177005#comment-14177005 ] ASF GitHub Bot commented on CB-7700: GitHub user sosahvictor opened a pull request: https://github.com/apache/cordova-plugin-splashscreen/pull/30 CB-7700 cordova-plugin-splashscreen documentation translation CB-7700 cordova-plugin-splashscreen documentation translation: cordova-plugin-splashscreen You can merge this pull request into a Git repository by running: $ git pull https://github.com/sosahvictor/cordova-plugin-splashscreen CB-7700cordova-plugin-splashscreen Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-plugin-splashscreen/pull/30.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #30 commit 3947f8570a72b04a9beb611cc1218dd483913d77 Author: Victor Sosa victo...@mx1.ibm.com Date: 2014-10-20T15:39:27Z CB-7700 cordova-plugin-splashscreen documentation translation: cordova-plugin-splashscreen Translations for October Key: CB-7700 URL: https://issues.apache.org/jira/browse/CB-7700 Project: Apache Cordova Issue Type: Improvement Components: Translation Reporter: Victor Adrian Sosa Herrera Assignee: Lisa Seacat DeLuca Priority: Minor -- 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-7700) Translations for October
[ https://issues.apache.org/jira/browse/CB-7700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14177011#comment-14177011 ] ASF GitHub Bot commented on CB-7700: GitHub user sosahvictor opened a pull request: https://github.com/apache/cordova-plugin-dialogs/pull/38 CB-7700 cordova-plugin-dialogs documentation translation CB-7700 cordova-plugin-dialogs documentation translation: cordova-plugin-dialogs You can merge this pull request into a Git repository by running: $ git pull https://github.com/sosahvictor/cordova-plugin-dialogs CB-7700cordova-plugin-dialogs Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-plugin-dialogs/pull/38.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #38 commit 408818dec39e84b60439922da4656e9482da5eb9 Author: Victor Sosa victo...@mx1.ibm.com Date: 2014-10-20T15:37:49Z CB-7700 cordova-plugin-dialogs documentation translation: cordova-plugin-dialogs Translations for October Key: CB-7700 URL: https://issues.apache.org/jira/browse/CB-7700 Project: Apache Cordova Issue Type: Improvement Components: Translation Reporter: Victor Adrian Sosa Herrera Assignee: Lisa Seacat DeLuca Priority: Minor -- 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-7823) Building FirefoxOS project creates invalid config.xml
Adam Fónagy created CB-7823: --- Summary: Building FirefoxOS project creates invalid config.xml Key: CB-7823 URL: https://issues.apache.org/jira/browse/CB-7823 Project: Apache Cordova Issue Type: Bug Components: CLI, FirefoxOS Affects Versions: 4.0.0 Environment: Ubuntu x64 14.04 Reporter: Adam Fónagy This is a snippet of my config.xml in the project directory: platform name=firefoxos icon height=128 src=res/firefoxos/icon128.png width=128 / icon height=60 src=res/firefoxos/icon60.png width=60 / /platform cordova build firefoxos command perpares the config.xml in platforms/firefoxos direcory with icon reltated settings like this: platform name=firefoxos icon height=128 src=icon/icon-128.png width=128 / icon height=60 src=icon/icon-60.png width=60 / /platform icon height=128 src=res/firefoxos/icon128.png width=128 / icon height=60 src=res/firefoxos/icon60.png width=60 / When I upload the app to my phone I see the icon is the default cordova icon. -- 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-7809) Put default app images in www/res
[ https://issues.apache.org/jira/browse/CB-7809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14177190#comment-14177190 ] Andrew Grieve commented on CB-7809: --- I believe the suggestion is that our default app template should use `icon` and `splash` tags. Put default app images in www/res - Key: CB-7809 URL: https://issues.apache.org/jira/browse/CB-7809 Project: Apache Cordova Issue Type: Improvement Components: CordovaLib Affects Versions: 3.5.0 Environment: Any Environment Reporter: Steve Husting Priority: Trivial Labels: icons, splashscreen People are confused about how to update the splash screens during their Android build. Why not place all the default app helloCordova icons and splashes in the location you recommend, in /helloCordova/android/res/* instead of in /helloCordova/platforms/android/res/*? Then fill the config.xml with the lines needed to port the files over to Android via CLI as you recommend. This example of proper placement and config.xml usage will remove all users' doubts about where to put the icons and splashes. I assume you could programmatically set up the default app so that the entire /platforms/android/res folder structure is reproduced in /helloCordova/android/res/ to make it easy to understand where to put the user's own files. They'll replace those icon.pngs and screen.pngs with their own. You would program the same thing with iOS files in /hellocordova/ios/res/ . Just a suggestion! -- 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-7823) Building FirefoxOS project creates invalid config.xml
[ https://issues.apache.org/jira/browse/CB-7823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14177194#comment-14177194 ] Adam Fónagy commented on CB-7823: - It seems manifest.webapp file in www directory has wrong icon path too. Building FirefoxOS project creates invalid config.xml - Key: CB-7823 URL: https://issues.apache.org/jira/browse/CB-7823 Project: Apache Cordova Issue Type: Bug Components: CLI, FirefoxOS Affects Versions: 4.0.0 Environment: Ubuntu x64 14.04 Reporter: Adam Fónagy This is a snippet of my config.xml in the project directory: platform name=firefoxos icon height=128 src=res/firefoxos/icon128.png width=128 / icon height=60 src=res/firefoxos/icon60.png width=60 / /platform cordova build firefoxos command perpares the config.xml in platforms/firefoxos direcory with icon reltated settings like this: platform name=firefoxos icon height=128 src=icon/icon-128.png width=128 / icon height=60 src=icon/icon-60.png width=60 / /platform icon height=128 src=res/firefoxos/icon128.png width=128 / icon height=60 src=res/firefoxos/icon60.png width=60 / When I upload the app to my phone I see the icon is the default cordova icon. -- 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-7809) Put default app images in www/res
[ https://issues.apache.org/jira/browse/CB-7809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14177203#comment-14177203 ] Steve Husting commented on CB-7809: --- Clarification: When we do a cordova platform add android, all the screen and icon files are generated in the /platforms/android folder. To encourage people to use the config.xml page, all icon and screen folders should be generated in a myApp/res/screen/android/ folder. People would see that folder and the config.xml page and understand where to put their icons and screens. Right now they see the icons and screens in the current /platforms/android location and wonder how to use the config.xml for icons and screens. If the myApp/res/ etc. folder was created upon cordova platform add android, there would be no doubt, and the workflow would simply work. Put default app images in www/res - Key: CB-7809 URL: https://issues.apache.org/jira/browse/CB-7809 Project: Apache Cordova Issue Type: Improvement Components: CordovaLib Affects Versions: 3.5.0 Environment: Any Environment Reporter: Steve Husting Priority: Trivial Labels: icons, splashscreen People are confused about how to update the splash screens during their Android build. Why not place all the default app helloCordova icons and splashes in the location you recommend, in /helloCordova/android/res/* instead of in /helloCordova/platforms/android/res/*? Then fill the config.xml with the lines needed to port the files over to Android via CLI as you recommend. This example of proper placement and config.xml usage will remove all users' doubts about where to put the icons and splashes. I assume you could programmatically set up the default app so that the entire /platforms/android/res folder structure is reproduced in /helloCordova/android/res/ to make it easy to understand where to put the user's own files. They'll replace those icon.pngs and screen.pngs with their own. You would program the same thing with iOS files in /hellocordova/ios/res/ . Just a suggestion! -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Comment Edited] (CB-7809) Put default app images in www/res
[ https://issues.apache.org/jira/browse/CB-7809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14177203#comment-14177203 ] Steve Husting edited comment on CB-7809 at 10/20/14 6:03 PM: - Clarification: When we do a cordova platform add android, all the screen and icon files are generated in the /platforms/android folder. To encourage people to use the config.xml page, all icon and screen folders should be generated in a myApp/res/screen/android/* folders. People would see that folder and the config.xml page and understand where to put their icons and screens. Right now they see the icons and screens in the current /platforms/android/* locations and wonder how to use the config.xml for icons and screens. If the myApp/res/* folder was created upon cordova platform add android, there would be no doubt, and the workflow would simply work. was (Author: websteve): Clarification: When we do a cordova platform add android, all the screen and icon files are generated in the /platforms/android folder. To encourage people to use the config.xml page, all icon and screen folders should be generated in a myApp/res/screen/android/ folder. People would see that folder and the config.xml page and understand where to put their icons and screens. Right now they see the icons and screens in the current /platforms/android location and wonder how to use the config.xml for icons and screens. If the myApp/res/ etc. folder was created upon cordova platform add android, there would be no doubt, and the workflow would simply work. Put default app images in www/res - Key: CB-7809 URL: https://issues.apache.org/jira/browse/CB-7809 Project: Apache Cordova Issue Type: Improvement Components: CordovaLib Affects Versions: 3.5.0 Environment: Any Environment Reporter: Steve Husting Priority: Trivial Labels: icons, splashscreen People are confused about how to update the splash screens during their Android build. Why not place all the default app helloCordova icons and splashes in the location you recommend, in /helloCordova/android/res/* instead of in /helloCordova/platforms/android/res/*? Then fill the config.xml with the lines needed to port the files over to Android via CLI as you recommend. This example of proper placement and config.xml usage will remove all users' doubts about where to put the icons and splashes. I assume you could programmatically set up the default app so that the entire /platforms/android/res folder structure is reproduced in /helloCordova/android/res/ to make it easy to understand where to put the user's own files. They'll replace those icon.pngs and screen.pngs with their own. You would program the same thing with iOS files in /hellocordova/ios/res/ . Just a suggestion! -- 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-6911) [CordovaJS][iOS 8] - deprecated attempt to access property errors when accessing anything off window.navigator
[ https://issues.apache.org/jira/browse/CB-6911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14177223#comment-14177223 ] Shazron Abdullah commented on CB-6911: -- Andrew, the bug was resolved as Fix Version: 3.7.0. 3.7.0 has not been released yet. To grab the fixes right now, you will have to patch your js. [CordovaJS][iOS 8] - deprecated attempt to access property errors when accessing anything off window.navigator Key: CB-6911 URL: https://issues.apache.org/jira/browse/CB-6911 Project: Apache Cordova Issue Type: Sub-task Components: CordovaJS Environment: iOS 8 beta 5 (device) Reporter: Jeff Schilling Assignee: Shazron Abdullah Fix For: 3.7.0 Attachments: Screen Shot 2014-09-01 at 9.03.30 pm.png, Screen Shot 2014-09-04 at 9.30.58 pm.png references to window.navigator.* (platform, geolocation) etc fail with Deprecated attempt to access property 'geolocation' on a non-Navigator object. -- 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-7633) [iOS 8][SplashScreen] Add support for iPhone 6 and iPhone 6 Plus resolutions
[ https://issues.apache.org/jira/browse/CB-7633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14177229#comment-14177229 ] Shazron Abdullah commented on CB-7633: -- cordova-ios iPhone 6 support will be in cordova-ios 3.7.0. https://issues.apache.org/jira/browse/CB-7648 https://issues.apache.org/jira/browse/CB-7632 Don't confuse the cordova-cli 4.0 release with the platform versions. Platforms are released independently now. For more info see: http://cordova.apache.org/announcements/2014/10/16/cordova-4.html [iOS 8][SplashScreen] Add support for iPhone 6 and iPhone 6 Plus resolutions Key: CB-7633 URL: https://issues.apache.org/jira/browse/CB-7633 Project: Apache Cordova Issue Type: Sub-task Components: Plugin SplashScreen Reporter: Shazron Abdullah Assignee: Shazron Abdullah See https://github.com/apache/cordova-plugin-splashscreen/pull/26 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Comment Edited] (CB-7809) Put default app images in www/res
[ https://issues.apache.org/jira/browse/CB-7809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14177203#comment-14177203 ] Steve Husting edited comment on CB-7809 at 10/20/14 6:20 PM: - Clarification: When we do a cordova platform add android, all the screen and icon files are generated in the /platforms/android folder. To encourage people to use the config.xml page, all icon and screen folders should be generated in a myApp/res/screen/android/* folders. People would see that folder and the config.xml page and understand where to put their icons and screens. Right now they see the icons and screens in the current /platforms/android/* locations and wonder how to use the config.xml for icons and screens. If the myApp/res/* folder was created upon cordova platform add android, there would be no doubt, and the workflow would simply work. To clarify further, the entire myApp/platforms/android/* structure can be placed in myApp/res/android/* as is (with the exception of /values and /xml). was (Author: websteve): Clarification: When we do a cordova platform add android, all the screen and icon files are generated in the /platforms/android folder. To encourage people to use the config.xml page, all icon and screen folders should be generated in a myApp/res/screen/android/* folders. People would see that folder and the config.xml page and understand where to put their icons and screens. Right now they see the icons and screens in the current /platforms/android/* locations and wonder how to use the config.xml for icons and screens. If the myApp/res/* folder was created upon cordova platform add android, there would be no doubt, and the workflow would simply work. Put default app images in www/res - Key: CB-7809 URL: https://issues.apache.org/jira/browse/CB-7809 Project: Apache Cordova Issue Type: Improvement Components: CordovaLib Affects Versions: 3.5.0 Environment: Any Environment Reporter: Steve Husting Priority: Trivial Labels: icons, splashscreen People are confused about how to update the splash screens during their Android build. Why not place all the default app helloCordova icons and splashes in the location you recommend, in /helloCordova/android/res/* instead of in /helloCordova/platforms/android/res/*? Then fill the config.xml with the lines needed to port the files over to Android via CLI as you recommend. This example of proper placement and config.xml usage will remove all users' doubts about where to put the icons and splashes. I assume you could programmatically set up the default app so that the entire /platforms/android/res folder structure is reproduced in /helloCordova/android/res/ to make it easy to understand where to put the user's own files. They'll replace those icon.pngs and screen.pngs with their own. You would program the same thing with iOS files in /hellocordova/ios/res/ . Just a suggestion! -- 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-7824) bounce out to system browser from inappbrowser
Kevin Lee Quinn created CB-7824: --- Summary: bounce out to system browser from inappbrowser Key: CB-7824 URL: https://issues.apache.org/jira/browse/CB-7824 Project: Apache Cordova Issue Type: Wish Components: Plugin InAppBrowser Reporter: Kevin Lee Quinn it would be great if there was an option with inappbrowser to add a button that opens the url in the system browser. so if I have a link that opens in the inappbrowser the user can bounce that out to the system browser to bookmark, share the url, whatever. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Comment Edited] (CB-7809) Put default app images in www/res
[ https://issues.apache.org/jira/browse/CB-7809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14177203#comment-14177203 ] Steve Husting edited comment on CB-7809 at 10/20/14 6:23 PM: - Clarification: When we do a cordova platform add android, all the screen and icon files are generated in the /platforms/android folder. To encourage people to use the config.xml page, all icon and screen folders should be generated in a myApp/res/screen/android/* folders. People would see that folder and the config.xml page and understand where to put their icons and screens. Right now they see the icons and screens in the current /platforms/android/* locations and wonder how to use the config.xml for icons and screens. If the myApp/res/* folder was created upon cordova platform add android, there would be no doubt, and the workflow would simply work. To clarify further, the entire myApp/platforms/android/* structure can be placed in myApp/res/android/* as is (with the exception of /values and /xml). That way, all icons would be named icon.png and screens screen.png in order to fulfill preference name=splashscreen value=screen was (Author: websteve): Clarification: When we do a cordova platform add android, all the screen and icon files are generated in the /platforms/android folder. To encourage people to use the config.xml page, all icon and screen folders should be generated in a myApp/res/screen/android/* folders. People would see that folder and the config.xml page and understand where to put their icons and screens. Right now they see the icons and screens in the current /platforms/android/* locations and wonder how to use the config.xml for icons and screens. If the myApp/res/* folder was created upon cordova platform add android, there would be no doubt, and the workflow would simply work. To clarify further, the entire myApp/platforms/android/* structure can be placed in myApp/res/android/* as is (with the exception of /values and /xml). Put default app images in www/res - Key: CB-7809 URL: https://issues.apache.org/jira/browse/CB-7809 Project: Apache Cordova Issue Type: Improvement Components: CordovaLib Affects Versions: 3.5.0 Environment: Any Environment Reporter: Steve Husting Priority: Trivial Labels: icons, splashscreen People are confused about how to update the splash screens during their Android build. Why not place all the default app helloCordova icons and splashes in the location you recommend, in /helloCordova/android/res/* instead of in /helloCordova/platforms/android/res/*? Then fill the config.xml with the lines needed to port the files over to Android via CLI as you recommend. This example of proper placement and config.xml usage will remove all users' doubts about where to put the icons and splashes. I assume you could programmatically set up the default app so that the entire /platforms/android/res folder structure is reproduced in /helloCordova/android/res/ to make it easy to understand where to put the user's own files. They'll replace those icon.pngs and screen.pngs with their own. You would program the same thing with iOS files in /hellocordova/ios/res/ . Just a suggestion! -- 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-7824) bounce out to system browser from inappbrowser
[ https://issues.apache.org/jira/browse/CB-7824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Lee Quinn updated CB-7824: Priority: Minor (was: Major) bounce out to system browser from inappbrowser -- Key: CB-7824 URL: https://issues.apache.org/jira/browse/CB-7824 Project: Apache Cordova Issue Type: Wish Components: Plugin InAppBrowser Reporter: Kevin Lee Quinn Priority: Minor it would be great if there was an option with inappbrowser to add a button that opens the url in the system browser. so if I have a link that opens in the inappbrowser the user can bounce that out to the system browser to bookmark, share the url, whatever. -- 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-7818) CLI builds ignore Distribution certificates
[ https://issues.apache.org/jira/browse/CB-7818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14177254#comment-14177254 ] ASF GitHub Bot commented on CB-7818: Github user shazron commented on the pull request: https://github.com/apache/cordova-ios/pull/114#issuecomment-59816419 Looks great! I'll pull this in for cordova-ios 3.7.0 CLI builds ignore Distribution certificates --- Key: CB-7818 URL: https://issues.apache.org/jira/browse/CB-7818 Project: Apache Cordova Issue Type: Bug Components: iOS Affects Versions: 3.5.0 Reporter: SidneyS Fix For: Master Hi, currently, cordova build --release --device yields in device builds using a default iOS Development-type Signing Identity. Intuitively, using release in conjunction with device should try to leverage a local iOS Distribution-type identity to enable CLI adhoc/inhouse-builds without patching xcconfig/xcodeproject files on runtime, or re-signing the created binary after using the default build process. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Comment Edited] (CB-7809) Put default app images in www/res
[ https://issues.apache.org/jira/browse/CB-7809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14177203#comment-14177203 ] Steve Husting edited comment on CB-7809 at 10/20/14 6:38 PM: - Clarification: When we do a cordova platform add android, all the screen and icon files are generated in the /platforms/android folder. To encourage people to use the config.xml page, all icon and screen folders should be generated in a myApp/res/screen/android/* folders. People would see that folder and the config.xml page and understand where to put their icons and screens. Right now they see the icons and screens in the current /platforms/android/* locations and wonder how to use the config.xml for icons and screens. If the myApp/res/* folder was created upon cordova platform add android, there would be no doubt, and the workflow would simply work. To clarify further, the entire myApp/platforms/android/* structure can be placed in myApp/res/android/* as is (with the exception of /values and /xml). That way, all icons would be named icon.png and screens screen.png in order to fulfill preference name=splashscreen value=screen Compounding the confusion is the fact that the preference name for the screen.png is screen, yet in the documentation we are told that the screen images names should be screen-hdpi-landscape.png and so on. Nowhere in the documentation do we allow for all these names in the config.xml file -- just value=screen. value=screen only makes sense if the myApp/platforms/android/* structure were set up as in /platforms/android/* where all the screen names will be consistently only screen.png. was (Author: websteve): Clarification: When we do a cordova platform add android, all the screen and icon files are generated in the /platforms/android folder. To encourage people to use the config.xml page, all icon and screen folders should be generated in a myApp/res/screen/android/* folders. People would see that folder and the config.xml page and understand where to put their icons and screens. Right now they see the icons and screens in the current /platforms/android/* locations and wonder how to use the config.xml for icons and screens. If the myApp/res/* folder was created upon cordova platform add android, there would be no doubt, and the workflow would simply work. To clarify further, the entire myApp/platforms/android/* structure can be placed in myApp/res/android/* as is (with the exception of /values and /xml). That way, all icons would be named icon.png and screens screen.png in order to fulfill preference name=splashscreen value=screen Put default app images in www/res - Key: CB-7809 URL: https://issues.apache.org/jira/browse/CB-7809 Project: Apache Cordova Issue Type: Improvement Components: CordovaLib Affects Versions: 3.5.0 Environment: Any Environment Reporter: Steve Husting Priority: Trivial Labels: icons, splashscreen People are confused about how to update the splash screens during their Android build. Why not place all the default app helloCordova icons and splashes in the location you recommend, in /helloCordova/android/res/* instead of in /helloCordova/platforms/android/res/*? Then fill the config.xml with the lines needed to port the files over to Android via CLI as you recommend. This example of proper placement and config.xml usage will remove all users' doubts about where to put the icons and splashes. I assume you could programmatically set up the default app so that the entire /platforms/android/res folder structure is reproduced in /helloCordova/android/res/ to make it easy to understand where to put the user's own files. They'll replace those icon.pngs and screen.pngs with their own. You would program the same thing with iOS files in /hellocordova/ios/res/ . Just a suggestion! -- 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-7818) CLI builds ignore Distribution certificates
[ https://issues.apache.org/jira/browse/CB-7818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shazron Abdullah updated CB-7818: - Fix Version/s: (was: Master) 3.7.0 CLI builds ignore Distribution certificates --- Key: CB-7818 URL: https://issues.apache.org/jira/browse/CB-7818 Project: Apache Cordova Issue Type: Bug Components: iOS Affects Versions: 3.5.0 Reporter: SidneyS Fix For: 3.7.0 Hi, currently, cordova build --release --device yields in device builds using a default iOS Development-type Signing Identity. Intuitively, using release in conjunction with device should try to leverage a local iOS Distribution-type identity to enable CLI adhoc/inhouse-builds without patching xcconfig/xcodeproject files on runtime, or re-signing the created binary after using the default build process. -- 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-7818) CLI builds ignore Distribution certificates
[ https://issues.apache.org/jira/browse/CB-7818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shazron Abdullah reassigned CB-7818: Assignee: Shazron Abdullah CLI builds ignore Distribution certificates --- Key: CB-7818 URL: https://issues.apache.org/jira/browse/CB-7818 Project: Apache Cordova Issue Type: Bug Components: iOS Affects Versions: 3.5.0 Reporter: SidneyS Assignee: Shazron Abdullah Fix For: 3.7.0 Hi, currently, cordova build --release --device yields in device builds using a default iOS Development-type Signing Identity. Intuitively, using release in conjunction with device should try to leverage a local iOS Distribution-type identity to enable CLI adhoc/inhouse-builds without patching xcconfig/xcodeproject files on runtime, or re-signing the created binary after using the default build process. -- 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-7818) CLI builds ignore Distribution certificates
[ https://issues.apache.org/jira/browse/CB-7818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14177370#comment-14177370 ] ASF GitHub Bot commented on CB-7818: Github user asfgit closed the pull request at: https://github.com/apache/cordova-ios/pull/114 CLI builds ignore Distribution certificates --- Key: CB-7818 URL: https://issues.apache.org/jira/browse/CB-7818 Project: Apache Cordova Issue Type: Bug Components: iOS Affects Versions: 3.5.0 Reporter: SidneyS Assignee: Shazron Abdullah Fix For: 3.7.0 Hi, currently, cordova build --release --device yields in device builds using a default iOS Development-type Signing Identity. Intuitively, using release in conjunction with device should try to leverage a local iOS Distribution-type identity to enable CLI adhoc/inhouse-builds without patching xcconfig/xcodeproject files on runtime, or re-signing the created binary after using the default build process. -- 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-7818) CLI builds ignore Distribution certificates
[ https://issues.apache.org/jira/browse/CB-7818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14177369#comment-14177369 ] ASF subversion and git services commented on CB-7818: - Commit c0db6382af2e2570be139d584f553ca5c046a941 in cordova-ios's branch refs/heads/master from [~SidneyS] [ https://git-wip-us.apache.org/repos/asf?p=cordova-ios.git;h=c0db638 ] CB-7818 - CLI builds ignore Distribution certificates (closes #114) Fixed build / xcconfig defaults for CI environments. cordova build -… …-device --release now builds using the iPhone Distribution-type profile, as opposed to the default cordova build --device, using the default iPhone Developer-type profile. Re-added build.xcconfig as shared .xcconfig for legacy compatibility. Implemented Configuration-level .xcconfig selection via inheritance. Added ASF comment section, short documentation. Signed-off-by: Shazron Abdullah shaz...@apache.org CLI builds ignore Distribution certificates --- Key: CB-7818 URL: https://issues.apache.org/jira/browse/CB-7818 Project: Apache Cordova Issue Type: Bug Components: iOS Affects Versions: 3.5.0 Reporter: SidneyS Assignee: Shazron Abdullah Fix For: 3.7.0 Hi, currently, cordova build --release --device yields in device builds using a default iOS Development-type Signing Identity. Intuitively, using release in conjunction with device should try to leverage a local iOS Distribution-type identity to enable CLI adhoc/inhouse-builds without patching xcconfig/xcodeproject files on runtime, or re-signing the created binary after using the default build process. -- 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-7818) CLI builds ignore Distribution certificates
[ https://issues.apache.org/jira/browse/CB-7818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shazron Abdullah resolved CB-7818. -- Resolution: Fixed Pulled in, tested. CLI builds ignore Distribution certificates --- Key: CB-7818 URL: https://issues.apache.org/jira/browse/CB-7818 Project: Apache Cordova Issue Type: Bug Components: iOS Affects Versions: 3.5.0 Reporter: SidneyS Assignee: Shazron Abdullah Fix For: 3.7.0 Hi, currently, cordova build --release --device yields in device builds using a default iOS Development-type Signing Identity. Intuitively, using release in conjunction with device should try to leverage a local iOS Distribution-type identity to enable CLI adhoc/inhouse-builds without patching xcconfig/xcodeproject files on runtime, or re-signing the created binary after using the default build process. -- 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-7825) cordova serve breaks silently when any platform's prepare step fails
Josh Soref created CB-7825:
--
Summary: cordova serve breaks silently when any platform's prepare
step fails
Key: CB-7825
URL: https://issues.apache.org/jira/browse/CB-7825
Project: Apache Cordova
Issue Type: Bug
Components: CLI, CordovaLib
Affects Versions: 4.0.0
Reporter: Josh Soref
Assignee: Josh Soref
{quote}
$ cordova serve
$
{quote}
totally unhelpful.
{quote}
for a in `cd platforms/; ls`; do cordova prepare $a /dev/null 2 /dev/null ||
echo $a is broken; done
android is broken
{quote}
Specifically, i'm using /tmp on OS X for my project, and /tmp self destructs,
so prepare failed due to:
{quote}
Error: ENOENT, no such file or directory
'/tmp/aa/platforms/android/res/values/strings.xml'
{quote}
Expected result:
cordova serve should serve all working platforms and spit out a warning for
broken platforms. If it can't serve any platforms, it should fail, and when it
fails, there should be an error code returned to its caller.
--
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-7033) cordova platform check command not working
[
https://issues.apache.org/jira/browse/CB-7033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14177461#comment-14177461
]
Josh Soref commented on CB-7033:
For reference, broken means that the version script failed.
There are various ways for things like that to happen.
One way is for a script/file which your version script depends on to go
missing/lose its execute bit.
The current cordova-android version script is pretty self contained, so it
should either fail because it lost its execute bit, or in this case it's so old
that it depended on lots of other stuff.
The reason that platform check didn't say anything is that you probably didn't
have enough of the android system in your path.
Roughly, if you can't do: cordova platform add android (typically because
android and ant aren't in your path), then it doesn't make sense to say
cordova android (version unknown - due to broken version script) could be
updated to cordova android (supposedly version X, but won't actually install).
Instead of cordova platform check giving something really
complicated/confusing, it currently just stays mum when it can't express
something helpful.
I think the up-to-date message should be changed to No platforms can be
updated at this time. which is more accurate.
It should also suggest checking to see if cordova itself is current, since if
you're running cordova 3.4.1, and the current version is cordova 4.0.0, the
check system won't be able to tell you about a newer version of cordova-android
than the one that shipped w/ 3.4.1.
cordova platform check command not working
--
Key: CB-7033
URL: https://issues.apache.org/jira/browse/CB-7033
Project: Apache Cordova
Issue Type: Bug
Components: CLI
Affects Versions: 3.4.0
Reporter: Victor Adrian Sosa Herrera
Priority: Minor
I have an app with Android installed and I know it was created with Cordova
3.3.1-0.1.2.
After running this command with a 3.4.1-1.0. CLI I get the following
{{$ cordova platform check}}
{{All platforms are up-to-date.}}
But after running cordova platform ls I get the following
{{$ cordova platform ls}}
{{Installed platforms: android broken}}
{{Available platforms: amazon-fireos, blackberry10, firefoxos, ubuntu}}
Using _platform check_ arguments I don't get the result I'm looking for (a
platform out-of-date), while using _platform ls_ it's not very clear, but I
presume the _broken_ platform is like an out-of-date message
--
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-7780) iPhone app on iPad (iOS 8)
[ https://issues.apache.org/jira/browse/CB-7780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14177553#comment-14177553 ] Shazron Abdullah commented on CB-7780: -- I posted the test project I used: https://github.com/shazron/CB-7780 I couldn't repo using iOS 8.1 (final) on an iPad 3. 1. iPad initially landscape mode 2. Launch Cordova app (set to iPhone only, Portrait only) 3. App launched in Portrait mode Looks normal to me? Not sure what you mean by viewport is pretty messed up, please clarify. iPhone app on iPad (iOS 8) -- Key: CB-7780 URL: https://issues.apache.org/jira/browse/CB-7780 Project: Apache Cordova Issue Type: Bug Components: iOS Affects Versions: 3.6.3 Reporter: Tom Bell When running an iPhone only, portrait only app on an iPad running iOS 8, the viewport is pretty messed up. I've tested this using a blank Cordova project from scratch. Removing the `height` and `width` options from the viewport. The viewport seems to resize to half the screen width, when viewing in landscape. It should keep the normal portrait viewport and be portrait. -- 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-7493) Add e2e test for 'space-in-path' and 'unicode in path/name' for core platforms.
[ https://issues.apache.org/jira/browse/CB-7493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14177559#comment-14177559 ] Shazron Abdullah commented on CB-7493: -- There are 4 components to this issue. iOS is resolved. Add e2e test for 'space-in-path' and 'unicode in path/name' for core platforms. --- Key: CB-7493 URL: https://issues.apache.org/jira/browse/CB-7493 Project: Apache Cordova Issue Type: Bug Components: Android, iOS, Windows, WP8 Reporter: Vladimir Kotikov Assignee: Jesse MacFadyen Since we have several issues with unicode in paths and app names it will be great to have automated testing of these cases. Best place to keep these tests is platform repo, so these tests can be ran via come CI service (Appveyor for WP8 and Windows, Travis CI for Android and iOS) For WP8 and windows platforms we already have such tests, so we need just to improve them to test new cases. For Android and iOS it will be necessary to implement tests. Implementation will be very similar to windows/wp8 implementation. Note that android currently doesn't have support for unicode symbols in app name (due to android tools restrictions). So test for android should contain only 'space' case test. -- 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-7780) iPhone app on iPad (iOS 8)
[ https://issues.apache.org/jira/browse/CB-7780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14177578#comment-14177578 ] Tom Bell commented on CB-7780: -- I'll clone your project and try it out tomorrow, and I'll screenshot my app if it's not the same. iPhone app on iPad (iOS 8) -- Key: CB-7780 URL: https://issues.apache.org/jira/browse/CB-7780 Project: Apache Cordova Issue Type: Bug Components: iOS Affects Versions: 3.6.3 Reporter: Tom Bell When running an iPhone only, portrait only app on an iPad running iOS 8, the viewport is pretty messed up. I've tested this using a blank Cordova project from scratch. Removing the `height` and `width` options from the viewport. The viewport seems to resize to half the screen width, when viewing in landscape. It should keep the normal portrait viewport and be portrait. -- 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-6911) [CordovaJS][iOS 8] - deprecated attempt to access property errors when accessing anything off window.navigator
[ https://issues.apache.org/jira/browse/CB-6911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14177595#comment-14177595 ] Andrew Busch commented on CB-6911: -- Ah right, I had just updated to Cordova 4.0 but looks like CordovaJS has a different release cycle and current version number. [CordovaJS][iOS 8] - deprecated attempt to access property errors when accessing anything off window.navigator Key: CB-6911 URL: https://issues.apache.org/jira/browse/CB-6911 Project: Apache Cordova Issue Type: Sub-task Components: CordovaJS Environment: iOS 8 beta 5 (device) Reporter: Jeff Schilling Assignee: Shazron Abdullah Fix For: 3.7.0 Attachments: Screen Shot 2014-09-01 at 9.03.30 pm.png, Screen Shot 2014-09-04 at 9.30.58 pm.png references to window.navigator.* (platform, geolocation) etc fail with Deprecated attempt to access property 'geolocation' on a non-Navigator object. -- 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-6481) Add unified hooks support for cordova app and plugins
[
https://issues.apache.org/jira/browse/CB-6481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14177598#comment-14177598
]
Josh Soref commented on CB-6481:
This broke:
{quote}
cordova platform check
{quote}
Add unified hooks support for cordova app and plugins
-
Key: CB-6481
URL: https://issues.apache.org/jira/browse/CB-6481
Project: Apache Cordova
Issue Type: New Feature
Components: CLI, Plugman
Reporter: Sergey Grebnov
Assignee: Sergey Grebnov
As per Proposal: hooks support for plugins dev mail thread discussion
Hi, I have an idea how we can add more flexibility to plugin developers.
Note, right now we have Application Developers – someone who use Cordova for
developing applications and Plugin Developers – someone who creates plugins
so that Application Developers can use them. For Application Developers we
expose hooks so that they can customize their build/package/etc process. I
want us to provide similar sort of flexibility to Plugin Developers so that
they can go beyond of source/, framework/ tags and get mechanism to add
custom installation, build logic required by a plugin. Example usage will
include: downloading/compiling additional binaries, marking source file to be
copied to output dir, changing target build platform, etc. At present time
the steps described could be only achieved by hooks manually added by
Application Developer, but the right way is to allow Plugin Developer to
expose this as part of plugin definition.
Example configuration could look like
```
script type=postinstall src=scripts/postinstall.js /
script type=preinstall src=scripts/preinstall.js /
script type=install src=scripts/install.js /
```
beforeinstall/preinstall – run before plugin is installed
install/postinstall/afterinstall – run after plugin is installed
uninstall – run after plugin is uninstalled
--
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-7597) Localizable.strings for Media Capture are in the default template, it should be in the plugin
[ https://issues.apache.org/jira/browse/CB-7597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shazron Abdullah reassigned CB-7597: Assignee: Shazron Abdullah Localizable.strings for Media Capture are in the default template, it should be in the plugin - Key: CB-7597 URL: https://issues.apache.org/jira/browse/CB-7597 Project: Apache Cordova Issue Type: Bug Components: iOS, Plugin Media Capture Reporter: Shazron Abdullah Assignee: Shazron Abdullah Create a new iOS project. See Resources - de.lproj, Resources - en.lproj, etc. These resources should be in the Media Capture plugin instead as resources -- 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-7597) Localizable.strings for Media Capture are in the default template, it should be in the plugin
[ https://issues.apache.org/jira/browse/CB-7597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14177671#comment-14177671 ] ASF subversion and git services commented on CB-7597: - Commit f7d70e2e8f8354743286011f70dcd79a3292a82e in cordova-plugin-media-capture's branch refs/heads/master from [~shazron] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-media-capture.git;h=f7d70e2 ] CB-7597 - Localizable.strings for Media Capture are in the default template, it should be in the plugin Localizable.strings for Media Capture are in the default template, it should be in the plugin - Key: CB-7597 URL: https://issues.apache.org/jira/browse/CB-7597 Project: Apache Cordova Issue Type: Bug Components: iOS, Plugin Media Capture Reporter: Shazron Abdullah Create a new iOS project. See Resources - de.lproj, Resources - en.lproj, etc. These resources should be in the Media Capture plugin instead as resources -- 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-7597) Localizable.strings for Media Capture are in the default template, it should be in the plugin
[ https://issues.apache.org/jira/browse/CB-7597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14177703#comment-14177703 ] ASF subversion and git services commented on CB-7597: - Commit 7a1d6c833041fa7662cfd87cab3772434a750c12 in cordova-ios's branch refs/heads/master from [~shazron] [ https://git-wip-us.apache.org/repos/asf?p=cordova-ios.git;h=7a1d6c8 ] CB-7597 - Localizable.strings for Media Capture are in the default template, it should be in the plugin Localizable.strings for Media Capture are in the default template, it should be in the plugin - Key: CB-7597 URL: https://issues.apache.org/jira/browse/CB-7597 Project: Apache Cordova Issue Type: Bug Components: iOS, Plugin Media Capture Reporter: Shazron Abdullah Assignee: Shazron Abdullah Create a new iOS project. See Resources - de.lproj, Resources - en.lproj, etc. These resources should be in the Media Capture plugin instead as resources -- 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-7597) Localizable.strings for Media Capture are in the default template, it should be in the plugin
[ https://issues.apache.org/jira/browse/CB-7597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shazron Abdullah resolved CB-7597. -- Resolution: Fixed Fix Version/s: 3.7.0 Localizable.strings for Media Capture are in the default template, it should be in the plugin - Key: CB-7597 URL: https://issues.apache.org/jira/browse/CB-7597 Project: Apache Cordova Issue Type: Bug Components: iOS, Plugin Media Capture Reporter: Shazron Abdullah Assignee: Shazron Abdullah Fix For: 3.7.0 Create a new iOS project. See Resources - de.lproj, Resources - en.lproj, etc. These resources should be in the Media Capture plugin instead as resources -- 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-7493) Add e2e test for 'space-in-path' and 'unicode in path/name' for core platforms.
[ https://issues.apache.org/jira/browse/CB-7493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14177708#comment-14177708 ] Jesse MacFadyen commented on CB-7493: - as are wp8 + windows Add e2e test for 'space-in-path' and 'unicode in path/name' for core platforms. --- Key: CB-7493 URL: https://issues.apache.org/jira/browse/CB-7493 Project: Apache Cordova Issue Type: Bug Components: Android, iOS, Windows, WP8 Reporter: Vladimir Kotikov Assignee: Jesse MacFadyen Since we have several issues with unicode in paths and app names it will be great to have automated testing of these cases. Best place to keep these tests is platform repo, so these tests can be ran via come CI service (Appveyor for WP8 and Windows, Travis CI for Android and iOS) For WP8 and windows platforms we already have such tests, so we need just to improve them to test new cases. For Android and iOS it will be necessary to implement tests. Implementation will be very similar to windows/wp8 implementation. Note that android currently doesn't have support for unicode symbols in app name (due to android tools restrictions). So test for android should contain only 'space' case test. -- 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-7826) Add CDVPlugin support for getting items from plugin resource bundles
Shazron Abdullah created CB-7826: Summary: Add CDVPlugin support for getting items from plugin resource bundles Key: CB-7826 URL: https://issues.apache.org/jira/browse/CB-7826 Project: Apache Cordova Issue Type: Bug Components: iOS Reporter: Shazron Abdullah Example: https://github.com/apache/cordova-plugin-media-capture/blob/f7d70e2e8f8354743286011f70dcd79a3292a82e/src/ios/CDVCapture.m#L34 Each plugin can have a PluginName.bundle with images, localization strings, etc and we provide an interface in CDVPlugin to grab them. Advantages: 1. Only one line in plugin.xml as a resource tag, versus N lines for N files 2. Namespacing of resources built in, no fear of resource name collision with other plugins, or the project template -- 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-7826) Add CDVPlugin support for getting items from plugin resource bundles
[ https://issues.apache.org/jira/browse/CB-7826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shazron Abdullah updated CB-7826: - Fix Version/s: 4.0.0 Add CDVPlugin support for getting items from plugin resource bundles Key: CB-7826 URL: https://issues.apache.org/jira/browse/CB-7826 Project: Apache Cordova Issue Type: Bug Components: iOS Reporter: Shazron Abdullah Fix For: 4.0.0 Example: https://github.com/apache/cordova-plugin-media-capture/blob/f7d70e2e8f8354743286011f70dcd79a3292a82e/src/ios/CDVCapture.m#L34 Each plugin can have a PluginName.bundle with images, localization strings, etc and we provide an interface in CDVPlugin to grab them. Advantages: 1. Only one line in plugin.xml as a resource tag, versus N lines for N files 2. Namespacing of resources built in, no fear of resource name collision with other plugins, or the project template -- 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-5079) Add settingsForKey function in CDVCommandDelegate (for plugins)
[ https://issues.apache.org/jira/browse/CB-5079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shazron Abdullah updated CB-5079: - Fix Version/s: 4.0.0 Add settingsForKey function in CDVCommandDelegate (for plugins) --- Key: CB-5079 URL: https://issues.apache.org/jira/browse/CB-5079 Project: Apache Cordova Issue Type: Improvement Components: iOS Affects Versions: Master Reporter: Shazron Abdullah Priority: Minor Fix For: 4.0.0 Because the CDVConfigParser lowercases the keys for settings, everytime a plugin wants to get a setting, it has to remember to lowercase the key (which can be error-prone). Have a function in the CDVCommandDelegate *settingsForKey* that helps with this, see example here: https://github.com/apache/cordova-labs/blob/eea7f9fdae739486424ebb8f3ca36ea8bf04730e/statusbar/src/ios/CDVStatusBar.m#L30-L33 However -- if a plugin uses this, it will not be compatible with earlier Cordova versions X if this gets implemented in X. So -- I'm hesitant to add this unless we can find a workaround so it works in all Cordova versions. Maybe through some runtime magic / categories etc, not sure yet, shouldn't be impossible since it's just a helper function. -- 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-7282) Configuration settings AutoHideSplashScreen not documented
[ https://issues.apache.org/jira/browse/CB-7282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shazron Abdullah updated CB-7282: - Component/s: (was: Docs) Configuration settings AutoHideSplashScreen not documented -- Key: CB-7282 URL: https://issues.apache.org/jira/browse/CB-7282 Project: Apache Cordova Issue Type: Bug Components: Plugin SplashScreen Affects Versions: 3.1.0, 3.2.0, 3.3.0, 3.4.0, 3.5.0, 3.6.0 Reporter: Andrey Kurdyumov Assignee: Andrey Kurdyumov The configuration settings AutoHideSplashScreen is available in the code, seems to be widely used, but it description is missing from the current documentation. That documentation initially was present in the Configration reference section, but after it was renamed to The config.xml file, information about that config value was missing. -- 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-5892) Remove deprecated window.Settings
[ https://issues.apache.org/jira/browse/CB-5892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shazron Abdullah reassigned CB-5892: Assignee: Shazron Abdullah Remove deprecated window.Settings - Key: CB-5892 URL: https://issues.apache.org/jira/browse/CB-5892 Project: Apache Cordova Issue Type: Bug Components: Plugin Device Reporter: Shazron Abdullah Assignee: Shazron Abdullah See https://github.com/apache/cordova-plugin-device/blob/fdf724801d5c2cade1ae8fa97841d8bd3387e3ba/src/ios/CDVDevice.m#L61-L65 -- 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-5892) Remove deprecated window.Settings
[ https://issues.apache.org/jira/browse/CB-5892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14177722#comment-14177722 ] ASF subversion and git services commented on CB-5892: - Commit 974ef81cbb4135c4a66d4d3b078aee864cefede6 in cordova-plugin-device's branch refs/heads/master from [~shazron] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-device.git;h=974ef81 ] CB-5892 - Remove deprecated window.Settings Remove deprecated window.Settings - Key: CB-5892 URL: https://issues.apache.org/jira/browse/CB-5892 Project: Apache Cordova Issue Type: Bug Components: Plugin Device Reporter: Shazron Abdullah See https://github.com/apache/cordova-plugin-device/blob/fdf724801d5c2cade1ae8fa97841d8bd3387e3ba/src/ios/CDVDevice.m#L61-L65 -- 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-5892) Remove deprecated window.Settings
[ https://issues.apache.org/jira/browse/CB-5892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shazron Abdullah resolved CB-5892. -- Resolution: Fixed Fix Version/s: (was: 3.6.0) Remove deprecated window.Settings - Key: CB-5892 URL: https://issues.apache.org/jira/browse/CB-5892 Project: Apache Cordova Issue Type: Bug Components: Plugin Device Reporter: Shazron Abdullah Assignee: Shazron Abdullah See https://github.com/apache/cordova-plugin-device/blob/fdf724801d5c2cade1ae8fa97841d8bd3387e3ba/src/ios/CDVDevice.m#L61-L65 -- 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-7068) How to use wkwebview in cordova based hybrid applications.(cordova 2.7.0)
[ https://issues.apache.org/jira/browse/CB-7068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14177731#comment-14177731 ] Shazron Abdullah commented on CB-7068: -- See CB-7043, there are some sub-tasks related to this. It's in an experimental stage. How to use wkwebview in cordova based hybrid applications.(cordova 2.7.0) - Key: CB-7068 URL: https://issues.apache.org/jira/browse/CB-7068 Project: Apache Cordova Issue Type: New Feature Components: iOS Affects Versions: 2.7.0 Environment: ios 8 Reporter: Nidhin Labels: patch how to use wkwebview in cordova based application. How to support both ios 7 and ios 8 if i use wkwebview. -- 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-6481) Add unified hooks support for cordova app and plugins
[ https://issues.apache.org/jira/browse/CB-6481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14177743#comment-14177743 ] ASF subversion and git services commented on CB-6481: - Commit 58b37f5bf010a62c882ab3acfb23b69a41c1710e in cordova-lib's branch refs/heads/master from [~jsoref] [ https://git-wip-us.apache.org/repos/asf?p=cordova-lib.git;h=58b37f5 ] CB-6481 (Fix cordova platform check) Add unified hooks support for cordova app and plugins - Key: CB-6481 URL: https://issues.apache.org/jira/browse/CB-6481 Project: Apache Cordova Issue Type: New Feature Components: CLI, Plugman Reporter: Sergey Grebnov Assignee: Sergey Grebnov As per Proposal: hooks support for plugins dev mail thread discussion Hi, I have an idea how we can add more flexibility to plugin developers. Note, right now we have Application Developers – someone who use Cordova for developing applications and Plugin Developers – someone who creates plugins so that Application Developers can use them. For Application Developers we expose hooks so that they can customize their build/package/etc process. I want us to provide similar sort of flexibility to Plugin Developers so that they can go beyond of source/, framework/ tags and get mechanism to add custom installation, build logic required by a plugin. Example usage will include: downloading/compiling additional binaries, marking source file to be copied to output dir, changing target build platform, etc. At present time the steps described could be only achieved by hooks manually added by Application Developer, but the right way is to allow Plugin Developer to expose this as part of plugin definition. Example configuration could look like ``` script type=postinstall src=scripts/postinstall.js / script type=preinstall src=scripts/preinstall.js / script type=install src=scripts/install.js / ``` beforeinstall/preinstall – run before plugin is installed install/postinstall/afterinstall – run after plugin is installed uninstall – run after plugin is uninstalled -- 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-6481) Add unified hooks support for cordova app and plugins
[ https://issues.apache.org/jira/browse/CB-6481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14177742#comment-14177742 ] ASF GitHub Bot commented on CB-6481: GitHub user jsoref opened a pull request: https://github.com/apache/cordova-lib/pull/107 CB-6481 (Fix cordova platform check) You can merge this pull request into a Git repository by running: $ git pull https://github.com/jsoref/cordova-lib cb_6481 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-lib/pull/107.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #107 commit 58b37f5bf010a62c882ab3acfb23b69a41c1710e Author: Josh Soref jso...@blackberry.com Date: 2014-10-21T00:51:30Z CB-6481 (Fix cordova platform check) Add unified hooks support for cordova app and plugins - Key: CB-6481 URL: https://issues.apache.org/jira/browse/CB-6481 Project: Apache Cordova Issue Type: New Feature Components: CLI, Plugman Reporter: Sergey Grebnov Assignee: Sergey Grebnov As per Proposal: hooks support for plugins dev mail thread discussion Hi, I have an idea how we can add more flexibility to plugin developers. Note, right now we have Application Developers – someone who use Cordova for developing applications and Plugin Developers – someone who creates plugins so that Application Developers can use them. For Application Developers we expose hooks so that they can customize their build/package/etc process. I want us to provide similar sort of flexibility to Plugin Developers so that they can go beyond of source/, framework/ tags and get mechanism to add custom installation, build logic required by a plugin. Example usage will include: downloading/compiling additional binaries, marking source file to be copied to output dir, changing target build platform, etc. At present time the steps described could be only achieved by hooks manually added by Application Developer, but the right way is to allow Plugin Developer to expose this as part of plugin definition. Example configuration could look like ``` script type=postinstall src=scripts/postinstall.js / script type=preinstall src=scripts/preinstall.js / script type=install src=scripts/install.js / ``` beforeinstall/preinstall – run before plugin is installed install/postinstall/afterinstall – run after plugin is installed uninstall – run after plugin is uninstalled -- 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-6481) Add unified hooks support for cordova app and plugins
[ https://issues.apache.org/jira/browse/CB-6481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14177745#comment-14177745 ] ASF GitHub Bot commented on CB-6481: Github user asfgit closed the pull request at: https://github.com/apache/cordova-lib/pull/107 Add unified hooks support for cordova app and plugins - Key: CB-6481 URL: https://issues.apache.org/jira/browse/CB-6481 Project: Apache Cordova Issue Type: New Feature Components: CLI, Plugman Reporter: Sergey Grebnov Assignee: Sergey Grebnov As per Proposal: hooks support for plugins dev mail thread discussion Hi, I have an idea how we can add more flexibility to plugin developers. Note, right now we have Application Developers – someone who use Cordova for developing applications and Plugin Developers – someone who creates plugins so that Application Developers can use them. For Application Developers we expose hooks so that they can customize their build/package/etc process. I want us to provide similar sort of flexibility to Plugin Developers so that they can go beyond of source/, framework/ tags and get mechanism to add custom installation, build logic required by a plugin. Example usage will include: downloading/compiling additional binaries, marking source file to be copied to output dir, changing target build platform, etc. At present time the steps described could be only achieved by hooks manually added by Application Developer, but the right way is to allow Plugin Developer to expose this as part of plugin definition. Example configuration could look like ``` script type=postinstall src=scripts/postinstall.js / script type=preinstall src=scripts/preinstall.js / script type=install src=scripts/install.js / ``` beforeinstall/preinstall – run before plugin is installed install/postinstall/afterinstall – run after plugin is installed uninstall – run after plugin is uninstalled -- 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-7820) cordova platfrom restore stops if a platforms fails to restore
[
https://issues.apache.org/jira/browse/CB-7820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14177747#comment-14177747
]
ASF GitHub Bot commented on CB-7820:
Github user jsoref commented on a diff in the pull request:
https://github.com/apache/cordova-lib/pull/106#discussion_r19124580
--- Diff: cordova-lib/src/cordova/restore.js ---
@@ -54,7 +54,22 @@ function installPlatformsFromConfigXML(cfg){
if(!targets || !targets.length ){
return Q.all('No platforms are listed in config.xml to restore');
}
-return platform('add', targets);
+
+// Run platform add for all the platforms seperately
--- End diff --
There's a trailing whitespace here.
You're using tabs below.
There's trailing whitespace on the blank line above here too.
cordova platfrom restore stops if a platforms fails to restore
--
Key: CB-7820
URL: https://issues.apache.org/jira/browse/CB-7820
Project: Apache Cordova
Issue Type: Bug
Components: CLI
Reporter: Gorkem ERCAN
Assignee: Gorkem ERCAN
cordova restore platforms stops restoring platforms if one of the platforms
fails to restore.
For a config.xml that has android and windows when run on MacOS cordova
restore will fail on windows and never execute android restore (depending on
their order)
--
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-7033) cordova platform check command not working
[
https://issues.apache.org/jira/browse/CB-7033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14177758#comment-14177758
]
ASF GitHub Bot commented on CB-7033:
GitHub user jsoref opened a pull request:
https://github.com/apache/cordova-lib/pull/108
CB-7033 Improve cordova platform check …
* Make a softer statement about up-to-date status
* Report when cordova is out of date
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jsoref/cordova-lib cb_7033
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cordova-lib/pull/108.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #108
commit 5cdbf7ac059f37f2ccba79049ab1e42338d408b6
Author: Josh Soref jso...@blackberry.com
Date: 2014-10-21T00:58:05Z
CB-7033 Improve cordova platform check
* Make a softer statement about up-to-date status
commit 3e8976835b5cbf4bcce6cfc188673a4d4d2d3941
Author: Josh Soref jso...@blackberry.com
Date: 2014-10-21T00:58:47Z
CB-7033 Improve cordova platform check
* Report when cordova is out of date
cordova platform check command not working
--
Key: CB-7033
URL: https://issues.apache.org/jira/browse/CB-7033
Project: Apache Cordova
Issue Type: Bug
Components: CLI
Affects Versions: 3.4.0
Reporter: Victor Adrian Sosa Herrera
Priority: Minor
I have an app with Android installed and I know it was created with Cordova
3.3.1-0.1.2.
After running this command with a 3.4.1-1.0. CLI I get the following
{{$ cordova platform check}}
{{All platforms are up-to-date.}}
But after running cordova platform ls I get the following
{{$ cordova platform ls}}
{{Installed platforms: android broken}}
{{Available platforms: amazon-fireos, blackberry10, firefoxos, ubuntu}}
Using _platform check_ arguments I don't get the result I'm looking for (a
platform out-of-date), while using _platform ls_ it's not very clear, but I
presume the _broken_ platform is like an out-of-date message
--
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-7033) cordova platform check command not working
[
https://issues.apache.org/jira/browse/CB-7033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Soref reassigned CB-7033:
--
Assignee: Josh Soref
cordova platform check command not working
--
Key: CB-7033
URL: https://issues.apache.org/jira/browse/CB-7033
Project: Apache Cordova
Issue Type: Bug
Components: CLI
Affects Versions: 3.4.0
Reporter: Victor Adrian Sosa Herrera
Assignee: Josh Soref
Priority: Minor
I have an app with Android installed and I know it was created with Cordova
3.3.1-0.1.2.
After running this command with a 3.4.1-1.0. CLI I get the following
{{$ cordova platform check}}
{{All platforms are up-to-date.}}
But after running cordova platform ls I get the following
{{$ cordova platform ls}}
{{Installed platforms: android broken}}
{{Available platforms: amazon-fireos, blackberry10, firefoxos, ubuntu}}
Using _platform check_ arguments I don't get the result I'm looking for (a
platform out-of-date), while using _platform ls_ it's not very clear, but I
presume the _broken_ platform is like an out-of-date message
--
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-7729) [Xcode 6] Support new --target(s) to ios-sim
[ https://issues.apache.org/jira/browse/CB-7729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shazron Abdullah updated CB-7729: - Summary: [Xcode 6] Support new --target(s) to ios-sim (was: [Xcode 6] Pass devicetypeid instead of --target to match changes to ios-sim) [Xcode 6] Support new --target(s) to ios-sim Key: CB-7729 URL: https://issues.apache.org/jira/browse/CB-7729 Project: Apache Cordova Issue Type: Sub-task Components: iOS Reporter: Shazron Abdullah Assignee: Shazron Abdullah See https://github.com/apache/cordova-ios/pull/107 -- 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-6933) Add simulator OS version option to iOS platform run/emulate scripts
[
https://issues.apache.org/jira/browse/CB-6933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shazron Abdullah resolved CB-6933.
--
Resolution: Fixed
Fix Version/s: 3.7.0
Assignee: Shazron Abdullah
This has been fixed in CB-7729
Add simulator OS version option to iOS platform run/emulate scripts
---
Key: CB-6933
URL: https://issues.apache.org/jira/browse/CB-6933
Project: Apache Cordova
Issue Type: Improvement
Components: CLI, iOS
Affects Versions: 3.5.0
Environment: iOS build environment
Reporter: James White
Assignee: Shazron Abdullah
Fix For: 3.7.0
Use case:
The existing {noformat}cordova run ios --emulator{noformat} and
{noformat}cordova emulate ios{noformat} scripts include an option
{noformat}--target{noformat} to specify the desired simulator configuration
when invoking the simulator. The simulator by default will launch with the
latest version of the iOS being simulated.
Adding a new option {noformat}--targetos{noformat} to the platform's
run/emulate scripts would allow developers to specify which version of iOS to
start the simulator with.
ie: {noformat}cordova run ios --debug --emulator --target=iPhone Retina
(4-inch) --targetos=6.1{noformat}
If the {noformat}--targetos{noformat} option is provided to the run/emulate
script being executed, the string {noformat}--sdk value{noformat} can be
appended to the TARGET_FLAG variable that gets passed to ios-sim.
--
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-6581) Write script to run CordovaLibTests from the command line
[ https://issues.apache.org/jira/browse/CB-6581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shazron Abdullah resolved CB-6581. -- Resolution: Fixed Fix Version/s: 3.7.0 This was added in the repo recently. npm test Write script to run CordovaLibTests from the command line - Key: CB-6581 URL: https://issues.apache.org/jira/browse/CB-6581 Project: Apache Cordova Issue Type: Improvement Components: iOS Reporter: Shazron Abdullah Assignee: Shazron Abdullah Fix For: 3.7.0 This can potentially be run when cordova-ios is installed using npm install. -- 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-7568) iOS APP no sound when the mute button is active
[ https://issues.apache.org/jira/browse/CB-7568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shazron Abdullah resolved CB-7568. -- Resolution: Duplicate Assignee: Shazron Abdullah Duping to CB-7708, which has updated info and workaround. Continue the discussion there. iOS APP no sound when the mute button is active --- Key: CB-7568 URL: https://issues.apache.org/jira/browse/CB-7568 Project: Apache Cordova Issue Type: Bug Components: iOS Affects Versions: 3.5.0, 3.6.0 Environment: iPad with mute on Reporter: Federico Ricciuti Assignee: Shazron Abdullah Labels: ios, ipad, javascript, mute, video I am developing a video streaming application for the iPad, a first version is already available on the App Store, but now it's only accessible from italy. The issue concern about the mute button, when active application volume is turned off. As this is not normal behavior in the app for the iPad, many people do not realize it and believe it is an application problem. I'm not using the Media object, but a Javascript HTML5 player (www.projekktor.com). The same player is also used in the web version and in this case it works correctly on iPad with Safari and Chrome (the sound is on even when the mute button is active). I have read that there is no way of knowing if the mute button is active or not. How is it possible to ignore mute button? Is there any work around? I definitely can not use the Media object because it does not have some features that I need. -- 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-975) camera.getPicture crashes app on iPad3 when capturing multiple images
[
https://issues.apache.org/jira/browse/CB-975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shazron Abdullah updated CB-975:
Component/s: (was: iOS)
camera.getPicture crashes app on iPad3 when capturing multiple images
-
Key: CB-975
URL: https://issues.apache.org/jira/browse/CB-975
Project: Apache Cordova
Issue Type: Bug
Components: Plugin Camera
Affects Versions: 1.7.0, 1.8.1, 1.9.0, 2.0.0
Environment: iOS 5.1.1
iPad 3 (device is not jailbbroken or anything special, stock standard)
Built on PhoneGap Build service
iPhone 4s
Reporter: Andrew Smith
Assignee: Lorin Beer
Priority: Critical
Labels: camera, memory
I have a page which allows users to capture multiple images, one after the
other. Somewhere between the second and fifth capture, the application
crashes. Restarting the device and closing other apps makes no difference as
to how long it takes to crash.
-deleted-I have not been able to test on an iPhone.-deleted-
Update: can confirm it happens on iPhone 4S too.
I have tried with both FILE_URI and DATA_URL, with no noticeable change.
Here is my pared down code which exhibits the detailed behaviour. This
method is called from an onclick event on a DIV element.
{code:javascript}
ModFormCommon.AddPhoto = function () {
if (!navigator.camera) {
alert(Photos are not supported on this device);
return;
}
navigator.camera.getPicture(
function( data ) {
alert(Photo taken: + data.length);
},
function (sMessage) {
alert(Photo error: + sMessage);
},
{
quality: 25,
//destinationType: Camera.DestinationType.FILE_URI
destinationType: Camera.DestinationType.DATA_URL
});
};
{code}
The Crashlog is sometimes proceeded by a low memory warning, but not always,
so don't know that it's relevant.
Crashlog is as follows:
Incident Identifier: F8CD8A48-0989-479C-AC7E-4CBF31BAE737
CrashReporter Key: f491a35dbb4b6f2e7c0d29faeee7feaf7813f4c8
Hardware Model: iPad3,3
Process: MDC [809]
Path:
/var/mobile/Applications/CC253554-F6B5-4E8F-BC83-27F34241AE80/MDC.app/MDC
Identifier: MDC
Version: ??? (???)
Code Type: ARM (Native)
Parent Process: launchd [1]
Date/Time: 2012-06-28 11:53:53.141 +1000
OS Version: iPhone OS 5.1.1 (9B206)
Report Version: 104
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x
Crashed Thread: 10
Thread 0 name: Dispatch queue: com.apple.main-thread
Thread 0:
0 libsystem_kernel.dylib0x35034004 0x35033000 + 4100
1 libsystem_kernel.dylib0x350341fa 0x35033000 + 4602
2 CoreFoundation0x32b413ec 0x32ab4000 + 578540
3 CoreFoundation0x32b400ea 0x32ab4000 + 573674
4 CoreFoundation0x32ac349e 0x32ab4000 + 62622
5 CoreFoundation0x32ac3366 0x32ab4000 + 62310
6 GraphicsServices 0x32c10432 0x32c0c000 + 17458
7 UIKit 0x350a2cce 0x35071000 + 203982
8 MDC 0x24c8 0x1000 + 5320
9 MDC 0x2444 0x1000 + 5188
Thread 1 name: Dispatch queue: com.apple.libdispatch-manager
Thread 1:
0 libsystem_kernel.dylib0x350343a8 0x35033000 + 5032
1 libdispatch.dylib 0x31298f04 0x31295000 + 16132
2 libdispatch.dylib 0x31298c22 0x31295000 + 15394
Thread 2 name: WebThread
Thread 2:
0 libsystem_kernel.dylib0x35034004 0x35033000 + 4100
1 libsystem_kernel.dylib0x350341fa 0x35033000 + 4602
2 CoreFoundation0x32b413ec 0x32ab4000 + 578540
3 CoreFoundation0x32b40124 0x32ab4000 + 573732
4 CoreFoundation0x32ac349e 0x32ab4000 + 62622
5 CoreFoundation0x32ac3366 0x32ab4000 + 62310
6 WebCore 0x35861c9c 0x357b8000 + 695452
7 libsystem_c.dylib 0x31f2b72e 0x31f1d000 + 59182
8 libsystem_c.dylib 0x31f2b5e8 0x31f1d000 + 58856
Thread 3 name: com.apple.NSURLConnectionLoader
Thread 3:
0 libsystem_kernel.dylib0x35034004 0x35033000 + 4100
1 libsystem_kernel.dylib0x350341fa 0x35033000 + 4602
2 CoreFoundation0x32b413ec 0x32ab4000 + 578540
3 CoreFoundation0x32b40124 0x32ab4000 + 573732
4 CoreFoundation0x32ac349e 0x32ab4000 +
[jira] [Resolved] (CB-6782) Update cordova emulate script for new ios-sim 2.0.0 64-bit support
[ https://issues.apache.org/jira/browse/CB-6782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shazron Abdullah resolved CB-6782. -- Resolution: Fixed Fix Version/s: (was: 3.6.0) 3.7.0 Assignee: Shazron Abdullah Update cordova emulate script for new ios-sim 2.0.0 64-bit support -- Key: CB-6782 URL: https://issues.apache.org/jira/browse/CB-6782 Project: Apache Cordova Issue Type: Task Components: iOS Affects Versions: 3.5.0 Reporter: Shazron Abdullah Assignee: Shazron Abdullah Fix For: 3.7.0 Depends on https://github.com/phonegap/ios-sim/issues/89 -- 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-7473) [ios] add missing licenses
[
https://issues.apache.org/jira/browse/CB-7473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shazron Abdullah resolved CB-7473.
--
Resolution: Duplicate
Assignee: Shazron Abdullah
Most of the items in your report are build artifacts.
[ios] add missing licenses
--
Key: CB-7473
URL: https://issues.apache.org/jira/browse/CB-7473
Project: Apache Cordova
Issue Type: Bug
Components: iOS
Reporter: Marcel Kinard
Assignee: Shazron Abdullah
Priority: Minor
The following files are missing licenses. It should be added before the next
release. (Is there a rat-exclude missing?)
{code}
./CordovaLib/Classes/NSData+Base64.h
./CordovaLib/Classes/NSData+Base64.m
./CordovaLib/build/CordovaLib.build/Debug-iphoneos/CordovaLib.build/CordovaLib.dep
./CordovaLib/build/CordovaLib.build/Debug-iphoneos/CordovaLib.build/Objects-normal/armv7/CDVCommandDelegateImpl.d
./CordovaLib/build/CordovaLib.build/Debug-iphoneos/CordovaLib.build/Objects-normal/armv7/CDVCommandDelegateImpl.dia
./CordovaLib/build/CordovaLib.build/Debug-iphoneos/CordovaLib.build/Objects-normal/armv7/CDVCommandQueue.d
./CordovaLib/build/CordovaLib.build/Debug-iphoneos/CordovaLib.build/Objects-normal/armv7/CDVCommandQueue.dia
./CordovaLib/build/CordovaLib.build/Debug-iphoneos/CordovaLib.build/Objects-normal/armv7/CDVConfigParser.d
./CordovaLib/build/CordovaLib.build/Debug-iphoneos/CordovaLib.build/Objects-normal/armv7/CDVConfigParser.dia
./CordovaLib/build/CordovaLib.build/Debug-iphoneos/CordovaLib.build/Objects-normal/armv7/CDVInvokedUrlCommand.d
./CordovaLib/build/CordovaLib.build/Debug-iphoneos/CordovaLib.build/Objects-normal/armv7/CDVInvokedUrlCommand.dia
./CordovaLib/build/CordovaLib.build/Debug-iphoneos/CordovaLib.build/Objects-normal/armv7/CDVJSON.d
./CordovaLib/build/CordovaLib.build/Debug-iphoneos/CordovaLib.build/Objects-normal/armv7/CDVJSON.dia
./CordovaLib/build/CordovaLib.build/Debug-iphoneos/CordovaLib.build/Objects-normal/armv7/CDVLocalStorage.d
./CordovaLib/build/CordovaLib.build/Debug-iphoneos/CordovaLib.build/Objects-normal/armv7/CDVLocalStorage.dia
./CordovaLib/build/CordovaLib.build/Debug-iphoneos/CordovaLib.build/Objects-normal/armv7/CDVPlugin.d
./CordovaLib/build/CordovaLib.build/Debug-iphoneos/CordovaLib.build/Objects-normal/armv7/CDVPlugin.dia
./CordovaLib/build/CordovaLib.build/Debug-iphoneos/CordovaLib.build/Objects-normal/armv7/CDVPluginResult.d
./CordovaLib/build/CordovaLib.build/Debug-iphoneos/CordovaLib.build/Objects-normal/armv7/CDVPluginResult.dia
./CordovaLib/build/CordovaLib.build/Debug-iphoneos/CordovaLib.build/Objects-normal/armv7/CDVShared.d
./CordovaLib/build/CordovaLib.build/Debug-iphoneos/CordovaLib.build/Objects-normal/armv7/CDVShared.dia
./CordovaLib/build/CordovaLib.build/Debug-iphoneos/CordovaLib.build/Objects-normal/armv7/CDVTimer.d
./CordovaLib/build/CordovaLib.build/Debug-iphoneos/CordovaLib.build/Objects-normal/armv7/CDVTimer.dia
./CordovaLib/build/CordovaLib.build/Debug-iphoneos/CordovaLib.build/Objects-normal/armv7/CDVURLProtocol.d
./CordovaLib/build/CordovaLib.build/Debug-iphoneos/CordovaLib.build/Objects-normal/armv7/CDVURLProtocol.dia
./CordovaLib/build/CordovaLib.build/Debug-iphoneos/CordovaLib.build/Objects-normal/armv7/CDVUserAgentUtil.d
./CordovaLib/build/CordovaLib.build/Debug-iphoneos/CordovaLib.build/Objects-normal/armv7/CDVUserAgentUtil.dia
./CordovaLib/build/CordovaLib.build/Debug-iphoneos/CordovaLib.build/Objects-normal/armv7/CDVViewController.d
./CordovaLib/build/CordovaLib.build/Debug-iphoneos/CordovaLib.build/Objects-normal/armv7/CDVViewController.dia
./CordovaLib/build/CordovaLib.build/Debug-iphoneos/CordovaLib.build/Objects-normal/armv7/CDVWebViewDelegate.d
./CordovaLib/build/CordovaLib.build/Debug-iphoneos/CordovaLib.build/Objects-normal/armv7/CDVWebViewDelegate.dia
./CordovaLib/build/CordovaLib.build/Debug-iphoneos/CordovaLib.build/Objects-normal/armv7/CDVWhitelist.d
./CordovaLib/build/CordovaLib.build/Debug-iphoneos/CordovaLib.build/Objects-normal/armv7/CDVWhitelist.dia
./CordovaLib/build/CordovaLib.build/Debug-iphoneos/CordovaLib.build/Objects-normal/armv7/Cordova.LinkFileList
./CordovaLib/build/CordovaLib.build/Debug-iphoneos/CordovaLib.build/Objects-normal/armv7/NSArray+Comparisons.d
./CordovaLib/build/CordovaLib.build/Debug-iphoneos/CordovaLib.build/Objects-normal/armv7/NSArray+Comparisons.dia
./CordovaLib/build/CordovaLib.build/Debug-iphoneos/CordovaLib.build/Objects-normal/armv7/NSData+Base64.d
./CordovaLib/build/CordovaLib.build/Debug-iphoneos/CordovaLib.build/Objects-normal/armv7/NSData+Base64.dia
[jira] [Commented] (CB-7033) cordova platform check command not working
[
https://issues.apache.org/jira/browse/CB-7033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14177806#comment-14177806
]
ASF GitHub Bot commented on CB-7033:
Github user jsoref commented on the pull request:
https://github.com/apache/cordova-lib/pull/108#issuecomment-59867354
Here's sample output:
```sh
An update of cordova is available: 4.0.0
android @ 3.6.4; current did not install, and thus its version cannot be
determined
blackberry10 @ broken could be updated to: 3.6.3
firefoxos @ 3.6.1 could be updated to: 3.6.3
```
cordova platform check command not working
--
Key: CB-7033
URL: https://issues.apache.org/jira/browse/CB-7033
Project: Apache Cordova
Issue Type: Bug
Components: CLI
Affects Versions: 3.4.0
Reporter: Victor Adrian Sosa Herrera
Assignee: Josh Soref
Priority: Minor
I have an app with Android installed and I know it was created with Cordova
3.3.1-0.1.2.
After running this command with a 3.4.1-1.0. CLI I get the following
{{$ cordova platform check}}
{{All platforms are up-to-date.}}
But after running cordova platform ls I get the following
{{$ cordova platform ls}}
{{Installed platforms: android broken}}
{{Available platforms: amazon-fireos, blackberry10, firefoxos, ubuntu}}
Using _platform check_ arguments I don't get the result I'm looking for (a
platform out-of-date), while using _platform ls_ it's not very clear, but I
presume the _broken_ platform is like an out-of-date message
--
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-7820) cordova platfrom restore stops if a platforms fails to restore
[
https://issues.apache.org/jira/browse/CB-7820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14177838#comment-14177838
]
ASF GitHub Bot commented on CB-7820:
Github user gorkem commented on a diff in the pull request:
https://github.com/apache/cordova-lib/pull/106#discussion_r19126554
--- Diff: cordova-lib/src/cordova/restore.js ---
@@ -54,7 +54,22 @@ function installPlatformsFromConfigXML(cfg){
if(!targets || !targets.length ){
return Q.all('No platforms are listed in config.xml to restore');
}
-return platform('add', targets);
+
+// Run platform add for all the platforms seperately
--- End diff --
Got a new development environment... updated now.
cordova platfrom restore stops if a platforms fails to restore
--
Key: CB-7820
URL: https://issues.apache.org/jira/browse/CB-7820
Project: Apache Cordova
Issue Type: Bug
Components: CLI
Reporter: Gorkem ERCAN
Assignee: Gorkem ERCAN
cordova restore platforms stops restoring platforms if one of the platforms
fails to restore.
For a config.xml that has android and windows when run on MacOS cordova
restore will fail on windows and never execute android restore (depending on
their order)
--
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-7827) manifest/application/activity[android:name] always CordovaApp
Sergey created CB-7827: -- Summary: manifest/application/activity[android:name] always CordovaApp Key: CB-7827 URL: https://issues.apache.org/jira/browse/CB-7827 Project: Apache Cordova Issue Type: Bug Components: CLI Affects Versions: 4.0.0 Environment: Windows 8.1 x64, NodeJs 0.10.32 Reporter: Sergey -- 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-7828) manifest/application/activity[android:name] always CordovaApp
Sergey created CB-7828: -- Summary: manifest/application/activity[android:name] always CordovaApp Key: CB-7828 URL: https://issues.apache.org/jira/browse/CB-7828 Project: Apache Cordova Issue Type: Bug Components: CLI Affects Versions: 4.0.0 Environment: Windows 8.1 x64, NodeJs 0.10.32 Reporter: Sergey -- 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-7828) manifest/application/activity[android:name] always CordovaApp
[ https://issues.apache.org/jira/browse/CB-7828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey updated CB-7828: --- Description: android build file always named CordovaApp instead of config.xml/name manifest/application/activity[android:name] always CordovaApp - Key: CB-7828 URL: https://issues.apache.org/jira/browse/CB-7828 Project: Apache Cordova Issue Type: Bug Components: CLI Affects Versions: 4.0.0 Environment: Windows 8.1 x64, NodeJs 0.10.32 Reporter: Sergey Labels: build, config.xml android build file always named CordovaApp instead of config.xml/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
