[jira] [Commented] (CB-8960) Add docs for AppendUserAgent, OverrideUserAgent
[ https://issues.apache.org/jira/browse/CB-8960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14627667#comment-14627667 ] Shazron Abdullah commented on CB-8960: -- The user-agent feature is slated for cordova-android 4.1.0 which is the next release. > Add docs for AppendUserAgent, OverrideUserAgent > --- > > Key: CB-8960 > URL: https://issues.apache.org/jira/browse/CB-8960 > Project: Apache Cordova > Issue Type: Bug > Components: Docs, iOS >Reporter: Shazron Abdullah > Fix For: 4.0.0 > > > See CB-3360 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Assigned] (CB-9272) App crashes on on iPad when run on PGB
[ https://issues.apache.org/jira/browse/CB-9272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jcesarmobile reassigned CB-9272: Assignee: jcesarmobile > App crashes on on iPad when run on PGB > -- > > Key: CB-9272 > URL: https://issues.apache.org/jira/browse/CB-9272 > Project: Apache Cordova > Issue Type: Bug > Environment: iPad Air (model#: MD788NF/A) >Reporter: Leroy van Engelen >Assignee: jcesarmobile > Attachments: appbase.zip > > > See https://issues.apache.org/jira/browse/CB-7577 -- 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-9347) You can no longer stack alerts in cordova-plugin-dialogs - commit #ee3b02b3 has caused this
[
https://issues.apache.org/jira/browse/CB-9347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14627684#comment-14627684
]
Shazron Abdullah commented on CB-9347:
--
Thank you! I think this is the same problem:
http://stackoverflow.com/questions/25932589/concurrent-uialertcontrollers
Not sure what the solution would be yet (no accepted answer to that SO question)
> You can no longer stack alerts in cordova-plugin-dialogs - commit #ee3b02b3
> has caused this
> ---
>
> Key: CB-9347
> URL: https://issues.apache.org/jira/browse/CB-9347
> Project: Apache Cordova
> Issue Type: Bug
> Components: iOS, Plugin Dialogs
>Affects Versions: 1.1.0
> Environment: Mac OS X Yosemite 10.10.4; XCode 6.4
>Reporter: Kelvin Dart
>Priority: Critical
>
> Previously in cordova-plugin-dialogs, you could stack alerts in Cordova like
> follows:
> {code}
> navigator.notification.alert('Notification 1', function () {}, 'Title 1');
> navigator.notification.alert('Notification 2', function () {}, 'Title 2');
> {code}
> And it would show 'Notification 2' then 'Notification 1'.
> Now you cannot, in commit: #ee3b02b3c78debe608263d847f7ac69bda1bfca0, there
> was quite a large overhaul in {{showDialogWithMessage}} in
> {{CDVNotification.m}}; this commit seems to add some code for iOS 8.3+ which
> uses {{UIAlertController}} instead of the old {{UIAlertView}}. The problem is
> here - unfortunately I do not know Obj-C too well in order to debug it.
> If you revert to a cordova-plugin-dialogs version prior to this, the stacked
> notifications work fine.
> I have created a small test harness which you can download
> [here|https://www.dropbox.com/s/62hdp3gjp2924er/CDVDialogsNotificationBug.zip?dl=0].
> Please could you implement the old behaviour as this has cause some aspects
> of my app to break - thanks!
> N.b. I have tagged the version as 1.1.0 as it would not allow me to tag 1.1.1.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-9347) You can no longer stack alerts in cordova-plugin-dialogs - commit #ee3b02b3 has caused this
[
https://issues.apache.org/jira/browse/CB-9347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14627687#comment-14627687
]
Shazron Abdullah commented on CB-9347:
--
If no solution is found, I think Cordova will just have to handle this:
1. Put the dialog info into a queue
2. If no alert is currently presenting, pop the queue, and present the alert --
else exit
3. After the alert is dismissed (in a button handler), goto (2)
> You can no longer stack alerts in cordova-plugin-dialogs - commit #ee3b02b3
> has caused this
> ---
>
> Key: CB-9347
> URL: https://issues.apache.org/jira/browse/CB-9347
> Project: Apache Cordova
> Issue Type: Bug
> Components: iOS, Plugin Dialogs
>Affects Versions: 1.1.0
> Environment: Mac OS X Yosemite 10.10.4; XCode 6.4
>Reporter: Kelvin Dart
>Priority: Critical
>
> Previously in cordova-plugin-dialogs, you could stack alerts in Cordova like
> follows:
> {code}
> navigator.notification.alert('Notification 1', function () {}, 'Title 1');
> navigator.notification.alert('Notification 2', function () {}, 'Title 2');
> {code}
> And it would show 'Notification 2' then 'Notification 1'.
> Now you cannot, in commit: #ee3b02b3c78debe608263d847f7ac69bda1bfca0, there
> was quite a large overhaul in {{showDialogWithMessage}} in
> {{CDVNotification.m}}; this commit seems to add some code for iOS 8.3+ which
> uses {{UIAlertController}} instead of the old {{UIAlertView}}. The problem is
> here - unfortunately I do not know Obj-C too well in order to debug it.
> If you revert to a cordova-plugin-dialogs version prior to this, the stacked
> notifications work fine.
> I have created a small test harness which you can download
> [here|https://www.dropbox.com/s/62hdp3gjp2924er/CDVDialogsNotificationBug.zip?dl=0].
> Please could you implement the old behaviour as this has cause some aspects
> of my app to break - thanks!
> N.b. I have tagged the version as 1.1.0 as it would not allow me to tag 1.1.1.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-9102) Crash when using a iOS Cordova plugin within a WebSocket event
[
https://issues.apache.org/jira/browse/CB-9102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14627689#comment-14627689
]
Shazron Abdullah commented on CB-9102:
--
Don't assume intent, or attack the developers here, it's not welcome. WebSocket
IS the purview of the system framework, we have no control over how it behaves.
> Crash when using a iOS Cordova plugin within a WebSocket event
> --
>
> Key: CB-9102
> URL: https://issues.apache.org/jira/browse/CB-9102
> Project: Apache Cordova
> Issue Type: Bug
> Components: iOS
>Affects Versions: 3.8.0
>Reporter: Iñaki Baz Castillo
> Labels: ios, plugin, websocket
>
> I've coded a cordova plugin for iOS. It is exported as a JavaScript object
> with multiple functions in `window.cordova.plugins.iosrtc`.
> If I use any of those exported functions within the callback of a WebSocket
> event (onopen, onmessage, etc), the plugin/app usually crashes:
> {code}
> Process 2326 stopped
> * thread #1: tid = 0x94ce5, 0x2e267474
> WebCore`WebCore::NavigationScheduler::schedule(std::__1::unique_ptr std::__1::default_delete >) + 276, queue =
> 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x0)
> frame #0: 0x2e267474
> WebCore`WebCore::NavigationScheduler::schedule(std::__1::unique_ptr std::__1::default_delete >) + 276
> WebCore`WebCore::NavigationScheduler::schedule:
> -> 0x2e267474 <+276>: ldrr2, [r0]
> 0x2e267476 <+278>: ldrr3, [r2, #0x10]
> 0x2e267478 <+280>: movr2, r10
> 0x2e26747a <+282>: blxr3
> (lldb)
> error: No auto repeat.
> (lldb) list
>30 {
>31 @autoreleasepool {
>32 int retVal = UIApplicationMain(argc, argv, nil,
> @"AppDelegate");
>33 return retVal;
>34 }
>35 }
> (lldb) bt
> * thread #1: tid = 0x94ce5, 0x2e267474
> WebCore`WebCore::NavigationScheduler::schedule(std::__1::unique_ptr std::__1::default_delete >) + 276, queue =
> 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x0)
> * frame #0: 0x2e267474
> WebCore`WebCore::NavigationScheduler::schedule(std::__1::unique_ptr std::__1::default_delete >) + 276
> frame #1: 0x2e26769e
> WebCore`WebCore::NavigationScheduler::scheduleLocationChange(WebCore::SecurityOrigin*,
> WebCore::URL const&, WTF::String const&, WebCore::LockHistory,
> WebCore::LockBackForwardList) + 498
> frame #2: 0x2de00c20 WebCore`WebCore::DOMWindow::setLocation(WTF::String
> const&, WebCore::DOMWindow&, WebCore::DOMWindow&,
> WebCore::SetLocationLocking) + 172
> frame #3: 0x2e22b0e2 WebCore`WebCore::Location::setHref(WTF::String
> const&, WebCore::DOMWindow&, WebCore::DOMWindow&) + 86
> frame #4: 0x2e03c5d6
> WebCore`WebCore::JSDOMWindow::setLocation(JSC::ExecState*, JSC::JSValue) + 142
> frame #5: 0x2daad47e WebCore`WebCore::JSDOMWindow::put(JSC::JSCell,
> JSC::ExecState, JSC::PropertyName, JSC::JSValue, JSC::PutPropertySlot&) + 446
> frame #6: 0x231a3436 JavaScriptCore`JSC::JSProxy::put(JSC::JSCell,
> JSC::ExecState, JSC::PropertyName, JSC::JSValue, JSC::PutPropertySlot&) + 54
> frame #7: 0x23199fc0 JavaScriptCore`llint_slow_path_put_by_id + 404
> frame #8: 0x233ca3ce JavaScriptCore`llint_entry + 9694
> {code}
> Sometimes it produces a different error:
> {code}
> 2015-06-01 15:29:17.810 cordovaIosrtcDemo[2298:602476] DiskCookieStorage
> changing policy from 2 to 0, cookie file:
> file:///private/var/mobile/Containers/Data/Application/3588C109-5F97-4E5F-83EA-36165871ACC3/Library/Cookies/Cookies.binarycookies
> 2015-06-01 15:29:18.083 cordovaIosrtcDemo[2298:602476] Apache Cordova native
> platform version 3.8.0 is starting.
> 2015-06-01 15:29:18.083 cordovaIosrtcDemo[2298:602476] Multi-tasking ->
> Device: YES, App: YES
> 2015-06-01 15:29:18.088 cordovaIosrtcDemo[2298:602476] Unlimited access to
> network resources
> 2015-06-01 15:29:18.277 cordovaIosrtcDemo[2298:602476] iosrtcPlugin#init()
> 2015-06-01 15:29:18.325 cordovaIosrtcDemo[2298:602476]
> PluginGetUserMedia#init()
> 2015-06-01 15:29:18.326 cordovaIosrtcDemo[2298:602476]
> [CDVTimer][iosrtcplugin] 55.085003ms
> 2015-06-01 15:29:18.326 cordovaIosrtcDemo[2298:602476]
> [CDVTimer][TotalPluginStartup] 55.342019ms
> 2015-06-01 15:29:18.967 cordovaIosrtcDemo[2298:602476] Resetting plugins due
> to page load.
> 2015-06-01 15:29:19.432 cordovaIosrtcDemo[2298:602476] Finished load of:
> file:///private/var/mobile/Containers/Bundle/Application/90A5F156-4893-490C-B608-A7D3715F379D/cordovaIosrtcDemo.app/www/index.html
> Process 2298 stopped
> * thread #8: tid = 0x931b5, 0x21e410e8 CoreFoundation`CFRelease + 1268, name
> = 'WebThread', stop reason = EXC_BREAKPOINT (code=EXC_ARM_BREAKPOINT,
> subcode=0xdefe)
> frame #0: 0x21e
[jira] [Commented] (CB-9272) App crashes on on iPad when run on PGB
[ https://issues.apache.org/jira/browse/CB-9272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14627691#comment-14627691 ] Shazron Abdullah commented on CB-9272: -- Hi [~lvanengelen] have you contacted the PGB devs with this issue? > App crashes on on iPad when run on PGB > -- > > Key: CB-9272 > URL: https://issues.apache.org/jira/browse/CB-9272 > Project: Apache Cordova > Issue Type: Bug > Environment: iPad Air (model#: MD788NF/A) >Reporter: Leroy van Engelen >Assignee: jcesarmobile > Attachments: appbase.zip > > > See https://issues.apache.org/jira/browse/CB-7577 -- 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-9347) You can no longer stack alerts in cordova-plugin-dialogs - commit #ee3b02b3 has caused this
[
https://issues.apache.org/jira/browse/CB-9347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14627692#comment-14627692
]
Kelvin Dart commented on CB-9347:
-
Hi [~shazron],
Spot on! That SO issue is exactly as described; agreed - that sounds like a
feasible solution to the problem.
Do I need to do anything to raise it as a FR, or does this bug report act as
the FR?
> You can no longer stack alerts in cordova-plugin-dialogs - commit #ee3b02b3
> has caused this
> ---
>
> Key: CB-9347
> URL: https://issues.apache.org/jira/browse/CB-9347
> Project: Apache Cordova
> Issue Type: Bug
> Components: iOS, Plugin Dialogs
>Affects Versions: 1.1.0
> Environment: Mac OS X Yosemite 10.10.4; XCode 6.4
>Reporter: Kelvin Dart
>Priority: Critical
>
> Previously in cordova-plugin-dialogs, you could stack alerts in Cordova like
> follows:
> {code}
> navigator.notification.alert('Notification 1', function () {}, 'Title 1');
> navigator.notification.alert('Notification 2', function () {}, 'Title 2');
> {code}
> And it would show 'Notification 2' then 'Notification 1'.
> Now you cannot, in commit: #ee3b02b3c78debe608263d847f7ac69bda1bfca0, there
> was quite a large overhaul in {{showDialogWithMessage}} in
> {{CDVNotification.m}}; this commit seems to add some code for iOS 8.3+ which
> uses {{UIAlertController}} instead of the old {{UIAlertView}}. The problem is
> here - unfortunately I do not know Obj-C too well in order to debug it.
> If you revert to a cordova-plugin-dialogs version prior to this, the stacked
> notifications work fine.
> I have created a small test harness which you can download
> [here|https://www.dropbox.com/s/62hdp3gjp2924er/CDVDialogsNotificationBug.zip?dl=0].
> Please could you implement the old behaviour as this has cause some aspects
> of my app to break - thanks!
> N.b. I have tagged the version as 1.1.0 as it would not allow me to tag 1.1.1.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-9347) You can no longer stack alerts in cordova-plugin-dialogs - commit #ee3b02b3 has caused this
[
https://issues.apache.org/jira/browse/CB-9347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14627694#comment-14627694
]
Shazron Abdullah commented on CB-9347:
--
This report will do.
> You can no longer stack alerts in cordova-plugin-dialogs - commit #ee3b02b3
> has caused this
> ---
>
> Key: CB-9347
> URL: https://issues.apache.org/jira/browse/CB-9347
> Project: Apache Cordova
> Issue Type: Bug
> Components: iOS, Plugin Dialogs
>Affects Versions: 1.1.0
> Environment: Mac OS X Yosemite 10.10.4; XCode 6.4
>Reporter: Kelvin Dart
>Priority: Critical
>
> Previously in cordova-plugin-dialogs, you could stack alerts in Cordova like
> follows:
> {code}
> navigator.notification.alert('Notification 1', function () {}, 'Title 1');
> navigator.notification.alert('Notification 2', function () {}, 'Title 2');
> {code}
> And it would show 'Notification 2' then 'Notification 1'.
> Now you cannot, in commit: #ee3b02b3c78debe608263d847f7ac69bda1bfca0, there
> was quite a large overhaul in {{showDialogWithMessage}} in
> {{CDVNotification.m}}; this commit seems to add some code for iOS 8.3+ which
> uses {{UIAlertController}} instead of the old {{UIAlertView}}. The problem is
> here - unfortunately I do not know Obj-C too well in order to debug it.
> If you revert to a cordova-plugin-dialogs version prior to this, the stacked
> notifications work fine.
> I have created a small test harness which you can download
> [here|https://www.dropbox.com/s/62hdp3gjp2924er/CDVDialogsNotificationBug.zip?dl=0].
> Please could you implement the old behaviour as this has cause some aspects
> of my app to break - thanks!
> N.b. I have tagged the version as 1.1.0 as it would not allow me to tag 1.1.1.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-9272) App crashes on on iPad when run on PGB
[ https://issues.apache.org/jira/browse/CB-9272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14627706#comment-14627706 ] jcesarmobile commented on CB-9272: -- He opened a topic about this on the phonegap build forum http://community.phonegap.com/nitobi/topics/file-inputs-on-ipad-crash-when-building-on-pgb > App crashes on on iPad when run on PGB > -- > > Key: CB-9272 > URL: https://issues.apache.org/jira/browse/CB-9272 > Project: Apache Cordova > Issue Type: Bug > Environment: iPad Air (model#: MD788NF/A) >Reporter: Leroy van Engelen >Assignee: jcesarmobile > Attachments: appbase.zip > > > See https://issues.apache.org/jira/browse/CB-7577 -- 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-9278) Restoring multiple platforms fails
[
https://issues.apache.org/jira/browse/CB-9278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14627771#comment-14627771
]
Omar Mefire commented on CB-9278:
-
ok, taking a look !
> Restoring multiple platforms fails
> --
>
> Key: CB-9278
> URL: https://issues.apache.org/jira/browse/CB-9278
> Project: Apache Cordova
> Issue Type: Bug
> Components: CordovaLib
>Affects Versions: Master
> Environment: OS X
>Reporter: Dmitry Blotsky
>Assignee: Omar Mefire
> Labels: cordova-lib, platform, restore, save
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> Steps to reproduce:
> 1. Create a blank app: {{cordova create test com.app.test test}}
> 2. Add and save a platform: {{cordova platform add --save ios}}
> 3. Add and save another platform: {{cordova platform add --save android}}
> 4. Remove the platforms: {{cordova platform remove android ios}}
> 5. Try to restore platforms automatically: {{cordova prepare}}
> Expected: both platforms installed and prepared
> Actual:
> {noformat}
> Error: Trying to initialize npm when settings have not been restored from a
> previous initialization.
> {noformat}
> Running {{cordova prepare}} again fixes the issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-9278) Restoring multiple platforms fails
[
https://issues.apache.org/jira/browse/CB-9278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14627772#comment-14627772
]
Omar Mefire commented on CB-9278:
-
ok, taking a look !
> Restoring multiple platforms fails
> --
>
> Key: CB-9278
> URL: https://issues.apache.org/jira/browse/CB-9278
> Project: Apache Cordova
> Issue Type: Bug
> Components: CordovaLib
>Affects Versions: Master
> Environment: OS X
>Reporter: Dmitry Blotsky
>Assignee: Omar Mefire
> Labels: cordova-lib, platform, restore, save
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> Steps to reproduce:
> 1. Create a blank app: {{cordova create test com.app.test test}}
> 2. Add and save a platform: {{cordova platform add --save ios}}
> 3. Add and save another platform: {{cordova platform add --save android}}
> 4. Remove the platforms: {{cordova platform remove android ios}}
> 5. Try to restore platforms automatically: {{cordova prepare}}
> Expected: both platforms installed and prepared
> Actual:
> {noformat}
> Error: Trying to initialize npm when settings have not been restored from a
> previous initialization.
> {noformat}
> Running {{cordova prepare}} again fixes the issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-9238) Media plugin cannot record audio on windows
[ https://issues.apache.org/jira/browse/CB-9238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14627781#comment-14627781 ] ASF GitHub Bot commented on CB-9238: Github user daserge commented on the pull request: https://github.com/apache/cordova-plugin-media/pull/58#issuecomment-121547583 @robpaveza, thanks for review, I have addressed your comments. > Media plugin cannot record audio on windows > --- > > Key: CB-9238 > URL: https://issues.apache.org/jira/browse/CB-9238 > Project: Apache Cordova > Issue Type: Bug > Components: Plugin Media, Windows >Reporter: Alexander Sorokin > > Steps to reproduce: > - create mobile spec app with media plugin > - run mobile spec app on windows store or windows phone > - go to media manual tests > - click "Record Audio 10 sec" > The result is: RecordAudio():Audio Error: 1 -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-9353) Memory issue in Android version when passing a large number of JSON objects in either direction
[
https://issues.apache.org/jira/browse/CB-9353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14627861#comment-14627861
]
Chris Brody commented on CB-9353:
-
I made a plugin based off a fork of cordova-ext-echo that can be used to
reproduce this issue at:
https://github.com/brodybits/cordova-ext-echo-repeat-object-test
This plugin adds three test functions, working on both Android and iOS:
- Echo.array_object_count(array, callback) - send an array object to Android or
iOS native implementation and get the number of elements in the callback
- Echo.repeat_it(object, n, callback) - send an object to Android or iOS native
implementation and get an array with the object repeated n times in the callback
- Echo.build_test(n, callback) - get an array of n objects from the Android or
iOS native implementation in the calllback
My test program is just a bunch of Javascript that I added to the onDeviceReady
function in www/js/index.js or assets/www/js/index.js:
// Echo object:
var Echo = cordova.require('org.apache.cordova.plugins.echo.Echo');
// Small array count test Javascript JSON --> platform:
Echo.array_object_count(['a',1,null,2], function(v) {
alert("Small array count is: " + v);
});
// Small repeat test platform JSON --> Javascript:
Echo.repeat_it({a: 1, b: 2}, 4, function(v) {
alert("Small repeat result: " + JSON.stringify(v));
});
// Small repeat build test platform JSON --> Javascript:
Echo.build_test(4, function(v) {
alert("Small build_test result: " + JSON.stringify(v));
});
// iterator:
var i;
// big test size:
var big_array_count = 20;
var big_result_count = 40;
//** ** XXX Big object array test - BROKEN [CRASHING] ON ANDROID:
// Big object array test Javascript JSON --> platform:
var big_object_array = [];
for (i=0; i platform:
var big_flat_array = [];
for (i=0; i Javascript:
Echo.repeat_it({a:"a", b:1234, c:5678}, big_result_count, function(v) {
alert("Big repeat test done");
});
// */
//** ** XXX Big repeat build test - BROKEN [CRASHING] ON ANDROID:
// Big repeat build test platform JSON --> Javascript:
Echo.build_test(big_result_count, function(v) {
alert("Big repeat build test done");
});
// */
Note that each "big test" section starts with "//**" and ends with "// */", so
it is very easily to remove the first "/" to comment the section out (and add
the "/" back again to re-enable the section).
The big object array test shows the problem where an array with a large number
of JSON objects from Javascript to Java causes a crash in
org.apache.cordova.CordovaPlugin.execute() when it attempts to decode the JSON.
The big repeat build test shows the problem where the Java code attempts to
create an array with a large number of JSON objects to send back to Javascript
but crashes (with the memory issue).
Note that all of the scenarios in the test program work fine in the iOS
implementation.
> Memory issue in Android version when passing a large number of JSON objects
> in either direction
> ---
>
> Key: CB-9353
> URL: https://issues.apache.org/jira/browse/CB-9353
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Reporter: Chris Brody
>
> As reported in
> https://github.com/litehelpers/Cordova-sqlite-storage/issues/18: when an
> array with a very large number of JSON objects is sent from Javascript to
> Java, I would encounter a memory problem in JSON as called by
> CordovaPlugin.execute():
> E/art (22291): Throwing OutOfMemoryError "Failed to allocate a 28 byte
> allocation with 20 free bytes and 20B until OOM" (recursive case)
> E/art (22291): "JavaBridge" prio=5 tid=25 Runnable
> E/art (22291): | group="main" sCount=0 dsCount=0 obj=0x12de6820
> self=0xb73ae620
> E/art (22291): | sysTid=22377 nice=0 cgrp=apps sched=0/0
> handle=0xb73aead8
> E/art (22291): | state=R schedstat=( 0 0 0 ) utm=653 stm=94 core=1
> HZ=100
> E/art (22291): | stack=0xa4ee1000-0xa4ee3000 stackSize=1036KB
> E/art (22291): | held mutexes= "mutator lock"(shared held)
> E/art (22291): at
> java.util.LinkedHashMap.addNewEntry(LinkedHashMap.java:195)
> E/art (22291): at java.util.HashMap.put(HashMap.java:403)
> E/art (22291): at org.json.JSONObject.put(JSONObject.java:264)
> E/art (22291): at org.json.JSONTokener.readObject(JSONTokener.java:385)
> E/art (22291): at org.json.JSONTokener.nextValue(JSONTokener.java:100)
> E/art (22291): at org.json.JSONTokener.readArray(JSO
[jira] [Created] (CB-9370) Cordova-js tests are failing on node 0.12
Vladimir Kotikov created CB-9370: Summary: Cordova-js tests are failing on node 0.12 Key: CB-9370 URL: https://issues.apache.org/jira/browse/CB-9370 Project: Apache Cordova Issue Type: Bug Components: CordovaJS Affects Versions: 4.1.0 Environment: Windows/Mac OSX machine, Node JS 0.12.7 Reporter: Vladimir Kotikov Assignee: Vladimir Kotikov Fix For: 4.1.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-9291) Cordova NPM package does not install when Node >= 0.12.x
[
https://issues.apache.org/jira/browse/CB-9291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14627993#comment-14627993
]
Vladimir Kotikov commented on CB-9291:
--
I didn't found any reason for that. Especially due to fact that {{engines}}
option in package.json doesn't actually restrict Node version (see
https://docs.npmjs.com/files/package.json#engines), until {{engineStrict}}
option is not specified (and it isn't).
So the only consequence of {{engines}} presense - the warning message, as shown
in the report
{noformat}
npm WARN engine cordova-js@4.0.0: wanted: {"node":"~0.10.x"} (current:
{"node":"0.12.6","npm":"2.11.2"})
{noformat}
Anyway it looks confusing, so probably we may remove {{engines}} totally or
make it less strict. E.g. {{node >= 0.10.x}}
> Cordova NPM package does not install when Node >= 0.12.x
>
>
> Key: CB-9291
> URL: https://issues.apache.org/jira/browse/CB-9291
> Project: Apache Cordova
> Issue Type: Bug
> Components: CordovaJS
>Affects Versions: 4.0.0
> Environment: Windows7 x64 with NodeJS 0.12.6
>Reporter: Robert
>Assignee: Vladimir Kotikov
>Priority: Critical
>
> Hi
> I am trying to install cordova in version 5.1.1 (also tried some previous
> versions) using node 0.12.6:
> npm cache clean dep-graph
> npm install -g cordova@5.1.1
> Unfortunately, cordova-js depends on an older version of node (~0.10.x) which
> seems the reason for cordova not being installable:
> {noformat}
> >npm install -g cordova@5.1.1
> npm WARN engine cordova-js@4.0.0: wanted: {"node":"~0.10.x"} (current:
> {"node":"0.12.6","npm":"2.11.2"})
> npm WARN engine npm@1.3.4: wanted: {"node":">=0.6","npm":"1"} (current:
> {"node":"0.12.6","npm":"2.11.2"})
> npm WARN engine xmlbuilder@2.2.1: wanted: {"node":"0.8.x || 0.10.x"}
> (current: {"node":"0.12.6","npm":"2.11.2"})
> npm WARN installMany normalize-package-data was bundled with npm@1.3.4, but
> bundled package wasn't found in unpacked tree
> C:\Users\robert\AppData\Roaming\npm\cordova ->
> C:\Users\robert\AppData\Roaming\npm\node_modules\cordova\bin\cordova
> cordova@5.1.1 C:\Users\robert\AppData\Roaming\npm\node_modules\cordova
> ├── underscore@1.7.0
> ├── q@1.0.1
> ├── nopt@3.0.1 (abbrev@1.0.7)
> └── cordova-lib@5.1.1 (valid-identifier@0.0.1, osenv@0.1.0,
> properties-parser@0.2.3, bplist-parser@0.0.6, mime@1.2.11, unorm@1.3.3,
> semver@2.1.0, rc@0.5.2, shelljs@0.3.0, dep-graph@1.1.0, through2@0.6.3,
> npmconf@0.1.16, xcode@0.6.7, d8@0.4.4, init-package-json@1.7.0,
> elementtree@0.1.6, request@2.47.0, glob@4.0.6, cordova-registry-mapper@1.1.8,
> tar@1.0.2, cordova-app-hello-world@3.9.0, cordova-js@4.0.0, plist@1.1.0,
> npm@1.3.4)
> {noformat}
> Thanks in advance.
--
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-9291) Cordova NPM package does not install when Node >= 0.12.x
[
https://issues.apache.org/jira/browse/CB-9291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14627993#comment-14627993
]
Vladimir Kotikov edited comment on CB-9291 at 7/15/15 12:46 PM:
I didn't found any reason for that. Especially due to fact that {{engines}}
option in package.json doesn't actually restrict Node version (see
https://docs.npmjs.com/files/package.json#engines), until {{engineStrict}}
option is not specified (and it isn't).
So the only consequence of {{engines}} presense - the warning message, as shown
in the report
{noformat}
npm WARN engine cordova-js@4.0.0: wanted: {"node":"~0.10.x"} (current:
{"node":"0.12.6","npm":"2.11.2"})
{noformat}
Anyway it looks confusing, so probably we may remove {{engines}} totally or
make it less strict. E.g. {{node >= 0.10.x}}
was (Author: vladimir.kotikov):
I didn't found any reason for that. Especially due to fact that {{engines}}
option in package.json doesn't actually restrict Node version (see
https://docs.npmjs.com/files/package.json#engines), until {{engineStrict}}
option is not specified (and it isn't).
So the only consequence of {{engines}} presense - the warning message, as shown
in the report
{noformat}
npm WARN engine cordova-js@4.0.0: wanted: {"node":"~0.10.x"} (current:
{"node":"0.12.6","npm":"2.11.2"})
{noformat}
Anyway it looks confusing, so probably we may remove {{engines}} totally or
make it less strict. E.g. {{node >= 0.10.x}}
> Cordova NPM package does not install when Node >= 0.12.x
>
>
> Key: CB-9291
> URL: https://issues.apache.org/jira/browse/CB-9291
> Project: Apache Cordova
> Issue Type: Bug
> Components: CordovaJS
>Affects Versions: 4.0.0
> Environment: Windows7 x64 with NodeJS 0.12.6
>Reporter: Robert
>Assignee: Vladimir Kotikov
>Priority: Critical
>
> Hi
> I am trying to install cordova in version 5.1.1 (also tried some previous
> versions) using node 0.12.6:
> npm cache clean dep-graph
> npm install -g cordova@5.1.1
> Unfortunately, cordova-js depends on an older version of node (~0.10.x) which
> seems the reason for cordova not being installable:
> {noformat}
> >npm install -g cordova@5.1.1
> npm WARN engine cordova-js@4.0.0: wanted: {"node":"~0.10.x"} (current:
> {"node":"0.12.6","npm":"2.11.2"})
> npm WARN engine npm@1.3.4: wanted: {"node":">=0.6","npm":"1"} (current:
> {"node":"0.12.6","npm":"2.11.2"})
> npm WARN engine xmlbuilder@2.2.1: wanted: {"node":"0.8.x || 0.10.x"}
> (current: {"node":"0.12.6","npm":"2.11.2"})
> npm WARN installMany normalize-package-data was bundled with npm@1.3.4, but
> bundled package wasn't found in unpacked tree
> C:\Users\robert\AppData\Roaming\npm\cordova ->
> C:\Users\robert\AppData\Roaming\npm\node_modules\cordova\bin\cordova
> cordova@5.1.1 C:\Users\robert\AppData\Roaming\npm\node_modules\cordova
> ├── underscore@1.7.0
> ├── q@1.0.1
> ├── nopt@3.0.1 (abbrev@1.0.7)
> └── cordova-lib@5.1.1 (valid-identifier@0.0.1, osenv@0.1.0,
> properties-parser@0.2.3, bplist-parser@0.0.6, mime@1.2.11, unorm@1.3.3,
> semver@2.1.0, rc@0.5.2, shelljs@0.3.0, dep-graph@1.1.0, through2@0.6.3,
> npmconf@0.1.16, xcode@0.6.7, d8@0.4.4, init-package-json@1.7.0,
> elementtree@0.1.6, request@2.47.0, glob@4.0.6, cordova-registry-mapper@1.1.8,
> tar@1.0.2, cordova-app-hello-world@3.9.0, cordova-js@4.0.0, plist@1.1.0,
> npm@1.3.4)
> {noformat}
> Thanks in advance.
--
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-9291) Cordova NPM package does not install when Node >= 0.12.x
[
https://issues.apache.org/jira/browse/CB-9291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14627995#comment-14627995
]
Vladimir Kotikov commented on CB-9291:
--
Also the few last lines of {{npm install}} output shows that, in fact, cordova
is properly installed. [~noonien], Could you please double check, that cordova
actually is not installed?
> Cordova NPM package does not install when Node >= 0.12.x
>
>
> Key: CB-9291
> URL: https://issues.apache.org/jira/browse/CB-9291
> Project: Apache Cordova
> Issue Type: Bug
> Components: CordovaJS
>Affects Versions: 4.0.0
> Environment: Windows7 x64 with NodeJS 0.12.6
>Reporter: Robert
>Assignee: Vladimir Kotikov
>Priority: Critical
>
> Hi
> I am trying to install cordova in version 5.1.1 (also tried some previous
> versions) using node 0.12.6:
> npm cache clean dep-graph
> npm install -g cordova@5.1.1
> Unfortunately, cordova-js depends on an older version of node (~0.10.x) which
> seems the reason for cordova not being installable:
> {noformat}
> >npm install -g cordova@5.1.1
> npm WARN engine cordova-js@4.0.0: wanted: {"node":"~0.10.x"} (current:
> {"node":"0.12.6","npm":"2.11.2"})
> npm WARN engine npm@1.3.4: wanted: {"node":">=0.6","npm":"1"} (current:
> {"node":"0.12.6","npm":"2.11.2"})
> npm WARN engine xmlbuilder@2.2.1: wanted: {"node":"0.8.x || 0.10.x"}
> (current: {"node":"0.12.6","npm":"2.11.2"})
> npm WARN installMany normalize-package-data was bundled with npm@1.3.4, but
> bundled package wasn't found in unpacked tree
> C:\Users\robert\AppData\Roaming\npm\cordova ->
> C:\Users\robert\AppData\Roaming\npm\node_modules\cordova\bin\cordova
> cordova@5.1.1 C:\Users\robert\AppData\Roaming\npm\node_modules\cordova
> ├── underscore@1.7.0
> ├── q@1.0.1
> ├── nopt@3.0.1 (abbrev@1.0.7)
> └── cordova-lib@5.1.1 (valid-identifier@0.0.1, osenv@0.1.0,
> properties-parser@0.2.3, bplist-parser@0.0.6, mime@1.2.11, unorm@1.3.3,
> semver@2.1.0, rc@0.5.2, shelljs@0.3.0, dep-graph@1.1.0, through2@0.6.3,
> npmconf@0.1.16, xcode@0.6.7, d8@0.4.4, init-package-json@1.7.0,
> elementtree@0.1.6, request@2.47.0, glob@4.0.6, cordova-registry-mapper@1.1.8,
> tar@1.0.2, cordova-app-hello-world@3.9.0, cordova-js@4.0.0, plist@1.1.0,
> npm@1.3.4)
> {noformat}
> Thanks in advance.
--
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-9291) Cordova NPM package does not install when Node >= 0.12.x
[
https://issues.apache.org/jira/browse/CB-9291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14627995#comment-14627995
]
Vladimir Kotikov edited comment on CB-9291 at 7/15/15 12:50 PM:
Also the few last lines of {{npm install}} output shows that, in fact, cordova
is properly installed. [~noonien], Could you please double check that?
was (Author: vladimir.kotikov):
Also the few last lines of {{npm install}} output shows that, in fact, cordova
is properly installed. [~noonien], Could you please double check, that cordova
actually is not installed?
> Cordova NPM package does not install when Node >= 0.12.x
>
>
> Key: CB-9291
> URL: https://issues.apache.org/jira/browse/CB-9291
> Project: Apache Cordova
> Issue Type: Bug
> Components: CordovaJS
>Affects Versions: 4.0.0
> Environment: Windows7 x64 with NodeJS 0.12.6
>Reporter: Robert
>Assignee: Vladimir Kotikov
>Priority: Critical
>
> Hi
> I am trying to install cordova in version 5.1.1 (also tried some previous
> versions) using node 0.12.6:
> npm cache clean dep-graph
> npm install -g cordova@5.1.1
> Unfortunately, cordova-js depends on an older version of node (~0.10.x) which
> seems the reason for cordova not being installable:
> {noformat}
> >npm install -g cordova@5.1.1
> npm WARN engine cordova-js@4.0.0: wanted: {"node":"~0.10.x"} (current:
> {"node":"0.12.6","npm":"2.11.2"})
> npm WARN engine npm@1.3.4: wanted: {"node":">=0.6","npm":"1"} (current:
> {"node":"0.12.6","npm":"2.11.2"})
> npm WARN engine xmlbuilder@2.2.1: wanted: {"node":"0.8.x || 0.10.x"}
> (current: {"node":"0.12.6","npm":"2.11.2"})
> npm WARN installMany normalize-package-data was bundled with npm@1.3.4, but
> bundled package wasn't found in unpacked tree
> C:\Users\robert\AppData\Roaming\npm\cordova ->
> C:\Users\robert\AppData\Roaming\npm\node_modules\cordova\bin\cordova
> cordova@5.1.1 C:\Users\robert\AppData\Roaming\npm\node_modules\cordova
> ├── underscore@1.7.0
> ├── q@1.0.1
> ├── nopt@3.0.1 (abbrev@1.0.7)
> └── cordova-lib@5.1.1 (valid-identifier@0.0.1, osenv@0.1.0,
> properties-parser@0.2.3, bplist-parser@0.0.6, mime@1.2.11, unorm@1.3.3,
> semver@2.1.0, rc@0.5.2, shelljs@0.3.0, dep-graph@1.1.0, through2@0.6.3,
> npmconf@0.1.16, xcode@0.6.7, d8@0.4.4, init-package-json@1.7.0,
> elementtree@0.1.6, request@2.47.0, glob@4.0.6, cordova-registry-mapper@1.1.8,
> tar@1.0.2, cordova-app-hello-world@3.9.0, cordova-js@4.0.0, plist@1.1.0,
> npm@1.3.4)
> {noformat}
> Thanks in advance.
--
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-9370) Cordova-js tests are failing on node 0.12
[
https://issues.apache.org/jira/browse/CB-9370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Kotikov updated CB-9370:
-
Description:
Since https://github.com/apache/cordova-js/pull/118 unit tests for cordova-js
started failing on AppVeyor CI with unclear message {{Fatal error: Cannot set
property length of [object Object] which has only a getter}}.
It looks like the origin of failures - updated NodeJS version on AppVeyor build
machines. Failure also can be reproduced on local machine with Node@0.12.5
installed.
The reason of failures - is outdated {{jsdom-nogyp}} dependency (last updated
about 2 years ago). The solution is to replace {{jsdom-nogyp}} with original
{{node-jsdom}}, which works fine with node@12.x. It also would be great to test
such cases through CI.
> Cordova-js tests are failing on node 0.12
> -
>
> Key: CB-9370
> URL: https://issues.apache.org/jira/browse/CB-9370
> Project: Apache Cordova
> Issue Type: Bug
> Components: CordovaJS
>Affects Versions: 4.1.0
> Environment: Windows/Mac OSX machine,
> Node JS 0.12.7
>Reporter: Vladimir Kotikov
>Assignee: Vladimir Kotikov
> Labels: cordova-js
> Fix For: 4.1.0
>
>
> Since https://github.com/apache/cordova-js/pull/118 unit tests for cordova-js
> started failing on AppVeyor CI with unclear message {{Fatal error: Cannot set
> property length of [object Object] which has only a getter}}.
> It looks like the origin of failures - updated NodeJS version on AppVeyor
> build machines. Failure also can be reproduced on local machine with
> Node@0.12.5 installed.
> The reason of failures - is outdated {{jsdom-nogyp}} dependency (last updated
> about 2 years ago). The solution is to replace {{jsdom-nogyp}} with original
> {{node-jsdom}}, which works fine with node@12.x. It also would be great to
> test such cases through CI.
--
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-9370) Cordova-js tests are failing on node 0.12
[
https://issues.apache.org/jira/browse/CB-9370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628037#comment-14628037
]
ASF GitHub Bot commented on CB-9370:
GitHub user vladimir-kotikov opened a pull request:
https://github.com/apache/cordova-js/pull/121
CB-9370 Fixes failing tests on Node 0.12 due to stale dependency
This PR fixes tests on AppVeyor, broken by updated NodeJS on CI machines as
described in [CB-9370](https://issues.apache.org/jira/browse/CB-9370). It also
adds build matrix that includes node 0.10 and 0.12 for both Travis and AppVeyor.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/MSOpenTech/cordova-js CB-9370
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cordova-js/pull/121.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 #121
commit 715e2bbefc25ca9c20f476c2f5f2a906b1356c85
Author: Vladimir Kotikov
Date: 2015-07-15T13:00:17Z
CB-9291 Loosens requirement for NodeJS version
commit 55003223d23dbf1dd20fa5c21a70c9d0fdf96db3
Author: Vladimir Kotikov
Date: 2015-07-15T13:05:21Z
CB-9370 Fixes failing tests on Node 0.12 due to stale dependency
This also adds Node@0.12 to test matrix for both Travis and AppVeyor
> Cordova-js tests are failing on node 0.12
> -
>
> Key: CB-9370
> URL: https://issues.apache.org/jira/browse/CB-9370
> Project: Apache Cordova
> Issue Type: Bug
> Components: CordovaJS
>Affects Versions: 4.1.0
> Environment: Windows/Mac OSX machine,
> Node JS 0.12.7
>Reporter: Vladimir Kotikov
>Assignee: Vladimir Kotikov
> Labels: cordova-js
> Fix For: 4.1.0
>
>
> Since https://github.com/apache/cordova-js/pull/118 unit tests for cordova-js
> started failing on AppVeyor CI with unclear message {{Fatal error: Cannot set
> property length of [object Object] which has only a getter}}.
> It looks like the origin of failures - updated NodeJS version on AppVeyor
> build machines. Failure also can be reproduced on local machine with
> Node@0.12.5 installed.
> The reason of failures - is outdated {{jsdom-nogyp}} dependency (last updated
> about 2 years ago). The solution is to replace {{jsdom-nogyp}} with original
> {{node-jsdom}}, which works fine with node@12.x. It also would be great to
> test such cases through CI.
--
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-9240) Cordova splash screen plugin iPad landscape mode issue
[
https://issues.apache.org/jira/browse/CB-9240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628081#comment-14628081
]
Hetal commented on CB-9240:
---
Hi Scott,
This is what my info.plist entries look like:
UISupportedInterfaceOrientations
UIInterfaceOrientationPortrait
UISupportedInterfaceOrientations~ipad
UIInterfaceOrientationPortrait
UIInterfaceOrientationLandscapeLeft
UIInterfaceOrientationPortraitUpsideDown
UIInterfaceOrientationLandscapeRight
UILaunchImages
UILaunchImageMinimumOSVersion
8.0
UILaunchImageName
Default
UILaunchImageOrientation
Portrait
UILaunchImageSize
{320, 480}
UILaunchImageMinimumOSVersion
8.0
UILaunchImageName
Default
UILaunchImageOrientation
Landscape
UILaunchImageSize
{320, 480}
UILaunchImageMinimumOSVersion
8.0
UILaunchImageName
Default-568h
UILaunchImageOrientation
Portrait
UILaunchImageSize
{320, 568}
UILaunchImageMinimumOSVersion
8.0
UILaunchImageName
Default-568h
UILaunchImageOrientation
Landscape
UILaunchImageSize
{320, 568}
UILaunchImageMinimumOSVersion
8.0
UILaunchImageName
Default-667h
UILaunchImageOrientation
Portrait
UILaunchImageSize
{375, 667}
UILaunchImageMinimumOSVersion
8.0
UILaunchImageName
Default-667h
UILaunchImageOrientation
Landscape
UILaunchImageSize
{375, 667}
UILaunchImageMinimumOSVersion
8.0
UILaunchImageName
Default-736h
UILaunchImageOrientation
Portrait
UILaunchImageSize
{414, 736}
UILaunchImageMinimumOSVersion
8.0
UILaunchImageName
Default-Landscape-736h
UILaunchImageOrientation
Landscape
UILaunchImageSize
{414, 736}
UILaunchImageMinimumOSVersion
8.0
UILaunchImageName
Default-Portrait
UILaunchImageOrientation
Portrait
UILaunchImageSize
{768, 1024}
UILaunchImageMinimumOSVersion
8.0
UILaunchImageName
Default-Landscape
UILaunchImageOrientation
Landscape
UILaunchImageSize
{768, 1024}
> Cordova splash screen plugin iPad landscape mode issue
> --
>
> Key: CB-9240
> URL: https://issues.apache.org/jira/browse/CB-9240
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin SplashScreen
> Environment: iPad iOS 8
>Reporter: Hetal
> Labels: ios, landscape, plugin, splashscreen
>
> I am using the Cordova splash screen plugin
> (https://github.com/apache/cordova-plugin-splashscreen) in my hybrid mobile
> app targeted for iOS. I have all the splash screen images added to my
> project. The reason for using this plugin is to elongate the time for which
> the s
[jira] [Commented] (CB-9291) Cordova NPM package does not install when Node >= 0.12.x
[
https://issues.apache.org/jira/browse/CB-9291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628156#comment-14628156
]
Nikhil Khandelwal commented on CB-9291:
---
This is the commit which adds it:
https://github.com/apache/cordova-js/commit/a7daa9efe9632715ca67dd81863a875958415501
and it's unclear why we add it. We're going to do a release soon and it would
be nice to get this in.
I would just remove it altogether. +[~stevegill]] to see if we need it for some
reason.
> Cordova NPM package does not install when Node >= 0.12.x
>
>
> Key: CB-9291
> URL: https://issues.apache.org/jira/browse/CB-9291
> Project: Apache Cordova
> Issue Type: Bug
> Components: CordovaJS
>Affects Versions: 4.0.0
> Environment: Windows7 x64 with NodeJS 0.12.6
>Reporter: Robert
>Assignee: Vladimir Kotikov
>Priority: Critical
>
> Hi
> I am trying to install cordova in version 5.1.1 (also tried some previous
> versions) using node 0.12.6:
> npm cache clean dep-graph
> npm install -g cordova@5.1.1
> Unfortunately, cordova-js depends on an older version of node (~0.10.x) which
> seems the reason for cordova not being installable:
> {noformat}
> >npm install -g cordova@5.1.1
> npm WARN engine cordova-js@4.0.0: wanted: {"node":"~0.10.x"} (current:
> {"node":"0.12.6","npm":"2.11.2"})
> npm WARN engine npm@1.3.4: wanted: {"node":">=0.6","npm":"1"} (current:
> {"node":"0.12.6","npm":"2.11.2"})
> npm WARN engine xmlbuilder@2.2.1: wanted: {"node":"0.8.x || 0.10.x"}
> (current: {"node":"0.12.6","npm":"2.11.2"})
> npm WARN installMany normalize-package-data was bundled with npm@1.3.4, but
> bundled package wasn't found in unpacked tree
> C:\Users\robert\AppData\Roaming\npm\cordova ->
> C:\Users\robert\AppData\Roaming\npm\node_modules\cordova\bin\cordova
> cordova@5.1.1 C:\Users\robert\AppData\Roaming\npm\node_modules\cordova
> ├── underscore@1.7.0
> ├── q@1.0.1
> ├── nopt@3.0.1 (abbrev@1.0.7)
> └── cordova-lib@5.1.1 (valid-identifier@0.0.1, osenv@0.1.0,
> properties-parser@0.2.3, bplist-parser@0.0.6, mime@1.2.11, unorm@1.3.3,
> semver@2.1.0, rc@0.5.2, shelljs@0.3.0, dep-graph@1.1.0, through2@0.6.3,
> npmconf@0.1.16, xcode@0.6.7, d8@0.4.4, init-package-json@1.7.0,
> elementtree@0.1.6, request@2.47.0, glob@4.0.6, cordova-registry-mapper@1.1.8,
> tar@1.0.2, cordova-app-hello-world@3.9.0, cordova-js@4.0.0, plist@1.1.0,
> npm@1.3.4)
> {noformat}
> Thanks in advance.
--
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-9370) Cordova-js tests are failing on node 0.12
[
https://issues.apache.org/jira/browse/CB-9370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628168#comment-14628168
]
ASF GitHub Bot commented on CB-9370:
Github user nikhilkh commented on the pull request:
https://github.com/apache/cordova-js/pull/121#issuecomment-121638909
LGTM overall.
> Cordova-js tests are failing on node 0.12
> -
>
> Key: CB-9370
> URL: https://issues.apache.org/jira/browse/CB-9370
> Project: Apache Cordova
> Issue Type: Bug
> Components: CordovaJS
>Affects Versions: 4.1.0
> Environment: Windows/Mac OSX machine,
> Node JS 0.12.7
>Reporter: Vladimir Kotikov
>Assignee: Vladimir Kotikov
> Labels: cordova-js
> Fix For: 4.1.0
>
>
> Since https://github.com/apache/cordova-js/pull/118 unit tests for cordova-js
> started failing on AppVeyor CI with unclear message {{Fatal error: Cannot set
> property length of [object Object] which has only a getter}}.
> It looks like the origin of failures - updated NodeJS version on AppVeyor
> build machines. Failure also can be reproduced on local machine with
> Node@0.12.5 installed.
> The reason of failures - is outdated {{jsdom-nogyp}} dependency (last updated
> about 2 years ago). The solution is to replace {{jsdom-nogyp}} with original
> {{node-jsdom}}, which works fine with node@12.x. It also would be great to
> test such cases through CI.
--
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-9370) Cordova-js tests are failing on node 0.12
[
https://issues.apache.org/jira/browse/CB-9370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628166#comment-14628166
]
ASF GitHub Bot commented on CB-9370:
Github user nikhilkh commented on a diff in the pull request:
https://github.com/apache/cordova-js/pull/121#discussion_r34685625
--- Diff: package.json ---
@@ -9,7 +9,7 @@
"url": "http://git-wip-us.apache.org/repos/asf/cordova-js.git";
},
"engines": {
-"node": "~0.10.x"
+"node": ">=0.10.x"
--- End diff --
This seems fine and should be a non-issue for most people - but I think we
should just remove it unless we really have a dependency on node >= 0.10
> Cordova-js tests are failing on node 0.12
> -
>
> Key: CB-9370
> URL: https://issues.apache.org/jira/browse/CB-9370
> Project: Apache Cordova
> Issue Type: Bug
> Components: CordovaJS
>Affects Versions: 4.1.0
> Environment: Windows/Mac OSX machine,
> Node JS 0.12.7
>Reporter: Vladimir Kotikov
>Assignee: Vladimir Kotikov
> Labels: cordova-js
> Fix For: 4.1.0
>
>
> Since https://github.com/apache/cordova-js/pull/118 unit tests for cordova-js
> started failing on AppVeyor CI with unclear message {{Fatal error: Cannot set
> property length of [object Object] which has only a getter}}.
> It looks like the origin of failures - updated NodeJS version on AppVeyor
> build machines. Failure also can be reproduced on local machine with
> Node@0.12.5 installed.
> The reason of failures - is outdated {{jsdom-nogyp}} dependency (last updated
> about 2 years ago). The solution is to replace {{jsdom-nogyp}} with original
> {{node-jsdom}}, which works fine with node@12.x. It also would be great to
> test such cases through CI.
--
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-9366) Log error.stack when a call to a plugin throws an exception
[ https://issues.apache.org/jira/browse/CB-9366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628175#comment-14628175 ] ASF GitHub Bot commented on CB-9366: Github user nikhilkh commented on the pull request: https://github.com/apache/cordova-js/pull/118#issuecomment-121640154 What's the downside of adding this? This is really an exceptional scenario and should not hit commonly to clutter console log with ugly stack traces. Also, rethrowing the error will reset it's stack property - depending on which runtime and platform you are using and hence. window.onerror might not get the actual stack that caused the error. Putting it in console.log makes sure it shows in ADB logcat, Windows debug logs - hence, it makes it easier for people to root cause such issues. > Log error.stack when a call to a plugin throws an exception > --- > > Key: CB-9366 > URL: https://issues.apache.org/jira/browse/CB-9366 > Project: Apache Cordova > Issue Type: Improvement > Components: CordovaJS >Affects Versions: Master >Reporter: Nikhil Khandelwal >Assignee: Nikhil Khandelwal >Priority: Minor > > This can help in isolating the cause of the 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-9370) Cordova-js tests are failing on node 0.12
[
https://issues.apache.org/jira/browse/CB-9370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628180#comment-14628180
]
ASF GitHub Bot commented on CB-9370:
Github user vladimir-kotikov commented on a diff in the pull request:
https://github.com/apache/cordova-js/pull/121#discussion_r34686348
--- Diff: package.json ---
@@ -9,7 +9,7 @@
"url": "http://git-wip-us.apache.org/repos/asf/cordova-js.git";
},
"engines": {
-"node": "~0.10.x"
+"node": ">=0.10.x"
--- End diff --
Sounds good. @stevengill, what do you think?
> Cordova-js tests are failing on node 0.12
> -
>
> Key: CB-9370
> URL: https://issues.apache.org/jira/browse/CB-9370
> Project: Apache Cordova
> Issue Type: Bug
> Components: CordovaJS
>Affects Versions: 4.1.0
> Environment: Windows/Mac OSX machine,
> Node JS 0.12.7
>Reporter: Vladimir Kotikov
>Assignee: Vladimir Kotikov
> Labels: cordova-js
> Fix For: 4.1.0
>
>
> Since https://github.com/apache/cordova-js/pull/118 unit tests for cordova-js
> started failing on AppVeyor CI with unclear message {{Fatal error: Cannot set
> property length of [object Object] which has only a getter}}.
> It looks like the origin of failures - updated NodeJS version on AppVeyor
> build machines. Failure also can be reproduced on local machine with
> Node@0.12.5 installed.
> The reason of failures - is outdated {{jsdom-nogyp}} dependency (last updated
> about 2 years ago). The solution is to replace {{jsdom-nogyp}} with original
> {{node-jsdom}}, which works fine with node@12.x. It also would be great to
> test such cases through CI.
--
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-9371) Prepare deletes orientation preferences
Connor Pearson created CB-9371: -- Summary: Prepare deletes orientation preferences Key: CB-9371 URL: https://issues.apache.org/jira/browse/CB-9371 Project: Apache Cordova Issue Type: Bug Components: CordovaLib Affects Versions: 5.1.1 Reporter: Connor Pearson If a user does not have a orientation preference defined in config.xml then running prepare will delete all orientation preferences in their info.plist. I'd expect prepare to overwrite the values if the user chose an orientation preferences, otherwise it should respect the values that are already there. -- 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-9371) Prepare deletes orientation preferences
[ https://issues.apache.org/jira/browse/CB-9371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628229#comment-14628229 ] ASF GitHub Bot commented on CB-9371: GitHub user cjpearson opened a pull request: https://github.com/apache/cordova-lib/pull/260 CB-9371: Don't delete orientation preferences by default You can merge this pull request into a Git repository by running: $ git pull https://github.com/cjpearson/cordova-lib orientation-bug Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-lib/pull/260.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 #260 commit a3c86157dd5354db26ba18eabc40cb8eaa8e0351 Author: Connor Pearson Date: 2015-07-15T15:06:09Z Don't delete orientation preferences by default > Prepare deletes orientation preferences > --- > > Key: CB-9371 > URL: https://issues.apache.org/jira/browse/CB-9371 > Project: Apache Cordova > Issue Type: Bug > Components: CordovaLib >Affects Versions: 5.1.1 >Reporter: Connor Pearson > > If a user does not have a orientation preference defined in config.xml then > running prepare will delete all orientation preferences in their info.plist. > I'd expect prepare to overwrite the values if the user chose an orientation > preferences, otherwise it should respect the values that are already there. -- 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-9372) cordova-android project template contains unused files (main.js/main.css)
Holly Schinsky created CB-9372: -- Summary: cordova-android project template contains unused files (main.js/main.css) Key: CB-9372 URL: https://issues.apache.org/jira/browse/CB-9372 Project: Apache Cordova Issue Type: Task Components: Android Reporter: Holly Schinsky Priority: Minor The apache-android create script produces a default project with extra files in the root folder that are not needed and could cause confusion - *main.js* and *main.css*. -- 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-9370) Cordova-js tests are failing on node 0.12
[
https://issues.apache.org/jira/browse/CB-9370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628444#comment-14628444
]
ASF GitHub Bot commented on CB-9370:
Github user stevengill commented on a diff in the pull request:
https://github.com/apache/cordova-js/pull/121#discussion_r34707474
--- Diff: package.json ---
@@ -9,7 +9,7 @@
"url": "http://git-wip-us.apache.org/repos/asf/cordova-js.git";
},
"engines": {
-"node": "~0.10.x"
+"node": ">=0.10.x"
--- End diff --
yeah, not needed IMO
> Cordova-js tests are failing on node 0.12
> -
>
> Key: CB-9370
> URL: https://issues.apache.org/jira/browse/CB-9370
> Project: Apache Cordova
> Issue Type: Bug
> Components: CordovaJS
>Affects Versions: 4.1.0
> Environment: Windows/Mac OSX machine,
> Node JS 0.12.7
>Reporter: Vladimir Kotikov
>Assignee: Vladimir Kotikov
> Labels: cordova-js
> Fix For: 4.1.0
>
>
> Since https://github.com/apache/cordova-js/pull/118 unit tests for cordova-js
> started failing on AppVeyor CI with unclear message {{Fatal error: Cannot set
> property length of [object Object] which has only a getter}}.
> It looks like the origin of failures - updated NodeJS version on AppVeyor
> build machines. Failure also can be reproduced on local machine with
> Node@0.12.5 installed.
> The reason of failures - is outdated {{jsdom-nogyp}} dependency (last updated
> about 2 years ago). The solution is to replace {{jsdom-nogyp}} with original
> {{node-jsdom}}, which works fine with node@12.x. It also would be great to
> test such cases through CI.
--
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-9273) "Copy www build phase" node is not found
[
https://issues.apache.org/jira/browse/CB-9273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628465#comment-14628465
]
Sergey Shakhnazarov commented on CB-9273:
-
[~shazron], what do you think of extending Xcode PATH like this?
{code}
shellScript = "export PATH=/usr/local/bin:~/.nvm/`nvm
version`/bin:`xcode-select --print-path`/usr/share/xcs/Node/bin:$PATH && node
cordova/lib/copy-www-build-step.js";
{code}
Do we need to handle absence of *nvm* additionally?
> "Copy www build phase" node is not found
>
>
> Key: CB-9273
> URL: https://issues.apache.org/jira/browse/CB-9273
> Project: Apache Cordova
> Issue Type: Bug
> Components: iOS
> Environment: cordova-ios 4.x
>Reporter: Shazron Abdullah
> Attachments: xcode-build-phase-node.png
>
>
> I have node installed using nvm, and the build phase cannot find node.
> The path to node in nvm is in $PATH in Terminal. It may not be in Xcode's
> environment variables.
--
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-8627) 'cordova plugin add git_url' erroneously updates fetch.json even when the 'add operation fails'
[ https://issues.apache.org/jira/browse/CB-8627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628483#comment-14628483 ] ASF GitHub Bot commented on CB-8627: Github user dblotsky commented on the pull request: https://github.com/apache/cordova-lib/pull/228#issuecomment-121700137 What's the status on this PR? > 'cordova plugin add git_url' erroneously updates fetch.json even when the > 'add operation fails' > --- > > Key: CB-8627 > URL: https://issues.apache.org/jira/browse/CB-8627 > Project: Apache Cordova > Issue Type: Bug > Components: CLI >Reporter: Omar Mefire >Assignee: Omar Mefire > > - cordova plugin add https://github.com/Wizcorp/phonegap-facebook-plugin.git > This results in fetch.json being updated with the plugin info even though > the plugin installation failed. It should not be the case. -- 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-9272) App crashes on on iPad when run on PGB
[ https://issues.apache.org/jira/browse/CB-9272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628545#comment-14628545 ] jcesarmobile edited comment on CB-9272 at 7/15/15 6:56 PM: --- I just can confirm that is a bug related to iOS 7 SDK I can reproduce it using phonegap build, or executing from Xcode 5, or installing iOS 7 SDK on Xcode 6 (/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/) and installing from there. The issue doesn't appear if I remove iOS 7 SDK from Xcode 6 or before installing it So, the problem might be that phonegap build uses Xcode 5, or they use Xcode 6 but they have iOS 7 SDK installed. I've found this phonegap build issue tracker, maybe you can report the issue there https://github.com/phonegap/build/issues/ EDIT: There is already an issue for this https://github.com/phonegap/build/issues/444 was (Author: jcesarmobile): I just can confirm that is a bug related to iOS 7 SDK I can reproduce it using phonegap build, or executing from Xcode 5, or installing iOS 7 SDK on Xcode 6 (/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/) and installing from there. The issue doesn't appear if I remove iOS 7 SDK from Xcode 6 or before installing it So, the problem might be that phonegap build uses Xcode 5, or they use Xcode 6 but they have iOS 7 SDK installed. I've found this phonegap build issue tracker, maybe you can report the issue there https://github.com/phonegap/build/issues/ > App crashes on on iPad when run on PGB > -- > > Key: CB-9272 > URL: https://issues.apache.org/jira/browse/CB-9272 > Project: Apache Cordova > Issue Type: Bug > Environment: iPad Air (model#: MD788NF/A) >Reporter: Leroy van Engelen >Assignee: jcesarmobile > Attachments: appbase.zip > > > See https://issues.apache.org/jira/browse/CB-7577 -- 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-9272) App crashes on on iPad when run on PGB
[ https://issues.apache.org/jira/browse/CB-9272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628545#comment-14628545 ] jcesarmobile commented on CB-9272: -- I just can confirm that is a bug related to iOS 7 SDK I can reproduce it using phonegap build, or executing from Xcode 5, or installing iOS 7 SDK on Xcode 6 (/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/) and installing from there. The issue doesn't appear if I remove iOS 7 SDK from Xcode 6 or before installing it So, the problem might be that phonegap build uses Xcode 5, or they use Xcode 6 but they have iOS 7 SDK installed. I've found this phonegap build issue tracker, maybe you can report the issue there https://github.com/phonegap/build/issues/ > App crashes on on iPad when run on PGB > -- > > Key: CB-9272 > URL: https://issues.apache.org/jira/browse/CB-9272 > Project: Apache Cordova > Issue Type: Bug > Environment: iPad Air (model#: MD788NF/A) >Reporter: Leroy van Engelen >Assignee: jcesarmobile > Attachments: appbase.zip > > > See https://issues.apache.org/jira/browse/CB-7577 -- 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-8789) Cordova iOS to support Asset Catalog for App icons and slapshscreens
[ https://issues.apache.org/jira/browse/CB-8789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628634#comment-14628634 ] ASF GitHub Bot commented on CB-8789: GitHub user theaccordance opened a pull request: https://github.com/apache/cordova-ios/pull/148 CB-8789 Asset Catalog support JIRA Issue: https://issues.apache.org/jira/browse/CB-8789 - Updated xcode templates to use Asset Catalog for icons and splash screens You can merge this pull request into a Git repository by running: $ git pull https://github.com/theaccordance/cordova-ios CB-8789 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-ios/pull/148.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 #148 commit ff4872e37f4657d86e41030c18c2b0c5bc3689f2 Author: Joe Mainwaring Date: 2015-07-15T19:55:56Z CB-8789 Asset Catalog support - Updated xcode templates to use Asset Catalog for icons and splash screens > Cordova iOS to support Asset Catalog for App icons and slapshscreens > > > Key: CB-8789 > URL: https://issues.apache.org/jira/browse/CB-8789 > Project: Apache Cordova > Issue Type: Improvement > Components: iOS >Reporter: Carlos Santana > > IBM has a future requirement to support Asset Catalog for App icons and > splash screens in our downstream distribution (MobileFirst) of Cordova. > Enterprise use cases: > Leverage Catalog Assets to manage splash screens and app icons, instead of > using deprecated methods. > Tasks: > - Modify Xcode project structure for Cordova to use Asset Catalog > - Modify Cordova CLI to manage icons and spashscreens my managing Asset > Catalog content. > IBM has intention on working on this changes in Cordova, but if someone else > wants to work on it before we get to it that also works for us :-) > Related JIRA issues: > [CB-8027 | https://issues.apache.org/jira/browse/CB-8027] -- 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-9273) "Copy www build phase" node is not found
[
https://issues.apache.org/jira/browse/CB-9273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628637#comment-14628637
]
Shazron Abdullah commented on CB-9273:
--
Your suggestion is even better!
I think a temporary PATH change works, I just tested it.
So, we change:
{code}
node cordova/lib/copy-www-build-step.js
{code}
To:
{code}
PATH=/usr/local/bin:~/.nvm/`nvm version`/bin:`xcode-select
--print-path`/usr/share/xcs/Node/bin:$PATH node
cordova/lib/copy-www-build-step.js
{code}
We could amend this to support "n" package manager as well:
https://github.com/tj/n
Not sure yet of the pathing for that.
> "Copy www build phase" node is not found
>
>
> Key: CB-9273
> URL: https://issues.apache.org/jira/browse/CB-9273
> Project: Apache Cordova
> Issue Type: Bug
> Components: iOS
> Environment: cordova-ios 4.x
>Reporter: Shazron Abdullah
> Attachments: xcode-build-phase-node.png
>
>
> I have node installed using nvm, and the build phase cannot find node.
> The path to node in nvm is in $PATH in Terminal. It may not be in Xcode's
> environment variables.
--
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-8789) Cordova iOS to support Asset Catalog for App icons and slapshscreens
[ https://issues.apache.org/jira/browse/CB-8789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628639#comment-14628639 ] ASF GitHub Bot commented on CB-8789: GitHub user theaccordance opened a pull request: https://github.com/apache/cordova-lib/pull/261 Cb-8789 JIRA Issue: https://issues.apache.org/jira/browse/CB-8789 Updated ios_parser.js script to copy icon & launch image files to asset catalog location You can merge this pull request into a Git repository by running: $ git pull https://github.com/theaccordance/cordova-lib CB-8789 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-lib/pull/261.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 #261 commit 61420d8ed292efcd1118f0061ac08c78e7ff89b3 Author: Joe Mainwaring Date: 2015-07-13T22:12:41Z CB-8789 iOS Asset Catalog Support - updated destination path for copying icons and launch images commit c437a0b179d43482de738ea290ad05f8c4da0519 Author: Joe Mainwaring Date: 2015-07-15T20:04:54Z Merge branch 'master' of https://git-wip-us.apache.org/repos/asf/cordova-lib into CB-8789 > Cordova iOS to support Asset Catalog for App icons and slapshscreens > > > Key: CB-8789 > URL: https://issues.apache.org/jira/browse/CB-8789 > Project: Apache Cordova > Issue Type: Improvement > Components: iOS >Reporter: Carlos Santana > > IBM has a future requirement to support Asset Catalog for App icons and > splash screens in our downstream distribution (MobileFirst) of Cordova. > Enterprise use cases: > Leverage Catalog Assets to manage splash screens and app icons, instead of > using deprecated methods. > Tasks: > - Modify Xcode project structure for Cordova to use Asset Catalog > - Modify Cordova CLI to manage icons and spashscreens my managing Asset > Catalog content. > IBM has intention on working on this changes in Cordova, but if someone else > wants to work on it before we get to it that also works for us :-) > Related JIRA issues: > [CB-8027 | https://issues.apache.org/jira/browse/CB-8027] -- 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-9366) Log error.stack when a call to a plugin throws an exception
[ https://issues.apache.org/jira/browse/CB-9366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628664#comment-14628664 ] ASF GitHub Bot commented on CB-9366: Github user purplecabbage commented on the pull request: https://github.com/apache/cordova-js/pull/118#issuecomment-121736314 Not a huge deal. I was assuming that most errors here would be the result of a missing callback, in which case stack.length is 0. In the case where the user has an error in their success/error handler this might help them, but I am still not sure how much more value they would get than window.onerror > Log error.stack when a call to a plugin throws an exception > --- > > Key: CB-9366 > URL: https://issues.apache.org/jira/browse/CB-9366 > Project: Apache Cordova > Issue Type: Improvement > Components: CordovaJS >Affects Versions: Master >Reporter: Nikhil Khandelwal >Assignee: Nikhil Khandelwal >Priority: Minor > > This can help in isolating the cause of the 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-9273) "Copy www build phase" node is not found
[
https://issues.apache.org/jira/browse/CB-9273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628669#comment-14628669
]
Shazron Abdullah commented on CB-9273:
--
For the "n" package manager its a bit tricky.
All installed node versions are installed at:
{code}
/usr/local/n/versions/node
{code}
... where the different versions are in subfolders with the version number as
the folder name. We'll have to assume that we should use the latest version.
So, the path to the latest "n" package manager node version bin folder is:
{code}
/usr/local/n/versions/node/`find /usr/local/n/versions/node -type d -maxdepth 1
-exec basename {} \; | tail -1`/bin
{code}
That's my first stab at it, maybe there's a simpler way. I couldn't find any
info in the "n" docs.
> "Copy www build phase" node is not found
>
>
> Key: CB-9273
> URL: https://issues.apache.org/jira/browse/CB-9273
> Project: Apache Cordova
> Issue Type: Bug
> Components: iOS
> Environment: cordova-ios 4.x
>Reporter: Shazron Abdullah
> Attachments: xcode-build-phase-node.png
>
>
> I have node installed using nvm, and the build phase cannot find node.
> The path to node in nvm is in $PATH in Terminal. It may not be in Xcode's
> environment variables.
--
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-9273) "Copy www build phase" node is not found
[
https://issues.apache.org/jira/browse/CB-9273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628669#comment-14628669
]
Shazron Abdullah edited comment on CB-9273 at 7/15/15 8:27 PM:
---
For the "n" package manager it's a bit tricky.
All installed node versions are installed at:
{code}
/usr/local/n/versions/node
{code}
... where the different versions are in subfolders with the version number as
the folder name. We'll have to assume that we should use the latest version.
So, the path to the latest "n" package manager node version bin folder is:
{code}
/usr/local/n/versions/node/`find /usr/local/n/versions/node -type d -maxdepth 1
-exec basename {} \; | tail -1`/bin
{code}
That's my first stab at it, maybe there's a simpler way. I couldn't find any
info in the "n" docs.
was (Author: shazron):
For the "n" package manager its a bit tricky.
All installed node versions are installed at:
{code}
/usr/local/n/versions/node
{code}
... where the different versions are in subfolders with the version number as
the folder name. We'll have to assume that we should use the latest version.
So, the path to the latest "n" package manager node version bin folder is:
{code}
/usr/local/n/versions/node/`find /usr/local/n/versions/node -type d -maxdepth 1
-exec basename {} \; | tail -1`/bin
{code}
That's my first stab at it, maybe there's a simpler way. I couldn't find any
info in the "n" docs.
> "Copy www build phase" node is not found
>
>
> Key: CB-9273
> URL: https://issues.apache.org/jira/browse/CB-9273
> Project: Apache Cordova
> Issue Type: Bug
> Components: iOS
> Environment: cordova-ios 4.x
>Reporter: Shazron Abdullah
> Attachments: xcode-build-phase-node.png
>
>
> I have node installed using nvm, and the build phase cannot find node.
> The path to node in nvm is in $PATH in Terminal. It may not be in Xcode's
> environment variables.
--
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-9359) Add support for app package bundling to Windows 8.1 / Windows 10
[ https://issues.apache.org/jira/browse/CB-9359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628691#comment-14628691 ] ASF GitHub Bot commented on CB-9359: GitHub user robpaveza opened a pull request: https://github.com/apache/cordova-windows/pull/101 CB-9359: Adds support for .appxbundle creation .appxbundle files are convenient app packages which can be uploaded to the Windows Store. They contain debug or release (typically release) versions of more than one of the x86, x64, and ARM architecture builds. To enable bundling, simply build for multiple architectures: cordova build windows -- --archs="x86 x64 arm" Bundling is disabled if `anycpu` is one of the architectures (or is the default architecture). You can explicitly disable bundling by passing the `--no-bundle` flag: cordova build windows -- --archs="x86 x64 arm" --no-bundle Bundling is not supported for Windows 8 as the feature is not available for that platform in general. You can merge this pull request into a Git repository by running: $ git pull https://github.com/MSOpenTech/cordova-windows CB-9359 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-windows/pull/101.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 #101 commit 97bc543d4983f93223d700aec3aadfaeb4e1e961 Author: Rob Paveza Date: 2015-07-13T20:37:45Z CB-9359: Adds support for .appxbundle creation .appxbundle files are convenient app packages which can be uploaded to the Windows Store. They contain debug or release (typically release) versions of more than one of the x86, x64, and ARM architecture builds. To enable bundling, simply build for multiple architectures: cordova build windows -- --archs="x86 x64 arm" Bundling is disabled if `anycpu` is one of the architectures (or is the default architecture). You can explicitly disable bundling by passing the `--no-bundle` flag: cordova build windows -- --archs="x86 x64 arm" --no-bundle Bundling is not supported for Windows 8 as the feature is not available for that platform in general. > Add support for app package bundling to Windows 8.1 / Windows 10 > > > Key: CB-9359 > URL: https://issues.apache.org/jira/browse/CB-9359 > Project: Apache Cordova > Issue Type: Task > Components: Windows >Reporter: Rob Paveza >Assignee: Rob Paveza > > When generating a release build, developers are able to submit a single > binary (an .appx bundle) to the Windows Store to avoid having to upload > multiple app packages (particularly when building an architecture-specific > app). This task should add a --bundle flag to enable automatic creation of > an .appxbundle for upload of the app to the Store. -- 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-9273) "Copy www build phase" node is not found
[
https://issues.apache.org/jira/browse/CB-9273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628693#comment-14628693
]
Shazron Abdullah commented on CB-9273:
--
A better way:
{code}
`find /usr/local/n/versions/node/* -maxdepth 0 -type d | tail -1`/bin
{code}
> "Copy www build phase" node is not found
>
>
> Key: CB-9273
> URL: https://issues.apache.org/jira/browse/CB-9273
> Project: Apache Cordova
> Issue Type: Bug
> Components: iOS
> Environment: cordova-ios 4.x
>Reporter: Shazron Abdullah
> Attachments: xcode-build-phase-node.png
>
>
> I have node installed using nvm, and the build phase cannot find node.
> The path to node in nvm is in $PATH in Terminal. It may not be in Xcode's
> environment variables.
--
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-9273) "Copy www build phase" node is not found
[
https://issues.apache.org/jira/browse/CB-9273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628697#comment-14628697
]
Sergey Shakhnazarov commented on CB-9273:
-
Thank you!
I will also test whether the following works as soon as I get to the Mac
tomorrow:
{code}
$(n bin $(n --latest))
{code}
> "Copy www build phase" node is not found
>
>
> Key: CB-9273
> URL: https://issues.apache.org/jira/browse/CB-9273
> Project: Apache Cordova
> Issue Type: Bug
> Components: iOS
> Environment: cordova-ios 4.x
>Reporter: Shazron Abdullah
> Attachments: xcode-build-phase-node.png
>
>
> I have node installed using nvm, and the build phase cannot find node.
> The path to node in nvm is in $PATH in Terminal. It may not be in Xcode's
> environment variables.
--
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-9273) "Copy www build phase" node is not found
[
https://issues.apache.org/jira/browse/CB-9273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628700#comment-14628700
]
Shazron Abdullah commented on CB-9273:
--
So the final Run Script can look like this:
{code}
NODEJS_PATH=/usr/local/bin
NVM_NODE_PATH=~/.nvm/`nvm version`/bin
N_NODE_PATH=`find /usr/local/n/versions/node/* -maxdepth 0 -type d | tail
-1`/bin
XCODE_NODE_PATH=`xcode-select --print-path`/usr/share/xcs/Node/bin
PATH=$NODEJS_PATH:$NVM_PATH:$N_PATH:$XCODE_NODE_PATH:$PATH node
cordova/lib/copy-www-build-step.js
{code}
> "Copy www build phase" node is not found
>
>
> Key: CB-9273
> URL: https://issues.apache.org/jira/browse/CB-9273
> Project: Apache Cordova
> Issue Type: Bug
> Components: iOS
> Environment: cordova-ios 4.x
>Reporter: Shazron Abdullah
> Attachments: xcode-build-phase-node.png
>
>
> I have node installed using nvm, and the build phase cannot find node.
> The path to node in nvm is in $PATH in Terminal. It may not be in Xcode's
> environment variables.
--
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-8789) Cordova iOS to support Asset Catalog for App icons and slapshscreens
[ https://issues.apache.org/jira/browse/CB-8789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shazron Abdullah updated CB-8789: - Labels: cordova-ios-4.0.x (was: ) > Cordova iOS to support Asset Catalog for App icons and slapshscreens > > > Key: CB-8789 > URL: https://issues.apache.org/jira/browse/CB-8789 > Project: Apache Cordova > Issue Type: Improvement > Components: iOS >Reporter: Carlos Santana > Labels: cordova-ios-4.0.x > > IBM has a future requirement to support Asset Catalog for App icons and > splash screens in our downstream distribution (MobileFirst) of Cordova. > Enterprise use cases: > Leverage Catalog Assets to manage splash screens and app icons, instead of > using deprecated methods. > Tasks: > - Modify Xcode project structure for Cordova to use Asset Catalog > - Modify Cordova CLI to manage icons and spashscreens my managing Asset > Catalog content. > IBM has intention on working on this changes in Cordova, but if someone else > wants to work on it before we get to it that also works for us :-) > Related JIRA issues: > [CB-8027 | https://issues.apache.org/jira/browse/CB-8027] -- 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-9370) Cordova-js tests are failing on node 0.12
[
https://issues.apache.org/jira/browse/CB-9370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628704#comment-14628704
]
ASF GitHub Bot commented on CB-9370:
Github user purplecabbage commented on the pull request:
https://github.com/apache/cordova-js/pull/121#issuecomment-121743440
lgtm!
> Cordova-js tests are failing on node 0.12
> -
>
> Key: CB-9370
> URL: https://issues.apache.org/jira/browse/CB-9370
> Project: Apache Cordova
> Issue Type: Bug
> Components: CordovaJS
>Affects Versions: 4.1.0
> Environment: Windows/Mac OSX machine,
> Node JS 0.12.7
>Reporter: Vladimir Kotikov
>Assignee: Vladimir Kotikov
> Labels: cordova-js
> Fix For: 4.1.0
>
>
> Since https://github.com/apache/cordova-js/pull/118 unit tests for cordova-js
> started failing on AppVeyor CI with unclear message {{Fatal error: Cannot set
> property length of [object Object] which has only a getter}}.
> It looks like the origin of failures - updated NodeJS version on AppVeyor
> build machines. Failure also can be reproduced on local machine with
> Node@0.12.5 installed.
> The reason of failures - is outdated {{jsdom-nogyp}} dependency (last updated
> about 2 years ago). The solution is to replace {{jsdom-nogyp}} with original
> {{node-jsdom}}, which works fine with node@12.x. It also would be great to
> test such cases through CI.
--
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-9359) Add support for app package bundling to Windows 8.1 / Windows 10
[ https://issues.apache.org/jira/browse/CB-9359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628716#comment-14628716 ] ASF GitHub Bot commented on CB-9359: Github user robpaveza closed the pull request at: https://github.com/apache/cordova-windows/pull/101 > Add support for app package bundling to Windows 8.1 / Windows 10 > > > Key: CB-9359 > URL: https://issues.apache.org/jira/browse/CB-9359 > Project: Apache Cordova > Issue Type: Task > Components: Windows >Reporter: Rob Paveza >Assignee: Rob Paveza > > When generating a release build, developers are able to submit a single > binary (an .appx bundle) to the Windows Store to avoid having to upload > multiple app packages (particularly when building an architecture-specific > app). This task should add a --bundle flag to enable automatic creation of > an .appxbundle for upload of the app to the Store. -- 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-9359) Add support for app package bundling to Windows 8.1 / Windows 10
[ https://issues.apache.org/jira/browse/CB-9359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628715#comment-14628715 ] ASF GitHub Bot commented on CB-9359: Github user robpaveza commented on the pull request: https://github.com/apache/cordova-windows/pull/101#issuecomment-121745707 I see a different history on AppVeyor than on my machine, I'm going to close the PR and re-create. > Add support for app package bundling to Windows 8.1 / Windows 10 > > > Key: CB-9359 > URL: https://issues.apache.org/jira/browse/CB-9359 > Project: Apache Cordova > Issue Type: Task > Components: Windows >Reporter: Rob Paveza >Assignee: Rob Paveza > > When generating a release build, developers are able to submit a single > binary (an .appx bundle) to the Windows Store to avoid having to upload > multiple app packages (particularly when building an architecture-specific > app). This task should add a --bundle flag to enable automatic creation of > an .appxbundle for upload of the app to the Store. -- 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-9359) Add support for app package bundling to Windows 8.1 / Windows 10
[ https://issues.apache.org/jira/browse/CB-9359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628723#comment-14628723 ] ASF GitHub Bot commented on CB-9359: GitHub user robpaveza opened a pull request: https://github.com/apache/cordova-windows/pull/102 CB-9359: Adds support for .appxbundle creation .appxbundle files are convenient app packages which can be uploaded to the Windows Store. They contain debug or release (typically release) versions of more than one of the x86, x64, and ARM architecture builds. To enable bundling, simply build for multiple architectures: cordova build windows -- --archs="x86 x64 arm" Bundling is disabled if `anycpu` is one of the architectures (or is the default architecture). You can explicitly disable bundling by passing the `--no-bundle` flag: cordova build windows -- --archs="x86 x64 arm" --no-bundle Bundling is not supported for Windows 8 as the feature is not available for that platform in general. You can merge this pull request into a Git repository by running: $ git pull https://github.com/MSOpenTech/cordova-windows CB-9359 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cordova-windows/pull/102.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 #102 commit 97bc543d4983f93223d700aec3aadfaeb4e1e961 Author: Rob Paveza Date: 2015-07-13T20:37:45Z CB-9359: Adds support for .appxbundle creation .appxbundle files are convenient app packages which can be uploaded to the Windows Store. They contain debug or release (typically release) versions of more than one of the x86, x64, and ARM architecture builds. To enable bundling, simply build for multiple architectures: cordova build windows -- --archs="x86 x64 arm" Bundling is disabled if `anycpu` is one of the architectures (or is the default architecture). You can explicitly disable bundling by passing the `--no-bundle` flag: cordova build windows -- --archs="x86 x64 arm" --no-bundle Bundling is not supported for Windows 8 as the feature is not available for that platform in general. commit 3ea4cd0561ab66da60dcf65bd59e46152919597b Author: Rob Paveza Date: 2015-07-15T20:44:51Z Merge branch 'master' of https://github.com/apache/cordova-windows into CB-9359 Conflicts: template/cordova/lib/build.js template/cordova/lib/run.js > Add support for app package bundling to Windows 8.1 / Windows 10 > > > Key: CB-9359 > URL: https://issues.apache.org/jira/browse/CB-9359 > Project: Apache Cordova > Issue Type: Task > Components: Windows >Reporter: Rob Paveza >Assignee: Rob Paveza > > When generating a release build, developers are able to submit a single > binary (an .appx bundle) to the Windows Store to avoid having to upload > multiple app packages (particularly when building an architecture-specific > app). This task should add a --bundle flag to enable automatic creation of > an .appxbundle for upload of the app to the Store. -- 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-9366) Log error.stack when a call to a plugin throws an exception
[ https://issues.apache.org/jira/browse/CB-9366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628760#comment-14628760 ] ASF GitHub Bot commented on CB-9366: Github user nikhilkh commented on the pull request: https://github.com/apache/cordova-js/pull/118#issuecomment-121752375 If you have multiple calls to cordova methods and one of them might be missing a callback or passing another incorrect argument (like in a scenario similar to the recent `new Media()` bug) a call stack tells you in your code the line which might have resulting in that exception causing your app to crash. The bug fixed in https://github.com/apache/cordova-plugin-media/commit/5f8738c5267be70562df9714e6f3971790b37d19 would have been much easier to identify from buildBot [ADB logs](https://ci.apache.org/builders/cordova-android-win/builds/31/steps/gathering-logs/logs/stdio) if we had a stack. Instead, I had to get into the debugger to identify the issue. > Log error.stack when a call to a plugin throws an exception > --- > > Key: CB-9366 > URL: https://issues.apache.org/jira/browse/CB-9366 > Project: Apache Cordova > Issue Type: Improvement > Components: CordovaJS >Affects Versions: Master >Reporter: Nikhil Khandelwal >Assignee: Nikhil Khandelwal >Priority: Minor > > This can help in isolating the cause of the 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-9278) Restoring multiple platforms fails
[
https://issues.apache.org/jira/browse/CB-9278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628781#comment-14628781
]
Omar Mefire commented on CB-9278:
-
This issue is due to the npmhelper.loadWithSettingsThenRestore function
(https://github.com/apache/cordova-lib/blob/master/cordova-lib/src/util/npm-helper.js#L34)
initializing values that are used across multiple function calls and
javascript/node.js being reentrant.
When restoring a single platform of the form @(e.g:
android@4.3.0), we make a call to lazy_load.npm_cache_add(), which loads some
settings using npm.load, runs the callback provided to npm_cache_add and then
restores npm.load settings.
> Restoring multiple platforms fails
> --
>
> Key: CB-9278
> URL: https://issues.apache.org/jira/browse/CB-9278
> Project: Apache Cordova
> Issue Type: Bug
> Components: CordovaLib
>Affects Versions: Master
> Environment: OS X
>Reporter: Dmitry Blotsky
>Assignee: Omar Mefire
> Labels: cordova-lib, platform, restore, save
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> Steps to reproduce:
> 1. Create a blank app: {{cordova create test com.app.test test}}
> 2. Add and save a platform: {{cordova platform add --save ios}}
> 3. Add and save another platform: {{cordova platform add --save android}}
> 4. Remove the platforms: {{cordova platform remove android ios}}
> 5. Try to restore platforms automatically: {{cordova prepare}}
> Expected: both platforms installed and prepared
> Actual:
> {noformat}
> Error: Trying to initialize npm when settings have not been restored from a
> previous initialization.
> {noformat}
> Running {{cordova prepare}} again fixes the issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Comment Edited] (CB-9278) Restoring multiple platforms fails
[
https://issues.apache.org/jira/browse/CB-9278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628781#comment-14628781
]
Omar Mefire edited comment on CB-9278 at 7/15/15 9:34 PM:
--
This issue is due to the npmhelper.loadWithSettingsThenRestore function
(https://github.com/apache/cordova-lib/blob/master/cordova-lib/src/util/npm-helper.js#L34)
initializing global values (used across multiple function calls) and
javascript/node.js being reentrant.
There is a kind of 'race condition' which arises when we try and restore
multiple platforms.
was (Author: omefire):
This issue is due to the npmhelper.loadWithSettingsThenRestore function
(https://github.com/apache/cordova-lib/blob/master/cordova-lib/src/util/npm-helper.js#L34)
initializing values that are used across multiple function calls and
javascript/node.js being reentrant.
When restoring a single platform of the form @(e.g:
android@4.3.0), we make a call to lazy_load.npm_cache_add(), which loads some
settings using npm.load, runs the callback provided to npm_cache_add and then
restores npm.load settings.
> Restoring multiple platforms fails
> --
>
> Key: CB-9278
> URL: https://issues.apache.org/jira/browse/CB-9278
> Project: Apache Cordova
> Issue Type: Bug
> Components: CordovaLib
>Affects Versions: Master
> Environment: OS X
>Reporter: Dmitry Blotsky
>Assignee: Omar Mefire
> Labels: cordova-lib, platform, restore, save
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> Steps to reproduce:
> 1. Create a blank app: {{cordova create test com.app.test test}}
> 2. Add and save a platform: {{cordova platform add --save ios}}
> 3. Add and save another platform: {{cordova platform add --save android}}
> 4. Remove the platforms: {{cordova platform remove android ios}}
> 5. Try to restore platforms automatically: {{cordova prepare}}
> Expected: both platforms installed and prepared
> Actual:
> {noformat}
> Error: Trying to initialize npm when settings have not been restored from a
> previous initialization.
> {noformat}
> Running {{cordova prepare}} again fixes the issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Comment Edited] (CB-9278) Restoring multiple platforms fails
[
https://issues.apache.org/jira/browse/CB-9278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628781#comment-14628781
]
Omar Mefire edited comment on CB-9278 at 7/15/15 9:36 PM:
--
This issue is due to the npmhelper.loadWithSettingsThenRestore function
(https://github.com/apache/cordova-lib/blob/master/cordova-lib/src/util/npm-helper.js#L34)
initializing global values (used across multiple function calls) and
javascript/node.js being reentrant.
There is a kind of 'race condition' which arises when we try and restore
multiple platforms.
The solution here would be to run the function we pass to
npmhelper.loadWithSettingsThenRestore() synchronously and not have it
interrupted.(https://github.com/apache/cordova-lib/blob/master/cordova-lib/src/cordova/lazy_load.js#L162)
was (Author: omefire):
This issue is due to the npmhelper.loadWithSettingsThenRestore function
(https://github.com/apache/cordova-lib/blob/master/cordova-lib/src/util/npm-helper.js#L34)
initializing global values (used across multiple function calls) and
javascript/node.js being reentrant.
There is a kind of 'race condition' which arises when we try and restore
multiple platforms.
> Restoring multiple platforms fails
> --
>
> Key: CB-9278
> URL: https://issues.apache.org/jira/browse/CB-9278
> Project: Apache Cordova
> Issue Type: Bug
> Components: CordovaLib
>Affects Versions: Master
> Environment: OS X
>Reporter: Dmitry Blotsky
>Assignee: Omar Mefire
> Labels: cordova-lib, platform, restore, save
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> Steps to reproduce:
> 1. Create a blank app: {{cordova create test com.app.test test}}
> 2. Add and save a platform: {{cordova platform add --save ios}}
> 3. Add and save another platform: {{cordova platform add --save android}}
> 4. Remove the platforms: {{cordova platform remove android ios}}
> 5. Try to restore platforms automatically: {{cordova prepare}}
> Expected: both platforms installed and prepared
> Actual:
> {noformat}
> Error: Trying to initialize npm when settings have not been restored from a
> previous initialization.
> {noformat}
> Running {{cordova prepare}} again fixes the issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-9172) Android "cordova run" sometimes locks up the emulator
[ https://issues.apache.org/jira/browse/CB-9172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628846#comment-14628846 ] ASF GitHub Bot commented on CB-9172: Github user dblotsky commented on the pull request: https://github.com/apache/cordova-medic/pull/57#issuecomment-121764740 This is a really hacky way to do retries in Buildbot, and I don't think we should do it. There is a way for this to be done in the script we call, so let's keep it only there. > Android "cordova run" sometimes locks up the emulator > - > > Key: CB-9172 > URL: https://issues.apache.org/jira/browse/CB-9172 > Project: Apache Cordova > Issue Type: Bug > Components: Android >Affects Versions: Master > Environment: Android on OSX and Windows >Reporter: Dmitry Blotsky > Labels: adb, android > Original Estimate: 48h > Remaining Estimate: 48h > > ADB commands used in "cordova run" for Android don't always wait for proper > success conditions on Android, sometimes calling operations at the wrong > time. For example, sometimes installation happens too soon after emulator > boot, and the emulator locks up. > The implementation of "cordova run" for Android should be made more robust. A > reference implementation can be found in the Jenkins Android code, here: > https://github.com/jenkinsci/android-emulator-plugin/blob/master/src/main/java/hudson/plugins/android_emulator/InstallBuilder.java. -- 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-488) FileTransfer.upload does not follow redirects on Android
[ https://issues.apache.org/jira/browse/CB-488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628845#comment-14628845 ] Artem Golovinsky commented on CB-488: - What is status? was it fixed? I get the same problem on 1.2.0 version of plugin. > FileTransfer.upload does not follow redirects on Android > > > Key: CB-488 > URL: https://issues.apache.org/jira/browse/CB-488 > Project: Apache Cordova > Issue Type: Bug > Components: Android >Affects Versions: 1.3.0, 1.4.0, 1.5.0 > Environment: Andoid device: Samsung Galaxy S Plus >Reporter: Wouter >Assignee: Andrew Grieve > Fix For: Master > > > We are trying to upload a local move file to Youtube though the Youtube API. > This API works in such a way that after uploading a file a redirect is done > to another location. Unfortunately the Android implementation of FileTransfer > does not follow this redirect. (The iPhone implementation does follow the > redirect.) > Steps to reproduce: > - Create a FileTransfer instance and call the upload method following the > example at > http://docs.phonegap.com/en/1.6.0/cordova_file_file.md.html#FileTransfer > - The server the file is posted to (in the sample this is > http://some.server.com/upload.php) should do a redirect to another location > to reproduce this issue. > Actual Result: > - In the success callback the FileUploadResult.responseCode is 302, and the > FileUploadResult.response is "Temporarily Moved" (or similar depending on the > webserver that responded with the redirect). > Expected Result: > - The redirect is followed and the result of the new location is retreived > and represented in the FileUploadResult instance. > Or (but lower preference): > - The FileUploadResult instance also contains the HTTP headers that were sent > with the response so that the Location header (containging the url to > redirect to) is known. -- 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-488) FileTransfer.upload does not follow redirects on Android
[ https://issues.apache.org/jira/browse/CB-488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628845#comment-14628845 ] Artem Golovinsky edited comment on CB-488 at 7/15/15 10:11 PM: --- What is status? was it fixed? I get the same problem on 1.2.0 version of plugin from git - https://github.com/apache/cordova-plugin-file-transfer/tree/r1.2.0 was (Author: garrys_game): What is status? was it fixed? I get the same problem on 1.2.0 version of plugin. > FileTransfer.upload does not follow redirects on Android > > > Key: CB-488 > URL: https://issues.apache.org/jira/browse/CB-488 > Project: Apache Cordova > Issue Type: Bug > Components: Android >Affects Versions: 1.3.0, 1.4.0, 1.5.0 > Environment: Andoid device: Samsung Galaxy S Plus >Reporter: Wouter >Assignee: Andrew Grieve > Fix For: Master > > > We are trying to upload a local move file to Youtube though the Youtube API. > This API works in such a way that after uploading a file a redirect is done > to another location. Unfortunately the Android implementation of FileTransfer > does not follow this redirect. (The iPhone implementation does follow the > redirect.) > Steps to reproduce: > - Create a FileTransfer instance and call the upload method following the > example at > http://docs.phonegap.com/en/1.6.0/cordova_file_file.md.html#FileTransfer > - The server the file is posted to (in the sample this is > http://some.server.com/upload.php) should do a redirect to another location > to reproduce this issue. > Actual Result: > - In the success callback the FileUploadResult.responseCode is 302, and the > FileUploadResult.response is "Temporarily Moved" (or similar depending on the > webserver that responded with the redirect). > Expected Result: > - The redirect is followed and the result of the new location is retreived > and represented in the FileUploadResult instance. > Or (but lower preference): > - The FileUploadResult instance also contains the HTTP headers that were sent > with the response so that the Location header (containging the url to > redirect to) is known. -- 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-9278) Restoring multiple platforms fails
[
https://issues.apache.org/jira/browse/CB-9278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628851#comment-14628851
]
Omar Mefire commented on CB-9278:
-
The strange thing is that all of the calls affecting this area are wrapped
inside a promise_util.Q_chainmap() call. so, it's all supposed to be run
sequentially.
https://github.com/apache/cordova-lib/blob/master/cordova-lib/src/cordova/platform.js#L92
> Restoring multiple platforms fails
> --
>
> Key: CB-9278
> URL: https://issues.apache.org/jira/browse/CB-9278
> Project: Apache Cordova
> Issue Type: Bug
> Components: CordovaLib
>Affects Versions: Master
> Environment: OS X
>Reporter: Dmitry Blotsky
>Assignee: Omar Mefire
> Labels: cordova-lib, platform, restore, save
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> Steps to reproduce:
> 1. Create a blank app: {{cordova create test com.app.test test}}
> 2. Add and save a platform: {{cordova platform add --save ios}}
> 3. Add and save another platform: {{cordova platform add --save android}}
> 4. Remove the platforms: {{cordova platform remove android ios}}
> 5. Try to restore platforms automatically: {{cordova prepare}}
> Expected: both platforms installed and prepared
> Actual:
> {noformat}
> Error: Trying to initialize npm when settings have not been restored from a
> previous initialization.
> {noformat}
> Running {{cordova prepare}} again fixes the issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Commented] (CB-9359) Add support for app package bundling to Windows 8.1 / Windows 10
[
https://issues.apache.org/jira/browse/CB-9359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628864#comment-14628864
]
ASF GitHub Bot commented on CB-9359:
Github user nikhilkh commented on a diff in the pull request:
https://github.com/apache/cordova-windows/pull/102#discussion_r34736868
--- Diff: template/cordova/lib/MSBuildTools.js ---
@@ -38,6 +38,13 @@ MSBuildTools.prototype.buildProject = function(projFile,
buildType, buildarch) {
'/p:Configuration=' + buildType,
'/p:Platform=' + buildarch];
+if (otherConfigProperties) {
--- End diff --
This approach is not consistent with other ways we've done this in the code
here. For packaging, we've leaned on generating a targets file every time we
build. We should use that same mechanism here:
https://github.com/apache/cordova-windows/blob/master/template/cordova/lib/prepare.js#L74
Also, one of the downsides of this approach is that IDE <-> command line
interop is broken. It's desirable for the IDE build to have the same results as
the command line build. By adding an additional property at command line this
can't be guaranteed.
> Add support for app package bundling to Windows 8.1 / Windows 10
>
>
> Key: CB-9359
> URL: https://issues.apache.org/jira/browse/CB-9359
> Project: Apache Cordova
> Issue Type: Task
> Components: Windows
>Reporter: Rob Paveza
>Assignee: Rob Paveza
>
> When generating a release build, developers are able to submit a single
> binary (an .appx bundle) to the Windows Store to avoid having to upload
> multiple app packages (particularly when building an architecture-specific
> app). This task should add a --bundle flag to enable automatic creation of
> an .appxbundle for upload of the app to the Store.
--
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-9359) Add support for app package bundling to Windows 8.1 / Windows 10
[
https://issues.apache.org/jira/browse/CB-9359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628925#comment-14628925
]
ASF GitHub Bot commented on CB-9359:
Github user robpaveza commented on a diff in the pull request:
https://github.com/apache/cordova-windows/pull/102#discussion_r34741242
--- Diff: template/cordova/lib/MSBuildTools.js ---
@@ -38,6 +38,13 @@ MSBuildTools.prototype.buildProject = function(projFile,
buildType, buildarch) {
'/p:Configuration=' + buildType,
'/p:Platform=' + buildarch];
+if (otherConfigProperties) {
--- End diff --
I'll look into the .targets approach.
However, I don't agree with the IDE-CLI interop dichotomy. In the IDE, you
almost always are building a single arch+mode target pair at a time (e.g.,
x86-debug). In VS, you can generate app package bundles, but you have to go
through a particular menu to do so, not use the typical MSBuild-invoking
"Build" step workflow. The same works here as well.
The change was designed 100% to be just like the "Create App Packages"
feature, just turned on by default when building arch-specific packages.
> Add support for app package bundling to Windows 8.1 / Windows 10
>
>
> Key: CB-9359
> URL: https://issues.apache.org/jira/browse/CB-9359
> Project: Apache Cordova
> Issue Type: Task
> Components: Windows
>Reporter: Rob Paveza
>Assignee: Rob Paveza
>
> When generating a release build, developers are able to submit a single
> binary (an .appx bundle) to the Windows Store to avoid having to upload
> multiple app packages (particularly when building an architecture-specific
> app). This task should add a --bundle flag to enable automatic creation of
> an .appxbundle for upload of the app to the Store.
--
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-488) FileTransfer.upload does not follow redirects on Android
[ https://issues.apache.org/jira/browse/CB-488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628926#comment-14628926 ] Joe Bowser commented on CB-488: --- [~garrys_game] You're the first person to ask about this bug in years. It hasn't been fixed, I closed it hoping that someone would re-open it. I'm going to re-open it and remove the assignment to Andrew so that anyone can grab it. > FileTransfer.upload does not follow redirects on Android > > > Key: CB-488 > URL: https://issues.apache.org/jira/browse/CB-488 > Project: Apache Cordova > Issue Type: Bug > Components: Android >Affects Versions: 1.3.0, 1.4.0, 1.5.0 > Environment: Andoid device: Samsung Galaxy S Plus >Reporter: Wouter >Assignee: Andrew Grieve > Fix For: Master > > > We are trying to upload a local move file to Youtube though the Youtube API. > This API works in such a way that after uploading a file a redirect is done > to another location. Unfortunately the Android implementation of FileTransfer > does not follow this redirect. (The iPhone implementation does follow the > redirect.) > Steps to reproduce: > - Create a FileTransfer instance and call the upload method following the > example at > http://docs.phonegap.com/en/1.6.0/cordova_file_file.md.html#FileTransfer > - The server the file is posted to (in the sample this is > http://some.server.com/upload.php) should do a redirect to another location > to reproduce this issue. > Actual Result: > - In the success callback the FileUploadResult.responseCode is 302, and the > FileUploadResult.response is "Temporarily Moved" (or similar depending on the > webserver that responded with the redirect). > Expected Result: > - The redirect is followed and the result of the new location is retreived > and represented in the FileUploadResult instance. > Or (but lower preference): > - The FileUploadResult instance also contains the HTTP headers that were sent > with the response so that the Location header (containging the url to > redirect to) is known. -- 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-9363) Cordova GeoLocation API not working in Android M Beta OS
[ https://issues.apache.org/jira/browse/CB-9363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser updated CB-9363: --- Priority: Major (was: Blocker) > Cordova GeoLocation API not working in Android M Beta OS > > > Key: CB-9363 > URL: https://issues.apache.org/jira/browse/CB-9363 > Project: Apache Cordova > Issue Type: Bug > Components: Android, Plugin Geolocation >Affects Versions: 3.6.3 > Environment: Android M Beta OS >Reporter: Giriprasath > > Cordova's Geolocation API is not working on Android device running with > Android M beta OS. While other API's like network, device, camera, etc.. > works fine in this beta OS. Only GeoLocation API doesn't work. Is this is an > API issue? (location option was enabled under Settings>App_Name>Permissions. > But my app is not shown under Settings>Location) > Note: Geolocation App works fine on the same app, installed over Android 5 & > below OS versions. > Have even tried with new permission model mentioned in Android site. No luck. > Tested Environment: Android M Beta Preview 1 & Preview 2 > Device: Nexus 5 > Code used as per following link; > http://plugins.cordova.io/#/package/org.apache.cordova.geolocation -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Reopened] (CB-488) FileTransfer.upload does not follow redirects on Android
[ https://issues.apache.org/jira/browse/CB-488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser reopened CB-488: --- Assignee: (was: Andrew Grieve) > FileTransfer.upload does not follow redirects on Android > > > Key: CB-488 > URL: https://issues.apache.org/jira/browse/CB-488 > Project: Apache Cordova > Issue Type: Bug > Components: Android >Affects Versions: 1.3.0, 1.4.0, 1.5.0 > Environment: Andoid device: Samsung Galaxy S Plus >Reporter: Wouter > Fix For: Master > > > We are trying to upload a local move file to Youtube though the Youtube API. > This API works in such a way that after uploading a file a redirect is done > to another location. Unfortunately the Android implementation of FileTransfer > does not follow this redirect. (The iPhone implementation does follow the > redirect.) > Steps to reproduce: > - Create a FileTransfer instance and call the upload method following the > example at > http://docs.phonegap.com/en/1.6.0/cordova_file_file.md.html#FileTransfer > - The server the file is posted to (in the sample this is > http://some.server.com/upload.php) should do a redirect to another location > to reproduce this issue. > Actual Result: > - In the success callback the FileUploadResult.responseCode is 302, and the > FileUploadResult.response is "Temporarily Moved" (or similar depending on the > webserver that responded with the redirect). > Expected Result: > - The redirect is followed and the result of the new location is retreived > and represented in the FileUploadResult instance. > Or (but lower preference): > - The FileUploadResult instance also contains the HTTP headers that were sent > with the response so that the Location header (containging the url to > redirect to) is known. -- 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-9363) Cordova GeoLocation API not working in Android M Beta OS
[ https://issues.apache.org/jira/browse/CB-9363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser resolved CB-9363. Resolution: Duplicate > Cordova GeoLocation API not working in Android M Beta OS > > > Key: CB-9363 > URL: https://issues.apache.org/jira/browse/CB-9363 > Project: Apache Cordova > Issue Type: Bug > Components: Android, Plugin Geolocation >Affects Versions: 3.6.3 > Environment: Android M Beta OS >Reporter: Giriprasath > > Cordova's Geolocation API is not working on Android device running with > Android M beta OS. While other API's like network, device, camera, etc.. > works fine in this beta OS. Only GeoLocation API doesn't work. Is this is an > API issue? (location option was enabled under Settings>App_Name>Permissions. > But my app is not shown under Settings>Location) > Note: Geolocation App works fine on the same app, installed over Android 5 & > below OS versions. > Have even tried with new permission model mentioned in Android site. No luck. > Tested Environment: Android M Beta Preview 1 & Preview 2 > Device: Nexus 5 > Code used as per following link; > http://plugins.cordova.io/#/package/org.apache.cordova.geolocation -- 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-9348) Unable to get linked contact's phone number, while using pickContact
[ https://issues.apache.org/jira/browse/CB-9348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser updated CB-9348: --- Priority: Major (was: Critical) > Unable to get linked contact's phone number, while using pickContact > > > Key: CB-9348 > URL: https://issues.apache.org/jira/browse/CB-9348 > Project: Apache Cordova > Issue Type: Bug > Components: Android, Plugin Contacts >Reporter: Dipanjan Chakraborty > > using cordova v5.1.1 and contacts plugin v1.1.0 > we are unable to fetch the mobile numbers from the phonebook especially if > there are contacts linked. > example: > the main contact is > Name: John Doe > mobile: 99 > the linked G+ contact is > Name J.Doe > mobile: 88 > When fetching the contact using pickContact , it does not fetch either phone > numbers. however, the name of the secondary (J.Doe) is fetched . > Appreciate any help on this issue. > Thanks in advance. -- 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-9363) Cordova GeoLocation API not working in Android M Beta OS
[ https://issues.apache.org/jira/browse/CB-9363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628929#comment-14628929 ] Joe Bowser commented on CB-9363: See CB-9105 > Cordova GeoLocation API not working in Android M Beta OS > > > Key: CB-9363 > URL: https://issues.apache.org/jira/browse/CB-9363 > Project: Apache Cordova > Issue Type: Bug > Components: Android, Plugin Geolocation >Affects Versions: 3.6.3 > Environment: Android M Beta OS >Reporter: Giriprasath > > Cordova's Geolocation API is not working on Android device running with > Android M beta OS. While other API's like network, device, camera, etc.. > works fine in this beta OS. Only GeoLocation API doesn't work. Is this is an > API issue? (location option was enabled under Settings>App_Name>Permissions. > But my app is not shown under Settings>Location) > Note: Geolocation App works fine on the same app, installed over Android 5 & > below OS versions. > Have even tried with new permission model mentioned in Android site. No luck. > Tested Environment: Android M Beta Preview 1 & Preview 2 > Device: Nexus 5 > Code used as per following link; > http://plugins.cordova.io/#/package/org.apache.cordova.geolocation -- 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-488) FileTransfer.upload does not follow redirects on Android
[ https://issues.apache.org/jira/browse/CB-488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628930#comment-14628930 ] Artem Golovinsky commented on CB-488: - [~bowserj] Yeah I see and it is very strange. Thank you a lot. > FileTransfer.upload does not follow redirects on Android > > > Key: CB-488 > URL: https://issues.apache.org/jira/browse/CB-488 > Project: Apache Cordova > Issue Type: Bug > Components: Android >Affects Versions: 1.3.0, 1.4.0, 1.5.0 > Environment: Andoid device: Samsung Galaxy S Plus >Reporter: Wouter > Fix For: Master > > > We are trying to upload a local move file to Youtube though the Youtube API. > This API works in such a way that after uploading a file a redirect is done > to another location. Unfortunately the Android implementation of FileTransfer > does not follow this redirect. (The iPhone implementation does follow the > redirect.) > Steps to reproduce: > - Create a FileTransfer instance and call the upload method following the > example at > http://docs.phonegap.com/en/1.6.0/cordova_file_file.md.html#FileTransfer > - The server the file is posted to (in the sample this is > http://some.server.com/upload.php) should do a redirect to another location > to reproduce this issue. > Actual Result: > - In the success callback the FileUploadResult.responseCode is 302, and the > FileUploadResult.response is "Temporarily Moved" (or similar depending on the > webserver that responded with the redirect). > Expected Result: > - The redirect is followed and the result of the new location is retreived > and represented in the FileUploadResult instance. > Or (but lower preference): > - The FileUploadResult instance also contains the HTTP headers that were sent > with the response so that the Location header (containging the url to > redirect to) is known. -- 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-9105) Android needs Geolocation code to handle the permissions in Android M
[ https://issues.apache.org/jira/browse/CB-9105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628936#comment-14628936 ] Joe Bowser commented on CB-9105: After working on adding the new permissions on Android it seems that the WebView will not grant the permissions, even though the app does have the permissions. [~agrieve] did ask for a repro case for Chrome, and I'll be filing something there based on the Cordova code I currently have here: https://github.com/infil00p/cordova-android/tree/m-compat > Android needs Geolocation code to handle the permissions in Android M > - > > Key: CB-9105 > URL: https://issues.apache.org/jira/browse/CB-9105 > Project: Apache Cordova > Issue Type: Bug > Components: Android, Plugin Geolocation >Reporter: Joe Bowser >Assignee: Joe Bowser > -- 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-7512) Android Gradle build requires API 19 and build tools 19.0.0 exactly
[ https://issues.apache.org/jira/browse/CB-7512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser resolved CB-7512. Resolution: Implemented I'm pretty sure that this never really got resolved, but that we are now dealing with newer build tools and a newer Android Plugin, and we're now far more down the depths of dependency hell. I'm closing this as implemented. > Android Gradle build requires API 19 and build tools 19.0.0 exactly > --- > > Key: CB-7512 > URL: https://issues.apache.org/jira/browse/CB-7512 > Project: Apache Cordova > Issue Type: Bug > Components: Android >Reporter: Ian Clelland >Assignee: Ian Clelland > -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Assigned] (CB-7503) Keypress event not working with soft keyboard in Android KitKat
[ https://issues.apache.org/jira/browse/CB-7503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser reassigned CB-7503: -- Assignee: Joe Bowser > Keypress event not working with soft keyboard in Android KitKat > --- > > Key: CB-7503 > URL: https://issues.apache.org/jira/browse/CB-7503 > Project: Apache Cordova > Issue Type: Bug > Components: Android >Affects Versions: Master, 3.5.0, 3.6.0, 3.7.0, 3.8.0, 3.9.0, 4.0.0 > Environment: Present in Android 4.4.2, 4.4.4, L > Not present in 4.1.2 > Present with software keyboard > Not present with hardware (i.e. bluetooth) keyboard > Fixed with Chromium M38 >Reporter: Lancho Pat >Assignee: Joe Bowser > Labels: bug,, javascript, workaround, > > See https://code.google.com/p/android/issues/detail?id=68284 > Update: Here is the issue in the chromium bugtracker: > https://code.google.com/p/chromium/issues/detail?id=118639 > WebViews that are based on Chromium below M38 don't receive keypress events > in Android 4.4.2 and above. -- 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-7503) Keypress event not working with soft keyboard in Android KitKat
[ https://issues.apache.org/jira/browse/CB-7503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628957#comment-14628957 ] Joe Bowser commented on CB-7503: I'm going to test this in Crosswalk, and if that allows a work-around, I'll probably just close this as "Won't Fix" since that work-around exists. I know it sounds kinda harsh, but bugs like this are part of the reason we wanted to do Third-Party Webviews in the first place. > Keypress event not working with soft keyboard in Android KitKat > --- > > Key: CB-7503 > URL: https://issues.apache.org/jira/browse/CB-7503 > Project: Apache Cordova > Issue Type: Bug > Components: Android >Affects Versions: Master, 3.5.0, 3.6.0, 3.7.0, 3.8.0, 3.9.0, 4.0.0 > Environment: Present in Android 4.4.2, 4.4.4, L > Not present in 4.1.2 > Present with software keyboard > Not present with hardware (i.e. bluetooth) keyboard > Fixed with Chromium M38 >Reporter: Lancho Pat >Assignee: Joe Bowser > Labels: bug,, javascript, workaround, > > See https://code.google.com/p/android/issues/detail?id=68284 > Update: Here is the issue in the chromium bugtracker: > https://code.google.com/p/chromium/issues/detail?id=118639 > WebViews that are based on Chromium below M38 don't receive keypress events > in Android 4.4.2 and above. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org For additional commands, e-mail: issues-h...@cordova.apache.org
[jira] [Assigned] (CB-9353) Memory issue in Android version when passing a large number of JSON objects in either direction
[ https://issues.apache.org/jira/browse/CB-9353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bowser reassigned CB-9353: -- Assignee: Joe Bowser > Memory issue in Android version when passing a large number of JSON objects > in either direction > --- > > Key: CB-9353 > URL: https://issues.apache.org/jira/browse/CB-9353 > Project: Apache Cordova > Issue Type: Bug > Components: Android >Reporter: Chris Brody >Assignee: Joe Bowser > > As reported in > https://github.com/litehelpers/Cordova-sqlite-storage/issues/18: when an > array with a very large number of JSON objects is sent from Javascript to > Java, I would encounter a memory problem in JSON as called by > CordovaPlugin.execute(): > E/art (22291): Throwing OutOfMemoryError "Failed to allocate a 28 byte > allocation with 20 free bytes and 20B until OOM" (recursive case) > E/art (22291): "JavaBridge" prio=5 tid=25 Runnable > E/art (22291): | group="main" sCount=0 dsCount=0 obj=0x12de6820 > self=0xb73ae620 > E/art (22291): | sysTid=22377 nice=0 cgrp=apps sched=0/0 > handle=0xb73aead8 > E/art (22291): | state=R schedstat=( 0 0 0 ) utm=653 stm=94 core=1 > HZ=100 > E/art (22291): | stack=0xa4ee1000-0xa4ee3000 stackSize=1036KB > E/art (22291): | held mutexes= "mutator lock"(shared held) > E/art (22291): at > java.util.LinkedHashMap.addNewEntry(LinkedHashMap.java:195) > E/art (22291): at java.util.HashMap.put(HashMap.java:403) > E/art (22291): at org.json.JSONObject.put(JSONObject.java:264) > E/art (22291): at org.json.JSONTokener.readObject(JSONTokener.java:385) > E/art (22291): at org.json.JSONTokener.nextValue(JSONTokener.java:100) > E/art (22291): at org.json.JSONTokener.readArray(JSONTokener.java:430) > E/art (22291): at org.json.JSONTokener.nextValue(JSONTokener.java:103) > E/art (22291): at org.json.JSONTokener.readObject(JSONTokener.java:385) > E/art (22291): at org.json.JSONTokener.nextValue(JSONTokener.java:100) > E/art (22291): at org.json.JSONTokener.readArray(JSONTokener.java:430) > E/art (22291): at org.json.JSONTokener.nextValue(JSONTokener.java:103) > E/art (22291): at org.json.JSONArray.(JSONArray.java:92) > E/art (22291): at org.json.JSONArray.(JSONArray.java:108) > E/art (22291): at > org.apache.cordova.CordovaPlugin.execute(CordovaPlugin.java:64) > E/art (22291): at > org.apache.cordova.PluginManager.execHelper(PluginManager.java:242) > E/art (22291): at > org.apache.cordova.PluginManager.exec(PluginManager.java:227) > E/art (22291): at > org.apache.cordova.ExposedJsApi.exec(ExposedJsApi.java:53) > E/art (22291): at > org.chromium.base.SystemMessageHandler.nativeDoRunLoopOnce(Native method) > E/art (22291): at > org.chromium.base.SystemMessageHandler.handleMessage(SystemMessageHandler.java:53) > E/art (22291): at android.os.Handler.dispatchMessage(Handler.java:102) > E/art (22291): at android.os.Looper.loop(Looper.java:135) > E/art (22291): at android.os.HandlerThread.run(HandlerThread.java:61) > The workaround, which took me some hard work to develop and test, is to send > my data as a flat array which the Java code has to interpret very carefully. > In addition, in case the Java code attempts to create an array with a very > large number of JSON objects in order to send a response I get similar > problem. The workaround was again to format the response data as a flat array > and interpret it very carefully on the Javascript side. > While I do have a workaround I find this to be very clumsy and hope we can > find a better solution. I am happy to make an isolated test plugin to > reproduce and demonstrate this issue if the Apache Cordova project is serious > about trying to fix it. -- 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-9330) Remove 'plugman publish' functionality from cordova-lib
[ https://issues.apache.org/jira/browse/CB-9330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628989#comment-14628989 ] ASF subversion and git services commented on CB-9330: - Commit 1a695603b53774d7a28d8b4e204c102c5b95e129 in cordova-lib's branch refs/heads/master from [~stevegill] [ https://git-wip-us.apache.org/repos/asf?p=cordova-lib.git;h=1a69560 ] CB-9330 updated wording for warning messages for removal of publish/unpublish commands > Remove 'plugman publish' functionality from cordova-lib > > > Key: CB-9330 > URL: https://issues.apache.org/jira/browse/CB-9330 > Project: Apache Cordova > Issue Type: Improvement >Reporter: Vladimir Kotikov >Assignee: Vladimir Kotikov > > Due to CPR write (publish) access shutdown starting from July 15 we need to > make some changes to remove CPR publishing related functionality from Cordova. > Things, that might be removed: > 1. 'plugman publish/unpublish' commands, > 2. 'registry.publish/unpublish' methods and all related stuff in > cordova-lib. -- 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-9330) Remove 'plugman publish' functionality from cordova-lib
[ https://issues.apache.org/jira/browse/CB-9330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628988#comment-14628988 ] ASF subversion and git services commented on CB-9330: - Commit 64c2c0013c1ba8996458164ce4eb7a133a0ae344 in cordova-lib's branch refs/heads/master from [~vladimir.kotikov] [ https://git-wip-us.apache.org/repos/asf?p=cordova-lib.git;h=64c2c00 ] CB-9330 Removes 'plugman publish' related functionality > Remove 'plugman publish' functionality from cordova-lib > > > Key: CB-9330 > URL: https://issues.apache.org/jira/browse/CB-9330 > Project: Apache Cordova > Issue Type: Improvement >Reporter: Vladimir Kotikov >Assignee: Vladimir Kotikov > > Due to CPR write (publish) access shutdown starting from July 15 we need to > make some changes to remove CPR publishing related functionality from Cordova. > Things, that might be removed: > 1. 'plugman publish/unpublish' commands, > 2. 'registry.publish/unpublish' methods and all related stuff in > cordova-lib. -- 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-9330) Remove 'plugman publish' functionality from cordova-lib
[ https://issues.apache.org/jira/browse/CB-9330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628990#comment-14628990 ] ASF GitHub Bot commented on CB-9330: Github user asfgit closed the pull request at: https://github.com/apache/cordova-lib/pull/254 > Remove 'plugman publish' functionality from cordova-lib > > > Key: CB-9330 > URL: https://issues.apache.org/jira/browse/CB-9330 > Project: Apache Cordova > Issue Type: Improvement >Reporter: Vladimir Kotikov >Assignee: Vladimir Kotikov > > Due to CPR write (publish) access shutdown starting from July 15 we need to > make some changes to remove CPR publishing related functionality from Cordova. > Things, that might be removed: > 1. 'plugman publish/unpublish' commands, > 2. 'registry.publish/unpublish' methods and all related stuff in > cordova-lib. -- 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-9359) Add support for app package bundling to Windows 8.1 / Windows 10
[ https://issues.apache.org/jira/browse/CB-9359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14629004#comment-14629004 ] ASF GitHub Bot commented on CB-9359: Github user dblotsky commented on the pull request: https://github.com/apache/cordova-windows/pull/102#issuecomment-121789647 Small question: do you think it's better to have an argument contain multiple values with an arbitrary separator (in other tools we sometimes use commas, or pipes, or also spaces), or is it better to have the argument be repeatable to likewise specify a list? > Add support for app package bundling to Windows 8.1 / Windows 10 > > > Key: CB-9359 > URL: https://issues.apache.org/jira/browse/CB-9359 > Project: Apache Cordova > Issue Type: Task > Components: Windows >Reporter: Rob Paveza >Assignee: Rob Paveza > > When generating a release build, developers are able to submit a single > binary (an .appx bundle) to the Windows Store to avoid having to upload > multiple app packages (particularly when building an architecture-specific > app). This task should add a --bundle flag to enable automatic creation of > an .appxbundle for upload of the app to the Store. -- 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-9359) Add support for app package bundling to Windows 8.1 / Windows 10
[ https://issues.apache.org/jira/browse/CB-9359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14629012#comment-14629012 ] ASF GitHub Bot commented on CB-9359: Github user robpaveza commented on the pull request: https://github.com/apache/cordova-windows/pull/102#issuecomment-121792352 I don't really have a preference. We could say be consistent with msbuild and do a pipe separator but I don't think that is terribly valuable. The archs argument is already existing and I don't think a redesign is in scope. > Add support for app package bundling to Windows 8.1 / Windows 10 > > > Key: CB-9359 > URL: https://issues.apache.org/jira/browse/CB-9359 > Project: Apache Cordova > Issue Type: Task > Components: Windows >Reporter: Rob Paveza >Assignee: Rob Paveza > > When generating a release build, developers are able to submit a single > binary (an .appx bundle) to the Windows Store to avoid having to upload > multiple app packages (particularly when building an architecture-specific > app). This task should add a --bundle flag to enable automatic creation of > an .appxbundle for upload of the app to the Store. -- 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-9359) Add support for app package bundling to Windows 8.1 / Windows 10
[ https://issues.apache.org/jira/browse/CB-9359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14629020#comment-14629020 ] ASF GitHub Bot commented on CB-9359: Github user dblotsky commented on the pull request: https://github.com/apache/cordova-windows/pull/102#issuecomment-121792934 Sounds fair! > Add support for app package bundling to Windows 8.1 / Windows 10 > > > Key: CB-9359 > URL: https://issues.apache.org/jira/browse/CB-9359 > Project: Apache Cordova > Issue Type: Task > Components: Windows >Reporter: Rob Paveza >Assignee: Rob Paveza > > When generating a release build, developers are able to submit a single > binary (an .appx bundle) to the Windows Store to avoid having to upload > multiple app packages (particularly when building an architecture-specific > app). This task should add a --bundle flag to enable automatic creation of > an .appxbundle for upload of the app to the Store. -- 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-9361) The coho verify-tags command does not work well in Windows
[
https://issues.apache.org/jira/browse/CB-9361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14629035#comment-14629035
]
ASF GitHub Bot commented on CB-9361:
Github user dblotsky commented on the pull request:
https://github.com/apache/cordova-coho/pull/91#issuecomment-121795384
Tried on bash and cmd on Windows, and on bash on OSX; all work fine. LGTM!
> The coho verify-tags command does not work well in Windows
> --
>
> Key: CB-9361
> URL: https://issues.apache.org/jira/browse/CB-9361
> Project: Apache Cordova
> Issue Type: Bug
> Components: Coho
>Reporter: Tim Barham
>Assignee: Tim Barham
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> The coho {{verify-tags}} command requires users to type {{Ctrl+D}} to trigger
> an {{EOF}}. However, this does not work from the Windows command prompt.
--
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-8936) Surface platform-specific logs in buildbot
[
https://issues.apache.org/jira/browse/CB-8936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14629053#comment-14629053
]
ASF GitHub Bot commented on CB-8936:
Github user dblotsky commented on a diff in the pull request:
https://github.com/apache/cordova-medic/pull/58#discussion_r34748954
--- Diff: medic/medic-run.js ---
@@ -222,6 +222,7 @@ function windowsSpecificPreparation(argv) {
var appUtilsPath = path.join(libPath,
"WindowsStoreAppUtils.ps1");
var srcScriptPath = path.join(CORDOVA_MEDIC_DIR, "lib",
"patches", "EnableDebuggingForPackage.ps1");
var destScriptPath = path.join(libPath,
"EnableDebuggingForPackage.ps1");
+var logScriptPath = path.join(CORDOVA_MEDIC_DIR, "lib",
"patches", "EnableLogging.ps1");
--- End diff --
Should this be part of the cordova-windows platform template?
> Surface platform-specific logs in buildbot
> --
>
> Key: CB-8936
> URL: https://issues.apache.org/jira/browse/CB-8936
> Project: Apache Cordova
> Issue Type: Task
> Components: Medic
>Reporter: Alexander Sorokin
>Assignee: Alexander Sorokin
>
> Platform specific logs (e.g. logcat for android, stderr.log and stdin.log for
> iOS etc.) should be gathered and displayed in buildbot.
--
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-8936) Surface platform-specific logs in buildbot
[
https://issues.apache.org/jira/browse/CB-8936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14629054#comment-14629054
]
ASF GitHub Bot commented on CB-8936:
Github user dblotsky commented on a diff in the pull request:
https://github.com/apache/cordova-medic/pull/58#discussion_r34749192
--- Diff: medic/medic-run.js ---
@@ -232,12 +233,18 @@ function windowsSpecificPreparation(argv) {
/^\s*\$appActivator .*$/gim,
"$&\n" +
--- End diff --
This was copied over from the old Medic code. Having said that,
improvements are in order at some point.
> Surface platform-specific logs in buildbot
> --
>
> Key: CB-8936
> URL: https://issues.apache.org/jira/browse/CB-8936
> Project: Apache Cordova
> Issue Type: Task
> Components: Medic
>Reporter: Alexander Sorokin
>Assignee: Alexander Sorokin
>
> Platform specific logs (e.g. logcat for android, stderr.log and stdin.log for
> iOS etc.) should be gathered and displayed in buildbot.
--
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-8936) Surface platform-specific logs in buildbot
[
https://issues.apache.org/jira/browse/CB-8936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14629058#comment-14629058
]
ASF GitHub Bot commented on CB-8936:
Github user dblotsky commented on a diff in the pull request:
https://github.com/apache/cordova-medic/pull/58#discussion_r34749430
--- Diff: medic/medic-run.js ---
@@ -232,12 +233,18 @@ function windowsSpecificPreparation(argv) {
/^\s*\$appActivator .*$/gim,
"$&\n" +
"powershell " + path.join(process.cwd(), destScriptPath) +
" $$ID\n" +
+"powershell " + path.join(process.cwd(), logScriptPath) +
"\n" +
"$Ole32 = Add-Type -MemberDefinition
'[DllImport(\"Ole32.dll\")]public static extern int
CoAllowSetForegroundWindow(IntPtr pUnk, IntPtr lpvReserved);' -Name 'Ole32'
-Namespace 'Win32' -PassThru\n" +
"
$Ole32::CoAllowSetForegroundWindow([System.Runtime.InteropServices.Marshal]::GetIUnknownForObject($appActivator),
[System.IntPtr]::Zero)",
appUtilsPath
);
}
+// write current time to a file to use it when gathering logs
+var now = new Date();
+var iso = now.toISOString();
+fs.writeFileSync('startTime.txt', iso, util.DEFAULT_ENCODING);
--- End diff --
This file is not necessary. It serves only to pass arguments from
`medic-run` to `medic-log`. Instead, please pass a start time to medic-log on
the command line from `cordova.conf`. You can do this by setting a `Property`
using `SetPropertyFromCommand`, and then passing it to the logging step.
> Surface platform-specific logs in buildbot
> --
>
> Key: CB-8936
> URL: https://issues.apache.org/jira/browse/CB-8936
> Project: Apache Cordova
> Issue Type: Task
> Components: Medic
>Reporter: Alexander Sorokin
>Assignee: Alexander Sorokin
>
> Platform specific logs (e.g. logcat for android, stderr.log and stdin.log for
> iOS etc.) should be gathered and displayed in buildbot.
--
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-9373) Plugman documentation issues
Jacob Weber created CB-9373:
---
Summary: Plugman documentation issues
Key: CB-9373
URL: https://issues.apache.org/jira/browse/CB-9373
Project: Apache Cordova
Issue Type: Bug
Components: Docs
Affects Versions: 5.0.0
Reporter: Jacob Weber
Priority: Minor
Found a couple issues on the [Using Plugman to Manage
Plugins|http://cordova.apache.org/docs/en/5.0.0/plugin_ref_plugman.md.html#Using%20Plugman%20to%20Manage%20Plugins]
page:
1. Under "Installing Core Plugins", it lists plugin IDs using the new naming
format (e.g. cordova-plugin-battery-status). But I can't use plugman to refer
to them using this format. For example:
{code}
$ plugman info cordova-plugin-battery-status
404 Not Found: cordova-plugin-battery-status
$ plugman info org.apache.cordova.battery-status
name: org.apache.cordova.battery-status
version: 0.2.12
$ plugman -v
0.23.3
$ plugman config get registry
http://registry.cordova.io
done
{code}
2. Under "Installing Core Plugins", there's a lot of text like this, that's
rendered as invisible HTML tags:
{code}
{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-57) Feature request: update media to support streaming
[ https://issues.apache.org/jira/browse/CB-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14629110#comment-14629110 ] Gaven Henry commented on CB-57: --- I have done a little work on modifying Media plugin to use avplayer for playing back URL's on iOS. This is implemented and working at the repo location below. I need to tidy it up a bit before submitting a pull request with the updates but so far so good, I am using it in my app and streams start playing almost instantly and all works as expected so far. I also want to implement some events for tracking current buffer amount and buffer status (empty / full) so that playback can be automatically resumed and the user can see buffer status but this would require platform specific changes to the media.js so I will hold off on those until after I have a clean PR in. All current Media functions work (seek, duration, getCurrentPosition, play, pause. Stop just calls pause at the moment as avplayer doesn't seem to have a "stop" method. In the mean time anyone that wants/needs it can just install from this branch on my fork: https://github.com/ghenry22/cordova-plugin-media/tree/background-threading > Feature request: update media to support streaming > -- > > Key: CB-57 > URL: https://issues.apache.org/jira/browse/CB-57 > Project: Apache Cordova > Issue Type: New Feature > Components: Plugin Media > Environment: iOS >Reporter: Shazron Abdullah >Priority: Minor > > reported at: https://github.com/phonegap/phonegap-iphone/issues/55 > by: https://github.com/hardeep > The AVAudioPlayer used to implement iOS media does not support streaming > audio. In order to do that we need to use the Audio Toolbox. Example and > more info here: > http://cocoawithlove.com/2009/06/revisiting-old-post-streaming-and.html > [Original LightHouse > ticket](http://phonegap.lighthouseapp.com/projects/20116/tickets/105) > This ticket has 0 attachment(s). -- 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-9361) The coho verify-tags command does not work well in Windows
[
https://issues.apache.org/jira/browse/CB-9361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14629161#comment-14629161
]
ASF GitHub Bot commented on CB-9361:
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-coho/pull/91
> The coho verify-tags command does not work well in Windows
> --
>
> Key: CB-9361
> URL: https://issues.apache.org/jira/browse/CB-9361
> Project: Apache Cordova
> Issue Type: Bug
> Components: Coho
>Reporter: Tim Barham
>Assignee: Tim Barham
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> The coho {{verify-tags}} command requires users to type {{Ctrl+D}} to trigger
> an {{EOF}}. However, this does not work from the Windows command prompt.
--
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-9361) The coho verify-tags command does not work well in Windows
[
https://issues.apache.org/jira/browse/CB-9361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14629160#comment-14629160
]
ASF subversion and git services commented on CB-9361:
-
Commit 7c23a5ce273addaf985465b78e59197e7b9fafec in cordova-coho's branch
refs/heads/master from [~TimBarham]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-coho.git;h=7c23a5c ]
CB-9361 Make verify-tags working nice with Windows command prompt.
The verify-tags command currently relies on users entering a Ctrl+D to trigger
the end of input. However, this doesn't work in the Windows command prompt.
I've modified this to use Node's readline module - read the input line by line,
then process when an empty line is encountered. This way, the tags can be
pasted then simply press Enter. Note that on Unix-like systems, Ctrl+D will
still work (and if you pipe in a file that doesn't have a blank line at the
end, that will still work), since the EOF will trigger the 'close' event.
> The coho verify-tags command does not work well in Windows
> --
>
> Key: CB-9361
> URL: https://issues.apache.org/jira/browse/CB-9361
> Project: Apache Cordova
> Issue Type: Bug
> Components: Coho
>Reporter: Tim Barham
>Assignee: Tim Barham
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> The coho {{verify-tags}} command requires users to type {{Ctrl+D}} to trigger
> an {{EOF}}. However, this does not work from the Windows command prompt.
--
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-8789) Cordova iOS to support Asset Catalog for App icons and slapshscreens
[ https://issues.apache.org/jira/browse/CB-8789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14629299#comment-14629299 ] ASF GitHub Bot commented on CB-8789: Github user shazron commented on the pull request: https://github.com/apache/cordova-ios/pull/148#issuecomment-121848272 This PR is failing the project create tests. > Cordova iOS to support Asset Catalog for App icons and slapshscreens > > > Key: CB-8789 > URL: https://issues.apache.org/jira/browse/CB-8789 > Project: Apache Cordova > Issue Type: Improvement > Components: iOS >Reporter: Carlos Santana > Labels: cordova-ios-4.0.x > > IBM has a future requirement to support Asset Catalog for App icons and > splash screens in our downstream distribution (MobileFirst) of Cordova. > Enterprise use cases: > Leverage Catalog Assets to manage splash screens and app icons, instead of > using deprecated methods. > Tasks: > - Modify Xcode project structure for Cordova to use Asset Catalog > - Modify Cordova CLI to manage icons and spashscreens my managing Asset > Catalog content. > IBM has intention on working on this changes in Cordova, but if someone else > wants to work on it before we get to it that also works for us :-) > Related JIRA issues: > [CB-8027 | https://issues.apache.org/jira/browse/CB-8027] -- 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-8789) Cordova iOS to support Asset Catalog for App icons and slapshscreens
[ https://issues.apache.org/jira/browse/CB-8789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14629305#comment-14629305 ] ASF GitHub Bot commented on CB-8789: Github user shazron commented on the pull request: https://github.com/apache/cordova-ios/pull/148#issuecomment-121849886 ``` The following build commands failed: CpResource test/Resources/icons/icon...@2x.png build/emulator/test.app/icon...@2x.png CpResource test/Resources/icons/icon-76.png build/emulator/test.app/icon-76.png ``` > Cordova iOS to support Asset Catalog for App icons and slapshscreens > > > Key: CB-8789 > URL: https://issues.apache.org/jira/browse/CB-8789 > Project: Apache Cordova > Issue Type: Improvement > Components: iOS >Reporter: Carlos Santana > Labels: cordova-ios-4.0.x > > IBM has a future requirement to support Asset Catalog for App icons and > splash screens in our downstream distribution (MobileFirst) of Cordova. > Enterprise use cases: > Leverage Catalog Assets to manage splash screens and app icons, instead of > using deprecated methods. > Tasks: > - Modify Xcode project structure for Cordova to use Asset Catalog > - Modify Cordova CLI to manage icons and spashscreens my managing Asset > Catalog content. > IBM has intention on working on this changes in Cordova, but if someone else > wants to work on it before we get to it that also works for us :-) > Related JIRA issues: > [CB-8027 | https://issues.apache.org/jira/browse/CB-8027] -- 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-9330) Remove 'plugman publish' functionality from cordova-lib
[ https://issues.apache.org/jira/browse/CB-9330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Kotikov closed CB-9330. Resolution: Fixed > Remove 'plugman publish' functionality from cordova-lib > > > Key: CB-9330 > URL: https://issues.apache.org/jira/browse/CB-9330 > Project: Apache Cordova > Issue Type: Improvement >Reporter: Vladimir Kotikov >Assignee: Vladimir Kotikov > > Due to CPR write (publish) access shutdown starting from July 15 we need to > make some changes to remove CPR publishing related functionality from Cordova. > Things, that might be removed: > 1. 'plugman publish/unpublish' commands, > 2. 'registry.publish/unpublish' methods and all related stuff in > cordova-lib. -- 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-8789) Cordova iOS to support Asset Catalog for App icons and slapshscreens
[ https://issues.apache.org/jira/browse/CB-8789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14629309#comment-14629309 ] ASF GitHub Bot commented on CB-8789: Github user shazron commented on the pull request: https://github.com/apache/cordova-ios/pull/148#issuecomment-121850800 Fix: remove the files in red from the templates:  > Cordova iOS to support Asset Catalog for App icons and slapshscreens > > > Key: CB-8789 > URL: https://issues.apache.org/jira/browse/CB-8789 > Project: Apache Cordova > Issue Type: Improvement > Components: iOS >Reporter: Carlos Santana > Labels: cordova-ios-4.0.x > > IBM has a future requirement to support Asset Catalog for App icons and > splash screens in our downstream distribution (MobileFirst) of Cordova. > Enterprise use cases: > Leverage Catalog Assets to manage splash screens and app icons, instead of > using deprecated methods. > Tasks: > - Modify Xcode project structure for Cordova to use Asset Catalog > - Modify Cordova CLI to manage icons and spashscreens my managing Asset > Catalog content. > IBM has intention on working on this changes in Cordova, but if someone else > wants to work on it before we get to it that also works for us :-) > Related JIRA issues: > [CB-8027 | https://issues.apache.org/jira/browse/CB-8027] -- 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-9273) "Copy www build phase" node is not found
[ https://issues.apache.org/jira/browse/CB-9273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14629313#comment-14629313 ] Shazron Abdullah commented on CB-9273: -- I'll add this change after CB-8789 PR is resolved > "Copy www build phase" node is not found > > > Key: CB-9273 > URL: https://issues.apache.org/jira/browse/CB-9273 > Project: Apache Cordova > Issue Type: Bug > Components: iOS > Environment: cordova-ios 4.x >Reporter: Shazron Abdullah > Attachments: xcode-build-phase-node.png > > > I have node installed using nvm, and the build phase cannot find node. > The path to node in nvm is in $PATH in Terminal. It may not be in Xcode's > environment variables. -- 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-9334) PluginManager permit only one plugin to remap the URI
[
https://issues.apache.org/jira/browse/CB-9334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14629315#comment-14629315
]
ASF GitHub Bot commented on CB-9334:
Github user omefire commented on a diff in the pull request:
https://github.com/apache/cordova-android/pull/195#discussion_r34760070
--- Diff: framework/src/org/apache/cordova/PluginManager.java ---
@@ -381,15 +374,16 @@ public void onReset() {
}
Uri remapUri(Uri uri) {
+Uri remap = uri;
for (CordovaPlugin plugin : this.pluginMap.values()) {
if (plugin != null) {
-Uri ret = plugin.remapUri(uri);
+Uri ret = plugin.remapUri(remap);
if (ret != null) {
-return ret;
+remap = ret;
}
}
}
-return null;
+return uri.equals(remap) ? null : remap;
--- End diff --
I suppose this returns null if no plugins ends up remapping the uri.
However, a comment as to why this is being done would be great !
> PluginManager permit only one plugin to remap the URI
> -
>
> Key: CB-9334
> URL: https://issues.apache.org/jira/browse/CB-9334
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
>Affects Versions: 3.7.1
>Reporter: Simon Pireyn
> Labels: android, plugins
>
> If a plugin return an URI and not null, the plugin manager stop calling
> remapUri and use the value returned. It doesn't allow another plugin to check
> or remap the URI
> ex: JsHybuggerPlugin gets all URL to eventually add
> "content://jsHybugger.org/" before every url.
> Or if I need with one plugin to replace "myserver://" with "http://myserver";
> and in another to replace {placeholders} or watherver.
> PluginManager should loop every plugins before returning the remapped URI.
--
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
