This is a migrated thread and some comments may be shown as answers.

console.log() does not log to the console in Graphite simulator for iOS simulators

12 Answers 200 Views
Report a bug
This is a migrated thread and some comments may be shown as answers.
This question is locked. New answers and comments are not allowed.
Matt Gmail
Top achievements
Rank 1
Matt Gmail asked on 25 Jun 2013, 11:08 PM
Just using the new version today, and console.log() does not log to the console in Graphite simulator for iOS simulators.  This is true when changing my existing project to use Cordova 2.7.0.  It still works in 2.4 I think, but this is no help since ION now requires 2.7.

12 Answers, 1 is accepted

Sort by
0
Nikola
Telerik team
answered on 26 Jun 2013, 07:38 AM
Hello Matt,

In Cordova 2.7 for iOS, the behavior of console.log() has been altered and now it logs only to the native console, and not the web console, accessible via the debug tools in the simulator. To access the native console, please find the "Show Output" button, located in the lower right hand corner in Graphite and switch to the "Device Simulator" tab. Your logs should appear there.

Please let me know if this works for you.

Regards,
Nikola
Telerik

Looking for tips & tricks directly from the Icenium team? Check out our blog!
Missed our first webinar, watch it here.
Share feedback and vote for features on our Feedback Portal.
0
Matt Gmail
Top achievements
Rank 1
answered on 26 Jun 2013, 03:34 PM
That works perfectly.  Thank you for the solution!
0
Relez
Top achievements
Rank 1
answered on 27 Jun 2013, 05:22 PM
Hello there, since I updated my Icenium Graphite to version 1.6, the notification alert doesnt shows up on the device simulator, here is the sample code I am using:

navigator.notification.confirm(
  'Are you sure?',
  function (buttonIndex) {
    if (buttonIndex === 1) //Do something
  },
  'Order',
  'Yes, No'
);

In the cordova doc I dont see any change, Am I doing something wrong?

Thanks!
0
Henrik
Top achievements
Rank 1
answered on 28 Jun 2013, 08:05 AM
We have the same problem here with navigator.notification
0
Deyan Varchev
Telerik team
answered on 28 Jun 2013, 08:08 AM
Hello,

 Thanks for reporting this. You are using the API as it should be used - nothing wrong there. We've made some serious changes to the simulator to make it work much like a real device than before. Along the way the navigator.notification api slipped. However, as this is a regression we'll do our best to fix it as soon as possible.

 Stay in touch for a fix on this.

 Regards,

Deyan Varchev
Telerik

Looking for tips & tricks directly from the Icenium team? Check out our blog!
Missed our first webinar, watch it here.
Share feedback and vote for features on our Feedback Portal.
0
MoriartyX64
Top achievements
Rank 1
answered on 30 Jun 2013, 10:46 AM
In addition to the original message, the "native debugger" logs all messages just fine. However, the great advantage of the web console was that it provided a locals view of objects. These could be folded/unfolded to inspect the contents of the object. 

For example, with  a pseudo object like this:
var myObject = { "value1", "value2" };

... would log something like the following in the Chrome/web debugger:

------------
myObject[]
> [0] value1
> [1] value2
------------

However, in the native console it's just a single, textual line:

------------
[object Object]
------------

This actually makes debugging more difficult than before. Perhaps something to take in consideration for a future update?
0
Henrik
Top achievements
Rank 1
answered on 01 Jul 2013, 06:09 AM
Yes, it is a step backwards I think. Only when simulating Android the debugger works.
0
Jan-Dirk
Top achievements
Rank 1
answered on 01 Jul 2013, 07:43 AM
If this is something initiated by Cordova, then it wouldn't probably take long before it the change appears in the Android simulator too.

I am with MoriartyX64, inspecting objects on their values in the simulator console  is (was) a great feature of the simulator.
0
Nikola
Telerik team
answered on 01 Jul 2013, 01:34 PM
Hi guys,

This is actually a regression that has been fixed in Cordova 2.9. We plan to patch this regression with an upcoming hotfix release that is expected to land later this week, so stay tuned.

Regards,
Nikola
Telerik

Looking for tips & tricks directly from the Icenium team? Check out our blog!
Missed our first webinar, watch it here.
Share feedback and vote for features on our Feedback Portal.
0
Matt Gmail
Top achievements
Rank 1
answered on 03 Jul 2013, 08:47 PM
Appears to be working well in the new version.  Thanks.
0
Randall
Top achievements
Rank 1
answered on 12 Sep 2013, 05:55 PM
Has Cordova 2.9+ been implemented as of yet?
0
Steve
Telerik team
answered on 13 Sep 2013, 11:11 AM
Hello Randall,

As my colleague mentioned and Matt confirmed, this issue has already been addressed and is working as expected in the current version of Icenium. The upcoming version of Icenium 1.8 would directly upgrade to Cordova 3.0.

Regards,
Steve
Telerik

Looking for tips & tricks directly from the Icenium team? Check out our blog!
Share feedback and vote for features on our Feedback Portal.
Tags
Report a bug
Asked by
Matt Gmail
Top achievements
Rank 1
Answers by
Nikola
Telerik team
Matt Gmail
Top achievements
Rank 1
Relez
Top achievements
Rank 1
Henrik
Top achievements
Rank 1
Deyan Varchev
Telerik team
MoriartyX64
Top achievements
Rank 1
Jan-Dirk
Top achievements
Rank 1
Randall
Top achievements
Rank 1
Steve
Telerik team
Share this question
or