AdminMartin Milesich (Admin, Tracepot)

My feedback

  1. 1 vote
    Vote
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      2 comments  ·  General Feedback  ·  Flag idea as inappropriate…  ·  Admin →
      AdminMartin Milesich (Admin, Tracepot) commented  · 

      The new major version is expected late January / early February.

    • 2 votes
      Vote
      Sign in
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        Signed in as (Sign out)
        You have left! (?) (thinking…)
        2 comments  ·  General Feedback  ·  Flag idea as inappropriate…  ·  Admin →

        Hi Andrew,

        We group issues by class name, file name (including the line number) and app version code. We do not use the whole first line of a stack trace anymore because it created lots of issues where only the first line was slightly different but the rest of the stack trace was the same. Usually when an ID of some sort is included that changes every time like a window ID.

        But I understand your problem. You are catching javascript exceptions and re-throwing them as java exceptions. In the current state all happens in the same file with the same class name and therefore is grouped as 1 issue.

        This is not an easy task to solve because I need to take into consideration stack traces from all other apps and there is no clear sign that this is javascript exception so use different grouping. I found some pattern…

        AdminMartin Milesich (Admin, Tracepot) commented  · 

        We are not using the first line of a stack trace because of the problem mentioned at https://github.com/ACRA/acra/issues/130 so we opted only for the class name part of that line. This created another problem where custom exception where grouped together because they use the base exception class.

        So the modification to grouping are to keep grouping with class name as it was before with the exception when the class name is java.lang.Exception then use the whole first line of stack trace. Based on my findings the base exception class is used rarely and almost always when developer throw the exception intentionally.

        I understand that every application is different and could use a different approach and custom configuration would solve that. The problem here is per app configuration will add a lot of complexity to collectors. I am not against it and welcome any improvements to grouping but this will require more feedback and a proper planning.

        I will leave this in Started state so anybody can contribute with their proposals to grouping crashes.

      • 12 votes
        Vote
        Sign in
        Check!
        (thinking…)
        Reset
        or sign in with
        • facebook
        • google
          Password icon
          Signed in as (Sign out)
          You have left! (?) (thinking…)
          started  ·  4 comments  ·  General Feedback  ·  Flag idea as inappropriate…  ·  Admin →
          AdminMartin Milesich (Admin, Tracepot) commented  · 

          @Anonymous Since ACRA 4.6.0 BuildConfig is included in crash reports and Tracepot will mark reports according to "BuildConfig.BUILD_TYPE" so you do not have to use custom data with "TRACEPOT_DEVELOP_MODE".

          AdminMartin Milesich (Admin, Tracepot) shared this idea  · 
        • 2 votes
          Vote
          Sign in
          Check!
          (thinking…)
          Reset
          or sign in with
          • facebook
          • google
            Password icon
            Signed in as (Sign out)
            You have left! (?) (thinking…)
            2 comments  ·  General Feedback  ·  Flag idea as inappropriate…  ·  Admin →

            I like this idea with applying tags to crash reports. I also see it as a quite complex feature. We will try to break it into smaller parts so you can enjoy it as soon as possible.

            AdminMartin Milesich (Admin, Tracepot) commented  · 

            Hi Jorge - What kind of categorisation do you have in mind? Like tags? Adding tags to a reported error and filter according them?

          Feedback and Knowledge Base