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 for Bug 33806 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
We are unable to produce filenames and line numbers from crash reports on Android (and iOS), when compiling a Release build.
I'm not sure what would be technically needed on Android. I believe for iOS we'd need a good dsym file (that's been uploaded to a server, say) and run some command line tools (like atos) to arrive at the data we need. Whatever that process is on iOS (I've not yet gotten it to work), I would hope there is a similar (or better) process for Android.
Bottom line: We need a documented way from which we can implement filename and line number information.
We're willing to script stuff out on our end, and invoke system tools on a server side -- assuming we know what the process needs to be.
If it's possible on Android to produce filenames and linenumbers from a Release Build (without full debugging information that would bloat the app by 15 MB and make it slow to start), then we'd be super happy.
Related Bug: https://bugzilla.xamarin.com/show_bug.cgi?id=33804
This should be "fixed" in Cycle 6, though we still need to write documentation on how this works:
The problem is that stack traces, as-is, will NOT contain filename and line numbers, as providing this information increases memory use. Instead, stack traces will be formatted to include IL offset information, and we'll provide tooling to "post process" the stack traces to convert the IL offset into filename+line numbers.
*** This bug has been marked as a duplicate of bug 18137 ***
We're still unable to observe line numbers from crash reports on Android in RELEASE mode. Is there any progress in
"writing documentation on how this works:
The process of "writing documentation on how this works" part resulted in us determining that it wasn't actually working as intended (oops), so parts have gone back to the drawing board as we figure out which way is up.
...which is why that section isn't present in the 6.0 release notes, while most of the other items in 5.1.99 *are* in the 6.0 release notes.
Please also confirm if this will work for iOS -- different platform and considerations, but same exact issue.
Crash reports without line number information are really not that great :( Would love this for both Android & iOS.
Im struggling getting line numbers in DEBUG releases, did any1 manage to get this? If so how?
And what is the status on getting this fixed?
I am using Xamarin.Forms 184.108.40.206 and still having that issue. In Debug Mode I get the line number where an excpetion occured but not in Release mode. When will that issue be fixed?
Ping. Any updates on this?