Acknowledged
CIQQA-3258

feature-request: include an example error message in the ERA reports

Currently we only see the error name in ERA. It would be helpful if we could also see at leas one random error's message. At least for exceptions (i.e when we see Unhandled Exception) there usually is an error message that the Monkey C code can see with e.getErrorMessage(). Please include that in ERA Viewer.

In case it's about multiple exceptions, then include at least one such ("random") message.

See also: https://forums.garmin.com/developer/connect-iq/i/bug-reports/feature-request-instead-of-unhandled-exception-give-actual-exception-s-name-in-era-viewer

Parents
  • > In case it's about multiple exceptions, then include at least one such ("random") message.

    Not sure if I understand why you are asking to see only one message for multiple exception types. If there's multiple unhandled exceptions, won't there be multiple ERA reports? Yes, currently all of those reports will be folded into a single item with multiple occurrences. But if the exception class name was added to the report, I would expect to get a separate report for each distinct exception class.

    e.g. Instead of getting 10 "Unhandled Exception" reports that are folded into a single item (as we currently would), I would expect something like:

    - 2 Unhandled Exception (OperationNotAllowedException)

    - 3 Unhandled Exception (StorageFullException)

    etc.

    It's no different than how the ERA viewer shows different items for different fatal errors (e.g. "Invalid Value", "Unhandled Exception", "Watchdog Tripped Error - Code Executed Too Long", etc.)

    If Garmin added the exception class name to the Unhandled Exception error, I would fully expect the ERA viewer to show a different item for each distinct class name.

Comment
  • > In case it's about multiple exceptions, then include at least one such ("random") message.

    Not sure if I understand why you are asking to see only one message for multiple exception types. If there's multiple unhandled exceptions, won't there be multiple ERA reports? Yes, currently all of those reports will be folded into a single item with multiple occurrences. But if the exception class name was added to the report, I would expect to get a separate report for each distinct exception class.

    e.g. Instead of getting 10 "Unhandled Exception" reports that are folded into a single item (as we currently would), I would expect something like:

    - 2 Unhandled Exception (OperationNotAllowedException)

    - 3 Unhandled Exception (StorageFullException)

    etc.

    It's no different than how the ERA viewer shows different items for different fatal errors (e.g. "Invalid Value", "Unhandled Exception", "Watchdog Tripped Error - Code Executed Too Long", etc.)

    If Garmin added the exception class name to the Unhandled Exception error, I would fully expect the ERA viewer to show a different item for each distinct class name.

Children
No Data