Open tranb3r opened 3 years ago
Note that I actually get outer stack traces for Crashes, but not for Errors, using Windows Desktop App. This doesn't include outer exception messages.
The format of the error report is quite different for Crashes and Errors, and I'm wondering about the requirements causing this difference.
This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs within 15 days of this comment.
Could you please fix it instead of closing it ? Thank you.
This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs within 15 days of this comment.
I still wouldn't appreciate automatic closing of this issue.
I notice that with version 4.5.0.
If we have this outer exception
Newtonsoft.Json.JsonSerializationException: Error converting value {null} to type 'System.Guid'. Path 'timesheets[48].uid', line 1, position 1122505.
and this inner exception
System.ArgumentException: Could not cast or convert from {null} to System.Guid.
then app centre would show like this
Newtonsoft.Json.JsonSerializationException: Could not cast or convert from {null} to System.Guid.
Note how the exception type is the outer exception but the message is actually from the inner exception.
I think it should show like how it shown if you perform ToString()
on the exception object rather than attempting to manipulate the exception into some shape or form.
So the above exception output would be
Newtonsoft.Json.JsonSerializationException: Error converting value {null} to type 'System.Guid'. Path 'timesheets[48].uid', line 1, position 1122505. ---> System.ArgumentException: Could not cast or convert from {null} to System.Guid.
.
.
.
This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs within 15 days of this comment.
I think I'm going to try crashlytics...
This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs within 15 days of this comment.
I still wouldn't appreciate automatic closing of this issue.
This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs within 15 days of this comment.
This isn't stale for our purposes.
This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs within 15 days of this comment.
This issue is still present and still relevant.
This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs within 15 days of this comment.
This issue is still present and still relevant.
This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs within 15 days of this comment.
This is still relevant.
This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs within 15 days of this comment.
This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs within 15 days of this comment.
This is still relevant.
This is a huge hole in the Microsoft game for actually using the product for what it's intended.. how much value is there in sending exceptions to app center if you cant see them? I wouldnt want my bonus dependent on it - wait! my bonus IS dependent on me using this efficiently -- so please don't close this as stale when it doesnt have a lot of activity because people have started to just accept that microsoft stuff prolly wont actually do what you need when the time comes unless you do all the research yourself in the reams of info on MS learn (great stuff by the way) This is intended to be an encouragement to treat 'developers with needs' with the same empathy you expect deserve. PS - I hope this reaches a human, I am skeptical.
Describe the solution you'd like In AppCenter issue report, only the top level exception (message and stacktrace) is shown. I think showing InnerExceptions (message and stacktrace) as well is critical for debugging. This information is available in the RAW tab, so why not showing it in the STACKTRACE tab as well?