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

> 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.

> 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.

Like I said in the other bug report, Travis.ConnectIQ already explained that Garmin omits the exception error message on purpose, to prevent devs from smuggling out user data via exceptions. I kind of doubt they're going to reverse course on that. (The problem is that CIQ devs can override getErrorMessage and return any string they want.)

Travis.ConnectIQ also said an internal ticket had been created to provide the exception class name in the ERA. For the case of standard exceptions, the exception class name should be just as good as the exception error message; in fact it should be better, since you can do an exact search for the exception class name in the API docs, which isn't possible for the exception error message (which is similar, but not identical, to the class name).