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

13 posts, 1 answers
  1. Answer
    Matt Gmail
    Matt Gmail avatar
    13 posts
    Member since:
    Mar 2013

    Posted 25 Jun 2013 Link to this post

    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.
  2. Nikola
    Admin
    Nikola avatar
    22 posts

    Posted 26 Jun 2013 Link to this post

    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.
  3. Matt Gmail
    Matt Gmail avatar
    13 posts
    Member since:
    Mar 2013

    Posted 26 Jun 2013 Link to this post

    That works perfectly.  Thank you for the solution!
  4. Relez
    Relez avatar
    45 posts
    Member since:
    Jan 2013

    Posted 27 Jun 2013 Link to this post

    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!
  5. Henrik
    Henrik avatar
    23 posts
    Member since:
    Jan 2013

    Posted 28 Jun 2013 Link to this post

    We have the same problem here with navigator.notification
  6. Deyan Varchev
    Admin
    Deyan Varchev avatar
    150 posts

    Posted 28 Jun 2013 Link to this post

    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.
  7. MoriartyX64
    MoriartyX64 avatar
    19 posts
    Member since:
    Jun 2013

    Posted 30 Jun 2013 Link to this post

    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?
  8. Henrik
    Henrik avatar
    23 posts
    Member since:
    Jan 2013

    Posted 01 Jul 2013 Link to this post

    Yes, it is a step backwards I think. Only when simulating Android the debugger works.
  9. Jan-Dirk
    Jan-Dirk avatar
    327 posts
    Member since:
    Jun 2012

    Posted 01 Jul 2013 Link to this post

    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.
  10. Nikola
    Admin
    Nikola avatar
    22 posts

    Posted 01 Jul 2013 Link to this post

    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.
  11. Matt Gmail
    Matt Gmail avatar
    13 posts
    Member since:
    Mar 2013

    Posted 03 Jul 2013 Link to this post

    Appears to be working well in the new version.  Thanks.
  12. Randall
    Randall avatar
    1 posts
    Member since:
    Sep 2013

    Posted 12 Sep 2013 Link to this post

    Has Cordova 2.9+ been implemented as of yet?
  13. Steve
    Admin
    Steve avatar
    10941 posts

    Posted 13 Sep 2013 Link to this post

    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.
Back to Top