Return-Path: X-Original-To: apmail-incubator-callback-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-callback-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id EB9CFD0F8 for ; Tue, 10 Jul 2012 21:52:38 +0000 (UTC) Received: (qmail 6369 invoked by uid 500); 10 Jul 2012 21:52:35 -0000 Delivered-To: apmail-incubator-callback-dev-archive@incubator.apache.org Received: (qmail 6254 invoked by uid 500); 10 Jul 2012 21:52:35 -0000 Mailing-List: contact callback-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: callback-dev@incubator.apache.org Delivered-To: mailing list callback-dev@incubator.apache.org Received: (qmail 6068 invoked by uid 99); 10 Jul 2012 21:52:35 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Jul 2012 21:52:35 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id 78F79142822 for ; Tue, 10 Jul 2012 21:52:35 +0000 (UTC) Date: Tue, 10 Jul 2012 21:52:35 +0000 (UTC) From: "Olivier Louvignes (JIRA)" To: callback-dev@incubator.apache.org Message-ID: <259393081.32047.1341957155498.JavaMail.jiratomcat@issues-vm> In-Reply-To: <1652656598.31513.1341953914917.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Commented] (CB-1023) cordova.logger is broken on 1.9.0 - won't log output to window console MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CB-1023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13410969#comment-13410969 ] Olivier Louvignes commented on CB-1023: --------------------------------------- Yep that's what I want (having both would not bother me). It is exactly the same code, so it is really weird that it behaves differently... Used to work well. It look like i got quite a few new/strange behaviors since I switched to compile CordovaLib myself (cleaver setup). But it may well be a "slow" iPad2 vs "fast" simulator timing issue. Do you have any idea how I could somehow override this behavior by either updating CordovaJS core (tried to tweak DebugConsole but got JS error - it looks like simulator logging (working) does not pass there.) Or by writing some js code to weinre so that it can take back the "power"? > cordova.logger is broken on 1.9.0 - won't log output to window console > ---------------------------------------------------------------------- > > Key: CB-1023 > URL: https://issues.apache.org/jira/browse/CB-1023 > Project: Apache Cordova > Issue Type: Bug > Components: weinre > Affects Versions: 1.9.0 > Environment: Cordova (Cleaver setup) 1.9.0 > Weinre (Latest from github) 2.0-PRE > Reporter: Olivier Louvignes > Assignee: Patrick Mueller > Labels: log > > I'm trying to correctly debug an app with weinre using 1.9.0 (cleaver) : > On the simulator I correctly get no logging to XCode & all the logging to weinre. > On a remote device (debugging via XCode), I get the logging in XCode & no logging to weinre : However, weinre does work (i can inspect vars, etc.) but the logging is going directly to XCode. > I tried this : > cordova.logger.useConsole(true) > true > window.console.log('hello') > undefined > cordova.logger.useConsole(false) > false > window.console.log('hello') > undefined > But the loggin still goes to XCode! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira