[jira] [Updated] (CB-11072) Android File plugin tests cause a crash sometimes
[ https://issues.apache.org/jira/browse/CB-11072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Khandelwal updated CB-11072: --- Labels: found-by-ci (was: ) > Android File plugin tests cause a crash sometimes > - > > Key: CB-11072 > URL: https://issues.apache.org/jira/browse/CB-11072 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin File >Reporter: Nikhil Khandelwal >Priority: Minor > Labels: found-by-ci > Attachments: cordova-android-osx_2276_gathering-logs_stdio.log > > > See attached logs for details > There is a very rare occurrence of this: > E/System ( 991): Uncaught exception thrown by finalizer > E/System ( 991): java.io.IOException: close failed: EBADF (Bad file number) > E/System ( 991):at libcore.io.IoUtils.close(IoUtils.java:46) > E/System ( 991):at > java.io.FileInputStream.close(FileInputStream.java:121) > E/System ( 991):at > java.io.FileInputStream.finalize(FileInputStream.java:142) > E/System ( 991):at > java.lang.Daemons$FinalizerDaemon.doFinalize(Daemons.java:187) > E/System ( 991):at > java.lang.Daemons$FinalizerDaemon.run(Daemons.java:170) > E/System ( 991):at java.lang.Thread.run(Thread.java:841) > E/System ( 991): Caused by: libcore.io.ErrnoException: close failed: EBADF > (Bad file number) > E/System ( 991):at libcore.io.Posix.close(Native Method) > E/System ( 991):at libcore.io.BlockGuardOs.close(BlockGuardOs.java:75) > E/System ( 991):at libcore.io.IoUtils.close(IoUtils.java:43) > E/System ( 991):... 5 more > E/System ( 991): Uncaught exception thrown by finalizer > E/System ( 991): java.io.IOException: close failed: EBADF (Bad file number) > E/System ( 991):at libcore.io.IoUtils.close(IoUtils.java:46) > E/System ( 991):at > java.io.FileInputStream.close(FileInputStream.java:121) > E/System ( 991):at > java.io.FileInputStream.finalize(FileInputStream.java:142) > E/System ( 991):at > java.lang.Daemons$FinalizerDaemon.doFinalize(Daemons.java:187) > E/System ( 991):at > java.lang.Daemons$FinalizerDaemon.run(Daemons.java:170) > E/System ( 991):at java.lang.Thread.run(Thread.java:841) > E/System ( 991): Caused by: libcore.io.ErrnoException: close failed: EBADF > (Bad file number) > E/System ( 991):at libcore.io.Posix.close(Native Method) > E/System ( 991):at libcore.io.BlockGuardOs.close(BlockGuardOs.java:75) > E/System ( 991):at libcore.io.IoUtils.close(IoUtils.java:43) > E/System ( 991):... 5 more > F/libc( 991): Fatal signal 6 (SIGABRT) at 0x03df (code=-6), thread > 1048 (Chrome_InProcRe) > E/eglCodecCommon( 991): glUtilsParamSize: unknow param 0x0b44 > E/eglCodecCommon( 991): glUtilsParamSize: unknow param 0x0bd0 > E/eglCodecCommon( 991): ERROR unknown type 0xe4e4e4e4 (glSizeof,72) > I/DEBUG ( 54): *** *** *** *** *** *** *** *** *** *** *** *** *** *** > *** *** > I/DEBUG ( 54): Build fingerprint: > 'generic/sdk/generic:4.4.4/KK/1743154:eng/test-keys' > I/DEBUG ( 54): Revision: '0' > I/DEBUG ( 54): pid: 991, tid: 1048, name: Chrome_InProcRe >>> > org.apache.mobilespec <<< > I/DEBUG ( 54): signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr > I/DEBUG ( 54): r0 r1 0418 r2 0006 r3 > I/DEBUG ( 54): r4 0006 r5 0009 r6 0418 r7 010c > I/DEBUG ( 54): r8 a737c7e4 r9 b9361a88 sl b900a8a8 fp > I/DEBUG ( 54): ip 0008 sp a737c770 lr b6ec2ead pc b6ed1e20 > cpsr 0010 > I/DEBUG ( 54): d0 41d5c2d1b853b5d0 d1 > I/DEBUG ( 54): d2 d3 > I/DEBUG ( 54): d4 41d5c2d1b852716d d5 > I/DEBUG ( 54): d6 4314c0bf492db510 d7 412e8480 > I/DEBUG ( 54): d8 d9 > I/DEBUG ( 54): d10 d11 > I/DEBUG ( 54): d12 d13 > I/DEBUG ( 54): d14 d15 > I/DEBUG ( 54): scr 2213 > I/DEBUG ( 54): > I/DEBUG ( 54): backtrace: > I/DEBUG ( 54): #00 pc 00021e20 /system/lib/libc.so (tgkill+12) > I/DEBUG ( 54): #01 pc 00012ea9 /system/lib/libc.so (pthread_kill+48) > I/DEBUG ( 54): #02 pc 000130bd /system/lib/libc.so (raise+10) > I/DEBUG ( 54): #03 pc 00011df3 /system/lib/libc.so > I/DEBUG ( 54): #04 pc 000216d4 /system/lib/libc.so (abort+4) > I/DEBUG ( 54): #05 pc 001a554d /system/lib/libwebviewchromium.so > I/DEBUG ( 54): #06 pc 00eb6de3 /system/lib/libwebviewchromium.so > I/DEBUG ( 54): #07 pc 00c9f353
[jira] [Updated] (CB-11072) Android File plugin tests cause a crash sometimes
[ https://issues.apache.org/jira/browse/CB-11072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Khandelwal updated CB-11072: --- Attachment: cordova-android-osx_2276_gathering-logs_stdio.log > Android File plugin tests cause a crash sometimes > - > > Key: CB-11072 > URL: https://issues.apache.org/jira/browse/CB-11072 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin File >Reporter: Nikhil Khandelwal >Priority: Minor > Attachments: cordova-android-osx_2276_gathering-logs_stdio.log > > > See attached logs for details > There is a very rare occurrence of this: > E/System ( 991): Uncaught exception thrown by finalizer > E/System ( 991): java.io.IOException: close failed: EBADF (Bad file number) > E/System ( 991):at libcore.io.IoUtils.close(IoUtils.java:46) > E/System ( 991):at > java.io.FileInputStream.close(FileInputStream.java:121) > E/System ( 991):at > java.io.FileInputStream.finalize(FileInputStream.java:142) > E/System ( 991):at > java.lang.Daemons$FinalizerDaemon.doFinalize(Daemons.java:187) > E/System ( 991):at > java.lang.Daemons$FinalizerDaemon.run(Daemons.java:170) > E/System ( 991):at java.lang.Thread.run(Thread.java:841) > E/System ( 991): Caused by: libcore.io.ErrnoException: close failed: EBADF > (Bad file number) > E/System ( 991):at libcore.io.Posix.close(Native Method) > E/System ( 991):at libcore.io.BlockGuardOs.close(BlockGuardOs.java:75) > E/System ( 991):at libcore.io.IoUtils.close(IoUtils.java:43) > E/System ( 991):... 5 more > E/System ( 991): Uncaught exception thrown by finalizer > E/System ( 991): java.io.IOException: close failed: EBADF (Bad file number) > E/System ( 991):at libcore.io.IoUtils.close(IoUtils.java:46) > E/System ( 991):at > java.io.FileInputStream.close(FileInputStream.java:121) > E/System ( 991):at > java.io.FileInputStream.finalize(FileInputStream.java:142) > E/System ( 991):at > java.lang.Daemons$FinalizerDaemon.doFinalize(Daemons.java:187) > E/System ( 991):at > java.lang.Daemons$FinalizerDaemon.run(Daemons.java:170) > E/System ( 991):at java.lang.Thread.run(Thread.java:841) > E/System ( 991): Caused by: libcore.io.ErrnoException: close failed: EBADF > (Bad file number) > E/System ( 991):at libcore.io.Posix.close(Native Method) > E/System ( 991):at libcore.io.BlockGuardOs.close(BlockGuardOs.java:75) > E/System ( 991):at libcore.io.IoUtils.close(IoUtils.java:43) > E/System ( 991):... 5 more > F/libc( 991): Fatal signal 6 (SIGABRT) at 0x03df (code=-6), thread > 1048 (Chrome_InProcRe) > E/eglCodecCommon( 991): glUtilsParamSize: unknow param 0x0b44 > E/eglCodecCommon( 991): glUtilsParamSize: unknow param 0x0bd0 > E/eglCodecCommon( 991): ERROR unknown type 0xe4e4e4e4 (glSizeof,72) > I/DEBUG ( 54): *** *** *** *** *** *** *** *** *** *** *** *** *** *** > *** *** > I/DEBUG ( 54): Build fingerprint: > 'generic/sdk/generic:4.4.4/KK/1743154:eng/test-keys' > I/DEBUG ( 54): Revision: '0' > I/DEBUG ( 54): pid: 991, tid: 1048, name: Chrome_InProcRe >>> > org.apache.mobilespec <<< > I/DEBUG ( 54): signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr > I/DEBUG ( 54): r0 r1 0418 r2 0006 r3 > I/DEBUG ( 54): r4 0006 r5 0009 r6 0418 r7 010c > I/DEBUG ( 54): r8 a737c7e4 r9 b9361a88 sl b900a8a8 fp > I/DEBUG ( 54): ip 0008 sp a737c770 lr b6ec2ead pc b6ed1e20 > cpsr 0010 > I/DEBUG ( 54): d0 41d5c2d1b853b5d0 d1 > I/DEBUG ( 54): d2 d3 > I/DEBUG ( 54): d4 41d5c2d1b852716d d5 > I/DEBUG ( 54): d6 4314c0bf492db510 d7 412e8480 > I/DEBUG ( 54): d8 d9 > I/DEBUG ( 54): d10 d11 > I/DEBUG ( 54): d12 d13 > I/DEBUG ( 54): d14 d15 > I/DEBUG ( 54): scr 2213 > I/DEBUG ( 54): > I/DEBUG ( 54): backtrace: > I/DEBUG ( 54): #00 pc 00021e20 /system/lib/libc.so (tgkill+12) > I/DEBUG ( 54): #01 pc 00012ea9 /system/lib/libc.so (pthread_kill+48) > I/DEBUG ( 54): #02 pc 000130bd /system/lib/libc.so (raise+10) > I/DEBUG ( 54): #03 pc 00011df3 /system/lib/libc.so > I/DEBUG ( 54): #04 pc 000216d4 /system/lib/libc.so (abort+4) > I/DEBUG ( 54): #05 pc 001a554d /system/lib/libwebviewchromium.so > I/DEBUG ( 54): #06 pc 00eb6de3 /system/lib/libwebviewchromium.so > I/DEBUG ( 54): #07 pc 00c9f353
[jira] [Updated] (CB-11072) Android File plugin tests cause a crash sometimes
[ https://issues.apache.org/jira/browse/CB-11072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikhil Khandelwal updated CB-11072: --- Description: See attached logs for details There is a very rare occurrence of this: E/System ( 991): Uncaught exception thrown by finalizer E/System ( 991): java.io.IOException: close failed: EBADF (Bad file number) E/System ( 991): at libcore.io.IoUtils.close(IoUtils.java:46) E/System ( 991): at java.io.FileInputStream.close(FileInputStream.java:121) E/System ( 991): at java.io.FileInputStream.finalize(FileInputStream.java:142) E/System ( 991): at java.lang.Daemons$FinalizerDaemon.doFinalize(Daemons.java:187) E/System ( 991): at java.lang.Daemons$FinalizerDaemon.run(Daemons.java:170) E/System ( 991): at java.lang.Thread.run(Thread.java:841) E/System ( 991): Caused by: libcore.io.ErrnoException: close failed: EBADF (Bad file number) E/System ( 991): at libcore.io.Posix.close(Native Method) E/System ( 991): at libcore.io.BlockGuardOs.close(BlockGuardOs.java:75) E/System ( 991): at libcore.io.IoUtils.close(IoUtils.java:43) E/System ( 991): ... 5 more E/System ( 991): Uncaught exception thrown by finalizer E/System ( 991): java.io.IOException: close failed: EBADF (Bad file number) E/System ( 991): at libcore.io.IoUtils.close(IoUtils.java:46) E/System ( 991): at java.io.FileInputStream.close(FileInputStream.java:121) E/System ( 991): at java.io.FileInputStream.finalize(FileInputStream.java:142) E/System ( 991): at java.lang.Daemons$FinalizerDaemon.doFinalize(Daemons.java:187) E/System ( 991): at java.lang.Daemons$FinalizerDaemon.run(Daemons.java:170) E/System ( 991): at java.lang.Thread.run(Thread.java:841) E/System ( 991): Caused by: libcore.io.ErrnoException: close failed: EBADF (Bad file number) E/System ( 991): at libcore.io.Posix.close(Native Method) E/System ( 991): at libcore.io.BlockGuardOs.close(BlockGuardOs.java:75) E/System ( 991): at libcore.io.IoUtils.close(IoUtils.java:43) E/System ( 991): ... 5 more F/libc( 991): Fatal signal 6 (SIGABRT) at 0x03df (code=-6), thread 1048 (Chrome_InProcRe) E/eglCodecCommon( 991): glUtilsParamSize: unknow param 0x0b44 E/eglCodecCommon( 991): glUtilsParamSize: unknow param 0x0bd0 E/eglCodecCommon( 991): ERROR unknown type 0xe4e4e4e4 (glSizeof,72) I/DEBUG ( 54): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** I/DEBUG ( 54): Build fingerprint: 'generic/sdk/generic:4.4.4/KK/1743154:eng/test-keys' I/DEBUG ( 54): Revision: '0' I/DEBUG ( 54): pid: 991, tid: 1048, name: Chrome_InProcRe >>> org.apache.mobilespec <<< I/DEBUG ( 54): signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr I/DEBUG ( 54): r0 r1 0418 r2 0006 r3 I/DEBUG ( 54): r4 0006 r5 0009 r6 0418 r7 010c I/DEBUG ( 54): r8 a737c7e4 r9 b9361a88 sl b900a8a8 fp I/DEBUG ( 54): ip 0008 sp a737c770 lr b6ec2ead pc b6ed1e20 cpsr 0010 I/DEBUG ( 54): d0 41d5c2d1b853b5d0 d1 I/DEBUG ( 54): d2 d3 I/DEBUG ( 54): d4 41d5c2d1b852716d d5 I/DEBUG ( 54): d6 4314c0bf492db510 d7 412e8480 I/DEBUG ( 54): d8 d9 I/DEBUG ( 54): d10 d11 I/DEBUG ( 54): d12 d13 I/DEBUG ( 54): d14 d15 I/DEBUG ( 54): scr 2213 I/DEBUG ( 54): I/DEBUG ( 54): backtrace: I/DEBUG ( 54): #00 pc 00021e20 /system/lib/libc.so (tgkill+12) I/DEBUG ( 54): #01 pc 00012ea9 /system/lib/libc.so (pthread_kill+48) I/DEBUG ( 54): #02 pc 000130bd /system/lib/libc.so (raise+10) I/DEBUG ( 54): #03 pc 00011df3 /system/lib/libc.so I/DEBUG ( 54): #04 pc 000216d4 /system/lib/libc.so (abort+4) I/DEBUG ( 54): #05 pc 001a554d /system/lib/libwebviewchromium.so I/DEBUG ( 54): #06 pc 00eb6de3 /system/lib/libwebviewchromium.so I/DEBUG ( 54): #07 pc 00c9f353 /system/lib/libwebviewchromium.so I/DEBUG ( 54): #08 pc 00eb7a4d /system/lib/libwebviewchromium.so I/DEBUG ( 54): #09 pc 00eb7df1 /system/lib/libwebviewchromium.so I/DEBUG ( 54): #10 pc 00eaa9df /system/lib/libwebviewchromium.so I/DEBUG ( 54): #11 pc 00cfc441 /system/lib/libwebviewchromium.so I/DEBUG ( 54): #12 pc 00cfc225 /system/lib/libwebviewchromium.so I/DEBUG ( 54): #13 pc 001b1641 /system/lib/libwebviewchromium.so I/DEBUG ( 54): #14 pc 001b20d1 /system/lib/libwebviewchromium.so I/DEBUG ( 54): #15 pc 001b222f
[jira] [Created] (CB-11072) Android File plugin tests cause a crash sometimes
Nikhil Khandelwal created CB-11072: -- Summary: Android File plugin tests cause a crash sometimes Key: CB-11072 URL: https://issues.apache.org/jira/browse/CB-11072 Project: Apache Cordova Issue Type: Bug Components: Plugin File Reporter: Nikhil Khandelwal Priority: Minor E/System ( 991): Uncaught exception thrown by finalizer E/System ( 991): java.io.IOException: close failed: EBADF (Bad file number) E/System ( 991): at libcore.io.IoUtils.close(IoUtils.java:46) E/System ( 991): at java.io.FileInputStream.close(FileInputStream.java:121) E/System ( 991): at java.io.FileInputStream.finalize(FileInputStream.java:142) E/System ( 991): at java.lang.Daemons$FinalizerDaemon.doFinalize(Daemons.java:187) E/System ( 991): at java.lang.Daemons$FinalizerDaemon.run(Daemons.java:170) E/System ( 991): at java.lang.Thread.run(Thread.java:841) E/System ( 991): Caused by: libcore.io.ErrnoException: close failed: EBADF (Bad file number) E/System ( 991): at libcore.io.Posix.close(Native Method) E/System ( 991): at libcore.io.BlockGuardOs.close(BlockGuardOs.java:75) E/System ( 991): at libcore.io.IoUtils.close(IoUtils.java:43) E/System ( 991): ... 5 more E/System ( 991): Uncaught exception thrown by finalizer E/System ( 991): java.io.IOException: close failed: EBADF (Bad file number) E/System ( 991): at libcore.io.IoUtils.close(IoUtils.java:46) E/System ( 991): at java.io.FileInputStream.close(FileInputStream.java:121) E/System ( 991): at java.io.FileInputStream.finalize(FileInputStream.java:142) E/System ( 991): at java.lang.Daemons$FinalizerDaemon.doFinalize(Daemons.java:187) E/System ( 991): at java.lang.Daemons$FinalizerDaemon.run(Daemons.java:170) E/System ( 991): at java.lang.Thread.run(Thread.java:841) E/System ( 991): Caused by: libcore.io.ErrnoException: close failed: EBADF (Bad file number) E/System ( 991): at libcore.io.Posix.close(Native Method) E/System ( 991): at libcore.io.BlockGuardOs.close(BlockGuardOs.java:75) E/System ( 991): at libcore.io.IoUtils.close(IoUtils.java:43) E/System ( 991): ... 5 more F/libc( 991): Fatal signal 6 (SIGABRT) at 0x03df (code=-6), thread 1048 (Chrome_InProcRe) E/eglCodecCommon( 991): glUtilsParamSize: unknow param 0x0b44 E/eglCodecCommon( 991): glUtilsParamSize: unknow param 0x0bd0 E/eglCodecCommon( 991): ERROR unknown type 0xe4e4e4e4 (glSizeof,72) I/DEBUG ( 54): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** I/DEBUG ( 54): Build fingerprint: 'generic/sdk/generic:4.4.4/KK/1743154:eng/test-keys' I/DEBUG ( 54): Revision: '0' I/DEBUG ( 54): pid: 991, tid: 1048, name: Chrome_InProcRe >>> org.apache.mobilespec <<< I/DEBUG ( 54): signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr I/DEBUG ( 54): r0 r1 0418 r2 0006 r3 I/DEBUG ( 54): r4 0006 r5 0009 r6 0418 r7 010c I/DEBUG ( 54): r8 a737c7e4 r9 b9361a88 sl b900a8a8 fp I/DEBUG ( 54): ip 0008 sp a737c770 lr b6ec2ead pc b6ed1e20 cpsr 0010 I/DEBUG ( 54): d0 41d5c2d1b853b5d0 d1 I/DEBUG ( 54): d2 d3 I/DEBUG ( 54): d4 41d5c2d1b852716d d5 I/DEBUG ( 54): d6 4314c0bf492db510 d7 412e8480 I/DEBUG ( 54): d8 d9 I/DEBUG ( 54): d10 d11 I/DEBUG ( 54): d12 d13 I/DEBUG ( 54): d14 d15 I/DEBUG ( 54): scr 2213 I/DEBUG ( 54): I/DEBUG ( 54): backtrace: I/DEBUG ( 54): #00 pc 00021e20 /system/lib/libc.so (tgkill+12) I/DEBUG ( 54): #01 pc 00012ea9 /system/lib/libc.so (pthread_kill+48) I/DEBUG ( 54): #02 pc 000130bd /system/lib/libc.so (raise+10) I/DEBUG ( 54): #03 pc 00011df3 /system/lib/libc.so I/DEBUG ( 54): #04 pc 000216d4 /system/lib/libc.so (abort+4) I/DEBUG ( 54): #05 pc 001a554d /system/lib/libwebviewchromium.so I/DEBUG ( 54): #06 pc 00eb6de3 /system/lib/libwebviewchromium.so I/DEBUG ( 54): #07 pc 00c9f353 /system/lib/libwebviewchromium.so I/DEBUG ( 54): #08 pc 00eb7a4d /system/lib/libwebviewchromium.so I/DEBUG ( 54): #09 pc 00eb7df1 /system/lib/libwebviewchromium.so I/DEBUG ( 54): #10 pc 00eaa9df /system/lib/libwebviewchromium.so I/DEBUG ( 54): #11 pc 00cfc441 /system/lib/libwebviewchromium.so I/DEBUG ( 54): #12 pc 00cfc225 /system/lib/libwebviewchromium.so I/DEBUG ( 54): #13 pc 001b1641 /system/lib/libwebviewchromium.so I/DEBUG (
[jira] [Created] (CB-11071) Cordova 4 removed the shouldRotateToOrientation call which breaks the screen orientation plugins
Adrian Leung created CB-11071: - Summary: Cordova 4 removed the shouldRotateToOrientation call which breaks the screen orientation plugins Key: CB-11071 URL: https://issues.apache.org/jira/browse/CB-11071 Project: Apache Cordova Issue Type: Bug Components: iOS Affects Versions: 4.0.0 Environment: Ionic 2, iOS, Android, Mac, Cordova 4.0 Reporter: Adrian Leung Cordova 4 removed the shouldRotateToOrientation call which breaks the screen orientation plugins that everyone else is using! If you are installing a fresh install of cordova you will likely get cordova iOS v4.0.x, there are a number of issues related to this already e.g #84. You could try an install cordova iOS from the 3 branch and you may have more luck. At this stage I have not had time to find a solution after cordova 4 removed the shouldRotateToOrientation call. https://github.com/gbenvenuti/cordova-plugin-screen-orientation/issues/98 -- 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-10898) 'Invalid Device State' when starting iOS simulator
[ https://issues.apache.org/jira/browse/CB-10898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15238363#comment-15238363 ] ASF GitHub Bot commented on CB-10898: - Github user asfgit closed the pull request at: https://github.com/apache/cordova-medic/pull/88 > 'Invalid Device State' when starting iOS simulator > -- > > Key: CB-10898 > URL: https://issues.apache.org/jira/browse/CB-10898 > Project: Apache Cordova > Issue Type: Bug >Reporter: Omar Mefire >Assignee: Omar Mefire >Priority: Critical > Labels: cordova-ios, found-by-ci > > When trying to run the mobilespec app on the iOS simulator, an error: > 'Invalid Device State' is encountered. > Log: > https://ci.apache.org/builders/cordova-ios/builds/2076/steps/running-tests/logs/stdio > == > Results at > '/Users/buildbot/slaves/apache/cordova-ios/mobilespec/platforms/ios/build/device/mobilespec.ipa' > > [] Waiting up to 1 seconds for iOS device to be connected > No target specified for emulator. Deploying to iPhone-6s-Plus, 9.1 simulator > An error was encountered processing the command > (domain=com.apple.CoreSimulator.SimError, code=159): > Invalid device state > logPath: > /Users/buildbot/slaves/apache/cordova-ios/mobilespec/platforms/ios/cordova/console.log > [MEDIC LOG Thu, 17 Mar 2016 06:06:24 GMT] Finished waiting for run command > [MEDIC LOG Thu, 17 Mar 2016 06:06:24 GMT] started waiting for test results > [MEDIC LOG Thu, 17 Mar 2016 06:30:25 GMT] Finished polling for mobilespec > results. > [MEDIC LOG Thu, 17 Mar 2016 06:30:25 GMT] Results Found: false > [MEDIC LOG Thu, 17 Mar 2016 06:30:25 GMT] Total attempts: 144 > [MEDIC LOG Thu, 17 Mar 2016 06:30:25 GMT] Failed attempts: 0 > [MEDIC LOG Thu, 17 Mar 2016 06:30:25 GMT] FATAL: Could not find test results. > Check the output of medic-log to see if the app crashed before it could > upload them to couchdb. > program finished with exit code 1 > elapsedTime=1491.694117 -- 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-10898) 'Invalid Device State' when starting iOS simulator
[ https://issues.apache.org/jira/browse/CB-10898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15238362#comment-15238362 ] ASF subversion and git services commented on CB-10898: -- Commit d45909b2e5decd2defebb5d1583e09e4270fe110 in cordova-medic's branch refs/heads/master from [~omefire] [ https://git-wip-us.apache.org/repos/asf?p=cordova-medic.git;h=d45909b ] CB-10898 Kill simulator Xcode6 style This closes #88 > 'Invalid Device State' when starting iOS simulator > -- > > Key: CB-10898 > URL: https://issues.apache.org/jira/browse/CB-10898 > Project: Apache Cordova > Issue Type: Bug >Reporter: Omar Mefire >Assignee: Omar Mefire >Priority: Critical > Labels: cordova-ios, found-by-ci > > When trying to run the mobilespec app on the iOS simulator, an error: > 'Invalid Device State' is encountered. > Log: > https://ci.apache.org/builders/cordova-ios/builds/2076/steps/running-tests/logs/stdio > == > Results at > '/Users/buildbot/slaves/apache/cordova-ios/mobilespec/platforms/ios/build/device/mobilespec.ipa' > > [] Waiting up to 1 seconds for iOS device to be connected > No target specified for emulator. Deploying to iPhone-6s-Plus, 9.1 simulator > An error was encountered processing the command > (domain=com.apple.CoreSimulator.SimError, code=159): > Invalid device state > logPath: > /Users/buildbot/slaves/apache/cordova-ios/mobilespec/platforms/ios/cordova/console.log > [MEDIC LOG Thu, 17 Mar 2016 06:06:24 GMT] Finished waiting for run command > [MEDIC LOG Thu, 17 Mar 2016 06:06:24 GMT] started waiting for test results > [MEDIC LOG Thu, 17 Mar 2016 06:30:25 GMT] Finished polling for mobilespec > results. > [MEDIC LOG Thu, 17 Mar 2016 06:30:25 GMT] Results Found: false > [MEDIC LOG Thu, 17 Mar 2016 06:30:25 GMT] Total attempts: 144 > [MEDIC LOG Thu, 17 Mar 2016 06:30:25 GMT] Failed attempts: 0 > [MEDIC LOG Thu, 17 Mar 2016 06:30:25 GMT] FATAL: Could not find test results. > Check the output of medic-log to see if the app crashed before it could > upload them to couchdb. > program finished with exit code 1 > elapsedTime=1491.694117 -- 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-10898) 'Invalid Device State' when starting iOS simulator
[ https://issues.apache.org/jira/browse/CB-10898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15238361#comment-15238361 ] ASF GitHub Bot commented on CB-10898: - GitHub user omefire opened a pull request: https://github.com/apache/cordova-medic/pull/88 CB-10898 Kill simulator Xcode6 style You can merge this pull request into a Git repository by running: $ git pull https://github.com/omefire/cordova-medic CB-10898 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-medic/pull/88.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 #88 commit 5694808d6ba42c3124664720004c8226aa66729f Author: Omar MefireDate: 2016-04-13T01:04:26Z CB-10898 Kill simulator Xcode6 style > 'Invalid Device State' when starting iOS simulator > -- > > Key: CB-10898 > URL: https://issues.apache.org/jira/browse/CB-10898 > Project: Apache Cordova > Issue Type: Bug >Reporter: Omar Mefire >Assignee: Omar Mefire >Priority: Critical > Labels: cordova-ios, found-by-ci > > When trying to run the mobilespec app on the iOS simulator, an error: > 'Invalid Device State' is encountered. > Log: > https://ci.apache.org/builders/cordova-ios/builds/2076/steps/running-tests/logs/stdio > == > Results at > '/Users/buildbot/slaves/apache/cordova-ios/mobilespec/platforms/ios/build/device/mobilespec.ipa' > > [] Waiting up to 1 seconds for iOS device to be connected > No target specified for emulator. Deploying to iPhone-6s-Plus, 9.1 simulator > An error was encountered processing the command > (domain=com.apple.CoreSimulator.SimError, code=159): > Invalid device state > logPath: > /Users/buildbot/slaves/apache/cordova-ios/mobilespec/platforms/ios/cordova/console.log > [MEDIC LOG Thu, 17 Mar 2016 06:06:24 GMT] Finished waiting for run command > [MEDIC LOG Thu, 17 Mar 2016 06:06:24 GMT] started waiting for test results > [MEDIC LOG Thu, 17 Mar 2016 06:30:25 GMT] Finished polling for mobilespec > results. > [MEDIC LOG Thu, 17 Mar 2016 06:30:25 GMT] Results Found: false > [MEDIC LOG Thu, 17 Mar 2016 06:30:25 GMT] Total attempts: 144 > [MEDIC LOG Thu, 17 Mar 2016 06:30:25 GMT] Failed attempts: 0 > [MEDIC LOG Thu, 17 Mar 2016 06:30:25 GMT] FATAL: Could not find test results. > Check the output of medic-log to see if the app crashed before it could > upload them to couchdb. > program finished with exit code 1 > elapsedTime=1491.694117 -- 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-10898) 'Invalid Device State' when starting iOS simulator
[ https://issues.apache.org/jira/browse/CB-10898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15238350#comment-15238350 ] ASF GitHub Bot commented on CB-10898: - Github user omefire commented on the pull request: https://github.com/apache/cordova-medic/pull/86#issuecomment-209170685 @dblotsky yeah, might be a good idea to add both, since the former string handles Xcode 6 if someone were to be still using it. > 'Invalid Device State' when starting iOS simulator > -- > > Key: CB-10898 > URL: https://issues.apache.org/jira/browse/CB-10898 > Project: Apache Cordova > Issue Type: Bug >Reporter: Omar Mefire >Assignee: Omar Mefire >Priority: Critical > Labels: cordova-ios, found-by-ci > > When trying to run the mobilespec app on the iOS simulator, an error: > 'Invalid Device State' is encountered. > Log: > https://ci.apache.org/builders/cordova-ios/builds/2076/steps/running-tests/logs/stdio > == > Results at > '/Users/buildbot/slaves/apache/cordova-ios/mobilespec/platforms/ios/build/device/mobilespec.ipa' > > [] Waiting up to 1 seconds for iOS device to be connected > No target specified for emulator. Deploying to iPhone-6s-Plus, 9.1 simulator > An error was encountered processing the command > (domain=com.apple.CoreSimulator.SimError, code=159): > Invalid device state > logPath: > /Users/buildbot/slaves/apache/cordova-ios/mobilespec/platforms/ios/cordova/console.log > [MEDIC LOG Thu, 17 Mar 2016 06:06:24 GMT] Finished waiting for run command > [MEDIC LOG Thu, 17 Mar 2016 06:06:24 GMT] started waiting for test results > [MEDIC LOG Thu, 17 Mar 2016 06:30:25 GMT] Finished polling for mobilespec > results. > [MEDIC LOG Thu, 17 Mar 2016 06:30:25 GMT] Results Found: false > [MEDIC LOG Thu, 17 Mar 2016 06:30:25 GMT] Total attempts: 144 > [MEDIC LOG Thu, 17 Mar 2016 06:30:25 GMT] Failed attempts: 0 > [MEDIC LOG Thu, 17 Mar 2016 06:30:25 GMT] FATAL: Could not find test results. > Check the output of medic-log to see if the app crashed before it could > upload them to couchdb. > program finished with exit code 1 > elapsedTime=1491.694117 -- 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-10957) iOS release-mode app contains build config files
[ https://issues.apache.org/jira/browse/CB-10957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omar Mefire resolved CB-10957. -- Resolution: Fixed > iOS release-mode app contains build config files > > > Key: CB-10957 > URL: https://issues.apache.org/jira/browse/CB-10957 > Project: Apache Cordova > Issue Type: Bug > Components: iOS >Affects Versions: 4.1.0 > Environment: cordova-ios 4.1.0 > cordova CLI 6.0.0 > Mac OS 10.11.3 >Reporter: Jacob Weber >Assignee: Omar Mefire > Labels: triaged > > Create a new app, add the iOS platform, and run {{cordova build --device > --release}}. > The resulting .ipa file contains the following files: > {code} > build-debug.xcconfig > build-release.xcconfig > build.xcconfig > {code} > I don't think the final app should contain these build files, especially not > debug versions. -- 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-10873) "cordova-plugin-camera" 2.1.1 seem cause the app shut down after use the capture photo (when use encodingType: Camera.EncodingType.JPEG)
[ https://issues.apache.org/jira/browse/CB-10873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15238347#comment-15238347 ] ASF GitHub Bot commented on CB-10873: - Github user omefire commented on the pull request: https://github.com/apache/cordova-plugin-camera/pull/205#issuecomment-209169845 For more details, see: https://issues.apache.org/jira/browse/CB-10873 > "cordova-plugin-camera" 2.1.1 seem cause the app shut down after use the > capture photo (when use encodingType: Camera.EncodingType.JPEG) > > > Key: CB-10873 > URL: https://issues.apache.org/jira/browse/CB-10873 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Camera >Affects Versions: 2.1.1 > Environment: Cordova Cli-6.0 > Cordova-iOS 4.1.0 > cordova-plugin-camera 2.1.1 > cordova-plugin-wkwebview-engine 1.0.2 > ipad mini iOS 9.2.1 > my config.xml have these lines > > > value="files,files-external,documents,sdcard,cache,cache-external,root" /> > value="library,library-nosync,documents,documents-nosync,cache,bundle,root" /> >Reporter: Colin Bau >Assignee: Omar Mefire > Labels: iOS, triaged, wfc > > this is my full test code > = > navigator.camera.getPicture(cameraSuccess, cameraError, null); > function cameraSuccess() { alert("Camera success.") } > function cameraError(message) { alert('Failed because: ' + message); } > = > step1,I use "navigator.camera.getPicture" > step2,it will appear a camera interface and I press the take photo button > step3,click the "use the photo" button > step4,it will back to my original app,but after 1-2 seconds,shut down > immediately > Android have no this problem,and it will trigger the "cameraSuccess" callback -- 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-10873) "cordova-plugin-camera" 2.1.1 seem cause the app shut down after use the capture photo (when use encodingType: Camera.EncodingType.JPEG)
[ https://issues.apache.org/jira/browse/CB-10873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15238341#comment-15238341 ] ASF GitHub Bot commented on CB-10873: - Github user omefire commented on the pull request: https://github.com/apache/cordova-plugin-camera/pull/205#issuecomment-209168919 What happens is that when trying to write the image source, we do it with a null/nil variable ```self.data```: https://github.com/omefire/cordova-plugin-camera/blob/CB-10873/src/ios/CDVCamera.m#L669-L671 > "cordova-plugin-camera" 2.1.1 seem cause the app shut down after use the > capture photo (when use encodingType: Camera.EncodingType.JPEG) > > > Key: CB-10873 > URL: https://issues.apache.org/jira/browse/CB-10873 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Camera >Affects Versions: 2.1.1 > Environment: Cordova Cli-6.0 > Cordova-iOS 4.1.0 > cordova-plugin-camera 2.1.1 > cordova-plugin-wkwebview-engine 1.0.2 > ipad mini iOS 9.2.1 > my config.xml have these lines > > > value="files,files-external,documents,sdcard,cache,cache-external,root" /> > value="library,library-nosync,documents,documents-nosync,cache,bundle,root" /> >Reporter: Colin Bau >Assignee: Omar Mefire > Labels: iOS, triaged, wfc > > this is my full test code > = > navigator.camera.getPicture(cameraSuccess, cameraError, null); > function cameraSuccess() { alert("Camera success.") } > function cameraError(message) { alert('Failed because: ' + message); } > = > step1,I use "navigator.camera.getPicture" > step2,it will appear a camera interface and I press the take photo button > step3,click the "use the photo" button > step4,it will back to my original app,but after 1-2 seconds,shut down > immediately > Android have no this problem,and it will trigger the "cameraSuccess" callback -- 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-10873) "cordova-plugin-camera" 2.1.1 seem cause the app shut down after use the capture photo (when use encodingType: Camera.EncodingType.JPEG)
[ https://issues.apache.org/jira/browse/CB-10873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15238339#comment-15238339 ] ASF GitHub Bot commented on CB-10873: - GitHub user omefire opened a pull request: https://github.com/apache/cordova-plugin-camera/pull/205 CB-10873 Avoid crash due to usage of uninitialized variable when writ… …ing geolocation data to image destination You can merge this pull request into a Git repository by running: $ git pull https://github.com/omefire/cordova-plugin-camera CB-10873 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-plugin-camera/pull/205.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 #205 commit f16dbff7138bc235615c5539ae7e5f8e0968e681 Author: Omar MefireDate: 2016-04-13T00:46:42Z CB-10873 Avoid crash due to usage of uninitialized variable when writing geolocation data to image destination > "cordova-plugin-camera" 2.1.1 seem cause the app shut down after use the > capture photo (when use encodingType: Camera.EncodingType.JPEG) > > > Key: CB-10873 > URL: https://issues.apache.org/jira/browse/CB-10873 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Camera >Affects Versions: 2.1.1 > Environment: Cordova Cli-6.0 > Cordova-iOS 4.1.0 > cordova-plugin-camera 2.1.1 > cordova-plugin-wkwebview-engine 1.0.2 > ipad mini iOS 9.2.1 > my config.xml have these lines > > > value="files,files-external,documents,sdcard,cache,cache-external,root" /> > value="library,library-nosync,documents,documents-nosync,cache,bundle,root" /> >Reporter: Colin Bau >Assignee: Omar Mefire > Labels: iOS, triaged, wfc > > this is my full test code > = > navigator.camera.getPicture(cameraSuccess, cameraError, null); > function cameraSuccess() { alert("Camera success.") } > function cameraError(message) { alert('Failed because: ' + message); } > = > step1,I use "navigator.camera.getPicture" > step2,it will appear a camera interface and I press the take photo button > step3,click the "use the photo" button > step4,it will back to my original app,but after 1-2 seconds,shut down > immediately > Android have no this problem,and it will trigger the "cameraSuccess" callback -- 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-2083) Cordova for WP8 getPicture Leaves Photos in Camera Roll
[ https://issues.apache.org/jira/browse/CB-2083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15238318#comment-15238318 ] ASF GitHub Bot commented on CB-2083: Github user riknoll commented on a diff in the pull request: https://github.com/apache/cordova-plugin-camera/pull/203#discussion_r59477164 --- Diff: jsdoc2md/TEMPLATE.md --- @@ -203,3 +203,194 @@ Tizen only supports a `destinationType` of [web_activities]: https://hacks.mozilla.org/2013/01/introducing-web-activities/ [wp8_bug]: https://issues.apache.org/jira/browse/CB-2083 [msdn_wp8_docs]: http://msdn.microsoft.com/en-us/library/windowsphone/develop/hh394006.aspx + +## Sample: Take Pictures, Select Pictures from the Picture Library, and Get Thumbnails + +The Camera plugin allows you to do things like open the device's Camera app and take a picture, or open the file picker and select one. The code snippets in this section demonstrate different tasks including: + +* Open the Camera app and [take a Picture](#takePicture) +* Take a picture and [return thumbnails](#getThumbnails) (resized picture) +* Take a picture and [generate a FileEntry object](#convert) +* [Select a file](#selectFile) from the picture library +* Select a JPEG image and [return thumbnails](#getFileThumbnails) (resized image) +* Select an image and [generate a FileEntry object](#convert) + +## Take a Picture + +Before you can take a picture, you need to set some Camera plugin options to pass into the Camera plugin's `getPicture` function. Here is a common set of recommendations. In this example, you create the object that you will use for the Camera options, and set the `sourceType` dynamically to support both the Camera app and the file picker. + +```js +function setOptions(srcType) { +var options = { +// Some common settings are 20, 50, and 100 +quality: 50, +destinationType: Camera.DestinationType.FILE_URI, +// In this app, dynamically set the picture source, Camera or photo gallery +sourceType: srcType, +encodingType: Camera.EncodingType.JPEG, +mediaType: Camera.MediaType.PICTURE, +allowEdit: true, +correctOrientation: true //Corrects Android orientation quirks +} +return options; +} +``` + +Typically, you want to use a FILE_URI instead of a DATA_URL to avoid most memory issues. JPEG is the recommended encoding type for Android. + +You take a picture by passing in the options object to `getPicture`, which takes a CameraOptions object as the third argument. When you call `setOptions`, pass `Camera.PictureSourceType.CAMERA` as the picture source. + +```js +function openCamera(selection) { + +var srcType = Camera.PictureSourceType.CAMERA; +var options = setOptions(srcType); +var func = copyToFile; + +navigator.camera.getPicture(function cameraSuccess(imageUri) { + +displayImage(imageUri); +// You may choose to copy the picture, save it somewhere, or upload. +func(imageUri); + +}, function cameraError(error) { +console.debug("Unable to obtain picture: " + error, "app"); + +}, options); +} +``` + +Once you take the picture, you can display it or do something else. In this example, call the app's `displayImage` function from the preceding code. + +```js +function displayImage(imgUri) { + +var elem = document.getElementById('imageFile'); +elem.src = imgUri; +} +``` + +## Take a Picture and Return Thumbnails (Resize the Picture) + +To get smaller images, you can return a resized image by passing both `targetHeight` and `targetWidth` values with your CameraOptions object. In this example, you resize the returned image to fit in a 100px by 100px box (the aspect ratio is maintained, so 100px is either the height or width, whichever is greater in the source). + +```js +function openCamera(selection) { + +var srcType = Camera.PictureSourceType.CAMERA; +var options = setOptions(srcType); +var func = copyToFile; + +if (selection == "camera-thmb") { +options.targetHeight = 100; +options.targetWidth = 100; +} + +navigator.camera.getPicture(function cameraSuccess(imageUri) { + +// Do something + +}, function cameraError(error) { +console.debug("Unable to obtain picture: " + error, "app"); + +}, options); +} +``` + +## Select a File from the Picture Library + +When selecting a file using the file picker, you also need to set the CameraOptions object. In this example, set the
[jira] [Commented] (CB-2083) Cordova for WP8 getPicture Leaves Photos in Camera Roll
[ https://issues.apache.org/jira/browse/CB-2083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15238303#comment-15238303 ] ASF GitHub Bot commented on CB-2083: Github user riknoll commented on a diff in the pull request: https://github.com/apache/cordova-plugin-camera/pull/203#discussion_r59476286 --- Diff: jsdoc2md/TEMPLATE.md --- @@ -203,3 +203,194 @@ Tizen only supports a `destinationType` of [web_activities]: https://hacks.mozilla.org/2013/01/introducing-web-activities/ [wp8_bug]: https://issues.apache.org/jira/browse/CB-2083 [msdn_wp8_docs]: http://msdn.microsoft.com/en-us/library/windowsphone/develop/hh394006.aspx + +## Sample: Take Pictures, Select Pictures from the Picture Library, and Get Thumbnails + +The Camera plugin allows you to do things like open the device's Camera app and take a picture, or open the file picker and select one. The code snippets in this section demonstrate different tasks including: + +* Open the Camera app and [take a Picture](#takePicture) +* Take a picture and [return thumbnails](#getThumbnails) (resized picture) +* Take a picture and [generate a FileEntry object](#convert) +* [Select a file](#selectFile) from the picture library +* Select a JPEG image and [return thumbnails](#getFileThumbnails) (resized image) +* Select an image and [generate a FileEntry object](#convert) + +## Take a Picture + +Before you can take a picture, you need to set some Camera plugin options to pass into the Camera plugin's `getPicture` function. Here is a common set of recommendations. In this example, you create the object that you will use for the Camera options, and set the `sourceType` dynamically to support both the Camera app and the file picker. + +```js +function setOptions(srcType) { +var options = { +// Some common settings are 20, 50, and 100 +quality: 50, +destinationType: Camera.DestinationType.FILE_URI, +// In this app, dynamically set the picture source, Camera or photo gallery +sourceType: srcType, +encodingType: Camera.EncodingType.JPEG, +mediaType: Camera.MediaType.PICTURE, +allowEdit: true, +correctOrientation: true //Corrects Android orientation quirks +} +return options; +} +``` + +Typically, you want to use a FILE_URI instead of a DATA_URL to avoid most memory issues. JPEG is the recommended encoding type for Android. + +You take a picture by passing in the options object to `getPicture`, which takes a CameraOptions object as the third argument. When you call `setOptions`, pass `Camera.PictureSourceType.CAMERA` as the picture source. + +```js +function openCamera(selection) { + +var srcType = Camera.PictureSourceType.CAMERA; +var options = setOptions(srcType); +var func = copyToFile; + +navigator.camera.getPicture(function cameraSuccess(imageUri) { + +displayImage(imageUri); +// You may choose to copy the picture, save it somewhere, or upload. +func(imageUri); + +}, function cameraError(error) { +console.debug("Unable to obtain picture: " + error, "app"); + +}, options); +} +``` + +Once you take the picture, you can display it or do something else. In this example, call the app's `displayImage` function from the preceding code. + +```js +function displayImage(imgUri) { + +var elem = document.getElementById('imageFile'); +elem.src = imgUri; +} +``` + +## Take a Picture and Return Thumbnails (Resize the Picture) + +To get smaller images, you can return a resized image by passing both `targetHeight` and `targetWidth` values with your CameraOptions object. In this example, you resize the returned image to fit in a 100px by 100px box (the aspect ratio is maintained, so 100px is either the height or width, whichever is greater in the source). + +```js +function openCamera(selection) { + +var srcType = Camera.PictureSourceType.CAMERA; +var options = setOptions(srcType); +var func = copyToFile; + +if (selection == "camera-thmb") { +options.targetHeight = 100; +options.targetWidth = 100; +} + +navigator.camera.getPicture(function cameraSuccess(imageUri) { + +// Do something + +}, function cameraError(error) { +console.debug("Unable to obtain picture: " + error, "app"); + +}, options); +} +``` + +## Select a File from the Picture Library + +When selecting a file using the file picker, you also need to set the CameraOptions object. In this example, set the
[jira] [Commented] (CB-2083) Cordova for WP8 getPicture Leaves Photos in Camera Roll
[ https://issues.apache.org/jira/browse/CB-2083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15238298#comment-15238298 ] ASF GitHub Bot commented on CB-2083: Github user riknoll commented on a diff in the pull request: https://github.com/apache/cordova-plugin-camera/pull/203#discussion_r59475889 --- Diff: jsdoc2md/TEMPLATE.md --- @@ -203,3 +203,194 @@ Tizen only supports a `destinationType` of [web_activities]: https://hacks.mozilla.org/2013/01/introducing-web-activities/ [wp8_bug]: https://issues.apache.org/jira/browse/CB-2083 [msdn_wp8_docs]: http://msdn.microsoft.com/en-us/library/windowsphone/develop/hh394006.aspx + +## Sample: Take Pictures, Select Pictures from the Picture Library, and Get Thumbnails + +The Camera plugin allows you to do things like open the device's Camera app and take a picture, or open the file picker and select one. The code snippets in this section demonstrate different tasks including: + +* Open the Camera app and [take a Picture](#takePicture) +* Take a picture and [return thumbnails](#getThumbnails) (resized picture) +* Take a picture and [generate a FileEntry object](#convert) +* [Select a file](#selectFile) from the picture library +* Select a JPEG image and [return thumbnails](#getFileThumbnails) (resized image) +* Select an image and [generate a FileEntry object](#convert) + +## Take a Picture + +Before you can take a picture, you need to set some Camera plugin options to pass into the Camera plugin's `getPicture` function. Here is a common set of recommendations. In this example, you create the object that you will use for the Camera options, and set the `sourceType` dynamically to support both the Camera app and the file picker. + +```js +function setOptions(srcType) { +var options = { +// Some common settings are 20, 50, and 100 +quality: 50, +destinationType: Camera.DestinationType.FILE_URI, +// In this app, dynamically set the picture source, Camera or photo gallery +sourceType: srcType, +encodingType: Camera.EncodingType.JPEG, +mediaType: Camera.MediaType.PICTURE, +allowEdit: true, +correctOrientation: true //Corrects Android orientation quirks +} +return options; +} +``` + +Typically, you want to use a FILE_URI instead of a DATA_URL to avoid most memory issues. JPEG is the recommended encoding type for Android. + +You take a picture by passing in the options object to `getPicture`, which takes a CameraOptions object as the third argument. When you call `setOptions`, pass `Camera.PictureSourceType.CAMERA` as the picture source. + +```js +function openCamera(selection) { + +var srcType = Camera.PictureSourceType.CAMERA; +var options = setOptions(srcType); +var func = copyToFile; + +navigator.camera.getPicture(function cameraSuccess(imageUri) { + +displayImage(imageUri); +// You may choose to copy the picture, save it somewhere, or upload. +func(imageUri); + +}, function cameraError(error) { +console.debug("Unable to obtain picture: " + error, "app"); + +}, options); +} +``` + +Once you take the picture, you can display it or do something else. In this example, call the app's `displayImage` function from the preceding code. + +```js +function displayImage(imgUri) { + +var elem = document.getElementById('imageFile'); +elem.src = imgUri; +} +``` + +## Take a Picture and Return Thumbnails (Resize the Picture) + +To get smaller images, you can return a resized image by passing both `targetHeight` and `targetWidth` values with your CameraOptions object. In this example, you resize the returned image to fit in a 100px by 100px box (the aspect ratio is maintained, so 100px is either the height or width, whichever is greater in the source). + +```js +function openCamera(selection) { + +var srcType = Camera.PictureSourceType.CAMERA; +var options = setOptions(srcType); +var func = copyToFile; + +if (selection == "camera-thmb") { +options.targetHeight = 100; +options.targetWidth = 100; +} + +navigator.camera.getPicture(function cameraSuccess(imageUri) { + +// Do something + +}, function cameraError(error) { +console.debug("Unable to obtain picture: " + error, "app"); + +}, options); +} +``` + +## Select a File from the Picture Library + +When selecting a file using the file picker, you also need to set the CameraOptions object. In this example, set the
[jira] [Commented] (CB-10986) Unable to install npm scoped plugin with cordova-cli@6.1.0
[ https://issues.apache.org/jira/browse/CB-10986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15238246#comment-15238246 ] ASF GitHub Bot commented on CB-10986: - Github user riknoll commented on the pull request: https://github.com/apache/cordova-lib/pull/425#issuecomment-209148999 @vladimir-kotikov updated to address feedback > Unable to install npm scoped plugin with cordova-cli@6.1.0 > -- > > Key: CB-10986 > URL: https://issues.apache.org/jira/browse/CB-10986 > Project: Apache Cordova > Issue Type: Bug > Components: CordovaLib >Affects Versions: 6.1.0 >Reporter: Darryl Pogue >Assignee: Richard B Knoll > Labels: regression, reproduced, triaged > > {code} > $ cordova create MyProject > $ cd ./MyProject > $ cordova platform add android > $ cordova plugin add @dpogue/cordova-plugin-crosswalk-webview > Error: Cannot find plugin.xml for plugin 'plugins'. Please try adding it > again. > {code} > This works as expected with cordova@6.0.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Comment Edited] (CB-10873) "cordova-plugin-camera" 2.1.1 seem cause the app shut down after use the capture photo (when use encodingType: Camera.EncodingType.JPEG)
[ https://issues.apache.org/jira/browse/CB-10873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15238074#comment-15238074 ] Omar Mefire edited comment on CB-10873 at 4/12/16 10:00 PM: can confirm that this issue happens only when I have the following preference in my config.xml: was (Author: omefire): can confirm that this issue happen only when I have the following preference in my config.xml: > "cordova-plugin-camera" 2.1.1 seem cause the app shut down after use the > capture photo (when use encodingType: Camera.EncodingType.JPEG) > > > Key: CB-10873 > URL: https://issues.apache.org/jira/browse/CB-10873 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Camera >Affects Versions: 2.1.1 > Environment: Cordova Cli-6.0 > Cordova-iOS 4.1.0 > cordova-plugin-camera 2.1.1 > cordova-plugin-wkwebview-engine 1.0.2 > ipad mini iOS 9.2.1 > my config.xml have these lines > > > value="files,files-external,documents,sdcard,cache,cache-external,root" /> > value="library,library-nosync,documents,documents-nosync,cache,bundle,root" /> >Reporter: Colin Bau >Assignee: Omar Mefire > Labels: iOS, triaged, wfc > > this is my full test code > = > navigator.camera.getPicture(cameraSuccess, cameraError, null); > function cameraSuccess() { alert("Camera success.") } > function cameraError(message) { alert('Failed because: ' + message); } > = > step1,I use "navigator.camera.getPicture" > step2,it will appear a camera interface and I press the take photo button > step3,click the "use the photo" button > step4,it will back to my original app,but after 1-2 seconds,shut down > immediately > Android have no this problem,and it will trigger the "cameraSuccess" callback -- 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-10873) "cordova-plugin-camera" 2.1.1 seem cause the app shut down after use the capture photo (when use encodingType: Camera.EncodingType.JPEG)
[ https://issues.apache.org/jira/browse/CB-10873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15238074#comment-15238074 ] Omar Mefire commented on CB-10873: -- can confirm that this issue happen only when I have the following preference in my config.xml: > "cordova-plugin-camera" 2.1.1 seem cause the app shut down after use the > capture photo (when use encodingType: Camera.EncodingType.JPEG) > > > Key: CB-10873 > URL: https://issues.apache.org/jira/browse/CB-10873 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Camera >Affects Versions: 2.1.1 > Environment: Cordova Cli-6.0 > Cordova-iOS 4.1.0 > cordova-plugin-camera 2.1.1 > cordova-plugin-wkwebview-engine 1.0.2 > ipad mini iOS 9.2.1 > my config.xml have these lines > > > value="files,files-external,documents,sdcard,cache,cache-external,root" /> > value="library,library-nosync,documents,documents-nosync,cache,bundle,root" /> >Reporter: Colin Bau >Assignee: Omar Mefire > Labels: iOS, triaged, wfc > > this is my full test code > = > navigator.camera.getPicture(cameraSuccess, cameraError, null); > function cameraSuccess() { alert("Camera success.") } > function cameraError(message) { alert('Failed because: ' + message); } > = > step1,I use "navigator.camera.getPicture" > step2,it will appear a camera interface and I press the take photo button > step3,click the "use the photo" button > step4,it will back to my original app,but after 1-2 seconds,shut down > immediately > Android have no this problem,and it will trigger the "cameraSuccess" callback -- 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-11001) Incorrect docs - "FullScreen" config.xml preference only applies to Android
[ https://issues.apache.org/jira/browse/CB-11001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15238068#comment-15238068 ] ASF GitHub Bot commented on CB-11001: - Github user nikhilkh commented on the pull request: https://github.com/apache/cordova-docs/pull/576#issuecomment-209119380 LGTM > Incorrect docs - "FullScreen" config.xml preference only applies to Android > --- > > Key: CB-11001 > URL: https://issues.apache.org/jira/browse/CB-11001 > Project: Apache Cordova > Issue Type: Bug > Components: Docs >Reporter: Jerroyd Moore >Assignee: Sergey Shakhnazarov > Labels: triaged > > The is ignored when I add it > and build for 8.1-phone. > {code} > $ cordova -v > 5.4.1 > $ cordova create foo > $ cd foo > $ cordova platform add windows > $ cordova prepare windows > $ cd platforms/windows/cordova > $ build.bat -r --appx=8.1-phone > {code} > Running it on a windows phone 8.1, the status bar is hidden. -- 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-11064) Update new engine package.json docs
[ https://issues.apache.org/jira/browse/CB-11064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15238059#comment-15238059 ] ASF subversion and git services commented on CB-11064: -- Commit cc773d2e74d4548ec4c32da204abb9ece7dbcb16 in cordova-docs's branch refs/heads/master from Richard Knoll [ https://git-wip-us.apache.org/repos/asf?p=cordova-docs.git;h=cc773d2 ] CB-11064: Adding a note to the engine tag spec and fixing a header This closes #577 > Update new engine package.json docs > --- > > Key: CB-11064 > URL: https://issues.apache.org/jira/browse/CB-11064 > Project: Apache Cordova > Issue Type: Bug > Components: Docs >Reporter: Richard B Knoll >Assignee: Richard B Knoll > Labels: triaged > > Update engine docs in plugin.xml to mention it's being deprecated eventually > and fix heading in plugin guide -- 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-11064) Update new engine package.json docs
[ https://issues.apache.org/jira/browse/CB-11064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15238060#comment-15238060 ] ASF GitHub Bot commented on CB-11064: - Github user asfgit closed the pull request at: https://github.com/apache/cordova-docs/pull/577 > Update new engine package.json docs > --- > > Key: CB-11064 > URL: https://issues.apache.org/jira/browse/CB-11064 > Project: Apache Cordova > Issue Type: Bug > Components: Docs >Reporter: Richard B Knoll >Assignee: Richard B Knoll > Labels: triaged > > Update engine docs in plugin.xml to mention it's being deprecated eventually > and fix heading in plugin guide -- 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] [Closed] (CB-11064) Update new engine package.json docs
[ https://issues.apache.org/jira/browse/CB-11064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard B Knoll closed CB-11064. Resolution: Fixed > Update new engine package.json docs > --- > > Key: CB-11064 > URL: https://issues.apache.org/jira/browse/CB-11064 > Project: Apache Cordova > Issue Type: Bug > Components: Docs >Reporter: Richard B Knoll >Assignee: Richard B Knoll > Labels: triaged > > Update engine docs in plugin.xml to mention it's being deprecated eventually > and fix heading in plugin guide -- 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-11064) Update new engine package.json docs
[ https://issues.apache.org/jira/browse/CB-11064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15238055#comment-15238055 ] ASF GitHub Bot commented on CB-11064: - Github user nikhilkh commented on the pull request: https://github.com/apache/cordova-docs/pull/577#issuecomment-209116138 LGTM > Update new engine package.json docs > --- > > Key: CB-11064 > URL: https://issues.apache.org/jira/browse/CB-11064 > Project: Apache Cordova > Issue Type: Bug > Components: Docs >Reporter: Richard B Knoll >Assignee: Richard B Knoll > Labels: triaged > > Update engine docs in plugin.xml to mention it's being deprecated eventually > and fix heading in plugin guide -- 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-11042) Add cordova run option to skip prepare
[ https://issues.apache.org/jira/browse/CB-11042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15237979#comment-15237979 ] Jason Ginchereau commented on CB-11042: --- With a small project, skipping the prepare step makes launching the app in VS about 1s faster (7s -> 6s) on an average-spec dev PC. It will save even more time with a larger project that has many HTML/JS/resource files that would be re-copied during the prepare step. This is one of a few things we're working on to streamline the dev inner loop of Cordova projects in VS. (Most others don't require changes to the Cordova runtime.) Saving seconds here and there can really add up. > Add cordova run option to skip prepare > -- > > Key: CB-11042 > URL: https://issues.apache.org/jira/browse/CB-11042 > Project: Apache Cordova > Issue Type: Improvement > Components: CordovaLib >Reporter: Jason Ginchereau >Assignee: Jason Ginchereau > > The 'cordova run' command currently always does a "prepare" operation for the > target platform before launching the app. There is a --nobuild option (to > skip building the native project), but there isn't a --noprepare option. > This option will be helpful to optimize build-and-run scenarios in the Visual > Studio tools for Cordova. VS always ensures the project is fully prepared and > built before trying to launch. So by the time it calls 'cordova run' there is > no need to do the prepare step, and it just causes the developer to wait > extra seconds for every iteration of the inner loop. -- 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-11042) Add cordova run option to skip prepare
[ https://issues.apache.org/jira/browse/CB-11042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15237971#comment-15237971 ] ASF GitHub Bot commented on CB-11042: - GitHub user jasongin opened a pull request: https://github.com/apache/cordova-cli/pull/244 CB-11042: Add cordova run option to skip prepare Parse and document a --noprepare option for the cordova run command. See https://github.com/apache/cordova-lib/pull/426 for the corresponding cordova-lib change that skips the prepare step if the noprepare option is specified. You can merge this pull request into a Git repository by running: $ git pull https://github.com/jasongin/cordova-cli CB-11042 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-cli/pull/244.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 #244 commit 053bbdf841997276112d1675913d7871792f3469 Author: Jason GinchereauDate: 2016-04-12T20:59:09Z CB-11042: Add cordova run option to skip prepare > Add cordova run option to skip prepare > -- > > Key: CB-11042 > URL: https://issues.apache.org/jira/browse/CB-11042 > Project: Apache Cordova > Issue Type: Improvement > Components: CordovaLib >Reporter: Jason Ginchereau >Assignee: Jason Ginchereau > > The 'cordova run' command currently always does a "prepare" operation for the > target platform before launching the app. There is a --nobuild option (to > skip building the native project), but there isn't a --noprepare option. > This option will be helpful to optimize build-and-run scenarios in the Visual > Studio tools for Cordova. VS always ensures the project is fully prepared and > built before trying to launch. So by the time it calls 'cordova run' there is > no need to do the prepare step, and it just causes the developer to wait > extra seconds for every iteration of the inner loop. -- 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-11042) Add cordova run option to skip prepare
[ https://issues.apache.org/jira/browse/CB-11042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15237966#comment-15237966 ] ASF GitHub Bot commented on CB-11042: - GitHub user jasongin opened a pull request: https://github.com/apache/cordova-lib/pull/426 CB-11042: Add cordova run option to skip prepare I'm also submitting a PR for the cordova-cli repo to parse and document the --noprepare option. You can merge this pull request into a Git repository by running: $ git pull https://github.com/jasongin/cordova-lib CB-11042 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-lib/pull/426.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 #426 commit 8b60d5f6e718d0e21ae5c39f5564e90dffda2bb0 Author: Jason GinchereauDate: 2016-04-12T20:57:06Z CB-11042: Add cordova run option to skip prepare > Add cordova run option to skip prepare > -- > > Key: CB-11042 > URL: https://issues.apache.org/jira/browse/CB-11042 > Project: Apache Cordova > Issue Type: Improvement > Components: CordovaLib >Reporter: Jason Ginchereau >Assignee: Jason Ginchereau > > The 'cordova run' command currently always does a "prepare" operation for the > target platform before launching the app. There is a --nobuild option (to > skip building the native project), but there isn't a --noprepare option. > This option will be helpful to optimize build-and-run scenarios in the Visual > Studio tools for Cordova. VS always ensures the project is fully prepared and > built before trying to launch. So by the time it calls 'cordova run' there is > no need to do the prepare step, and it just causes the developer to wait > extra seconds for every iteration of the inner loop. -- 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-10898) 'Invalid Device State' when starting iOS simulator
[ https://issues.apache.org/jira/browse/CB-10898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15237961#comment-15237961 ] ASF GitHub Bot commented on CB-10898: - Github user dblotsky commented on the pull request: https://github.com/apache/cordova-medic/pull/86#issuecomment-209098826 @omefire please add both `"iOS Simulator"` and `"Simulator"` to that array. > 'Invalid Device State' when starting iOS simulator > -- > > Key: CB-10898 > URL: https://issues.apache.org/jira/browse/CB-10898 > Project: Apache Cordova > Issue Type: Bug >Reporter: Omar Mefire >Assignee: Omar Mefire >Priority: Critical > Labels: cordova-ios, found-by-ci > > When trying to run the mobilespec app on the iOS simulator, an error: > 'Invalid Device State' is encountered. > Log: > https://ci.apache.org/builders/cordova-ios/builds/2076/steps/running-tests/logs/stdio > == > Results at > '/Users/buildbot/slaves/apache/cordova-ios/mobilespec/platforms/ios/build/device/mobilespec.ipa' > > [] Waiting up to 1 seconds for iOS device to be connected > No target specified for emulator. Deploying to iPhone-6s-Plus, 9.1 simulator > An error was encountered processing the command > (domain=com.apple.CoreSimulator.SimError, code=159): > Invalid device state > logPath: > /Users/buildbot/slaves/apache/cordova-ios/mobilespec/platforms/ios/cordova/console.log > [MEDIC LOG Thu, 17 Mar 2016 06:06:24 GMT] Finished waiting for run command > [MEDIC LOG Thu, 17 Mar 2016 06:06:24 GMT] started waiting for test results > [MEDIC LOG Thu, 17 Mar 2016 06:30:25 GMT] Finished polling for mobilespec > results. > [MEDIC LOG Thu, 17 Mar 2016 06:30:25 GMT] Results Found: false > [MEDIC LOG Thu, 17 Mar 2016 06:30:25 GMT] Total attempts: 144 > [MEDIC LOG Thu, 17 Mar 2016 06:30:25 GMT] Failed attempts: 0 > [MEDIC LOG Thu, 17 Mar 2016 06:30:25 GMT] FATAL: Could not find test results. > Check the output of medic-log to see if the app crashed before it could > upload them to couchdb. > program finished with exit code 1 > elapsedTime=1491.694117 -- 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-10937) Icons are more than stretched since cordova-android 5.1.0
[ https://issues.apache.org/jira/browse/CB-10937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15237912#comment-15237912 ] Alexis Kofman commented on CB-10937: Hello [~nux], Even if a plugin is not released yet, it is possible to add a dependency from a git sha1 in your config.xml file : {code:xml} https://github.com/apache/cordova-plugin-inappbrowser#c6ff803113eb71c39bf41a774204efdebcce0377; /> {code} Hope it helps. > Icons are more than stretched since cordova-android 5.1.0 > - > > Key: CB-10937 > URL: https://issues.apache.org/jira/browse/CB-10937 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin InAppBrowser > Environment: android >Reporter: Alexis Kofman > Labels: android, inappbrowser > > Since cordova-android@5.0.1 and more especially this commit > https://github.com/apache/cordova-android/commit/73fd9e4dfa5dffde2eb14ebd6c736ca462d1e29f, > the theme has been updated. > The inappbrowser plugin use images as background property of Button views. > So, depending on default margin values in the Theme, background images can be > stretched. > A fix could be to use ImageButton views instead and chose a scaleType if > needed. > Here is what we have today using a version of cordova-android >= 5.1.0 : > !https://cloud.githubusercontent.com/assets/579922/13982920/e81236c8-f0ec-11e5-9eeb-f969cba3b375.png|width=100%! -- 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-6498) Misleading documentation in Android Quirks
[ https://issues.apache.org/jira/browse/CB-6498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15237778#comment-15237778 ] ASF GitHub Bot commented on CB-6498: GitHub user daserge opened a pull request: https://github.com/apache/cordova-plugin-splashscreen/pull/97 CB-6498 Misleading documentation in Android Quirks [Jira issue](https://issues.apache.org/jira/browse/CB-6498) This is constantly causing confusion: http://stackoverflow.com/questions/36575576/cordova-splash-screen-plugin http://stackoverflow.com/questions/25513126/cordova-3-4-splashscreen-not-working?rq=1 http://stackoverflow.com/questions/36181366/splashscreen-doesnt-work-with-cordova-6-0-0 You can merge this pull request into a Git repository by running: $ git pull https://github.com/MSOpenTech/cordova-plugin-splashscreen CB-6498 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-plugin-splashscreen/pull/97.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 #97 commit 91c7e985aeb885a75b6e0222a64c23e5af7c5baa Author: dasergeDate: 2016-04-12T18:55:50Z CB-6498 Misleading documentation in Android Quirks > Misleading documentation in Android Quirks > -- > > Key: CB-6498 > URL: https://issues.apache.org/jira/browse/CB-6498 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin SplashScreen >Reporter: Kuan Yi Ming > Attachments: 0001-Fixed-doccument-issue.patch > > > As per the docs under the Android Quirks section: > {code} > In your config.xml, you need to add the following preference > `` > Where foo is the name of the splashscreen file. Preferably a 9 patch file. > Make sure to add your splashcreen files to your res/xml directory under the > appropriate folders. > {code} > The documentation implies the splashscreen files go into the res/xml > directory, but they actually go into the res/drawable folders instead. The > file name is also optional (if not present, it defaults to splash.png) but > this is not mentioned here. -- 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-11043) Android App crashes while trying to save contact with phonenumbers array with deleted values
[ https://issues.apache.org/jira/browse/CB-11043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15237742#comment-15237742 ] ASF GitHub Bot commented on CB-11043: - Github user asfgit closed the pull request at: https://github.com/apache/cordova-plugin-contacts/pull/121 > Android App crashes while trying to save contact with phonenumbers array with > deleted values > > > Key: CB-11043 > URL: https://issues.apache.org/jira/browse/CB-11043 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Contacts >Reporter: Sarangan Rajamanickam >Assignee: Sarangan Rajamanickam > Labels: Android, triaged, wfc > -- 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-11043) Android App crashes while trying to save contact with phonenumbers array with deleted values
[ https://issues.apache.org/jira/browse/CB-11043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15237740#comment-15237740 ] ASF subversion and git services commented on CB-11043: -- Commit d7dd9378fd87d4a6689c7fef57a48a9e9c0a23ba in cordova-plugin-contacts's branch refs/heads/master from [~sarangan12] [ https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-contacts.git;h=d7dd937 ] CB-11043: Android App crashes while trying to save contact with phone numbers array with deleted values This closes #121 > Android App crashes while trying to save contact with phonenumbers array with > deleted values > > > Key: CB-11043 > URL: https://issues.apache.org/jira/browse/CB-11043 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Contacts >Reporter: Sarangan Rajamanickam >Assignee: Sarangan Rajamanickam > Labels: Android, triaged, wfc > -- 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-11070) Document SplashScreenBackgroundColor
[ https://issues.apache.org/jira/browse/CB-11070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15237736#comment-15237736 ] ASF GitHub Bot commented on CB-11070: - GitHub user daserge opened a pull request: https://github.com/apache/cordova-docs/pull/578 CB-11070 Document SplashScreenBackgroundColor Also documented Windows-specific transparent BackgroundColor [Jira issue](https://issues.apache.org/jira/browse/CB-11070) You can merge this pull request into a Git repository by running: $ git pull https://github.com/MSOpenTech/cordova-docs CB-11070 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-docs/pull/578.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 #578 commit 086241aa2308d7476c5456dc7a49f58fb1be3f9a Author: dasergeDate: 2016-04-12T18:34:33Z CB-11070 Document SplashScreenBackgroundColor Also documented Windows-specific transparent BackgroundColor > Document SplashScreenBackgroundColor > > > Key: CB-11070 > URL: https://issues.apache.org/jira/browse/CB-11070 > Project: Apache Cordova > Issue Type: Bug > Components: Docs >Reporter: Sergey Shakhnazarov >Assignee: Sergey Shakhnazarov > -- 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-10951) Android audio focus should be respected
[ https://issues.apache.org/jira/browse/CB-10951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser resolved CB-10951. - Resolution: Fixed Tested and merged! > Android audio focus should be respected > --- > > Key: CB-10951 > URL: https://issues.apache.org/jira/browse/CB-10951 > Project: Apache Cordova > Issue Type: Improvement > Components: Android, Plugin Media >Affects Versions: Master > Environment: Android >Reporter: Fabrice Lebas >Assignee: Joe Bowser > Original Estimate: 48h > Remaining Estimate: 48h > > Playing a media will not stop other applications that are already playing a > media. Other applications playing a media will not cause cordova to stop > playing its media. This is because the audio focus logic is not implemented. > This results in both applications playing audio at the same time. Although > this behaviour is valid (sound effects, notifications) this is not the > expected behavior for most applications playing a media. -- 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-9701) Audio player keeps playing when an incoming call comes in on Marshmallow
[ https://issues.apache.org/jira/browse/CB-9701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser resolved CB-9701. Resolution: Duplicate > Audio player keeps playing when an incoming call comes in on Marshmallow > > > Key: CB-9701 > URL: https://issues.apache.org/jira/browse/CB-9701 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Media >Reporter: Joe Bowser >Assignee: Joe Bowser > Labels: Android > > This is caused by the use of phone state on earlier versions of Android. > However, it's possible to have the same behaviour without listening to the > phone state, and the plugin should probably be updated. > http://developer.android.com/training/managing-audio/audio-focus.html -- 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-9701) Audio player keeps playing when an incoming call comes in on Marshmallow
[ https://issues.apache.org/jira/browse/CB-9701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15237728#comment-15237728 ] Joe Bowser commented on CB-9701: Duplicate of CB-10951 > Audio player keeps playing when an incoming call comes in on Marshmallow > > > Key: CB-9701 > URL: https://issues.apache.org/jira/browse/CB-9701 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Media >Reporter: Joe Bowser >Assignee: Joe Bowser > Labels: Android > > This is caused by the use of phone state on earlier versions of Android. > However, it's possible to have the same behaviour without listening to the > phone state, and the plugin should probably be updated. > http://developer.android.com/training/managing-audio/audio-focus.html -- 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-10951) Android audio focus should be respected
[ https://issues.apache.org/jira/browse/CB-10951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15237722#comment-15237722 ] ASF GitHub Bot commented on CB-10951: - Github user asfgit closed the pull request at: https://github.com/apache/cordova-plugin-media/pull/88 > Android audio focus should be respected > --- > > Key: CB-10951 > URL: https://issues.apache.org/jira/browse/CB-10951 > Project: Apache Cordova > Issue Type: Improvement > Components: Android, Plugin Media >Affects Versions: Master > Environment: Android >Reporter: Fabrice Lebas >Assignee: Joe Bowser > Original Estimate: 48h > Remaining Estimate: 48h > > Playing a media will not stop other applications that are already playing a > media. Other applications playing a media will not cause cordova to stop > playing its media. This is because the audio focus logic is not implemented. > This results in both applications playing audio at the same time. Although > this behaviour is valid (sound effects, notifications) this is not the > expected behavior for most applications playing a media. -- 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-10898) 'Invalid Device State' when starting iOS simulator
[ https://issues.apache.org/jira/browse/CB-10898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omar Mefire resolved CB-10898. -- Resolution: Fixed > 'Invalid Device State' when starting iOS simulator > -- > > Key: CB-10898 > URL: https://issues.apache.org/jira/browse/CB-10898 > Project: Apache Cordova > Issue Type: Bug >Reporter: Omar Mefire >Assignee: Omar Mefire >Priority: Critical > Labels: cordova-ios, found-by-ci > > When trying to run the mobilespec app on the iOS simulator, an error: > 'Invalid Device State' is encountered. > Log: > https://ci.apache.org/builders/cordova-ios/builds/2076/steps/running-tests/logs/stdio > == > Results at > '/Users/buildbot/slaves/apache/cordova-ios/mobilespec/platforms/ios/build/device/mobilespec.ipa' > > [] Waiting up to 1 seconds for iOS device to be connected > No target specified for emulator. Deploying to iPhone-6s-Plus, 9.1 simulator > An error was encountered processing the command > (domain=com.apple.CoreSimulator.SimError, code=159): > Invalid device state > logPath: > /Users/buildbot/slaves/apache/cordova-ios/mobilespec/platforms/ios/cordova/console.log > [MEDIC LOG Thu, 17 Mar 2016 06:06:24 GMT] Finished waiting for run command > [MEDIC LOG Thu, 17 Mar 2016 06:06:24 GMT] started waiting for test results > [MEDIC LOG Thu, 17 Mar 2016 06:30:25 GMT] Finished polling for mobilespec > results. > [MEDIC LOG Thu, 17 Mar 2016 06:30:25 GMT] Results Found: false > [MEDIC LOG Thu, 17 Mar 2016 06:30:25 GMT] Total attempts: 144 > [MEDIC LOG Thu, 17 Mar 2016 06:30:25 GMT] Failed attempts: 0 > [MEDIC LOG Thu, 17 Mar 2016 06:30:25 GMT] FATAL: Could not find test results. > Check the output of medic-log to see if the app crashed before it could > upload them to couchdb. > program finished with exit code 1 > elapsedTime=1491.694117 -- 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-8383) pause event don't fire when 'KeepRunning' is false
[ https://issues.apache.org/jira/browse/CB-8383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15237705#comment-15237705 ] Joe Bowser commented on CB-8383: I'm sure in theory we could, but leaving an app and coming back to it is tricky to test and I'm not sure how to write the JUnit test for it. > pause event don't fire when 'KeepRunning' is false > -- > > Key: CB-8383 > URL: https://issues.apache.org/jira/browse/CB-8383 > Project: Apache Cordova > Issue Type: Bug > Components: Android >Affects Versions: Master, 3.5.0, 4.0.0, 4.1.3 > Environment: Mac osx 10.9 >Reporter: hugefactory > Original Estimate: 1h > Remaining Estimate: 1h > > Under Android, when a project use 'KeepRunning=false' in the config.xml file, > the 'pause' event in javascript don't fire when application go to background. > Next, 'pause' event fire when 'resume' is call and when the application > resume. > The problem is in 'CordovaWebView.java' in the 'handlePause' method : > public void handlePause(boolean keepRunning) { > LOG.d(TAG, "Handle the pause"); > // Send pause event to JavaScript > > this.loadUrl("javascript:try{cordova.fireDocumentEvent('pause');}catch(e){console.log('exception > firing pause event from native');};"); > // Forward to plugins > if (this.pluginManager != null) { > this.pluginManager.onPause(keepRunning); > } > // If app doesn't want to run in background > if (!keepRunning) { > // Pause JavaScript timers (including setInterval) > this.pauseTimers(); > } > paused = true; > > } > As you can see, 'pauseTimers()' is call immediatly when we choose > 'KeepRunning' false. > According to the Android documentation, 'pauseTimer()' stop all javascript > activitythen the 'pause' javascript callback is not execute (it's execute > after, when the 'resumeTimers()' is call and the application resume. > I suggest to delay the 'pauseTimers()' for 1 or 2 sec. Then the javascript > 'pause' can execute before the application is really stop : > //OLD > //this.pauseTimers(); > //NEW > final Handler handler = new Handler(); > handler.postDelayed(new Runnable() { > @Override > public void run() { > LOG.d(TAG, "Handle the pauseTimers"); > pauseTimers(); > } > }, 1000); > } > Thanks. -- 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-10982) Plugin for ios platform didn't copy custom Framework to Application
[ https://issues.apache.org/jira/browse/CB-10982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15237703#comment-15237703 ] Omar Mefire commented on CB-10982: -- Hi [~maslo...@gmail.com], I have added added been able to successfully call your plugin's exposed functionality and been able to trace the call all the way back to native land (framework) and back. So, I can't repro this issue. I don't see the framework in the 'Embedded Binaries' in Xcode either, but I can't see the error you're seeing. Try resetting your simulator and trying again. > Plugin for ios platform didn't copy custom Framework to Application > --- > > Key: CB-10982 > URL: https://issues.apache.org/jira/browse/CB-10982 > Project: Apache Cordova > Issue Type: Bug > Components: iOS >Affects Versions: 6.0.0, 6.1.0 > Environment: Iphone 6S Simulator ios 9.3 >Reporter: Sergei Alexandrovich Maslov >Assignee: Omar Mefire > Labels: triaged, wfc > Attachments: scr1.png, scr2.png, test.zip > > > Custom ios framework from custom plugin didn't add to Embedded Binaries > section on target project. This causes an error on runtime " Reason: image > not found" > Steps to reproduce - > 1) Create empty Custom ios Framework. (MyFramework) > 2) Create ios Plugin. > I include MyFramework using this line in plugin.xml > > 3) Create project using Cordova. Add ios platform and ios plugin. > 4) Compile and Run. > 5) Get Error. -- 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-11064) Update new engine package.json docs
[ https://issues.apache.org/jira/browse/CB-11064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15237700#comment-15237700 ] ASF GitHub Bot commented on CB-11064: - Github user purplecabbage commented on the pull request: https://github.com/apache/cordova-docs/pull/577#issuecomment-209042894 lgtm! > Update new engine package.json docs > --- > > Key: CB-11064 > URL: https://issues.apache.org/jira/browse/CB-11064 > Project: Apache Cordova > Issue Type: Bug > Components: Docs >Reporter: Richard B Knoll >Assignee: Richard B Knoll > Labels: triaged > > Update engine docs in plugin.xml to mention it's being deprecated eventually > and fix heading in plugin guide -- 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-8383) pause event don't fire when 'KeepRunning' is false
[ https://issues.apache.org/jira/browse/CB-8383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15237696#comment-15237696 ] Jesse MacFadyen commented on CB-8383: - Can we write tests for this? This seems to be a hard condition to verify. attn: [~bowserj] > pause event don't fire when 'KeepRunning' is false > -- > > Key: CB-8383 > URL: https://issues.apache.org/jira/browse/CB-8383 > Project: Apache Cordova > Issue Type: Bug > Components: Android >Affects Versions: Master, 3.5.0, 4.0.0, 4.1.3 > Environment: Mac osx 10.9 >Reporter: hugefactory > Original Estimate: 1h > Remaining Estimate: 1h > > Under Android, when a project use 'KeepRunning=false' in the config.xml file, > the 'pause' event in javascript don't fire when application go to background. > Next, 'pause' event fire when 'resume' is call and when the application > resume. > The problem is in 'CordovaWebView.java' in the 'handlePause' method : > public void handlePause(boolean keepRunning) { > LOG.d(TAG, "Handle the pause"); > // Send pause event to JavaScript > > this.loadUrl("javascript:try{cordova.fireDocumentEvent('pause');}catch(e){console.log('exception > firing pause event from native');};"); > // Forward to plugins > if (this.pluginManager != null) { > this.pluginManager.onPause(keepRunning); > } > // If app doesn't want to run in background > if (!keepRunning) { > // Pause JavaScript timers (including setInterval) > this.pauseTimers(); > } > paused = true; > > } > As you can see, 'pauseTimers()' is call immediatly when we choose > 'KeepRunning' false. > According to the Android documentation, 'pauseTimer()' stop all javascript > activitythen the 'pause' javascript callback is not execute (it's execute > after, when the 'resumeTimers()' is call and the application resume. > I suggest to delay the 'pauseTimers()' for 1 or 2 sec. Then the javascript > 'pause' can execute before the application is really stop : > //OLD > //this.pauseTimers(); > //NEW > final Handler handler = new Handler(); > handler.postDelayed(new Runnable() { > @Override > public void run() { > LOG.d(TAG, "Handle the pauseTimers"); > pauseTimers(); > } > }, 1000); > } > Thanks. -- 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-10898) 'Invalid Device State' when starting iOS simulator
[ https://issues.apache.org/jira/browse/CB-10898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15237682#comment-15237682 ] ASF subversion and git services commented on CB-10898: -- Commit f57a7e6794f895be609fc00e5fc4fe71f72790df in cordova-medic's branch refs/heads/master from [~omefire] [ https://git-wip-us.apache.org/repos/asf?p=cordova-medic.git;h=f57a7e6 ] CB-10898 Kill iOS Simulator, Xcode7 style With Xcode7, the way to kill the simulator is now by running: "killall -9 Simulator" This closes #86 > 'Invalid Device State' when starting iOS simulator > -- > > Key: CB-10898 > URL: https://issues.apache.org/jira/browse/CB-10898 > Project: Apache Cordova > Issue Type: Bug >Reporter: Omar Mefire >Assignee: Omar Mefire >Priority: Critical > Labels: cordova-ios, found-by-ci > > When trying to run the mobilespec app on the iOS simulator, an error: > 'Invalid Device State' is encountered. > Log: > https://ci.apache.org/builders/cordova-ios/builds/2076/steps/running-tests/logs/stdio > == > Results at > '/Users/buildbot/slaves/apache/cordova-ios/mobilespec/platforms/ios/build/device/mobilespec.ipa' > > [] Waiting up to 1 seconds for iOS device to be connected > No target specified for emulator. Deploying to iPhone-6s-Plus, 9.1 simulator > An error was encountered processing the command > (domain=com.apple.CoreSimulator.SimError, code=159): > Invalid device state > logPath: > /Users/buildbot/slaves/apache/cordova-ios/mobilespec/platforms/ios/cordova/console.log > [MEDIC LOG Thu, 17 Mar 2016 06:06:24 GMT] Finished waiting for run command > [MEDIC LOG Thu, 17 Mar 2016 06:06:24 GMT] started waiting for test results > [MEDIC LOG Thu, 17 Mar 2016 06:30:25 GMT] Finished polling for mobilespec > results. > [MEDIC LOG Thu, 17 Mar 2016 06:30:25 GMT] Results Found: false > [MEDIC LOG Thu, 17 Mar 2016 06:30:25 GMT] Total attempts: 144 > [MEDIC LOG Thu, 17 Mar 2016 06:30:25 GMT] Failed attempts: 0 > [MEDIC LOG Thu, 17 Mar 2016 06:30:25 GMT] FATAL: Could not find test results. > Check the output of medic-log to see if the app crashed before it could > upload them to couchdb. > program finished with exit code 1 > elapsedTime=1491.694117 -- 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-10898) 'Invalid Device State' when starting iOS simulator
[ https://issues.apache.org/jira/browse/CB-10898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15237684#comment-15237684 ] ASF GitHub Bot commented on CB-10898: - Github user asfgit closed the pull request at: https://github.com/apache/cordova-medic/pull/86 > 'Invalid Device State' when starting iOS simulator > -- > > Key: CB-10898 > URL: https://issues.apache.org/jira/browse/CB-10898 > Project: Apache Cordova > Issue Type: Bug >Reporter: Omar Mefire >Assignee: Omar Mefire >Priority: Critical > Labels: cordova-ios, found-by-ci > > When trying to run the mobilespec app on the iOS simulator, an error: > 'Invalid Device State' is encountered. > Log: > https://ci.apache.org/builders/cordova-ios/builds/2076/steps/running-tests/logs/stdio > == > Results at > '/Users/buildbot/slaves/apache/cordova-ios/mobilespec/platforms/ios/build/device/mobilespec.ipa' > > [] Waiting up to 1 seconds for iOS device to be connected > No target specified for emulator. Deploying to iPhone-6s-Plus, 9.1 simulator > An error was encountered processing the command > (domain=com.apple.CoreSimulator.SimError, code=159): > Invalid device state > logPath: > /Users/buildbot/slaves/apache/cordova-ios/mobilespec/platforms/ios/cordova/console.log > [MEDIC LOG Thu, 17 Mar 2016 06:06:24 GMT] Finished waiting for run command > [MEDIC LOG Thu, 17 Mar 2016 06:06:24 GMT] started waiting for test results > [MEDIC LOG Thu, 17 Mar 2016 06:30:25 GMT] Finished polling for mobilespec > results. > [MEDIC LOG Thu, 17 Mar 2016 06:30:25 GMT] Results Found: false > [MEDIC LOG Thu, 17 Mar 2016 06:30:25 GMT] Total attempts: 144 > [MEDIC LOG Thu, 17 Mar 2016 06:30:25 GMT] Failed attempts: 0 > [MEDIC LOG Thu, 17 Mar 2016 06:30:25 GMT] FATAL: Could not find test results. > Check the output of medic-log to see if the app crashed before it could > upload them to couchdb. > program finished with exit code 1 > elapsedTime=1491.694117 -- 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-9600) FileUploadOptions params not posted on iOS
[ https://issues.apache.org/jira/browse/CB-9600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15237681#comment-15237681 ] ASF GitHub Bot commented on CB-9600: Github user daserge commented on the pull request: https://github.com/apache/cordova-plugin-file-transfer/pull/121#issuecomment-209040166 App JS code with FileUploadOptions would be useful too. > FileUploadOptions params not posted on iOS > -- > > Key: CB-9600 > URL: https://issues.apache.org/jira/browse/CB-9600 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin File Transfer >Affects Versions: 3.5.0, 3.7.0 > Environment: iPhone - iOS 8.4.1 >Reporter: TipsTrade >Assignee: jcesarmobile > > Using an app built using build.phonegap.com I'm finding that the > FileUploadOptions.params values aren't being posted - iOS (8.4.1) only posts > the file multipart data. This isn't a server side error as I've watched the > POST using tcpdump/Wireshark and netcat. > * PhoneGap v.3.7.0 > * Ionic Framework v.1.0.1 > * AngularJS v.1.3.13 > This is the code that is used to upload a test file. It generates a temporary > file and attempts to upload it. > {code:javascript} > $scope.doUploadTest = function() { > var q = $q.defer(); > var promise = q.promise; > var text = "Test file content: " + new Date(); > $window.requestFileSystem(LocalFileSystem.TEMPORARY, text.length, > function(fs) { > q.resolve(fs); > }, function(err) { > q.reject(err); > }); > promise > .then(function(fs) { > var qFile = $q.defer(); > fs.root.getFile("upload.tmp", {create: true, exclusive: false}, > function(entry) { > qFile.resolve(entry); > }, function(err) { > qFile.reject(err); > }); > return qFile.promise; > }) > .then(function(entry) { > console.log("got file: " + entry.nativeURL); > var qWriter = $q.defer(); > entry.createWriter(function(writer) { > qWriter.resolve({writer: writer, entry: entry}); > }, function(err) { > qWriter.reject(err); > }); > return qWriter.promise; > }) > .then(function(response) { > var qWrite = $q.defer(); > response.writer.onwriteend = function(evt) { > qWrite.resolve(response.entry); > }; > response.writer.write(text); > return qWrite.promise; > }) > .then(function(entry) { > $scope.error = entry; > var qUpload = $q.defer(); > var options = new FileUploadOptions(); > options.params = { > Value: { > list: [1, 2, 3], > text: "foo bar baz", > number: 1234 > } > }; > options.fileKey = "thefile"; > options.fileName = entry.name; > options.mimeType = "text/plain"; > options.chunkedMode = false; > options.headers = { > "X-Upload": (new Date()).toString() > }; > var ft = new FileTransfer(); > ft.upload(entry.nativeURL, "http://192.168.0.30:9100/;, > function(success) { > entry.remove(); > qUpload.resolve(success); > }, function(err) { > entry.remove(); > qUpload.reject(err); > }, options); > // Abort after 3 seconds > $timeout(function() { > console.log("Aborting upload - timed out"); > ft.abort(); > }, 3000); > return qUpload.promise; > }) > .then(function(response) { > console.log("Upload succeeded"); > $scope.error = response; > }) > .catch(function(err) { > console.log("Upload failed"); > $scope.error = err; > }); > ; > }; > {code} > The request made by an iPhone 6 (iOS v.8.4.1) is as follows: > {noformat} > POST / HTTP/1.1 > Host: 192.168.0.30:9100 > Content-Type: multipart/form-data; > boundary=+org.apache.cordova.formBoundary > Accept-Encoding: gzip, deflate > X-Upload: Tue Sep 01 2015 12:12:49 GMT+0100 (BST) > Connection: keep-alive > Accept: */* > User-Agent: Mozilla/5.0 (iPhone; CPU iPhone OS 8_4_1 like Mac OS X) > AppleWebKit/600.1.4 (KHTML, like Gecko) Mobile/12H321 (5348809648) > Content-Length: 261 > Accept-Language: en-us > X-Requested-With: XMLHttpRequest > --+org.apache.cordova.formBoundary > Content-Disposition: form-data; name="thefile"; filename="upload.tmp" > Content-Type: text/plain > Content-Length: 58 > Test file content: Tue Sep 01 2015 12:12:49 GMT+0100 (BST) > --+org.apache.cordova.formBoundary-- > {noformat} > On a Motorola Moto X (2nd gen, Android 5.1) the request is this: > {noformat} > POST / HTTP/1.1 > Content-Type: multipart/form-data; boundary=+ > X-Upload: Tue Sep 01 2015 12:52:24 GMT+0100 (BST) > User-Agent: Dalvik/2.1.0 (Linux; U;
[jira] [Commented] (CB-9600) FileUploadOptions params not posted on iOS
[ https://issues.apache.org/jira/browse/CB-9600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15237671#comment-15237671 ] ASF GitHub Bot commented on CB-9600: Github user purplecabbage commented on the pull request: https://github.com/apache/cordova-plugin-file-transfer/pull/121#issuecomment-209038768 @mirko77 Please provide more details, and repro steps in JIRA [ https://issues.apache.org/jira/browse/CB-9600 ] Where are you posting to? What kind of server is it? What is it getting? > FileUploadOptions params not posted on iOS > -- > > Key: CB-9600 > URL: https://issues.apache.org/jira/browse/CB-9600 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin File Transfer >Affects Versions: 3.5.0, 3.7.0 > Environment: iPhone - iOS 8.4.1 >Reporter: TipsTrade >Assignee: jcesarmobile > > Using an app built using build.phonegap.com I'm finding that the > FileUploadOptions.params values aren't being posted - iOS (8.4.1) only posts > the file multipart data. This isn't a server side error as I've watched the > POST using tcpdump/Wireshark and netcat. > * PhoneGap v.3.7.0 > * Ionic Framework v.1.0.1 > * AngularJS v.1.3.13 > This is the code that is used to upload a test file. It generates a temporary > file and attempts to upload it. > {code:javascript} > $scope.doUploadTest = function() { > var q = $q.defer(); > var promise = q.promise; > var text = "Test file content: " + new Date(); > $window.requestFileSystem(LocalFileSystem.TEMPORARY, text.length, > function(fs) { > q.resolve(fs); > }, function(err) { > q.reject(err); > }); > promise > .then(function(fs) { > var qFile = $q.defer(); > fs.root.getFile("upload.tmp", {create: true, exclusive: false}, > function(entry) { > qFile.resolve(entry); > }, function(err) { > qFile.reject(err); > }); > return qFile.promise; > }) > .then(function(entry) { > console.log("got file: " + entry.nativeURL); > var qWriter = $q.defer(); > entry.createWriter(function(writer) { > qWriter.resolve({writer: writer, entry: entry}); > }, function(err) { > qWriter.reject(err); > }); > return qWriter.promise; > }) > .then(function(response) { > var qWrite = $q.defer(); > response.writer.onwriteend = function(evt) { > qWrite.resolve(response.entry); > }; > response.writer.write(text); > return qWrite.promise; > }) > .then(function(entry) { > $scope.error = entry; > var qUpload = $q.defer(); > var options = new FileUploadOptions(); > options.params = { > Value: { > list: [1, 2, 3], > text: "foo bar baz", > number: 1234 > } > }; > options.fileKey = "thefile"; > options.fileName = entry.name; > options.mimeType = "text/plain"; > options.chunkedMode = false; > options.headers = { > "X-Upload": (new Date()).toString() > }; > var ft = new FileTransfer(); > ft.upload(entry.nativeURL, "http://192.168.0.30:9100/;, > function(success) { > entry.remove(); > qUpload.resolve(success); > }, function(err) { > entry.remove(); > qUpload.reject(err); > }, options); > // Abort after 3 seconds > $timeout(function() { > console.log("Aborting upload - timed out"); > ft.abort(); > }, 3000); > return qUpload.promise; > }) > .then(function(response) { > console.log("Upload succeeded"); > $scope.error = response; > }) > .catch(function(err) { > console.log("Upload failed"); > $scope.error = err; > }); > ; > }; > {code} > The request made by an iPhone 6 (iOS v.8.4.1) is as follows: > {noformat} > POST / HTTP/1.1 > Host: 192.168.0.30:9100 > Content-Type: multipart/form-data; > boundary=+org.apache.cordova.formBoundary > Accept-Encoding: gzip, deflate > X-Upload: Tue Sep 01 2015 12:12:49 GMT+0100 (BST) > Connection: keep-alive > Accept: */* > User-Agent: Mozilla/5.0 (iPhone; CPU iPhone OS 8_4_1 like Mac OS X) > AppleWebKit/600.1.4 (KHTML, like Gecko) Mobile/12H321 (5348809648) > Content-Length: 261 > Accept-Language: en-us > X-Requested-With: XMLHttpRequest > --+org.apache.cordova.formBoundary > Content-Disposition: form-data; name="thefile"; filename="upload.tmp" > Content-Type: text/plain > Content-Length: 58 > Test file content: Tue Sep 01 2015 12:12:49 GMT+0100 (BST) > --+org.apache.cordova.formBoundary-- > {noformat} > On a Motorola Moto X (2nd gen, Android 5.1) the request is this: > {noformat} > POST / HTTP/1.1 >
[jira] [Commented] (CB-9600) FileUploadOptions params not posted on iOS
[ https://issues.apache.org/jira/browse/CB-9600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15237665#comment-15237665 ] ASF GitHub Bot commented on CB-9600: Github user mirko77 commented on the pull request: https://github.com/apache/cordova-plugin-file-transfer/pull/121#issuecomment-209035343 I am still having the issue using the plugin version 1.5 on iOS 9.2.1 POST request is empty, FILE is ok > FileUploadOptions params not posted on iOS > -- > > Key: CB-9600 > URL: https://issues.apache.org/jira/browse/CB-9600 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin File Transfer >Affects Versions: 3.5.0, 3.7.0 > Environment: iPhone - iOS 8.4.1 >Reporter: TipsTrade >Assignee: jcesarmobile > > Using an app built using build.phonegap.com I'm finding that the > FileUploadOptions.params values aren't being posted - iOS (8.4.1) only posts > the file multipart data. This isn't a server side error as I've watched the > POST using tcpdump/Wireshark and netcat. > * PhoneGap v.3.7.0 > * Ionic Framework v.1.0.1 > * AngularJS v.1.3.13 > This is the code that is used to upload a test file. It generates a temporary > file and attempts to upload it. > {code:javascript} > $scope.doUploadTest = function() { > var q = $q.defer(); > var promise = q.promise; > var text = "Test file content: " + new Date(); > $window.requestFileSystem(LocalFileSystem.TEMPORARY, text.length, > function(fs) { > q.resolve(fs); > }, function(err) { > q.reject(err); > }); > promise > .then(function(fs) { > var qFile = $q.defer(); > fs.root.getFile("upload.tmp", {create: true, exclusive: false}, > function(entry) { > qFile.resolve(entry); > }, function(err) { > qFile.reject(err); > }); > return qFile.promise; > }) > .then(function(entry) { > console.log("got file: " + entry.nativeURL); > var qWriter = $q.defer(); > entry.createWriter(function(writer) { > qWriter.resolve({writer: writer, entry: entry}); > }, function(err) { > qWriter.reject(err); > }); > return qWriter.promise; > }) > .then(function(response) { > var qWrite = $q.defer(); > response.writer.onwriteend = function(evt) { > qWrite.resolve(response.entry); > }; > response.writer.write(text); > return qWrite.promise; > }) > .then(function(entry) { > $scope.error = entry; > var qUpload = $q.defer(); > var options = new FileUploadOptions(); > options.params = { > Value: { > list: [1, 2, 3], > text: "foo bar baz", > number: 1234 > } > }; > options.fileKey = "thefile"; > options.fileName = entry.name; > options.mimeType = "text/plain"; > options.chunkedMode = false; > options.headers = { > "X-Upload": (new Date()).toString() > }; > var ft = new FileTransfer(); > ft.upload(entry.nativeURL, "http://192.168.0.30:9100/;, > function(success) { > entry.remove(); > qUpload.resolve(success); > }, function(err) { > entry.remove(); > qUpload.reject(err); > }, options); > // Abort after 3 seconds > $timeout(function() { > console.log("Aborting upload - timed out"); > ft.abort(); > }, 3000); > return qUpload.promise; > }) > .then(function(response) { > console.log("Upload succeeded"); > $scope.error = response; > }) > .catch(function(err) { > console.log("Upload failed"); > $scope.error = err; > }); > ; > }; > {code} > The request made by an iPhone 6 (iOS v.8.4.1) is as follows: > {noformat} > POST / HTTP/1.1 > Host: 192.168.0.30:9100 > Content-Type: multipart/form-data; > boundary=+org.apache.cordova.formBoundary > Accept-Encoding: gzip, deflate > X-Upload: Tue Sep 01 2015 12:12:49 GMT+0100 (BST) > Connection: keep-alive > Accept: */* > User-Agent: Mozilla/5.0 (iPhone; CPU iPhone OS 8_4_1 like Mac OS X) > AppleWebKit/600.1.4 (KHTML, like Gecko) Mobile/12H321 (5348809648) > Content-Length: 261 > Accept-Language: en-us > X-Requested-With: XMLHttpRequest > --+org.apache.cordova.formBoundary > Content-Disposition: form-data; name="thefile"; filename="upload.tmp" > Content-Type: text/plain > Content-Length: 58 > Test file content: Tue Sep 01 2015 12:12:49 GMT+0100 (BST) > --+org.apache.cordova.formBoundary-- > {noformat} > On a Motorola Moto X (2nd gen, Android 5.1) the request is this: > {noformat} > POST / HTTP/1.1 > Content-Type: multipart/form-data; boundary=+ > X-Upload: Tue Sep 01 2015 12:52:24
[jira] [Created] (CB-11070) Document SplashScreenBackgroundColor
Sergey Shakhnazarov created CB-11070: Summary: Document SplashScreenBackgroundColor Key: CB-11070 URL: https://issues.apache.org/jira/browse/CB-11070 Project: Apache Cordova Issue Type: Bug Components: Docs Reporter: Sergey Shakhnazarov Assignee: Sergey Shakhnazarov -- 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-11064) Update new engine package.json docs
[ https://issues.apache.org/jira/browse/CB-11064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15237619#comment-15237619 ] ASF GitHub Bot commented on CB-11064: - GitHub user riknoll opened a pull request: https://github.com/apache/cordova-docs/pull/577 CB-11064: Adding a note to the engine tag spec and fixing a header @nikhilkh when you have a moment You can merge this pull request into a Git repository by running: $ git pull https://github.com/MSOpenTech/cordova-docs CB-11064 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-docs/pull/577.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 #577 commit fc2eeaa3e5b25e1ffd0919aa40e5076f0b58e7db Author: Richard KnollDate: 2016-04-12T17:42:20Z CB-11064: Adding a note to the engine tag spec and fixing a header > Update new engine package.json docs > --- > > Key: CB-11064 > URL: https://issues.apache.org/jira/browse/CB-11064 > Project: Apache Cordova > Issue Type: Bug > Components: Docs >Reporter: Richard B Knoll >Assignee: Richard B Knoll > Labels: triaged > > Update engine docs in plugin.xml to mention it's being deprecated eventually > and fix heading in plugin guide -- 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-11001) Incorrect docs - "FullScreen" config.xml preference only applies to Android
[ https://issues.apache.org/jira/browse/CB-11001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15237649#comment-15237649 ] ASF GitHub Bot commented on CB-11001: - Github user daserge commented on the pull request: https://github.com/apache/cordova-docs/pull/576#issuecomment-209030235 Updated, thank you! > Incorrect docs - "FullScreen" config.xml preference only applies to Android > --- > > Key: CB-11001 > URL: https://issues.apache.org/jira/browse/CB-11001 > Project: Apache Cordova > Issue Type: Bug > Components: Docs >Reporter: Jerroyd Moore >Assignee: Sergey Shakhnazarov > Labels: triaged > > The is ignored when I add it > and build for 8.1-phone. > {code} > $ cordova -v > 5.4.1 > $ cordova create foo > $ cd foo > $ cordova platform add windows > $ cordova prepare windows > $ cd platforms/windows/cordova > $ build.bat -r --appx=8.1-phone > {code} > Running it on a windows phone 8.1, the status bar is hidden. -- 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-10957) iOS release-mode app contains build config files
[ https://issues.apache.org/jira/browse/CB-10957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15237585#comment-15237585 ] ASF subversion and git services commented on CB-10957: -- Commit b7e3be104ab9b12d14713f3c32898ff2464a in cordova-ios's branch refs/heads/master from [~omefire] [ https://git-wip-us.apache.org/repos/asf?p=cordova-ios.git;h=b7e3be1 ] CB-10957 Remove build*.xconfig from build outputs: *.ipa, *.app This closes #214 > iOS release-mode app contains build config files > > > Key: CB-10957 > URL: https://issues.apache.org/jira/browse/CB-10957 > Project: Apache Cordova > Issue Type: Bug > Components: iOS >Affects Versions: 4.1.0 > Environment: cordova-ios 4.1.0 > cordova CLI 6.0.0 > Mac OS 10.11.3 >Reporter: Jacob Weber >Assignee: Omar Mefire > Labels: triaged > > Create a new app, add the iOS platform, and run {{cordova build --device > --release}}. > The resulting .ipa file contains the following files: > {code} > build-debug.xcconfig > build-release.xcconfig > build.xcconfig > {code} > I don't think the final app should contain these build files, especially not > debug versions. -- 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-10957) iOS release-mode app contains build config files
[ https://issues.apache.org/jira/browse/CB-10957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15237586#comment-15237586 ] ASF GitHub Bot commented on CB-10957: - Github user asfgit closed the pull request at: https://github.com/apache/cordova-ios/pull/214 > iOS release-mode app contains build config files > > > Key: CB-10957 > URL: https://issues.apache.org/jira/browse/CB-10957 > Project: Apache Cordova > Issue Type: Bug > Components: iOS >Affects Versions: 4.1.0 > Environment: cordova-ios 4.1.0 > cordova CLI 6.0.0 > Mac OS 10.11.3 >Reporter: Jacob Weber >Assignee: Omar Mefire > Labels: triaged > > Create a new app, add the iOS platform, and run {{cordova build --device > --release}}. > The resulting .ipa file contains the following files: > {code} > build-debug.xcconfig > build-release.xcconfig > build.xcconfig > {code} > I don't think the final app should contain these build files, especially not > debug versions. -- 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-10957) iOS release-mode app contains build config files
[ https://issues.apache.org/jira/browse/CB-10957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15237582#comment-15237582 ] ASF GitHub Bot commented on CB-10957: - Github user omefire commented on the pull request: https://github.com/apache/cordova-ios/pull/214#issuecomment-209017316 @shazron I'm merging this in. I've addressed your CR notes. > iOS release-mode app contains build config files > > > Key: CB-10957 > URL: https://issues.apache.org/jira/browse/CB-10957 > Project: Apache Cordova > Issue Type: Bug > Components: iOS >Affects Versions: 4.1.0 > Environment: cordova-ios 4.1.0 > cordova CLI 6.0.0 > Mac OS 10.11.3 >Reporter: Jacob Weber >Assignee: Omar Mefire > Labels: triaged > > Create a new app, add the iOS platform, and run {{cordova build --device > --release}}. > The resulting .ipa file contains the following files: > {code} > build-debug.xcconfig > build-release.xcconfig > build.xcconfig > {code} > I don't think the final app should contain these build files, especially not > debug versions. -- 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-10898) 'Invalid Device State' when starting iOS simulator
[ https://issues.apache.org/jira/browse/CB-10898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15237579#comment-15237579 ] ASF GitHub Bot commented on CB-10898: - Github user nikhilkh commented on the pull request: https://github.com/apache/cordova-medic/pull/86#issuecomment-209016620 LGTM, > 'Invalid Device State' when starting iOS simulator > -- > > Key: CB-10898 > URL: https://issues.apache.org/jira/browse/CB-10898 > Project: Apache Cordova > Issue Type: Bug >Reporter: Omar Mefire >Assignee: Omar Mefire >Priority: Critical > Labels: cordova-ios, found-by-ci > > When trying to run the mobilespec app on the iOS simulator, an error: > 'Invalid Device State' is encountered. > Log: > https://ci.apache.org/builders/cordova-ios/builds/2076/steps/running-tests/logs/stdio > == > Results at > '/Users/buildbot/slaves/apache/cordova-ios/mobilespec/platforms/ios/build/device/mobilespec.ipa' > > [] Waiting up to 1 seconds for iOS device to be connected > No target specified for emulator. Deploying to iPhone-6s-Plus, 9.1 simulator > An error was encountered processing the command > (domain=com.apple.CoreSimulator.SimError, code=159): > Invalid device state > logPath: > /Users/buildbot/slaves/apache/cordova-ios/mobilespec/platforms/ios/cordova/console.log > [MEDIC LOG Thu, 17 Mar 2016 06:06:24 GMT] Finished waiting for run command > [MEDIC LOG Thu, 17 Mar 2016 06:06:24 GMT] started waiting for test results > [MEDIC LOG Thu, 17 Mar 2016 06:30:25 GMT] Finished polling for mobilespec > results. > [MEDIC LOG Thu, 17 Mar 2016 06:30:25 GMT] Results Found: false > [MEDIC LOG Thu, 17 Mar 2016 06:30:25 GMT] Total attempts: 144 > [MEDIC LOG Thu, 17 Mar 2016 06:30:25 GMT] Failed attempts: 0 > [MEDIC LOG Thu, 17 Mar 2016 06:30:25 GMT] FATAL: Could not find test results. > Check the output of medic-log to see if the app crashed before it could > upload them to couchdb. > program finished with exit code 1 > elapsedTime=1491.694117 -- 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-10996) Plugin API reference is deprecated with no alternative
[ https://issues.apache.org/jira/browse/CB-10996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15237571#comment-15237571 ] ASF GitHub Bot commented on CB-10996: - Github user riknoll commented on the pull request: https://github.com/apache/cordova-docs/pull/575#issuecomment-209013648 @dblotsky why change the headers from what's in the TOC? It might be a little weird to have two links on the page with different text going to the same place. Same with "Writing Apps/Plugins" vs. "Create Apps/Plugins". Also, why are some of the headings in the TOC here and others not? The platform guides need entries in my opinion. > Plugin API reference is deprecated with no alternative > -- > > Key: CB-10996 > URL: https://issues.apache.org/jira/browse/CB-10996 > Project: Apache Cordova > Issue Type: Bug > Components: Docs >Reporter: Tommy-Carlos Williams > Labels: docs, triaged > > https://cordova.apache.org/docs/en/latest/cordova/plugins/pluginapis.html > (linked to from "Plugin APIs" under "API Reference at > https://cordova.apache.org/docs/en/latest/) redirects to a deprecated warning > with only a link back to /latest > This "deprecated" page is a glorified 404. There really should be a landing > page with links to the plugin APIs rather than only being available via the > Table of Contents links on the left. -- 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-10898) 'Invalid Device State' when starting iOS simulator
[ https://issues.apache.org/jira/browse/CB-10898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15237565#comment-15237565 ] ASF GitHub Bot commented on CB-10898: - GitHub user omefire opened a pull request: https://github.com/apache/cordova-medic/pull/86 CB-10898 Kill iOS Simulator, Xcode7 style With Xcode7, the way to kill the simulator is now by running: "killall -9 Simulator" You can merge this pull request into a Git repository by running: $ git pull https://github.com/omefire/cordova-medic CB-10898 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-medic/pull/86.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 #86 commit 7bd4a4fe45b0c05cc84329d7e5462f558eeeb214 Author: Omar MefireDate: 2016-04-12T17:13:03Z CB-10898 Kill iOS Simulator, Xcode7 style With Xcode7, the way to kill the simulator is now by running: "killall -9 Simulator" > 'Invalid Device State' when starting iOS simulator > -- > > Key: CB-10898 > URL: https://issues.apache.org/jira/browse/CB-10898 > Project: Apache Cordova > Issue Type: Bug >Reporter: Omar Mefire >Assignee: Omar Mefire >Priority: Critical > Labels: cordova-ios, found-by-ci > > When trying to run the mobilespec app on the iOS simulator, an error: > 'Invalid Device State' is encountered. > Log: > https://ci.apache.org/builders/cordova-ios/builds/2076/steps/running-tests/logs/stdio > == > Results at > '/Users/buildbot/slaves/apache/cordova-ios/mobilespec/platforms/ios/build/device/mobilespec.ipa' > > [] Waiting up to 1 seconds for iOS device to be connected > No target specified for emulator. Deploying to iPhone-6s-Plus, 9.1 simulator > An error was encountered processing the command > (domain=com.apple.CoreSimulator.SimError, code=159): > Invalid device state > logPath: > /Users/buildbot/slaves/apache/cordova-ios/mobilespec/platforms/ios/cordova/console.log > [MEDIC LOG Thu, 17 Mar 2016 06:06:24 GMT] Finished waiting for run command > [MEDIC LOG Thu, 17 Mar 2016 06:06:24 GMT] started waiting for test results > [MEDIC LOG Thu, 17 Mar 2016 06:30:25 GMT] Finished polling for mobilespec > results. > [MEDIC LOG Thu, 17 Mar 2016 06:30:25 GMT] Results Found: false > [MEDIC LOG Thu, 17 Mar 2016 06:30:25 GMT] Total attempts: 144 > [MEDIC LOG Thu, 17 Mar 2016 06:30:25 GMT] Failed attempts: 0 > [MEDIC LOG Thu, 17 Mar 2016 06:30:25 GMT] FATAL: Could not find test results. > Check the output of medic-log to see if the app crashed before it could > upload them to couchdb. > program finished with exit code 1 > elapsedTime=1491.694117 -- 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-10898) 'Invalid Device State' when starting iOS simulator
[ https://issues.apache.org/jira/browse/CB-10898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15237564#comment-15237564 ] Omar Mefire commented on CB-10898: -- This time around, the reason why it showed up on the CI was because the simulator hung and wasn't responding. I had to log into the machine and manually kill the simulator, which fixed the issue. cordova-medic was supposed to kill the simulator before and after every run. that didn't happen because with Xcode 7, the way you kill the simulator has changed from 'killall -9 "iOS Simulator" ' to " killall -9 "Simulator" ' Running 'killall -9 "iOS Simulator" ' was erroring out with: "[MEDIC LOG Tue, 12 Apr 2016 12:08:23 GMT] running the following command: [MEDIC LOG Tue, 12 Apr 2016 12:08:23 GMT] killall -9 "iOS Simulator" No matching processes belonging to you were found WARNING: kill command returned 1 program finished with exit code 0 elapsedTime=0.330458" https://ci.apache.org/builders/cordova-ios/builds/2278/steps/killing-running-tasks/logs/stdio > 'Invalid Device State' when starting iOS simulator > -- > > Key: CB-10898 > URL: https://issues.apache.org/jira/browse/CB-10898 > Project: Apache Cordova > Issue Type: Bug >Reporter: Omar Mefire >Assignee: Omar Mefire >Priority: Critical > Labels: cordova-ios, found-by-ci > > When trying to run the mobilespec app on the iOS simulator, an error: > 'Invalid Device State' is encountered. > Log: > https://ci.apache.org/builders/cordova-ios/builds/2076/steps/running-tests/logs/stdio > == > Results at > '/Users/buildbot/slaves/apache/cordova-ios/mobilespec/platforms/ios/build/device/mobilespec.ipa' > > [] Waiting up to 1 seconds for iOS device to be connected > No target specified for emulator. Deploying to iPhone-6s-Plus, 9.1 simulator > An error was encountered processing the command > (domain=com.apple.CoreSimulator.SimError, code=159): > Invalid device state > logPath: > /Users/buildbot/slaves/apache/cordova-ios/mobilespec/platforms/ios/cordova/console.log > [MEDIC LOG Thu, 17 Mar 2016 06:06:24 GMT] Finished waiting for run command > [MEDIC LOG Thu, 17 Mar 2016 06:06:24 GMT] started waiting for test results > [MEDIC LOG Thu, 17 Mar 2016 06:30:25 GMT] Finished polling for mobilespec > results. > [MEDIC LOG Thu, 17 Mar 2016 06:30:25 GMT] Results Found: false > [MEDIC LOG Thu, 17 Mar 2016 06:30:25 GMT] Total attempts: 144 > [MEDIC LOG Thu, 17 Mar 2016 06:30:25 GMT] Failed attempts: 0 > [MEDIC LOG Thu, 17 Mar 2016 06:30:25 GMT] FATAL: Could not find test results. > Check the output of medic-log to see if the app crashed before it could > upload them to couchdb. > program finished with exit code 1 > elapsedTime=1491.694117 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10986) Unable to install npm scoped plugin with cordova-cli@6.1.0
[ https://issues.apache.org/jira/browse/CB-10986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15237561#comment-15237561 ] ASF GitHub Bot commented on CB-10986: - Github user riknoll commented on the pull request: https://github.com/apache/cordova-lib/pull/425#issuecomment-209011899 @vladimir-kotikov To clarify the plugin mapper comments: I left in the scope with the intention that the mapping would fail if the scope was present. I don't think there is a case for remapping old plugin ids that have a scope added, because if you are giving a scope then you know what npm package you are trying to fetch. We should never remap in that scenario and I'll try and clarify that in the code. As for changing the API, I'm fine with the approach you suggested (separate class, one function, etc.). I think I just dug myself into a hole with the initial way I wrote the code and didn't refactor when I should have :) > Unable to install npm scoped plugin with cordova-cli@6.1.0 > -- > > Key: CB-10986 > URL: https://issues.apache.org/jira/browse/CB-10986 > Project: Apache Cordova > Issue Type: Bug > Components: CordovaLib >Affects Versions: 6.1.0 >Reporter: Darryl Pogue >Assignee: Richard B Knoll > Labels: regression, reproduced, triaged > > {code} > $ cordova create MyProject > $ cd ./MyProject > $ cordova platform add android > $ cordova plugin add @dpogue/cordova-plugin-crosswalk-webview > Error: Cannot find plugin.xml for plugin 'plugins'. Please try adding it > again. > {code} > This works as expected with cordova@6.0.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11001) Incorrect docs - "FullScreen" config.xml preference only applies to Android
[ https://issues.apache.org/jira/browse/CB-11001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15237556#comment-15237556 ] ASF GitHub Bot commented on CB-11001: - Github user nikhilkh commented on the pull request: https://github.com/apache/cordova-docs/pull/576#issuecomment-209011002 LGTM otherwise > Incorrect docs - "FullScreen" config.xml preference only applies to Android > --- > > Key: CB-11001 > URL: https://issues.apache.org/jira/browse/CB-11001 > Project: Apache Cordova > Issue Type: Bug > Components: Docs >Reporter: Jerroyd Moore >Assignee: Sergey Shakhnazarov > Labels: triaged > > The is ignored when I add it > and build for 8.1-phone. > {code} > $ cordova -v > 5.4.1 > $ cordova create foo > $ cd foo > $ cordova platform add windows > $ cordova prepare windows > $ cd platforms/windows/cordova > $ build.bat -r --appx=8.1-phone > {code} > Running it on a windows phone 8.1, the status bar is hidden. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10986) Unable to install npm scoped plugin with cordova-cli@6.1.0
[ https://issues.apache.org/jira/browse/CB-10986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15237543#comment-15237543 ] ASF GitHub Bot commented on CB-10986: - Github user riknoll commented on a diff in the pull request: https://github.com/apache/cordova-lib/pull/425#discussion_r59412823 --- Diff: cordova-lib/src/cordova/plugin.js --- @@ -410,6 +422,9 @@ function getPluginVariables(variables){ } function getVersionFromConfigFile(plugin, cfg){ +if (cordova_util.isScopedRegistryPluginSpec(plugin)) { --- End diff -- Good point > Unable to install npm scoped plugin with cordova-cli@6.1.0 > -- > > Key: CB-10986 > URL: https://issues.apache.org/jira/browse/CB-10986 > Project: Apache Cordova > Issue Type: Bug > Components: CordovaLib >Affects Versions: 6.1.0 >Reporter: Darryl Pogue >Assignee: Richard B Knoll > Labels: regression, reproduced, triaged > > {code} > $ cordova create MyProject > $ cd ./MyProject > $ cordova platform add android > $ cordova plugin add @dpogue/cordova-plugin-crosswalk-webview > Error: Cannot find plugin.xml for plugin 'plugins'. Please try adding it > again. > {code} > This works as expected with cordova@6.0.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-11001) Incorrect docs - "FullScreen" config.xml preference only applies to Android
[ https://issues.apache.org/jira/browse/CB-11001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15237542#comment-15237542 ] ASF GitHub Bot commented on CB-11001: - Github user nikhilkh commented on a diff in the pull request: https://github.com/apache/cordova-docs/pull/576#discussion_r59412777 --- Diff: www/docs/en/dev/config_ref/index.md --- @@ -255,7 +255,7 @@ platform. See [Customize icons topic](images.html) for more information. EnableWebGL(boolean) | *Default: false* ==OS X **4.0.0**== Set to true to enable WebGL on the web view. ErrorUrl(URL) | *Default: null* ==Android== If set, will display the referenced page upon an error in the application instead of a dialog with the title "Application Error". ErrorUrl(string) | ==iOS== If set, will display the referenced local page upon an error in the application. - FullScreen(boolean) | *Default: false* Allows you to hide the status bar at the top of the screen. + FullScreen(boolean) | *Default: false* ==Android== Allows you to hide the status bar at the top of the screen. __Note__: Recommended platform-agnostic way to achieve this is to use the [StatusBar plugin](https://cordova.apache.org/docs/en/latest/reference/cordova-plugin-statusbar). --- End diff -- It's recommended to provide a relative reference to the plugin docs as that ensures version and language is correct. > Incorrect docs - "FullScreen" config.xml preference only applies to Android > --- > > Key: CB-11001 > URL: https://issues.apache.org/jira/browse/CB-11001 > Project: Apache Cordova > Issue Type: Bug > Components: Docs >Reporter: Jerroyd Moore >Assignee: Sergey Shakhnazarov > Labels: triaged > > The is ignored when I add it > and build for 8.1-phone. > {code} > $ cordova -v > 5.4.1 > $ cordova create foo > $ cd foo > $ cordova platform add windows > $ cordova prepare windows > $ cd platforms/windows/cordova > $ build.bat -r --appx=8.1-phone > {code} > Running it on a windows phone 8.1, the status bar is hidden. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10986) Unable to install npm scoped plugin with cordova-cli@6.1.0
[ https://issues.apache.org/jira/browse/CB-10986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15237541#comment-15237541 ] ASF GitHub Bot commented on CB-10986: - Github user riknoll commented on a diff in the pull request: https://github.com/apache/cordova-lib/pull/425#discussion_r59412652 --- Diff: cordova-lib/src/cordova/util.js --- @@ -401,3 +407,48 @@ function getAvailableNpmVersions(module_name) { }); }); } + +/** + * Extracts the name and spec from an npm style package spec that follows the + * format of (@scope/)?package(@spec)? + * @param {String} raw The raw npm style package spec + * @returns {String[]} An array containing the package name with optional scope + * followed by the plugin spec (either value may be null + * if not matched) + */ +function parseRegistryPluginSpec(raw) { +var split = NPM_SPEC_REGEX.exec(raw); +if (split) { +var package = split[1] ? split[1] + split[2] : split[2]; +var version = split[3] || null; +return [package, version]; +} else { +return [null, null]; +} +} + +/** + * Extracts the package name from an npm style package spec of the format + * (@scope/)?package(@spec)?. Useful for getting the id used for directories + * created for install + * @param {String} raw The raw npm style package spec + * @returns {String}The package name without scope or version or the original + * string if it isn't an npm package spec + */ +function extractPluginId(raw) { +var split = NPM_SPEC_REGEX.exec(raw); +return split ? split[2] : raw; +} + + +/** + * Determines if a string is a package spec of the format @scope/package(@spec)? + * or not + * @param {String} raw The raw npm style package spec + * @returns {boolean} True if the given string follows the format of an npm style + * package spec or false otherwise + */ +function isScopedRegistryPluginSpec(raw) { --- End diff -- This function was provided to match the existing checks we do for `isDirectory`, `isUrl`, etc in the plugin code. I'm fine with unifying the API though, since three functions is probably unnecessary. > Unable to install npm scoped plugin with cordova-cli@6.1.0 > -- > > Key: CB-10986 > URL: https://issues.apache.org/jira/browse/CB-10986 > Project: Apache Cordova > Issue Type: Bug > Components: CordovaLib >Affects Versions: 6.1.0 >Reporter: Darryl Pogue >Assignee: Richard B Knoll > Labels: regression, reproduced, triaged > > {code} > $ cordova create MyProject > $ cd ./MyProject > $ cordova platform add android > $ cordova plugin add @dpogue/cordova-plugin-crosswalk-webview > Error: Cannot find plugin.xml for plugin 'plugins'. Please try adding it > again. > {code} > This works as expected with cordova@6.0.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10951) Android audio focus should be respected
[ https://issues.apache.org/jira/browse/CB-10951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15237539#comment-15237539 ] Fabrice Lebas commented on CB-10951: Yes, I tested this with phone calls and skype calls. Audio stops properly on these evens and resumes afterwards. > Android audio focus should be respected > --- > > Key: CB-10951 > URL: https://issues.apache.org/jira/browse/CB-10951 > Project: Apache Cordova > Issue Type: Improvement > Components: Android, Plugin Media >Affects Versions: Master > Environment: Android >Reporter: Fabrice Lebas >Assignee: Joe Bowser > Original Estimate: 48h > Remaining Estimate: 48h > > Playing a media will not stop other applications that are already playing a > media. Other applications playing a media will not cause cordova to stop > playing its media. This is because the audio focus logic is not implemented. > This results in both applications playing audio at the same time. Although > this behaviour is valid (sound effects, notifications) this is not the > expected behavior for most applications playing a media. -- 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-10937) Icons are more than stretched since cordova-android 5.1.0
[ https://issues.apache.org/jira/browse/CB-10937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15237467#comment-15237467 ] Maciej Jaros commented on CB-10937: --- Hi. When should this fix be available? Not sure how plugin versioning works now (upgrading from PG 3.7 ;-)). > Icons are more than stretched since cordova-android 5.1.0 > - > > Key: CB-10937 > URL: https://issues.apache.org/jira/browse/CB-10937 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin InAppBrowser > Environment: android >Reporter: Alexis Kofman > Labels: android, inappbrowser > > Since cordova-android@5.0.1 and more especially this commit > https://github.com/apache/cordova-android/commit/73fd9e4dfa5dffde2eb14ebd6c736ca462d1e29f, > the theme has been updated. > The inappbrowser plugin use images as background property of Button views. > So, depending on default margin values in the Theme, background images can be > stretched. > A fix could be to use ImageButton views instead and chose a scaleType if > needed. > Here is what we have today using a version of cordova-android >= 5.1.0 : > !https://cloud.githubusercontent.com/assets/579922/13982920/e81236c8-f0ec-11e5-9eeb-f969cba3b375.png|width=100%! -- 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-10950) Phonegap app in the background when capture and select image for gallery app stop/restart.
[ https://issues.apache.org/jira/browse/CB-10950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15237382#comment-15237382 ] ignacio Chiazzo commented on CB-10950: --- [~riknoll] it didn´t work, when the app is killed by the SO, the app will never go to the action onResume, this action is only executed when the app is on pause and the SO didn't kill the app (take a look at http://developer.android.com/reference/android/app/Activity.html). Theoretically when the app is killed, and the so want to restore the activity, the onCreate is executed and not the onResume. I tried using the onCreate function but it didn't work. Any of you found a solution to this problem, and want to share a example? > Phonegap app in the background when capture and select image for gallery app > stop/restart. > --- > > Key: CB-10950 > URL: https://issues.apache.org/jira/browse/CB-10950 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Camera >Affects Versions: 5.0.1 >Reporter: Lokesh Patel > Labels: android, triaged, wfc > > Hi, > In android application when the user tries for capturing images and select > image from gallery app stop/restart. > I found below details after search lots of google and forums: > " The Phonegap (Cordova) Camera Plugin calls the native camera and this makes > Android Garbage Collector to kill background applications." > Thanks, > Lokesh Patel -- 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-11069) CDVViewController appURL is nil if wwwFolderName is the path to a framework
[ https://issues.apache.org/jira/browse/CB-11069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15237233#comment-15237233 ] ASF GitHub Bot commented on CB-11069: - GitHub user mirkoluchi opened a pull request: https://github.com/apache/cordova-ios/pull/217 CB-11069 - CDVViewController appURL is nil if wwwFolderName is the path to a framework Fix -[CDVViewController appUrl] method to take into account a wwwFolderName which is a framework You can merge this pull request into a Git repository by running: $ git pull https://github.com/mirkoluchi/cordova-ios feature/CB-11069 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-ios/pull/217.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 #217 commit 6ab3a773985bd3cbbf61e26e762f23415925533a Author: Mirko LuchiDate: 2016-04-12T14:15:36Z CB-11069 - CDVViewController appURL is nil if wwwFolderName is the path to a framework Fix -[CDVViewController appUrl] method to take into account a wwwFolderName which is a framework > CDVViewController appURL is nil if wwwFolderName is the path to a framework > --- > > Key: CB-11069 > URL: https://issues.apache.org/jira/browse/CB-11069 > Project: Apache Cordova > Issue Type: Bug > Components: CordovaLib >Affects Versions: 3.5.0 >Reporter: Mirko Luchi >Priority: Minor > > The -appUrl method of the CDVViewController doesn't take into account the > case where the wwwFolderName property is set to the path of a framework, > falling back to method -[CDVCommandDelegate pathForResource:], which returns > nil. -- 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-11069) CDVViewController appURL is nil if wwwFolderName is the path to a framework
Mirko Luchi created CB-11069: Summary: CDVViewController appURL is nil if wwwFolderName is the path to a framework Key: CB-11069 URL: https://issues.apache.org/jira/browse/CB-11069 Project: Apache Cordova Issue Type: Bug Reporter: Mirko Luchi Priority: Minor The -appUrl method of the CDVViewController doesn't take into account the case where the wwwFolderName property is set to the path of a framework, falling back to method -[CDVCommandDelegate pathForResource:], which returns nil. -- 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-11069) CDVViewController appURL is nil if wwwFolderName is the path to a framework
[ https://issues.apache.org/jira/browse/CB-11069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mirko Luchi updated CB-11069: - Affects Version/s: 3.5.0 Component/s: CordovaLib > CDVViewController appURL is nil if wwwFolderName is the path to a framework > --- > > Key: CB-11069 > URL: https://issues.apache.org/jira/browse/CB-11069 > Project: Apache Cordova > Issue Type: Bug > Components: CordovaLib >Affects Versions: 3.5.0 >Reporter: Mirko Luchi >Priority: Minor > > The -appUrl method of the CDVViewController doesn't take into account the > case where the wwwFolderName property is set to the path of a framework, > falling back to method -[CDVCommandDelegate pathForResource:], which returns > nil. -- 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-10702) Android SplashMaintainAspectRatio not work
[ https://issues.apache.org/jira/browse/CB-10702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Shakhnazarov updated CB-10702: - Labels: android no-repro triaged (was: android triaged) > Android SplashMaintainAspectRatio not work > -- > > Key: CB-10702 > URL: https://issues.apache.org/jira/browse/CB-10702 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin SplashScreen >Reporter: Matteo Romanelli >Priority: Minor > Labels: android, no-repro, triaged > > The splash screen is loaded and the delay work well but it is deformed. > I'm using > apache cordova: 4.3.0 > splashscreen plugin version: 3.2.1-dev > visual studio community 2015 > android 5.1.1 and others > i have tried this 2 configurations: > FIRST: all the preference out > > > > > > > > > > > > > > > SECOND: specific reference in > > > > > > > > > > > > > > -- 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-10702) Android SplashMaintainAspectRatio not work
[ https://issues.apache.org/jira/browse/CB-10702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15237201#comment-15237201 ] Sergey Shakhnazarov commented on CB-10702: -- Cannot reproduce on the latest (master) plugin version and latest published cordova-android. [~L4B], could you please share a test project if this is still actual? > Android SplashMaintainAspectRatio not work > -- > > Key: CB-10702 > URL: https://issues.apache.org/jira/browse/CB-10702 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin SplashScreen >Reporter: Matteo Romanelli >Priority: Minor > Labels: android, no-repro, triaged, wfc > > The splash screen is loaded and the delay work well but it is deformed. > I'm using > apache cordova: 4.3.0 > splashscreen plugin version: 3.2.1-dev > visual studio community 2015 > android 5.1.1 and others > i have tried this 2 configurations: > FIRST: all the preference out > > > > > > > > > > > > > > > SECOND: specific reference in > > > > > > > > > > > > > > -- 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-10702) Android SplashMaintainAspectRatio not work
[ https://issues.apache.org/jira/browse/CB-10702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Shakhnazarov updated CB-10702: - Labels: android no-repro triaged wfc (was: android no-repro triaged) > Android SplashMaintainAspectRatio not work > -- > > Key: CB-10702 > URL: https://issues.apache.org/jira/browse/CB-10702 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin SplashScreen >Reporter: Matteo Romanelli >Priority: Minor > Labels: android, no-repro, triaged, wfc > > The splash screen is loaded and the delay work well but it is deformed. > I'm using > apache cordova: 4.3.0 > splashscreen plugin version: 3.2.1-dev > visual studio community 2015 > android 5.1.1 and others > i have tried this 2 configurations: > FIRST: all the preference out > > > > > > > > > > > > > > > SECOND: specific reference in > > > > > > > > > > > > > > -- 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-6992) iOS platform add/prepare fails if app display name contains unicode characters.
[ https://issues.apache.org/jira/browse/CB-6992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15237092#comment-15237092 ] ASF GitHub Bot commented on CB-6992: GitHub user tony-- opened a pull request: https://github.com/apache/cordova-ios/pull/216 CB-6992 Fix non-working create case, add new test Added name normalization from prepare to createProject in order to support the case where the user edits name in config.xml, then adds ios platform to project. Also added a new test since the existing test was passing. The new test used a different unicode string. It fails without this fix and passes with this fix. Please see [this JIRA comment](https://issues.apache.org/jira/browse/CB-6992?focusedCommentId=15237088=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15237088) for additional background info. You can merge this pull request into a Git repository by running: $ git pull https://github.com/tony--/cordova-ios CB6992-platform-api-create Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-ios/pull/216.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 #216 commit c2a4ebbf81f3b088bb00ebaf499e0068337ff6ab Author: Tony HomerDate: 2016-04-11T20:27:59Z CB-6992 Fix non-working create case, add new test > iOS platform add/prepare fails if app display name contains unicode > characters. > --- > > Key: CB-6992 > URL: https://issues.apache.org/jira/browse/CB-6992 > Project: Apache Cordova > Issue Type: Bug > Components: CLI >Affects Versions: 3.5.0 > Environment: uname: Darwin 13.1.0 Darwin Kernel Version 13.1.0: Thu > Jan 16 19:40:37 PST 2014; root:xnu-2422.90.20~2/RELEASE_X86_64 x86_64 > cordova-dev -v: 3.5.0-0.2.4 > cordova-lib: 0.21.3 > Node 0.10.26 > iOS >Reporter: Vladimir Kotikov >Assignee: Shazron Abdullah >Priority: Critical > Labels: cli, configParser, cordova-ios-4.0.x, ios, ios-deploy > > Repro steps: > # cordova create test-umlaÜt com.test.umlaÜt umlaÜt > # cd test-umlaÜt/ > # cordova platform add ios > Platform add fails with following error: > {noformat} > mv: dest file already exists: > /Users/user/test/test-umlaÜt/platforms/ios/umlaÜt/umlaÜt-Info.plist > mv: dest file already exists: > /Users/user/test/test-umlaÜt/platforms/ios/umlaÜt/umlaÜt-Prefix.pch > shell.js: internal error > Error: EINVAL, invalid argument > '/Users/user/test/test-umlaÜt/platforms/ios/umlaÜt.xcodeproj' > at Object.fs.renameSync (fs.js:543:18) > at > /usr/local/lib/node_modules/cordova/node_modules/cordova-lib/node_modules/shelljs/shell.js:495:8 > at Array.forEach (native) > at Object._mv > (/usr/local/lib/node_modules/cordova/node_modules/cordova-lib/node_modules/shelljs/shell.js:471:11) > at Object.mv > (/usr/local/lib/node_modules/cordova/node_modules/cordova-lib/node_modules/shelljs/shell.js:1491:23) > at pbxProject. > (/usr/local/lib/node_modules/cordova/node_modules/cordova-lib/src/cordova/metadata/ios_parser.js:145:27) > at pbxProject.EventEmitter.emit (events.js:98:17) > at pbxProject. > (/usr/local/lib/node_modules/cordova/node_modules/cordova-lib/node_modules/xcode/lib/pbxProject.js:30:18) > at ChildProcess.EventEmitter.emit (events.js:98:17) > at handleMessage (child_process.js:318:10) > {noformat} -- 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-10962) cordova run ios hangs on safequit
[ https://issues.apache.org/jira/browse/CB-10962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15237089#comment-15237089 ] ASF GitHub Bot commented on CB-10962: - Github user akofman closed the pull request at: https://github.com/apache/cordova-ios/pull/212 > cordova run ios hangs on safequit > - > > Key: CB-10962 > URL: https://issues.apache.org/jira/browse/CB-10962 > Project: Apache Cordova > Issue Type: Bug > Components: iOS >Affects Versions: 6.1.0 > Environment: OSX 10.11.4 >Reporter: Mike Hartington >Priority: Critical > Labels: triaged > > Creating a fresh cordova project with cordova-cli 6.1.0, you can't deploy to > a physical device from the command line > steps to reproduce. > {code} > cordova create testProject > cd testProject > cordova platform add ios > cordova run ios > {code} > you should be able to deploy, but the app will hang at the splashscreen and > not boot. The CLI will just print out > {code} > (lldb) command script add -s asynchronous -f > fruitstrap_123e4ad9c89eea2666bd159b569f670a1f5b99c6.safequit_command safequit > (lldb) connect > (lldb) run > success > (lldb) safequit > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-6992) iOS platform add/prepare fails if app display name contains unicode characters.
[ https://issues.apache.org/jira/browse/CB-6992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15237088#comment-15237088 ] Tony Homer commented on CB-6992: Downstream in Intel XDK, we had a user report an issue with building an app with an arabic name. I reproduced the issue using Cordova CLI: 1. Create a new project using CLI (`cordova create arabic-test-cli`) 2. Edit config.xml, change name to: إثرا 3. `cordova platform add ios@4.0.1` 4. `cordova build ios --device` (xcodebuild: error: The project 'إثرا.xcodeproj' does not contain a target named 'إثرا'.) 5. Build fails After some experimenting I found that build succeeds if the platform is added before editing the name in config.xml. 1. Create a new project using CLI (`cordova create arabic-test-cli`) 2. `cordova platform add ios@4.0.1` 3. Edit config.xml, change name to: إثرا 4. `cordova prepare ios` 5. `cordova build ios --device` 6. Build succeeds (** BUILD SUCCEEDED ** ... Results at '/Users/ajhomer/arabic-test-cli-2/platforms/ios/build/device/إثرا.ipa') This made me suspect a discrepancy between name handling in create and prepare. I compared name handling in prepare and create and noticed that the name is normalized by prepare but not by createPlatform. Applying the name normalization from prepare to create makes the above fail steps succeed. I'm not sure why the existing unicode create tests pass (e.g., 'create project with unicode name, no spaces') but since they do, I added a new test using the string from my test case. This test fails without name normalization on create. Adding name normalization makes the test pass. I'll open a PR with these 2 changes (name normalization on create and new create name test). > iOS platform add/prepare fails if app display name contains unicode > characters. > --- > > Key: CB-6992 > URL: https://issues.apache.org/jira/browse/CB-6992 > Project: Apache Cordova > Issue Type: Bug > Components: CLI >Affects Versions: 3.5.0 > Environment: uname: Darwin 13.1.0 Darwin Kernel Version 13.1.0: Thu > Jan 16 19:40:37 PST 2014; root:xnu-2422.90.20~2/RELEASE_X86_64 x86_64 > cordova-dev -v: 3.5.0-0.2.4 > cordova-lib: 0.21.3 > Node 0.10.26 > iOS >Reporter: Vladimir Kotikov >Assignee: Shazron Abdullah >Priority: Critical > Labels: cli, configParser, cordova-ios-4.0.x, ios, ios-deploy > > Repro steps: > # cordova create test-umlaÜt com.test.umlaÜt umlaÜt > # cd test-umlaÜt/ > # cordova platform add ios > Platform add fails with following error: > {noformat} > mv: dest file already exists: > /Users/user/test/test-umlaÜt/platforms/ios/umlaÜt/umlaÜt-Info.plist > mv: dest file already exists: > /Users/user/test/test-umlaÜt/platforms/ios/umlaÜt/umlaÜt-Prefix.pch > shell.js: internal error > Error: EINVAL, invalid argument > '/Users/user/test/test-umlaÜt/platforms/ios/umlaÜt.xcodeproj' > at Object.fs.renameSync (fs.js:543:18) > at > /usr/local/lib/node_modules/cordova/node_modules/cordova-lib/node_modules/shelljs/shell.js:495:8 > at Array.forEach (native) > at Object._mv > (/usr/local/lib/node_modules/cordova/node_modules/cordova-lib/node_modules/shelljs/shell.js:471:11) > at Object.mv > (/usr/local/lib/node_modules/cordova/node_modules/cordova-lib/node_modules/shelljs/shell.js:1491:23) > at pbxProject. > (/usr/local/lib/node_modules/cordova/node_modules/cordova-lib/src/cordova/metadata/ios_parser.js:145:27) > at pbxProject.EventEmitter.emit (events.js:98:17) > at pbxProject. > (/usr/local/lib/node_modules/cordova/node_modules/cordova-lib/node_modules/xcode/lib/pbxProject.js:30:18) > at ChildProcess.EventEmitter.emit (events.js:98:17) > at handleMessage (child_process.js:318:10) > {noformat} -- 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-11068) Application getting crashed on Android, iOS and Windows(Universal) when more than 20 images are captured using BASE64 DATA URL format.
COE created CB-11068: Summary: Application getting crashed on Android, iOS and Windows(Universal) when more than 20 images are captured using BASE64 DATA URL format. Key: CB-11068 URL: https://issues.apache.org/jira/browse/CB-11068 Project: Apache Cordova Issue Type: Bug Components: Plugin Camera Affects Versions: 3.5.0 Environment: Android, Windows and iOS mobiles Reporter: COE Priority: Critical We have used Cordova for our hybrid mobile application targeting multiple platforms with usage of Camera Plugin. After a certain no of images are captured, the camera feature is getting crashed and application is becoming inaccessible. Please suggest us a possible solution. -- 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-10709) Allow-navigation rule for iFrame urls on cordova-ios
[ https://issues.apache.org/jira/browse/CB-10709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15237028#comment-15237028 ] Juuso Karjalainen edited comment on CB-10709 at 4/12/16 11:46 AM: -- Anyone got a solution for this? I am having the same issue. [~harshabonthu] you said you have a solution and that you're going to create a PR but I couldn't find one. Did you create one or can I hear from you directly that what is the solution to this problem (Other than downgrading to lower cordova-ios version)? was (Author: thepio): Anyone got a solution for this? I am having the same issue. [~harshabonthu] you said you have a solution and that you're going to create a PR but I couldn't find one. Did you do one or can I hear from you directly that what is the solution (Other than downgrading to lower cordova-ios version)? > Allow-navigation rule for iFrame urls on cordova-ios > > > Key: CB-10709 > URL: https://issues.apache.org/jira/browse/CB-10709 > Project: Apache Cordova > Issue Type: Bug > Components: iOS, Plugin Whitelist >Affects Versions: 6.0.0 >Reporter: Harsha Kiran > Labels: cordova-ios-4.1.1, triaged > > Currently with Whitelist plugin set to
[jira] [Commented] (CB-10709) Allow-navigation rule for iFrame urls on cordova-ios
[ https://issues.apache.org/jira/browse/CB-10709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15237028#comment-15237028 ] Juuso Karjalainen commented on CB-10709: Anyone got a solution for this? I am having the same issue. [~harshabonthu] you said you have a solution and that you're going to create a PR but I couldn't find one. Did you do one or can I hear from you directly that what is the solution (Other than downgrading to lower cordova-ios version)? > Allow-navigation rule for iFrame urls on cordova-ios > > > Key: CB-10709 > URL: https://issues.apache.org/jira/browse/CB-10709 > Project: Apache Cordova > Issue Type: Bug > Components: iOS, Plugin Whitelist >Affects Versions: 6.0.0 >Reporter: Harsha Kiran > Labels: cordova-ios-4.1.1, triaged > > Currently with Whitelist plugin set to
[jira] [Commented] (CB-11010) Unexpected EOF while finding contacts in iPhone 6s
[ https://issues.apache.org/jira/browse/CB-11010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15237018#comment-15237018 ] Sergey Shakhnazarov commented on CB-11010: -- Note: This does not reproduce on iPhone6+ and iPad Pro 9.2.1 devices. > Unexpected EOF while finding contacts in iPhone 6s > -- > > Key: CB-11010 > URL: https://issues.apache.org/jira/browse/CB-11010 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Contacts >Affects Versions: 2.0.0 > Environment: iOS 9.2.1, iOS 9.3 in iPhone 6s >Reporter: Gowtham > Labels: iOS, mustfix, triaged > > I tried accessing the contacts using contacts plugin v2.0.1 with the > following code > var options = new ContactFindOptions(); > options.filter = ""; > options.multiple = true; > var fields = ["displayName","phoneNumbers"]; > > navigator.contacts.find(fields, gotContacts, errorHandler, options); > This throws me an SyntaxError: Unexpected EOF in iPhone 6s models. > I tested the same in iPhone 5s and iPhone 6, this works fine. Also it works > fine in iPhone 6s Simulator. > I tested in three iPhone 6s phones where the iOS is 9.3 for two phones and > 9.2.1 for one. > All three phones have contacts more than 400. > All three returned me the same error. -- 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-11001) Incorrect docs - "FullScreen" config.xml preference only applies to Android
[ https://issues.apache.org/jira/browse/CB-11001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15237012#comment-15237012 ] ASF GitHub Bot commented on CB-11001: - GitHub user daserge opened a pull request: https://github.com/apache/cordova-docs/pull/576 CB-11001 Incorrect docs - "FullScreen" config.xml preference only app… …lies to Android [Jira issue](https://issues.apache.org/jira/browse/CB-11001) You can merge this pull request into a Git repository by running: $ git pull https://github.com/MSOpenTech/cordova-docs CB-11001 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-docs/pull/576.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 #576 commit 375e6f56318604073ff52d82dc0fc8adc8962bdf Author: dasergeDate: 2016-04-12T11:25:22Z CB-11001 Incorrect docs - "FullScreen" config.xml preference only applies to Android > Incorrect docs - "FullScreen" config.xml preference only applies to Android > --- > > Key: CB-11001 > URL: https://issues.apache.org/jira/browse/CB-11001 > Project: Apache Cordova > Issue Type: Bug > Components: Docs >Reporter: Jerroyd Moore >Assignee: Sergey Shakhnazarov > Labels: triaged > > The is ignored when I add it > and build for 8.1-phone. > {code} > $ cordova -v > 5.4.1 > $ cordova create foo > $ cd foo > $ cordova platform add windows > $ cordova prepare windows > $ cd platforms/windows/cordova > $ build.bat -r --appx=8.1-phone > {code} > Running it on a windows phone 8.1, the status bar is hidden. -- 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-11067) Content-Length missing in multipart form upload header on Android
[ https://issues.apache.org/jira/browse/CB-11067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Odd Christer Brovig updated CB-11067: - Description: On iOS Content-Length is sent as part of header for multipart form. On Android only Content-Disposition and Content-Type is sent. Is there a special reason for this? I see that the file size is read after the beforeData is converted to bytes. >From FileTransfer.java: {code:java} beforeData.append(LINE_START).append(BOUNDARY).append(LINE_END); beforeData.append("Content-Disposition: form-data; name=\"").append(fileKey).append("\";"); beforeData.append(" filename=\"").append(fileName).append('"').append(LINE_END); beforeData.append("Content-Type: ").append(mimeType).append(LINE_END).append(LINE_END); byte[] beforeDataBytes = beforeData.toString().getBytes("UTF-8"); byte[] tailParamsBytes = (LINE_END + LINE_START + BOUNDARY + LINE_START + LINE_END).getBytes("UTF-8"); {code} >From CDVFileTransfer.m: {code} [postBodyBeforeFile appendData:formBoundaryData]; [postBodyBeforeFile appendData:[[NSString stringWithFormat:@"Content-Disposition: form-data; name=\"%@\"; filename=\"%@\"\r\n", fileKey, fileName] dataUsingEncoding:NSUTF8StringEncoding]]; if (mimeType != nil) { [postBodyBeforeFile appendData:[[NSString stringWithFormat:@"Content-Type: %@\r\n", mimeType] dataUsingEncoding:NSUTF8StringEncoding]]; } [postBodyBeforeFile appendData:[[NSString stringWithFormat:@"Content-Length: %ld\r\n\r\n", (long)[fileData length]] dataUsingEncoding:NSUTF8StringEncoding]]; {code} was: On iOS Content-Length is sent as part of header for multipart form. On Android only Content-Disposition and Content-Type is sent. Is there a special reason for this? I see that the file size is read after the beforeData is converted to bytes. >From FileTransfer.java: ``` beforeData.append(LINE_START).append(BOUNDARY).append(LINE_END); beforeData.append("Content-Disposition: form-data; name=\"").append(fileKey).append("\";"); beforeData.append(" filename=\"").append(fileName).append('"').append(LINE_END); beforeData.append("Content-Type: ").append(mimeType).append(LINE_END).append(LINE_END); byte[] beforeDataBytes = beforeData.toString().getBytes("UTF-8"); byte[] tailParamsBytes = (LINE_END + LINE_START + BOUNDARY + LINE_START + LINE_END).getBytes("UTF-8"); ``` >From CDVFileTransfer.m: ``` [postBodyBeforeFile appendData:formBoundaryData]; [postBodyBeforeFile appendData:[[NSString stringWithFormat:@"Content-Disposition: form-data; name=\"%@\"; filename=\"%@\"\r\n", fileKey, fileName] dataUsingEncoding:NSUTF8StringEncoding]]; if (mimeType != nil) { [postBodyBeforeFile appendData:[[NSString stringWithFormat:@"Content-Type: %@\r\n", mimeType] dataUsingEncoding:NSUTF8StringEncoding]]; } [postBodyBeforeFile appendData:[[NSString stringWithFormat:@"Content-Length: %ld\r\n\r\n", (long)[fileData length]] dataUsingEncoding:NSUTF8StringEncoding]]; ``` > Content-Length missing in multipart form upload header on Android > - > > Key: CB-11067 > URL: https://issues.apache.org/jira/browse/CB-11067 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin File Transfer > Environment: Plugin version 1.5.0 > chunked = false >Reporter: Odd Christer Brovig > > On iOS Content-Length is sent as part of header for multipart form. On > Android only Content-Disposition and Content-Type is sent. > Is there a special reason for this? I see that the file size is read after > the beforeData is converted to bytes. > From FileTransfer.java: > {code:java} > > beforeData.append(LINE_START).append(BOUNDARY).append(LINE_END); > beforeData.append("Content-Disposition: form-data; > name=\"").append(fileKey).append("\";"); > beforeData.append(" > filename=\"").append(fileName).append('"').append(LINE_END); > beforeData.append("Content-Type: > ").append(mimeType).append(LINE_END).append(LINE_END); > byte[] beforeDataBytes = > beforeData.toString().getBytes("UTF-8"); > byte[] tailParamsBytes = (LINE_END + LINE_START + > BOUNDARY + LINE_START + LINE_END).getBytes("UTF-8"); > {code} > From CDVFileTransfer.m: > {code} > [postBodyBeforeFile appendData:formBoundaryData]; > [postBodyBeforeFile appendData:[[NSString > stringWithFormat:@"Content-Disposition: form-data; name=\"%@\"; > filename=\"%@\"\r\n", fileKey, fileName] >
[jira] [Created] (CB-11067) Content-Length missing in multipart form upload header on Android
Odd Christer Brovig created CB-11067: Summary: Content-Length missing in multipart form upload header on Android Key: CB-11067 URL: https://issues.apache.org/jira/browse/CB-11067 Project: Apache Cordova Issue Type: Bug Components: Plugin File Transfer Environment: Plugin version 1.5.0 chunked = false Reporter: Odd Christer Brovig On iOS Content-Length is sent as part of header for multipart form. On Android only Content-Disposition and Content-Type is sent. Is there a special reason for this? I see that the file size is read after the beforeData is converted to bytes. >From FileTransfer.java: ``` beforeData.append(LINE_START).append(BOUNDARY).append(LINE_END); beforeData.append("Content-Disposition: form-data; name=\"").append(fileKey).append("\";"); beforeData.append(" filename=\"").append(fileName).append('"').append(LINE_END); beforeData.append("Content-Type: ").append(mimeType).append(LINE_END).append(LINE_END); byte[] beforeDataBytes = beforeData.toString().getBytes("UTF-8"); byte[] tailParamsBytes = (LINE_END + LINE_START + BOUNDARY + LINE_START + LINE_END).getBytes("UTF-8"); ``` >From CDVFileTransfer.m: ``` [postBodyBeforeFile appendData:formBoundaryData]; [postBodyBeforeFile appendData:[[NSString stringWithFormat:@"Content-Disposition: form-data; name=\"%@\"; filename=\"%@\"\r\n", fileKey, fileName] dataUsingEncoding:NSUTF8StringEncoding]]; if (mimeType != nil) { [postBodyBeforeFile appendData:[[NSString stringWithFormat:@"Content-Type: %@\r\n", mimeType] dataUsingEncoding:NSUTF8StringEncoding]]; } [postBodyBeforeFile appendData:[[NSString stringWithFormat:@"Content-Length: %ld\r\n\r\n", (long)[fileData length]] dataUsingEncoding:NSUTF8StringEncoding]]; ``` -- 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-11022) Adding plugins prepares platforms, which is redundant and slow
[ https://issues.apache.org/jira/browse/CB-11022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15236943#comment-15236943 ] ASF GitHub Bot commented on CB-11022: - Github user vladimir-kotikov commented on the pull request: https://github.com/apache/cordova-lib/pull/423#issuecomment-208828579 > do we also need changes to iOS and Windows platforms Exactly. Changes for windows and iOS is on their go > Adding plugins prepares platforms, which is redundant and slow > -- > > Key: CB-11022 > URL: https://issues.apache.org/jira/browse/CB-11022 > Project: Apache Cordova > Issue Type: Bug > Components: CordovaLib >Reporter: Jason Ginchereau >Assignee: Vladimir Kotikov > Labels: triaged > > For CB-9617, a change was made to automatically do a 'cordova prepare' > operation after adding every plugin. As part of the prepare, all the files > from the project's www directory are re-copied into the platform_www > directory. For a large project with lots of source files, images, and other > resources, this copy operation is potentially time-consuming. And it is > redundant and unnecessary when adding a plugin, because those files do not > need to be changed when adding a plugin. > For a large project with many plugins, this slow redundant operation is > repeated for every plugin, making the first-time build (installing all the > plugins) take a very long time. As an extreme case, a customer reported their > large project (35 plugins, ~150 MB in www) takes about 2 hours to build the > first time. Most of that time is spent repeatedly preparing the platforms > after adding each plugin. The log line that appears to be slow says it is > "Generating config.xml from defaults for platform ", but what it is > actually doing is redundantly copying lots of files from www. > This issue can also be observed at a smaller scale when building the Cordova > mobilespec project, which contains tests for all the core plugins. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10986) Unable to install npm scoped plugin with cordova-cli@6.1.0
[ https://issues.apache.org/jira/browse/CB-10986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15236937#comment-15236937 ] ASF GitHub Bot commented on CB-10986: - Github user vladimir-kotikov commented on the pull request: https://github.com/apache/cordova-lib/pull/425#issuecomment-208825623 As a general comment, i'd love to see the methods for dealing with plugin spec returning a structured result instead of an array. This IMO would make the code more readable, as it's really hard to follow, what e.g. `parseRegistryPluginSpec(target)[0]` means. Also, factoring this into a separate class could help to improve readability. Something like `PluginSpec.parse(target).version`is much more easy to understand, at least personally for me :) > Unable to install npm scoped plugin with cordova-cli@6.1.0 > -- > > Key: CB-10986 > URL: https://issues.apache.org/jira/browse/CB-10986 > Project: Apache Cordova > Issue Type: Bug > Components: CordovaLib >Affects Versions: 6.1.0 >Reporter: Darryl Pogue >Assignee: Richard B Knoll > Labels: regression, reproduced, triaged > > {code} > $ cordova create MyProject > $ cd ./MyProject > $ cordova platform add android > $ cordova plugin add @dpogue/cordova-plugin-crosswalk-webview > Error: Cannot find plugin.xml for plugin 'plugins'. Please try adding it > again. > {code} > This works as expected with cordova@6.0.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10986) Unable to install npm scoped plugin with cordova-cli@6.1.0
[ https://issues.apache.org/jira/browse/CB-10986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15236926#comment-15236926 ] ASF GitHub Bot commented on CB-10986: - Github user vladimir-kotikov commented on a diff in the pull request: https://github.com/apache/cordova-lib/pull/425#discussion_r59349270 --- Diff: cordova-lib/src/plugman/uninstall.js --- @@ -145,10 +145,9 @@ module.exports.uninstallPlugin = function(id, plugins_dir, options) { var deps = pluginInfo.getDependencies(); var deps_path; deps.forEach(function (d) { -var splitVersion = d.id.split('@'); -deps_path = path.join(plugin_dir, '..', splitVersion[0]); +deps_path = path.join(plugin_dir, '..', cordovaUtil.extractPluginId(d.id)); if (!fs.existsSync(deps_path)) { -var newId = pluginMapper[splitVersion[0]]; +var newId = pluginMapper[cordovaUtil.parseRegistryPluginSpec(d.id)[0] || d.id]; --- End diff -- You use `extractPluginId` in L148 but `parseRegistryPluginSpec` here but they will return different results in case if there is a scoped dependency in plugin.xml. Is that intentional? > Unable to install npm scoped plugin with cordova-cli@6.1.0 > -- > > Key: CB-10986 > URL: https://issues.apache.org/jira/browse/CB-10986 > Project: Apache Cordova > Issue Type: Bug > Components: CordovaLib >Affects Versions: 6.1.0 >Reporter: Darryl Pogue >Assignee: Richard B Knoll > Labels: regression, reproduced, triaged > > {code} > $ cordova create MyProject > $ cd ./MyProject > $ cordova platform add android > $ cordova plugin add @dpogue/cordova-plugin-crosswalk-webview > Error: Cannot find plugin.xml for plugin 'plugins'. Please try adding it > again. > {code} > This works as expected with cordova@6.0.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10986) Unable to install npm scoped plugin with cordova-cli@6.1.0
[ https://issues.apache.org/jira/browse/CB-10986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15236921#comment-15236921 ] ASF GitHub Bot commented on CB-10986: - Github user vladimir-kotikov commented on a diff in the pull request: https://github.com/apache/cordova-lib/pull/425#discussion_r59347954 --- Diff: cordova-lib/src/plugman/install.js --- @@ -90,35 +90,37 @@ module.exports = function installPlugin(platform, project_dir, id, plugins_dir, // Returns a promise. function possiblyFetch(id, plugins_dir, options) { // Split @Version from the plugin id if it exists. -var splitVersion = id.split('@'); +var splitVersion = cordovaUtil.parseRegistryPluginSpec(id); +var extractedId = splitVersion[0] || id; //Check if a mapping exists for the plugin id //if it does, convert id to new name id -var newId = pluginMapper.oldToNew[splitVersion[0]]; +var newId = pluginMapper.oldToNew[extractedId]; --- End diff -- As above, should we pass plugin id instead of scoped id to plugin mapper? > Unable to install npm scoped plugin with cordova-cli@6.1.0 > -- > > Key: CB-10986 > URL: https://issues.apache.org/jira/browse/CB-10986 > Project: Apache Cordova > Issue Type: Bug > Components: CordovaLib >Affects Versions: 6.1.0 >Reporter: Darryl Pogue >Assignee: Richard B Knoll > Labels: regression, reproduced, triaged > > {code} > $ cordova create MyProject > $ cd ./MyProject > $ cordova platform add android > $ cordova plugin add @dpogue/cordova-plugin-crosswalk-webview > Error: Cannot find plugin.xml for plugin 'plugins'. Please try adding it > again. > {code} > This works as expected with cordova@6.0.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10986) Unable to install npm scoped plugin with cordova-cli@6.1.0
[ https://issues.apache.org/jira/browse/CB-10986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15236920#comment-15236920 ] ASF GitHub Bot commented on CB-10986: - Github user vladimir-kotikov commented on a diff in the pull request: https://github.com/apache/cordova-lib/pull/425#discussion_r59347577 --- Diff: cordova-lib/src/plugman/fetch.js --- @@ -205,8 +206,9 @@ function fetchPlugin(plugin_src, plugins_dir, options) { // Helper function for checking expected plugin IDs against reality. function checkID(expectedIdAndVersion, pinfo) { if (!expectedIdAndVersion) return; -var expectedId = expectedIdAndVersion.split('@')[0]; -var expectedVersion = expectedIdAndVersion.split('@')[1]; +var parts = cordovaUtil.parseRegistryPluginSpec(expectedIdAndVersion); +var expectedId = parts[0] || expectedIdAndVersion; +var expectedVersion = parts[1]; if (expectedId != pinfo.id) { --- End diff -- Since you use `parseRegistryPluginSpec`, it is possible that `expectedId` would be specified as `@scope/id`, but from what i understand, pluginInfo.id could not contain scope so this comparison will always be truthy in this case > Unable to install npm scoped plugin with cordova-cli@6.1.0 > -- > > Key: CB-10986 > URL: https://issues.apache.org/jira/browse/CB-10986 > Project: Apache Cordova > Issue Type: Bug > Components: CordovaLib >Affects Versions: 6.1.0 >Reporter: Darryl Pogue >Assignee: Richard B Knoll > Labels: regression, reproduced, triaged > > {code} > $ cordova create MyProject > $ cd ./MyProject > $ cordova platform add android > $ cordova plugin add @dpogue/cordova-plugin-crosswalk-webview > Error: Cannot find plugin.xml for plugin 'plugins'. Please try adding it > again. > {code} > This works as expected with cordova@6.0.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10986) Unable to install npm scoped plugin with cordova-cli@6.1.0
[ https://issues.apache.org/jira/browse/CB-10986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15236905#comment-15236905 ] ASF GitHub Bot commented on CB-10986: - Github user vladimir-kotikov commented on a diff in the pull request: https://github.com/apache/cordova-lib/pull/425#discussion_r59346334 --- Diff: cordova-lib/src/plugman/fetch.js --- @@ -132,8 +132,9 @@ function fetchPlugin(plugin_src, plugins_dir, options) { )); } // If not found in local search path, fetch from the registry. -var splitVersion = plugin_src.split('@'); -var newID = pluginMapperotn[splitVersion[0]]; +var splitVersion = cordovaUtil.parseRegistryPluginSpec(plugin_src); +var oldId = splitVersion[0] || plugin_src; +var newID = pluginMapperotn[oldId]; --- End diff -- Since `oldId` could be either package id or scope + package id i'm not sure how this will work with plugin mapper. Should we use `extractPluginId` instead of `parseRegistryPluginSpec` in L135? > Unable to install npm scoped plugin with cordova-cli@6.1.0 > -- > > Key: CB-10986 > URL: https://issues.apache.org/jira/browse/CB-10986 > Project: Apache Cordova > Issue Type: Bug > Components: CordovaLib >Affects Versions: 6.1.0 >Reporter: Darryl Pogue >Assignee: Richard B Knoll > Labels: regression, reproduced, triaged > > {code} > $ cordova create MyProject > $ cd ./MyProject > $ cordova platform add android > $ cordova plugin add @dpogue/cordova-plugin-crosswalk-webview > Error: Cannot find plugin.xml for plugin 'plugins'. Please try adding it > again. > {code} > This works as expected with cordova@6.0.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10986) Unable to install npm scoped plugin with cordova-cli@6.1.0
[ https://issues.apache.org/jira/browse/CB-10986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15236897#comment-15236897 ] ASF GitHub Bot commented on CB-10986: - Github user vladimir-kotikov commented on a diff in the pull request: https://github.com/apache/cordova-lib/pull/425#discussion_r59345185 --- Diff: cordova-lib/src/cordova/plugin.js --- @@ -410,6 +422,9 @@ function getPluginVariables(variables){ } function getVersionFromConfigFile(plugin, cfg){ +if (cordova_util.isScopedRegistryPluginSpec(plugin)) { --- End diff -- Should we chack for this before calling `extractPluginId`? From what i understand, `extractPluginId` will return id without scope even if plugin spec contains scope expression. > Unable to install npm scoped plugin with cordova-cli@6.1.0 > -- > > Key: CB-10986 > URL: https://issues.apache.org/jira/browse/CB-10986 > Project: Apache Cordova > Issue Type: Bug > Components: CordovaLib >Affects Versions: 6.1.0 >Reporter: Darryl Pogue >Assignee: Richard B Knoll > Labels: regression, reproduced, triaged > > {code} > $ cordova create MyProject > $ cd ./MyProject > $ cordova platform add android > $ cordova plugin add @dpogue/cordova-plugin-crosswalk-webview > Error: Cannot find plugin.xml for plugin 'plugins'. Please try adding it > again. > {code} > This works as expected with cordova@6.0.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Created] (CB-11066) uap-prefixed capabilities are not being removed from package.windows10.appxmanifest on plugin rm
Sergey Shakhnazarov created CB-11066: Summary: uap-prefixed capabilities are not being removed from package.windows10.appxmanifest on plugin rm Key: CB-11066 URL: https://issues.apache.org/jira/browse/CB-11066 Project: Apache Cordova Issue Type: Bug Components: Windows Reporter: Sergey Shakhnazarov 1. Some cordova-plugin-capabities {{plugin.xml}} includes: {noformat} {noformat} 2. cordova plugin add ..\cordova-plugin-capabities 3. package.windows10.appxmanifest now includes: {noformat} {noformat} 4. cordova plugin rm cordova-plugin-capabities 5. package.windows10.appxmanifest now actually includes: {noformat} {noformat} *Expected*: {noformat} {noformat} -- 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] [Closed] (CB-11033) Contacts plugin Appium tests: modifying a contact can take more than a minute on an emulator
[ https://issues.apache.org/jira/browse/CB-11033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Sorokin closed CB-11033. -- Resolution: Fixed > Contacts plugin Appium tests: modifying a contact can take more than a minute > on an emulator > > > Key: CB-11033 > URL: https://issues.apache.org/jira/browse/CB-11033 > Project: Apache Cordova > Issue Type: Bug > Components: Appium, Plugin Contacts >Affects Versions: Master > Environment: Windows 8.1, Android emulator, Api level 19 >Reporter: Alexander Sorokin >Assignee: Alexander Sorokin > Labels: triaged > > https://ci.apache.org/builders/cordova-android-win/builds/2053/steps/running-appium-tests/logs/stdio > {noformat} > Error: [executeAsync(null,["Dooney Evans","Urist","McContact"])] Error > response status: 28, , ScriptTimeout - A script did not complete before its > timeout expired. Selenium error: asynchronous script timeout: result was not > received in 60 seconds > {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10986) Unable to install npm scoped plugin with cordova-cli@6.1.0
[ https://issues.apache.org/jira/browse/CB-10986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15236823#comment-15236823 ] ASF GitHub Bot commented on CB-10986: - Github user vladimir-kotikov commented on a diff in the pull request: https://github.com/apache/cordova-lib/pull/425#discussion_r59339491 --- Diff: cordova-lib/src/cordova/util.js --- @@ -401,3 +407,48 @@ function getAvailableNpmVersions(module_name) { }); }); } + +/** + * Extracts the name and spec from an npm style package spec that follows the + * format of (@scope/)?package(@spec)? + * @param {String} raw The raw npm style package spec + * @returns {String[]} An array containing the package name with optional scope + * followed by the plugin spec (either value may be null + * if not matched) + */ +function parseRegistryPluginSpec(raw) { +var split = NPM_SPEC_REGEX.exec(raw); +if (split) { +var package = split[1] ? split[1] + split[2] : split[2]; +var version = split[3] || null; +return [package, version]; +} else { +return [null, null]; +} +} + +/** + * Extracts the package name from an npm style package spec of the format + * (@scope/)?package(@spec)?. Useful for getting the id used for directories + * created for install + * @param {String} raw The raw npm style package spec + * @returns {String}The package name without scope or version or the original + * string if it isn't an npm package spec + */ +function extractPluginId(raw) { +var split = NPM_SPEC_REGEX.exec(raw); +return split ? split[2] : raw; +} + + +/** + * Determines if a string is a package spec of the format @scope/package(@spec)? + * or not + * @param {String} raw The raw npm style package spec + * @returns {boolean} True if the given string follows the format of an npm style + * package spec or false otherwise + */ +function isScopedRegistryPluginSpec(raw) { --- End diff -- This function might be unnecessary if `parseRegistryPluginSpec` would return a structured result with e.g. `scope` field, so you can just check if `spec.scope` is defined > Unable to install npm scoped plugin with cordova-cli@6.1.0 > -- > > Key: CB-10986 > URL: https://issues.apache.org/jira/browse/CB-10986 > Project: Apache Cordova > Issue Type: Bug > Components: CordovaLib >Affects Versions: 6.1.0 >Reporter: Darryl Pogue >Assignee: Richard B Knoll > Labels: regression, reproduced, triaged > > {code} > $ cordova create MyProject > $ cd ./MyProject > $ cordova platform add android > $ cordova plugin add @dpogue/cordova-plugin-crosswalk-webview > Error: Cannot find plugin.xml for plugin 'plugins'. Please try adding it > again. > {code} > This works as expected with cordova@6.0.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10986) Unable to install npm scoped plugin with cordova-cli@6.1.0
[ https://issues.apache.org/jira/browse/CB-10986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15236820#comment-15236820 ] ASF GitHub Bot commented on CB-10986: - Github user vladimir-kotikov commented on a diff in the pull request: https://github.com/apache/cordova-lib/pull/425#discussion_r59339185 --- Diff: cordova-lib/src/cordova/util.js --- @@ -401,3 +407,48 @@ function getAvailableNpmVersions(module_name) { }); }); } + +/** + * Extracts the name and spec from an npm style package spec that follows the + * format of (@scope/)?package(@spec)? + * @param {String} raw The raw npm style package spec + * @returns {String[]} An array containing the package name with optional scope --- End diff -- IMO returning an array is not very convenient to use. This leads to guessing, what is the 0th item of the result in the expressions like `cordova_util.parseRegistryPluginSpec(target)[0]`. I'd prefer to use structured result. something like `npm-package-arg` returns (https://github.com/npm/npm-package-arg#examples) > Unable to install npm scoped plugin with cordova-cli@6.1.0 > -- > > Key: CB-10986 > URL: https://issues.apache.org/jira/browse/CB-10986 > Project: Apache Cordova > Issue Type: Bug > Components: CordovaLib >Affects Versions: 6.1.0 >Reporter: Darryl Pogue >Assignee: Richard B Knoll > Labels: regression, reproduced, triaged > > {code} > $ cordova create MyProject > $ cd ./MyProject > $ cordova platform add android > $ cordova plugin add @dpogue/cordova-plugin-crosswalk-webview > Error: Cannot find plugin.xml for plugin 'plugins'. Please try adding it > again. > {code} > This works as expected with cordova@6.0.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-10975) 'plugin add ../local/path/to/plugin' cannot access plugin via parent directory. Fails with 404 from npmjs.org
[ https://issues.apache.org/jira/browse/CB-10975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15236791#comment-15236791 ] ASF GitHub Bot commented on CB-10975: - Github user vladimir-kotikov commented on the pull request: https://github.com/apache/cordova-lib/pull/421#issuecomment-208765981 I think this is not a regression, since this code has been added recently in #363 (see the diff [here](https://github.com/MSOpenTech/cordova-lib/commit/45a235fa73e5b23ed9fa44734449503976b999e3#diff-5a4020497db170abc9410280ac313316R297)). I'll add the test for this scenario. > 'plugin add ../local/path/to/plugin' cannot access plugin via parent > directory. Fails with 404 from npmjs.org > -- > > Key: CB-10975 > URL: https://issues.apache.org/jira/browse/CB-10975 > Project: Apache Cordova > Issue Type: Bug > Components: CLI >Affects Versions: 6.1.1 > Environment: Windows 7 >Reporter: Brendan P Flynn >Assignee: Vladimir Kotikov > Labels: reproduced, triaged > > cordova app directory structure: > app > -/bin (build scripts) > -/custom_plugins > -/com.myorg.myplugin > -/platforms > -/plugins > -/test > -/www > These attempts to add the plugin work in the command line: > C:...\app\bin>cordova plugin add ../custom_plugins/com.myorg.myplugin > --searchpath ../ > AND > C:...\app>cordova plugin add custom_plugins/com.myorg.myplugin > This attempt does not work in command line: > C:...\app\bin>cordova plugin add ../custom_plugins/com.myorg.myplugin > Error: Registry returned 404 for GET on https://registry.npmjs.org/myorg > Despite the example [cordova plugin add ../cordova-plugin-camera] from the > docs > (https://cordova.apache.org/docs/en/latest/reference/cordova-cli/index.html#cordova-plugin-command) > If --searchpath is required to find a local plugin in a parent directory, > then that should be documented and the examples should be changed. > If --searchpath is not required, then this is a bug? -- 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] [Closed] (CB-10797) WKWebView CSS Position:Fixed Moves
[ https://issues.apache.org/jira/browse/CB-10797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] vB Results, LLC. closed CB-10797. - Resolution: Won't Fix > WKWebView CSS Position:Fixed Moves > -- > > Key: CB-10797 > URL: https://issues.apache.org/jira/browse/CB-10797 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin WKWebViewEngine >Affects Versions: 6.0.0, 5.4.1 > Environment: iOS 9 > Cordova 6.0.0 > Cordova-iOS 4.1.0 > Cordova-Plugin-WkWebView-Engine 1.0.1 >Reporter: vB Results, LLC. > Labels: iOS, triaged > > CSS fixed position elements exhibit major problems in the WKWebView Engine -- > they are not fixed. They move and often break the layout -- to resolve a > similar problem in Android we had to go with Crosswalk. > This isn't present in Mobile Safari so we've been looking at moving to > Crosswalk since support for iOS is coming soon. Not sure if this is an Apple > or Cordova bug; I'd prefer to stick with WKWebView if the latter. -- 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-10797) WKWebView CSS Position:Fixed Moves
[ https://issues.apache.org/jira/browse/CB-10797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15236745#comment-15236745 ] vB Results, LLC. edited comment on CB-10797 at 4/12/16 7:29 AM: [~shazron] I discovered the cause of this. In a typical browser, you scroll the content and the viewport is static. In WKWebView it's the inverse -- content is static, the viewport is what scrolls/moves (hello ScrollView?). So, technically, fixed position elements are being laid out in the right place on the page, but this position wasn't implemented to work with a scrolling viewport. Proper support was apparently introduced to Safari in iOS 5, but left out of WKWebView. Is there any way to enable the legacy content scrolling functionality? This is out of the scope of cordova, so I'm closing this issue, but if anyone knows a native fix to this do share in the comments here. The only option I know of so far is mucking with the onscroll event in JS and that is very hacky. was (Author: vbresults): [~shazron] I discovered the cause of this. In a typical browser, you scroll the content and the viewport is static. In WKWebView it's the inverse -- content is static, the viewport is what scrolls/moves (hello ScrollView?). So, technically, fixed position elements are being laid out in the right place on the page, but this position wasn't implemented to work with a scrolling viewport. Proper support was apparently introduced to Safari in iOS 5, but left out of WKWebView. I think this was done by design to discourage developers from implementing non-native scrolling. Very ham-fisted way to go about it but it is what it is. Also, Crosswalk for iOS is just a wrapper for WKWebView so no luck there. Is there any way to enable the legacy content scrolling functionality? This is out of the scope of cordova, so I'm closing this issue, but if anyone knows a native fix to this do share in the comments here. The only option I know of so far is mucking with the onscroll event in JS and that is very hacky. > WKWebView CSS Position:Fixed Moves > -- > > Key: CB-10797 > URL: https://issues.apache.org/jira/browse/CB-10797 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin WKWebViewEngine >Affects Versions: 6.0.0, 5.4.1 > Environment: iOS 9 > Cordova 6.0.0 > Cordova-iOS 4.1.0 > Cordova-Plugin-WkWebView-Engine 1.0.1 >Reporter: vB Results, LLC. > Labels: iOS, triaged > > CSS fixed position elements exhibit major problems in the WKWebView Engine -- > they are not fixed. They move and often break the layout -- to resolve a > similar problem in Android we had to go with Crosswalk. > This isn't present in Mobile Safari so we've been looking at moving to > Crosswalk since support for iOS is coming soon. Not sure if this is an Apple > or Cordova bug; I'd prefer to stick with WKWebView if the latter. -- 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-8976) platforms/android/build.gradle modifies android versionCode
[ https://issues.apache.org/jira/browse/CB-8976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15236751#comment-15236751 ] Alexander S. commented on CB-8976: -- I've cordova 6.1.1 installed, removed all platforms, did ionic state restore, and then built android apk. In config.xml I have 3143, in platforms/android/build/intermediates/manifests/full/debug/AndroidManifest.xml 31438. > platforms/android/build.gradle modifies android versionCode > --- > > Key: CB-8976 > URL: https://issues.apache.org/jira/browse/CB-8976 > Project: Apache Cordova > Issue Type: Bug > Components: Android > Environment: Android >Reporter: zack dykes >Assignee: Joe Bowser >Priority: Minor > > cordova 5.0.0 > platforms/android/build.gradle modifies android versionCode at ln 178 > as I understand it max size for versionCode is (2^31)-1 > http://stackoverflow.com/a/24246191/126600 > in my config.xml: > {code} > android-versionCode="1385039613" > {code} > when I run {{cordova build android}}, I get: > {code} > FAILURE: Build failed with an exception. > * Where: > Build file > '/Users/zackd/dev/code/cordova/cordova-ansr-fat-client/ondeviceresearch/platforms/android/build.gradle' > line: 178 > * What went wrong: > A problem occurred evaluating root project 'android'. > > For input string: "13850396130" > {code} > and build.gradle, ln 178 > {code} > versionCode cdvVersionCode ?: Integer.parseInt("" + > privateHelpers.extractIntFromManifest("versionCode") + "0") > {code} > looks like this is appending "0" to my versionCode, producing 13850396130 > which is larger than max size for android versionCode > if I mod ln 178 as follows, build succeeds > {code} > versionCode cdvVersionCode ?: Integer.parseInt("" + > privateHelpers.extractIntFromManifest("versionCode")) > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Comment Edited] (CB-10797) WKWebView CSS Position:Fixed Moves
[ https://issues.apache.org/jira/browse/CB-10797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15236745#comment-15236745 ] vB Results, LLC. edited comment on CB-10797 at 4/12/16 7:28 AM: [~shazron] I discovered the cause of this. In a typical browser, you scroll the content and the viewport is static. In WKWebView it's the inverse -- content is static, the viewport is what scrolls/moves (hello ScrollView?). So, technically, fixed position elements are being laid out in the right place on the page, but this position wasn't implemented to work with a scrolling viewport. Proper support was apparently introduced to Safari in iOS 5, but left out of WKWebView. I think this was done by design to discourage developers from implementing non-native scrolling. Very ham-fisted way to go about it but it is what it is. Also, Crosswalk for iOS is just a wrapper for WKWebView so no luck there. Is there any way to enable the legacy content scrolling functionality? This is out of the scope of cordova, so I'm closing this issue, but if anyone knows a native fix to this do share in the comments here. The only option I know of so far is mucking with the onscroll event in JS and that is very hacky. was (Author: vbresults): [~shazron] I discovered the cause of this. In a typical browser, you scroll the content and the viewport is static. In WKWebView it's the inverse -- content is static, the viewport is what scrolls/moves. So, technically, fixed position elements are being laid out in the right place on the page, but this position wasn't implemented to work with a scrolling viewport. Proper support was apparently introduced to Safari in iOS 5, but left out of WKWebView. I think this was done by design to discourage developers from implementing non-native scrolling. Very ham-fisted way to go about it but it is what it is. Also, Crosswalk for iOS is just a wrapper for WKWebView so no luck there. Is there any way to enable the legacy content scrolling functionality? This is out of the scope of cordova, so I'm closing this issue, but if anyone knows a native fix to this do share in the comments here. The only option I know of so far is mucking with the onscroll event in JS and that is very hacky. > WKWebView CSS Position:Fixed Moves > -- > > Key: CB-10797 > URL: https://issues.apache.org/jira/browse/CB-10797 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin WKWebViewEngine >Affects Versions: 6.0.0, 5.4.1 > Environment: iOS 9 > Cordova 6.0.0 > Cordova-iOS 4.1.0 > Cordova-Plugin-WkWebView-Engine 1.0.1 >Reporter: vB Results, LLC. > Labels: iOS, triaged > > CSS fixed position elements exhibit major problems in the WKWebView Engine -- > they are not fixed. They move and often break the layout -- to resolve a > similar problem in Android we had to go with Crosswalk. > This isn't present in Mobile Safari so we've been looking at moving to > Crosswalk since support for iOS is coming soon. Not sure if this is an Apple > or Cordova bug; I'd prefer to stick with WKWebView if the latter. -- 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-10797) WKWebView CSS Position:Fixed Moves
[ https://issues.apache.org/jira/browse/CB-10797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15236745#comment-15236745 ] vB Results, LLC. commented on CB-10797: --- [~shazron] I discovered the cause of this. In a typical browser, you scroll the content and the viewport is static. In WKWebView it's the inverse -- content is static, the viewport is what scrolls/moves. So, technically, fixed positions are being laid out in the right place on the page, but this position wasn't implemented to work with a scrolling viewport. Proper support was apparently introduced to Safari in iOS 5, but left out of WKWebView. I think this was done by design to discourage developers from implementing non-native scrolling. Very ham-fisted way to go about it but it is what it is. Also, Crosswalk for iOS is just a wrapper for WKWebView so no luck there. Is there any way to enable the legacy content scrolling functionality? This is out of the scope of cordova, so I'm closing this issue, but if anyone knows a native fix to this do share in the comments here. The only option I know of so far is mucking with the onscroll event in JS and that is very hacky. > WKWebView CSS Position:Fixed Moves > -- > > Key: CB-10797 > URL: https://issues.apache.org/jira/browse/CB-10797 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin WKWebViewEngine >Affects Versions: 6.0.0, 5.4.1 > Environment: iOS 9 > Cordova 6.0.0 > Cordova-iOS 4.1.0 > Cordova-Plugin-WkWebView-Engine 1.0.1 >Reporter: vB Results, LLC. > Labels: iOS, triaged > > CSS fixed position elements exhibit major problems in the WKWebView Engine -- > they are not fixed. They move and often break the layout -- to resolve a > similar problem in Android we had to go with Crosswalk. > This isn't present in Mobile Safari so we've been looking at moving to > Crosswalk since support for iOS is coming soon. Not sure if this is an Apple > or Cordova bug; I'd prefer to stick with WKWebView if the latter. > Example of affected app: > https://itunes.apple.com/en/app/apex-online-racing/id1087710643?mt=8 (when > you scroll down, the header adds a class to position-fix the navigation at > the top, broken in 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] [Updated] (CB-10797) WKWebView CSS Position:Fixed Moves
[ https://issues.apache.org/jira/browse/CB-10797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] vB Results, LLC. updated CB-10797: -- Description: CSS fixed position elements exhibit major problems in the WKWebView Engine -- they are not fixed. They move and often break the layout -- to resolve a similar problem in Android we had to go with Crosswalk. This isn't present in Mobile Safari so we've been looking at moving to Crosswalk since support for iOS is coming soon. Not sure if this is an Apple or Cordova bug; I'd prefer to stick with WKWebView if the latter. was: CSS fixed position elements exhibit major problems in the WKWebView Engine -- they are not fixed. They move and often break the layout -- to resolve a similar problem in Android we had to go with Crosswalk. This isn't present in Mobile Safari so we've been looking at moving to Crosswalk since support for iOS is coming soon. Not sure if this is an Apple or Cordova bug; I'd prefer to stick with WKWebView if the latter. Example of affected app: https://itunes.apple.com/en/app/apex-online-racing/id1087710643?mt=8 (when you scroll down, the header adds a class to position-fix the navigation at the top, broken in WKWebView) > WKWebView CSS Position:Fixed Moves > -- > > Key: CB-10797 > URL: https://issues.apache.org/jira/browse/CB-10797 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin WKWebViewEngine >Affects Versions: 6.0.0, 5.4.1 > Environment: iOS 9 > Cordova 6.0.0 > Cordova-iOS 4.1.0 > Cordova-Plugin-WkWebView-Engine 1.0.1 >Reporter: vB Results, LLC. > Labels: iOS, triaged > > CSS fixed position elements exhibit major problems in the WKWebView Engine -- > they are not fixed. They move and often break the layout -- to resolve a > similar problem in Android we had to go with Crosswalk. > This isn't present in Mobile Safari so we've been looking at moving to > Crosswalk since support for iOS is coming soon. Not sure if this is an Apple > or Cordova bug; I'd prefer to stick with WKWebView if the latter. -- 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-10797) WKWebView CSS Position:Fixed Moves
[ https://issues.apache.org/jira/browse/CB-10797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15236745#comment-15236745 ] vB Results, LLC. edited comment on CB-10797 at 4/12/16 7:27 AM: [~shazron] I discovered the cause of this. In a typical browser, you scroll the content and the viewport is static. In WKWebView it's the inverse -- content is static, the viewport is what scrolls/moves. So, technically, fixed position elements are being laid out in the right place on the page, but this position wasn't implemented to work with a scrolling viewport. Proper support was apparently introduced to Safari in iOS 5, but left out of WKWebView. I think this was done by design to discourage developers from implementing non-native scrolling. Very ham-fisted way to go about it but it is what it is. Also, Crosswalk for iOS is just a wrapper for WKWebView so no luck there. Is there any way to enable the legacy content scrolling functionality? This is out of the scope of cordova, so I'm closing this issue, but if anyone knows a native fix to this do share in the comments here. The only option I know of so far is mucking with the onscroll event in JS and that is very hacky. was (Author: vbresults): [~shazron] I discovered the cause of this. In a typical browser, you scroll the content and the viewport is static. In WKWebView it's the inverse -- content is static, the viewport is what scrolls/moves. So, technically, fixed positions are being laid out in the right place on the page, but this position wasn't implemented to work with a scrolling viewport. Proper support was apparently introduced to Safari in iOS 5, but left out of WKWebView. I think this was done by design to discourage developers from implementing non-native scrolling. Very ham-fisted way to go about it but it is what it is. Also, Crosswalk for iOS is just a wrapper for WKWebView so no luck there. Is there any way to enable the legacy content scrolling functionality? This is out of the scope of cordova, so I'm closing this issue, but if anyone knows a native fix to this do share in the comments here. The only option I know of so far is mucking with the onscroll event in JS and that is very hacky. > WKWebView CSS Position:Fixed Moves > -- > > Key: CB-10797 > URL: https://issues.apache.org/jira/browse/CB-10797 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin WKWebViewEngine >Affects Versions: 6.0.0, 5.4.1 > Environment: iOS 9 > Cordova 6.0.0 > Cordova-iOS 4.1.0 > Cordova-Plugin-WkWebView-Engine 1.0.1 >Reporter: vB Results, LLC. > Labels: iOS, triaged > > CSS fixed position elements exhibit major problems in the WKWebView Engine -- > they are not fixed. They move and often break the layout -- to resolve a > similar problem in Android we had to go with Crosswalk. > This isn't present in Mobile Safari so we've been looking at moving to > Crosswalk since support for iOS is coming soon. Not sure if this is an Apple > or Cordova bug; I'd prefer to stick with WKWebView if the latter. -- 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