Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
GitHub or Developer Community with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
Customers are often seeing reports of stack traces like the following:
> at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () <0x00028>
> at System.Runtime.CompilerServices.AsyncMethodBuilderCore.m__0 (object) <0x0003f>
> at Android.App.SyncContext/c__AnonStorey0.<>m__0 () <0x00027>
>at Java.Lang.Thread/RunnableImplementor.Run () <0x0003f>
>at Java.Lang.IRunnableInvoker.n_Run (intptr,intptr) <0x0003b>
> at (wrapper dynamic-method) object.31f43723-97b7-438f-9a43-a2a20d7dd8af (intptr,intptr) <0x0003b>
More context here: https://forums.xamarin.com/discussion/comment/139241/
The above stack trace is reported incorrectly. However, when reproduced, a customer noticed that there is better stack trace information available.
See the forum post for more info on what's expected.
**Build Date & Platform:**
The users on the forum were able to work around this by using reflection to set the private field "stack_trace" to null in the Exception class so that it's rebuilt when the public properties are used for things like Insights.
*** This bug has been marked as a duplicate of bug 33305 ***